octet33

joined 4 years ago
[–] octet33@lemmy.ml 19 points 1 year ago (1 children)

Fossil fuels.

Things have slowly drifted from "we might wanna consider doing something before this becomes a problem" to "we need an immediate and concrete plan" to "anything short of immediate and drastic action is killing and will continue to kill people" over the course of the last decade or two.

[–] octet33@lemmy.ml 14 points 1 year ago (6 children)

So either FB isn't actually E2E, or their implementation is Twitter-grade broken.

[–] octet33@lemmy.ml 4 points 1 year ago (3 children)

The thing is, Lemmy is decentralized. You don't need to have an account on an instance (server) to use that instance's "subreddits" (communities) - instances communicate their activity to each other automatically, so any instance will do (provided the instances haven't banned each other). It's just like email.

So it's pretty simple to just stop accepting sign-ups once an instance starts to become impractically large. Anyone can start an instance for just the cost of a domain ($10ish/year, or free if it's a subdomain of an existing website) and a server (that random computer you already have lying around will do just fine, for free). And a small instance can do fine on just donations and the good will of the operator.

[–] octet33@lemmy.ml 1 points 1 year ago

Fine.

To be fair, I used Mastodon long before Elon acquired twitter, so I'm pretty comfortable with federated social media. The fragmentation inherent to federation might make small communities difficult to form, but it also protects against the eternal specter of power-tripping mods, so I can't complain.

I just hope it doesn't have the same memory utilization as the Mastodon web client. Seriously. I flat-out can't leave a single Mastodon tab open in the background, because it'll eat all my RAM. No other social media I've used does this.