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.
I alternate
I have a dad joke, but it’s yo momma.
Apparently this is what makes someone turn neutral.
Hey, at least the number of fingers on the visible hand check out.
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.
Not very. If it boots it boots. Although the ACPI implementation may be a little less buggy (plus you can fix it yourself if needed), so if you’re having power management issues it may help.
The pregnancy test merely provided the case. Looked cool though.
Well, irdc stands for “I really don’t care”, and I guess “derp” and “foo” speak for themselves…in the long run it doesn’t really matter.
willemijn@derp:~/lemmy/volumes$ sudo du -hs postgres/
3.0G postgres/
This is the PostgreSQL database on a freshly-rebuilt server (that is, one with a small WAL) which has been running for nearly 3 weeks now.
Compressed pg_dump
rsync’ed to off-site server.
“Password cannot contain username”
“Password must contain digits”
“Password cannot contain reversed misspellings of predynastic Egyptian pharaohs”
And now…
“Password cannot contain JavaScript”