Formerly /u/Zagorath on the alien site.

  • 6 Posts
  • 527 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle








  • In addition to what Blaze said, there’s a much more public desire to leave Instagram because of how publicly awful Facebook and Zuckerberg are. Spez is not really any better, but outside of our bubble people don’t really see that as much—party because he has so much less money to push his ideas outside of Reddit.

    And it’s just fortuitous that unlike Twitter, Instagram doesn’t have any real competition that isn’t using Activity Pub.




  • In Sync, when you see your comment, does it create a link you can click to go to murd0x’s profile? If so, nice! Sync is doing the right thing in this context. I know already that Jerboa, the app from the main Lemmy devs, does this correctly.

    But lemmy-ui, the interface you’ll see on most instances if you open it up in your web browser, that is not clickable, but the /u/username is clickable. It’s an obvious bug/shortcoming in lemmy-ui.


  • Hey, I just discovered this and discovered that you seem to be the developer of it.

    It seems to be broken in at least two ways, and doing some very unexpected (at least insomuch as it attempts to replicate RES behaviour, and also IMO how I would expect it to behave) things with alternative keyboard layouts.

    Broken: upvoting posts. If I have a post selected and press “a”, it takes me to the post in the poster’s instance, the same as clicking the little fediverse logo. If I press “z”, it upvotes. Voting works fine on comments with a = upvote, z = downvote.

    “Disable arrow key scrolling” also seems to disable the use of arrow keys inside of a text box.

    Keyboard layouts: in short, you seem to be using event.code, which detects which physical hardware key is depressed, instead of event.key, which detects the character that was typed. It means that if I want to move forward and backward, I have to press the key I would normally expect to type h/t.

    To be clear: this is not wrong necessarily. It’s actually sort of my preferred way for video games to do things, so I can type the keys in the space that WASD are and move around, for example. But as my personal preference, and my experience of how most browser extensions do things (including RES), this is not how I’d prefer it to be done.

    I use Dvorak, which by coincidence keeps a and m in the same places as QWERTY (as well as the number keys), but moves everything else around to be more efficient and ergonomic. It also has the benefit of putting j and k where QWERTY has c and v, allowing for convenient one-handed use of the “next” and “previous” comment buttons along with upvoting, while keeping the right hand on the mouse for scrolling. And I could easily reach to the numpad enter key with my mouse hand to collapse a section (side note: using event.code means only the main enter key works. Using event.key, both enter keys are Enter). QWERTY requires two hands on the keyboard.

    Screenshot showing the Dvorak home row, the enter key, and the numpad enter key, results after executing a keydown event listener for console.log()



  • I had not. I had no idea that even existed, thanks!

    Do they have a Lemmy community for feedback? It’s super buggy right now unfortunately, with “a” taking me to the post on the poster’s instance, instead of upvoting (or at least taking me to the post on my instance…), and with all keyboard shortcuts handling alternative keyboard layouts in what I would consider to be the wrong way (though this is possibly debatable/up to preference).


  • Zagorath@aussie.zonetoAnnouncements@lemmy.mlLemmy AMA March 2025
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 month ago

    Yeah a lot of former Reddit apps that switched to Lemmy did a really lazy job of it and haven’t implemented all of the Lemmy text parsing syntax properly. Spoilers are one of the most common issues, but so are subscript (including ~multiple word subscript~) and superscript (and ^multiple words of it^).

    If your app doesn’t parse text correctly 2 years later, it may be time to consider switching.


  • New users should be able to join a “default instance” that is federated with all instances so people can window shop for the instance they prefer.

    Almost by definition, any default instance is likely to get defederated by some other instances, if that default grows too large. Being default means it’s more likely to attract more people of all sorts. And some of those won’t get along with the federation policies of some stricter instances.


  • Personally when I want to share something to multiple communities, I deliberately space out the posts in time. It has the slight downside of potentially showing up for a person repeatedly for days, but I think this is outweighed by the upside of them not seeing the same post multiple times within a few minutes, which is really annoying. And it has the added advantage of being more likely to be seen by people who weren’t online at the right time to see it the first time.