Bitwarden checks all the boxes. I've had great experience with it. https://bitwarden.com/

I will say, auto-fill on load is a bad idea. On desktop I keep my auto-fill bound to a key so it doesn't actually end up in fields it shouldn't be.

2FA is locked behind the $10/year premium if that's something you wanted, but beyond that the free plan has everything 99% of people will use. They do third party security audits, have public white papers, and is completely open source.

It's the heavy machinery required to do it that's the problem. This is also not Elon Musk's building, but a building Twitter rents. The building management company were the ones who called the police.

a lot of hate for capitalism here

The fediverse is largely populated by 2SLGBTQIA+ people and people of colour who are oppressed by capitalist regimes. The other big contingent is marxists and people who like FOSS. FOSS, at its core, is anti-capitalist.

You're in a place founded by anti-capitalism, that exists in spite of capitalism, asking "why is there so much anti-capitalism here?"

Your post history is public.

Did you experience this often?

Edit: Y U P

FOSS Discord Alternative. Takes all the design language of Discord too without the nitro garbage. It's still not fully featured, but it's a cool little alternative if you can find a community you like. I personally am rooting for Matrix/Element tho.

https://revolt.chat/

"usersurname". I like that.

Don't fill in this field, that turns your instance into a whitelist server. Remove everything from the allowed instances list

Because the redneck themed one wants to call queer people groomers and have them sentenced to death by firing squad.

They want to make 1.5 million single family homes "to attack the housing crisis".

The most expensive type of home.

We should leave instances who federate with threads.

you do it from an already existing post.

In the latter case, I think it might be feasible to prevent upvotes from being counted multiple times if the username is identical on different instances, since upvotes are public. Is there already a mechanism to do this?

If @[email protected] upvotes and @[email protected] downvotes, how do we decide which is the canonical vote? How can we say for sure they're even run by the same user?

Also, isn’t it much more common in the Fediverse than on central platforms for the same user to have multiple accounts with different usernames?

This was the norm on Reddit too.

I suppose this would only be possible if the different instances would log IP addresses and share this information with other instances. That doesn’t seem desirable to me at all, and probably wouldn’t be legal, at least in Europe, because of the GDPR. Are there other possibilities? Cookies?

Let's not inundate the fediverse with tracking cookies and privacy invasion.

I get where you're coming from, but I just think that the solutions to these problems aren't actually solutions, and they're a case where the cure is worse than the ailment.

Bravely Default, Xenogears, Final Fantasy 5, Final Fantasy 9, Final Fantasy 10, Final Fantasy 11, Final Fantasy 12, Zelda ALTTP, Zelda MM, Harvest Moon A Wonderful Life, Xenoblade 1, Xenoblade 3...

I set a rule with myself. I'll play games while I'm having fun and then stop when there's something else. I don't really care to beat games, I'll play them to enjoy them! 😊

idk I quite like the changes he's making. Rate limiting, preventing people who don't sign up from using it, killing embeds. It's all great for reducing the net presence of what has become an almost entirely white nationalist platform. If anything he's not rolling out these changes fast enough, for if he was, Twitter would have also restricted itself from having new sign ups (like Voat in its later years) and eventually completely shutting down.

Since they're so expensive, Ford's developer donors make more money off single-family homes than anything affordable.

There's also many small-to-medium sized instances that just haven't bothered signing that will be defederating. Mastodon.social's gonna be one of the few who do, and I already think it's fine to defederate from them too tbh.

I think this is going outside the realm of self-hosting and moreso into actually creating a server architecture. All servers would need to use the same database, so you'd want likely as its own server a database server, caches on the front-end servers so popular things aren't queried for the same info again and again.

I've never set up anything like this, so this is just me trying to think of how I'd throw it together, I'm sure there's a bunch of async problems I've not even considered how to tackle, and even having the DB be offsite from either of the front-end servers would be less than ideal.

I suppose you could have the DB in one of the servers, but then that one now has the same frontend-load as the other while it also is the only one doing DB queries, so the load's not really being distributed properly. 🫠

Meta's fine with transphobia. I am not. It can hardly be called a decision at that point, I don't need Libs of Titkok and their ilk filling my federated feed.