I, on the other hand, go to HN to complain apparently. :-)
I, on the other hand, go to HN to complain apparently. :-)
There tends to be some drama around different attitudes to moderation on other servers but other than that they're usually fairly well-behaved and predictable by comparison. Twitter on the other hand seems to have opened some kind of hell portal giving 4chan a run for its money.
Twitter/Reddit/HN are too toxic for me to visit every morning, so I started allowing myself to visit these sites 1-2 per week before 5 pm. Evenings are fine as I’m already done with my work.
People are actually kind when you see each other’s faces. It’s bizarre how big the difference is.
It worrying how long it takes to realise it's happened. But after reading the several tweets from conspiracy nuts and right wing fruit cakes you notice.
Dunking was always a part of twitter culture, but it's got far more vicious, unrestrained, and stupid lately.
A client or service will inevitably be compromised. And with it, the private keys of some, or assumed all, using it, whether stored by the service or logged on entry by a compromised system.
Private keys should be chained, master->subkey, with subkey the public key of the service __or a solution like that or that ends in the same result. When (not if) a service or key is compromised, the key can be blacklisted and/or any key co-signed by a compromised service blacklisted.
I'm confused by the oversight. It's also been raised here https://github.com/nostr-protocol/nostr/issues/97
Until then, I'll have to keep my updates of what I had for breakfast to myself.