It’s the gold rush of lemmy/kbin apps!
The lemmy devs will be removing websockets (what keeps updating the main page automatically,) in the 0.18 (next) release. That should fix the issue.
That should hopefully resolve a lot of UI issues.
I love the fact we can look up open bugs and their status, and even pull the code down and make changes if we so choose. Open source is awesome!
For the most part I personally have not witnessed any bad behavior or trolls. Lemmy has been a breath of fresh air, and people seem genuinely happy to be here. I hope it stays that way.
BUT…
Have a look at the mod log on any instance. It’s a public log of moderator actions and gets federated along with everything else.
Definitely some people getting banned for the usual reasons. People will be people. 🤷🏻♂️
https://hakbox.social/modlog (may contain NSFW material).
And my axe!
What about second breakfast?
Boil’em mash’em stick’em in a stew
They’re taking the hobbits to Isengard!
Help I can’t stop!
Let's just hope we can keep it that way! 🙂
Hey I’m a redditor and I’ve gone as far as setup my own instance rather than register on the “big ones”.
If you want to block an entire instance, I think the only way is to run your own instance and add it to the blocked list, or join / signup on an instance that already blocks it, then browse lemmy from there.
Alternatively, if you want to block just certain subs from an instance, if you have not "joined" the sub, you should see a "block" button in the sidebar.
It would be great if the instance kept a pulse on how federation to other instances is going and showed a health check in the app sidebar and near instance names to temper user expectations.
That sounds like a great idea!
Ooh, that’s a good one. I use that a lot too.
Hey there! I believe this is just server load related. If you leave the page alone, it will eventually change to ✅ Joined. That has been my experience at least.
Just a wild guess, because I haven't looked at the code / implementation yet in GitHub, but It's very possible they use a message queue to store subscription requests for processing. That is what my the observed behavior would lead me to believe. If that's not the case, the delayed sub would be complete server delay while the request is processing...
Yes, there is: 0.18.2-rc.1, which has the hot fix, but will also require a DB query to "fix" the modlog once upgraded.