This is a garbage article that's presenting rushed low-quality software fixes as evidence of "the woke mind virus".

Evidence is links to their own publication, a Twitter screenshot, and "everyone I talked to said ...". The author is clearly talking about a small, trusted group that back the author's pre-existing views.

Trying to not have blantenly racist AI, another Tay, is a really difficult problem. Google's "throw it at the wall and see what sticks" approach to products, the features-first promotion process, and employees' honest desires to do the right are combined into a complex, awesome, and also flawed product.

It's simpler and more entertaining to believe that there's some conspiracy than to acknowledge the complexity, and the author uses that to further their victim complex.

K

My serious answer, not an argument: Use d-feet to inspect what's available on the system and session buses. That'll show the benefit of introspection and a common serialization mechanism.

About the security comments: Some access control mechanisms aren't just allow/deny, and many need more than socket permissions. Those benefit from DBus policies, and PolicyKit integration helps for more complex needs. You can always DIY it, that's Linux/FOSS life, but these are great tools to have in your toolbox. I'll avoid credential passing via sockets whenever I can and have something else do it.