Tesla is also a Linux base.

Google constantly does this unethical bundling of features with privacy switches. I remember when I used to use Android that turning off Location History meant you couldn’t save your home and work address on Google Maps.

You’re conflating privacy with anonymity. Signal is not anonymous, but it is private.

This reply from July shows they’re still working on it, it’s just challenging: https://nitter.net/photomatt/status/1676415784548184065

Is Tumblr still working on this? It’s a little depressing to think Facebook of all companies might beat you to it.

Yeah 😕 They are orders of magnitude bigger and better capitalized than us. Not an excuse, just reality.

For real. Wanna try Mastodon? Make an account on mastodon.social. Wanna try Lemmy? Make an account on Lemmy.world. Once people buy into the platforms they can migrate to smaller/niche instances if they’d like. Simply things at first, active users will then slowly figure out the rest.

Unless I’m missing something, this isn’t a messaging standard like RCS or XMPP. This is just a way to do E2EE messaging. Just like Signal and Whatsapp both use the Signal protocol for E2EE messaging but are completely siloed networks, MLS would be much the same.

People look at the big picture in polls(X candidate is leading in polls) and then say they’re wrong when Y candidate wins, but it’s way more nuanced than that.

The 2016 polls were not that far off. Hillary won the popular vote, as the polls predicted. The key states she lost, she lost by small margins within, or not too far from, the margin of error.

If you look at FiveThirtyEight’s final prediction for 2016, Trump had a 28.6% chance of winning. That’s between a 1 in 3 and 1 in 4 chance! But the media narrative was that Trump had 0 chance, and what happened happened.

This is the exact suggestion I saw posted around here when news of the speech was shared. You love to see it

That’s not how ActivityPub works. You can’t embed trackers or scripts into posts. You can’t even do the basic trackers that emails have(loading a 1px image) since your instance pulls the image from the originating server and caches it.

It makes sense to pause registrations if an instance is actively overloaded, but there’s no reason it can’t keep growing if more hardware is added and the performance issues are resolved.

Why even bother with beehaw? Just join any instance that federates with them.