![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://derp.foo/pictrs/image/11562610-c411-43fd-a26e-a6e9b5b4f736.png)
So ‘truncate’ and ‘table’ are OK?
So ‘truncate’ and ‘table’ are OK?
Ah good. Now I know what specs not to buy.
Interestingly, there is some evidence that suggests that antioxidants like vitamin C, especially when taken in the excessively large doses that are fashionable these days, can interfere with the immune system (which relies on oxidation reactions in order to clear pathogens and precancerous cells) and preclude gains from exercise (oxidation is used as a signal by the body to eg. induce muscle mass growth).
One thing about the pre-Internet times I don’t hear much about is how much more centralised our media were and how, as a result, people or ideas on the fringe of society didn’t get much attention. That includes for instance how the strange ideas about vaccines or ethnic groups now spread much easier than they did before the Internet, but also how trans* people and other marginalised groups find it much easier to find and support each other and be a united front against oppression.
In summary, I don’t thing that what has been termed “the great awokening”, nor the organised opposition against it, could have taken place before the Internet. At least not at this scale.
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.
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.
Indeed.
Same on the eyebrow raise, but instead like Seven of Nine.
In my opinion this runs counter to the idea of federation
The rest of the internet runs counter to the idea of federation, yet Lemmy must work with it.
You mean like lmmy.to?
I posted a script to do just that a while ago.
Having multiple sufficiently-powered virtual machines makes OS development really low friction. Though I’d personally go for a blade subrack instead.