hey, take me with you

  • 1 Post
  • 5 Comments
Joined 2 years ago
cake
Cake day: June 26th, 2023

help-circle
  • I enjoy using your instance, thank you. The problem at hand is not about the usability (UI/UX, performance, etc.) of Discord but rather it’s private, closed source for-profit existence being used as a “support” channel for a free and open (source, platform, communication) environment. I personally see it as a compromise of morals/ethics if you’re really into the open nature of code and communication, and am sad to now have learned you’ve landed on closed-off Discord instead of an open alternative which might have some rough edges.




  • Even on 0.18.3, something is… off. There seems to be some sort of preference for content which is new and all coming from the same community within a short amount of time; for example, there’s a local community which had the moderator post a flurry of content within a short time frame, all with no upvote ranks to speak of (1 or 2) but it flooded Local/Hot for every single post which I ended up blocking last night (in fact, it was 2 of them sadly - unrelated communities).

    They did nothing wrong (not spammers, etc. - just bootstrapping and adding content to their communities), but Lemmy’s Local/Hot algo prioritized flooding my eyeballs with every single post they made in entire pages of content simply because of whatever is wrong in code, not taking into account votes or ranks somehow. My only choice is to block them to stop the madness, not because I dislike their content per se.



  • One of the features missing from the Lemmy codebase, but is present in kbin, is the ability for a user to soft-block an entire remote instance. This does not have to be because it violates any rules, it’s simply because I as a user find the type of content on that remote instance undesirable to have in my life. Over on kbin.social, I can simply add that remote instance to my personal domain block list and all the content disappears from view, without affecting anyone else but me.

    Playing whack-a-mole with individual communities on remote instances is a losing game, Lemmy codebase needs to mature and add the domain blocking feature at a user level - every user should be allowed to block people, communities and domains to their liking.