Bonum Certa Men Certa

Sirius Open Source: Buy Your Own Desk, Bring/Buy Your Own Device (BYOD), Repair and Maintain Your Computer at Your Own Expense and Time

Desk for Sirius? Who owns what?

Sirius Open Source desk



Summary: The previous part in the Sirius ‘Open Source’ series showed the financial issues at Sirius; to make matters worse, the company does not provide any means for work to its NOC staff (except an ancient Cisco phone, about 20 years old and bought second hand through eBay)

THE articles that we published about the EPO showed that as horrible and autocratic António Campinos has been, at least the Office chipped in and covered expenses for home working, such as ergonomic chairs. At Sirius, however, the company pays for nothing of that sort. Not for desk, chair, computer, and so on. Workers are on their own; technical problems with a work device? That's your problem. That's your device. The company won't cover it. Then they impose bloatware on staff -- software that ordinary machines cannot run (yes, staff did complain; it was a common problem) or can barely run. Does the company help procure suitable hardware? No. Was it asked about it? Yes.



Here is an internal report circulated in the company earlier this month (a day prior to departure):


Remote Workers' Procurement and Other Costs



Equipping staff with suitable assets is a basic, very basic, requirement. Roy has covered the legal aspects of that for many years in his Web sites. In Sirius, the company failed to equip home workers ("work-from-home" staff) with any computers or chairs or anything required to do the work. The managers expect staff to pay for purchasing and maintenance of all work equipment at their own expense in their own time. There's no IT department to help with computer issues or even issue a replacement.

To make matters worse, bloated software which requires very powerful and expensive computers was introduced some years ago. Roy and colleagues also complained about this bloat, but that fell on deaf ears (Roy internally suggested the company can purchase suitable equipment or cover the costs of that). That's aside from the very low (by market standards) salary, adding further burden. More on financial aspects shall be discussed later.

In recent months workers began observing that Sirius had customers with no way to access their systems. So how are workers supposed to deal with tickets they receive? There was expectation of dealing with queries by using "Google" to throw some answer at a client (as if the client cannot access Google), otherwise find an associate or escalate. It was starting to get hard to even tell apart clients and non-clients, as documentation was scarce and outdated to the point where clients were vaguely described and their status was unclear. Sentences like "Google is your friend" were said inside the company (Google is surveillance, it's not a friend) and our skillset ought not rely on using search engines, following a textual script (like clerical staff in a call centre), or mere escalation to some other company. As noted before, many associates are at best loosely connected to the company and are in effect third parties.

About a year ago Roy faced disciplinary action over something unjust (to him). Instead of an independent, impartial tribunal acting as arbitrator it was likely the culprits judging the incident, then resorting to cover-up/distortion over the sequence of events to pass to the blame to 'low-level' staff. This started to become a typical modus operandi, which dated back several years, as a later section will explain in detail.

These issues turned out to be more widespread as staff managed to communicate with one another. For instance, lots of people were having phone issues. The company did not admit this; individual people reported it, then there was blaming of the people unable to use a defective "service" that keeps changing and breaking things that previously worked. Instead of admitting this migration was a mistake and acknowledging prior warning were given, there was only further entrenchment. More details will be given in the last section.

Recent Techrights' Posts

Linux Kernel Becoming a Slopfest - Part 6 - Seeing Who Contaminates Linux With Slop (And Also Admits It)
Today we begin looking at some culprits
2026: The Year Galleries Realised the Need to Flag or Cull Slop Images
Society needs to shun slopfarms, people who use LLM slop (for anything at all), companies that use bots (which they dub "agents"), and so-called 'coders' who volley garbage into project and software hubs
Software Freedom Day Celebrated in 5 or 6 Continent
Software Freedom Day (SFD) 2026 was big this year
Enjoy the Giving/Sharing, Not Taking
We've long supported what we believed in, even with the little money we had
 
Links 21/09/2026: "Back On My Bicycle" and American Regime's War on Media Escalates Further
Links for the day
SLAPP Censorship - Part 192 Out of 200: The Hired Guns of Garrett and Graveley Sent Us USB Sticks (One to Me, One to My Wife) Showing Lozza Talking to Garrett About Censoring/Deplatforming Techrights the Same Time Graveley Was Copy-Pasting Garrett's Lawsuit
Next year we plan to bring this matter to the Court of Appeal
SLAPP Censorship - Part 191 Out of 200: Garrett, Graveley and Lozza
They talk to and coordinate with one another
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, September 20, 2026
IRC logs for Sunday, September 20, 2026
Gemini Links 21/09/2026: Digital Hoarder, GTD, Minimalism vs Digital Minimalism, Rejection of LLMs
Links for the day
Links 20/09/2026: "Google Now Asking For Users’ Video Selfies" and Energy Prices Set to Rise
Links for the day
Links 20/09/2026: Amazon Layoffs, Flock 'Buyouts' (Silent Layoffs)
Links for the day
USCIS and Microsoft Rumours: Curbs on Lowering Salaries by Importing Cheaper Replacements?
It seems like Microsoft's mass layoffs and efforts to cheapen the workforce face obstacles
Gemini Links 20/09/2026: "Music While Working" and Radio Silence
Links for the day
Clownflare Data From Canada
We've like to think many people are attempting to install GNU/Linux over the weekend
SLAPP Censorship - Part 190 Out of 200: Plagiarism, Back Doors, and Sabotage of Linux
This can go on for a decade or longer
Linux Kernel Becoming a Slopfest - Part 5 - Kernel Dependency on Plagiarism Giant Microsoft is a Death Blow to Any Kernel
Microsoft is bringing copyright-infringing slop into Linux
GNU/Linux Has Grown a Lot Lately
Based on Clownflare
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, September 19, 2026
IRC logs for Saturday, September 19, 2026
Links 19/09/2026: Many Patents Become Candidates for Annulment and Linux [sic] Foundation Takes More Slop Money to Promote Malicious Bots
Links for the day
Gemini Links 19/09/2026: The Fundamental Human Assets, The History of Gopher's "i" Type, and ROOPHLOCH 2026
Links for the day
Links 19/09/2026: "OpenAI and Microsoft Knew They Were Starting a ‘Doom Loop’ [of Mass Plagiarism 'Normalised' by Brute Force] for the web", Calling It "Hey Hi"
Links for the day
8 Series Going on at the Moment in Techrights
4 series about SLAPPs and related matters
Linux Kernel Becoming a Slopfest - Part 4 - Outsourcing to Microsoft, Approaching 10 Gigabytes
Can we blame Microsoft for those DDoS attacks? Partly.
SLAPP Censorship - Part 189 Out of 200: A Terrible Idea to Condemn Projects for Using Slop 'Code' When Your Own Employer Does This (and Profits From Every Company Doing So) or to Call Distros 'Not Secure' While You Advance Back Doors
"I don’t want a back door. I want a front door."
Software Freedom Day 2026 is Today, Week-long Celebration in Brazil
In Brazil, Clownflare reckons about 1 in 20 laptops/desktops might use GNU/Linux already
Red Hat Lost 2,000 Staff (Net Loss)
Maybe by year's end it'll be a 20% reduction
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, September 18, 2026
IRC logs for Friday, September 18, 2026