The admin of sh.itjust.works has been approached but as of yet has failed to reply to concerned Lemmy users. I’m glad Beehaw admins look out for us by cutting off instances that host communities like this.
The admin of sh.itjust.works has been approached but as of yet has failed to reply to concerned Lemmy users. I’m glad Beehaw admins look out for us by cutting off instances that host communities like this.
I think it’s reasonable to have an account on another federated server, especially if they’re a smaller (sub 100 users) instance that requires applications. In my experience after switching to a smaller server, I was able to see a similar amount of activity on my feed by subscribing to a wide range of communities I’m even mildly interested in.
I like browsing by New and on Beehaw, it’s a bit rough because I would see a lot of NSFW communities and have to constantly manually block them, and as it’s a more active instance, I would run into the “person subscribes to new community and feed fills with those posts” bug very often. On the smaller instance, there’s a lot of overlap between my subs and other users’ subs in terms of content so New is still a pleasant browsing experience.
I’m watching the drama from lemmy.today and it’s very nice to not get involved in the politics of all this. It’s still super small and maybe it will always be, but that’s not a problem since we are using federated tech and can take part of every community that exists anywhere. :)
Using a small instance offers the luxary of being neutral in all this.
I don’t know that bug. Can you describe it a bit more? Not sure if you typoed there.
It’s something to do with the web sockets implementation in 0.17 - when any person on your instance subscribes to a community, the community’s posts get added to the top of the web ui feed (possibly only if you’re on page 1?). so if I’m on page 1 of new and someone subscribes to a self-hosted community, I’ll be flooded with all the recent posts from that community as I’m scrolling through the feed.
should be fixed in 0.18 since web sockets are removed there, and it’s also less of a deal on small instances as I said.