

I blame management for the existence of option d


I blame management for the existence of option d


I agree with the sentiment, but to be fair, the two latest major Linux vulnerabilities have been present in the kernel since around 2017, which predates vibe coding by a couple of years.


Check back in a couple of hours to see that the account will have been deleted. It seems to be a pattern of accounts being created, posting a bunch of news-like links, and then being purged. It is probably to make it impossible to filter out whatever it is they’re trying to push.
“Beax ya mea+ ya SocI DePle+c” – A Modern Day Poet
Hah, like that’s gonna stop me! Bring on the coming decades, my body is ready!


I wouldn’t spend any more energy on them. They made it clear that they’re here to talk at people rather than talking with people.


Just a small pointer: If the goal was to convince the person you replied to, the third condescending paragraph is a surefire way to make them not listen, which is a shame because the first two paragraphs are actually solid arguments.


I curse the day I acquired reading comprehension!


That lists entirely blocked instances (defederated instances), yes, but the original post talks about blocking specific communities of an instance, which I didn’t think was possible.


Didn’t even know an instance could block a specific community of another instance. I thought the only option was defederation. Is there any way to see/list the communities blocked by an instance?
I mean, sure, but that’s mostly because I’ve gotten absolutely no feedback