The tweet wasn’t easily available on nitter (it wasn’t being highlighted).
It just so happened to be the canonical source for this piece of information. And it wasn’t being run by an antisemite at the time the linked tweet was being written.
Exactly. The good kind of failure.
Hyperloop was always a project to sabotage high-speed rail. Good thing it failed.
I have a dad joke, but it’s yo momma.
Apparently this is what makes someone turn neutral.
Don’t worry, with media independence being an area of concern for the EU, and with the Digital Services Act in the process of being enacted, we’ll no doubt soon Brussels-effect your biggest media providers into compliance. The rest will follow soon thereafter.
Not YouTube: too controversial. But I wouldn’t put it past him to start his own federated service.
I don’t need to smoke anything, I simply live in the EU where this is commonplace.
This is a bad look for Apple: it shows that there’s basically no editorial independence at Apple TV, something that has been a well-established feature at for-profit newspapers and television channels for decades. This clearly demonstrates that Apple TV cannot be trusted when it comes to serious news.
Nah, must’ve been thing
One idea to prevent tags being spammed would be to have them be moderated as well. Thoughts?
As I’m saying, I don’t think you need to: manually subscribing to each trusted instance via ActivityPub should suffice. The pass/fail determination can be done when querying for known images.
How about a federated system for sharing “known safe” image attestations? That way, the trust list is something managed locally by each participating instance.
Edit: thinking about it some more, a federated image classification system would allow some instances to be more strict than others.
Yes: it prevents things like death threats mods have been known to receive on the centralised Lemmy precursor.
I concur. I have one since they’re available. Nothing compares other than my phone display really. Though the refresh rate could be a little higher (and thus the latency a little lower).
Indeed.
Having multiple sufficiently-powered virtual machines makes OS development really low friction. Though I’d personally go for a blade subrack instead.