Azzu

I think it's a non-issue, because from context everyone will know if the instance or you are meant.

Should've maybe called the instance something different entirely if you didn't want that problem :D

I mean you can just ventilate whenever you spill something.

The larger problem would be the entire water-based ecosystem.

There's constant mentions about "I read your report", so yes, I assume they communicate most routine things by mail.

That's my main argument as well. Doesn't it go against the entire concept of this server to take user's choice away? Instance blocking is super simple, if anyone doesn't want to see it, they can, without it needing to be enforced on everyone.

The only reason for defederation should be admin overhead, i.e. an instance creates so much rule-breaking content that it can't be handled any other way by admins.

Binding the interface is definitely the recommended way to go about it, it was in some manual when I first informed myself about torrenting. But it's not required and easy to miss if you don't consume correct resources, it's not obvious.

Extra protein, have fun.

Aber ernsthaft, warum nicht drauf scheißen und trotzdem kochen?

HTML/CSS/JS is just a possible frontend technology. It doesn't really matter if your frontend is written in that or written in Qt or whatever. What matters in the end is that the developers are good ones. If the developers suck, the frontend will suck.

There aren't many good developers.

Was about to say... "said by an Instagram model who eats 1 grape a day"

Not quite true.. by default it goes to the previous/next tab in the list, but if you accidentally clicked somewhere else entirely in the list then going back/forward from that point does not get you to the tab you previously had selected.

Afaik there is a setting for it, but you have to have it enabled beforehand so it builds the history.

They really should have robbed him for $1 less.

There is no other reason to do it like this in a Lemmy post other than you want to publicly discredit the devs somehow. This is quite obviously a mistake and not a way to harvest admin passwords. Just fixing it and not trying to stir up shit would have been the right thing to do.

OP managed to find the bug. He knows how to fix it. Obviously he'd know how to make an issue about it, and probably even know how to contribute his fix that he already made in the official way to the open source project.

You do not possess these skills so obviously you're not the one who should make the issue.

Yet he decided to somehow create this public post highlighting something that could be sketchy to try to publicly discredit the devs. There is no other reason to do it like this.