01.29.23
Gemini version available ♊︎Not Tolerating Proprietary ‘Bossware’ in the Workplace (or at Home in Case of Work-From-Home)
Video download link | md5sum 9a90a5de7aacd9fc4b8847cf61321f6a
When Sirius Abandoned Jabber for Bossware
Creative Commons Attribution-No Derivative Works 4.0
Summary: The company known as Sirius ‘Open Source’ generally rejected… Open Source. Today’s focus was the migration to Slack.
THE above video discusses the migration/transition/downgrade from Jabber to a truly terrible, centralised, proprietary and vulnerable platform known as Slack. Aside from technical problems and various glaring limitations, Slack was a risk not just to Sirius ‘Open Source’ but also to its clients.
No matter the hard evidence and how much I pointed this out (maybe a dozen times, at personal risk), that always fell on deaf ears. The company was already governed by incompetent people.
“From what we can gather, Red Hat staff was subjected to similar treatment after IBM had bought the company.”It was abundantly clear that many colleagues did not like this. Some opposed this. Some faced disciplinary action for antagonising. That would include me. So in a company called “Open Source” we’re meant to assume that adopting proprietary software — and not because some client requires it — is considered acceptable. Whereas insisting on the company’s values is considered an offense.
From what we can gather, Red Hat staff was subjected to similar treatment after IBM had bought the company. It’s hard to believe that later this year it will be 5 years since that announcement. █