Exactly what is meant by “asteroid” is left up to the viewers’ interpretation and imagination. I took it to be about climate change.

Don’t expect too much rigour or depth from a short-form video.

Individuals, yeah. Instance admins are going to need to designate reposters if they refuse to self-designate (and Lemmy doesn’t have functionality for them to do that, except as a bot) and then it’s up to individuals to decide whether they filter out reposters or not.

It’s manually-applied and reversible. I can’t reliably code an automatic reposter detection system because they’re all different. It’s going to have to be a human judgement.

Similar to labelling things as AI-generated or NSFW - being a reposter isn’t necessarily bad. It just means that people who don’t mind whether they see it can do so and those who don’t want to can avoid it, without the conflict that ensues when people with different needs and tastes are forced to share space.

Not yet, this functionality isn’t running on a live server.

Yes the screenshot is just the user settings. Admins are going to have to manually designate accounts as reposters because I haven’t even tried to make an automated detection. That would be very hard to get right.

Working on it!

The NoGoogleAi firefox extension solves this.

Except you don’t live anywhere because you’re a bot.

Technically, it shares a lot of characteristics with databases. You can put data in there and get data out again later, sure. But it’s optimized for short term caching of data, to reduce load on a real database, reduce network requests, that kind of thing.

In programming you can often use tools in ways they were not intended for and it’ll still work but the costs of that decision might not become apparent until much later. This is one of those. Over time you’ll start to have issues with durability guarantees, complex querying and indexing, transactions and consistency, recovery after failure, backups and restoration, data growth, operational tooling, migrations and schema evolution, concurrency, debugging and observability. None of that shows up during initial development work so you won’t notice until you’re in way too deep.

Redis is not a database. If you use it like one, it won’t be long before you regret it.

The omarchy website lists them.