Good question sometimes I find posts that have been posted 3 years ago in Hot… It seems really broken

Aye

Wtf just do your calls in the stairway awkwardly smiling at passing coworkers like the rest of us

Sure they can, they can ban the user from the entire instance or from the community. To all users of sh.itjust.works for example the content will still appear, but it won’t show on beehaw anymore.

Here’s the PR that implemented this: https://github.com/LemmyNet/lemmy/issues/1298

It seems to me like they don’t want to give up any control by adding mods (currently it’s only the admins) and choose the easy way out by reducing the amount they have to moderate…

Especially the UI seems hastily coded

Ladies and gentlemen, let me just say, this courtroom, tremendous courtroom, it’s really fantastic, okay? Nobody’s ever seen a courtroom like this before, believe me. And I must say, I’ve been to a lot of courtrooms, folks. Many courtrooms, lots of them.

Now, I know what you’re all thinking: “Why is the greatest businessman in the world standing in front of you today?” Well, let me tell you, it’s all a big misunderstanding. Huge, tremendous misunderstanding. They say I’m being accused of being too charismatic, too charming, and too good-looking. Can you believe that? It’s a real witch hunt, folks. Sad!

It opens the item (post, comment) in the instance that it was created on. For example I’m on https://sh.itjust.works so if I click on that button of your post it opens this post on https://lemmy.world, which is your instance.

Thanks! I will check it out.

I added a mark as read button to the posts but now patiently waiting till the WebSockets -> REST API transition is complete so it can get merged.

The front end needs a lot of work… Every bit is appreciated and the maintainers are pretty fast at reviewing and providing feedback which is nice to see.

Same this is such a hopeless timeline…

Just a “normal” http API as far as I know. There won’t be any live notifications/data on release but this can be added using polling at a later stage. It was mainly done because websockets just don’t scale well at all with thousands of users.

Don’t feel the need to “fit in with the crowd”. Individuality is more fun anyways.

Lemmys WebSockets are being phased out currently and thus all bugs regarding them (wrong vote counters, posts being pushed in at the top in the wrong categories, etc.) are gonna go away as soon as the transition is complete.

There’s the setting „Show read posts“ which can be disabled to hide already read and/or up-/downvoted posts.

Would love to hear some more details on the misconfiguration if you want to share @TheDude@sh.itjust.works

Already resolved itself, the Nodes counter had the same dip so probably just servers not responding.

This is great! Thanks for your work.

What an awesome time to be alive if you just look at the scientific progress and ignore the slow societal collapse.

GitHub would probably be the best place for feature requests.

That said the feature you’re talking about is already (sorta) available. You can head over to your settings and disable “Show read posts” which will hide posts you either A) opened or B) up- downvoted.

I recently contributed a mark post as read button to the lemmy-ui which will hopefully be merged & released soon-ish.