Ram

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?”

Nuke Studio

Bitwarden only autofills if the page’s URL is the same as the account in your vault. So it actually helps you make sure that you aren’t putting your info into a phishing site or something

This is true, though wasn’t my concern. My concern is that it (and other PW managers ofc) can sometimes fill in fields its not supposed to, and you end up accidentally including a username or password in a GET header.

although, I’m pretty sure autofill is disabled by default anyway?

Auto-fill on page-load is, yes.

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

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.

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.

AT Protocol can do this in the way of DNS DIDs, but ActivityPub doesn’t have this functionality.

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

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. 🫠

“usersurname”. I like that.

Oh you can just hit the “All” button on the communities page!

Because the size of it, the sheer centralization around it, it creeps me out.

I’ve already blocked mastodon.social.

I’d recommend anyone using this to really consider how much data this’ll use on their system.