Gemini version available ♊︎

Distortion of Timelines and Chronic Cover-up at Sirius ‘Open Source’

Posted in Deception, Free/Libre Software at 7:20 pm by Dr. Roy Schestowitz

Sirius staff; Sirius managers
Clients chasing while managers chasing staff that works overnight, entrapping the staff for using faulty processes and faulty software (the management’s own fault)

Summary: Lately we’ve focused on nepotism and special treatment at Sirius ‘Open Source’; today we show how the “club” (or the clique, which is sometimes literally family members) avoids responsibility and liability

THIS series has inevitably become long because there’s plenty left to say and a lot to demonstrate with more practical examples (sans names of people and companies, especially clients).

We’ve already shared several examples of management passing blame to staff that did nothing wrong while failing to hold itself accountable for its own failures. A year ago there was one classic example of this when a message about a potential client resulted in disciplinary warnings; I joked that since we had received no instructions whatsoever I can at best say “hi, it’s Roy” when picking up the phone. To spare all the ‘gory’ details, here’s a message I sent back then:

I’ve just caught up with E-mail.

I remember the scenario very well. This was the first time ever that I received a call over Google Voice while connected (online).

The browser requested authorisation for microphone access and other things before I could pick up the call AND also be heard. This is inevitably what happens when there’s no thorough testing of such new protocols (Rianne did do some testing on her laptop).

It boils down to our instructions (which I have saved locally) coming late and without any training after that. Or even being able to test it “live” in my browser, which understandably limits what site site wants to do with my hardware.

I hope this clarify what happened and helps prevent future such scenario (browser settings have been changed accordingly).


I got the following reply:

Hi Roy,

Many thanks for your reply with responses on the points raised.

I will check on the points you have noted and get back to you to see if there were any steps where there was an issue with the process and any areas that we could have improved on.

I think a key point though is that nothing should prevent us from answering any call with a professional greeting that sounds like a Service desk response. First impressions are vital for customer confidence of course. This is something that with your years of valuable experience should be well-practiced.

Thank you for resolving the browser settings though for future calls and engaging with this change.

And then me again:

Just to note (I’ve not yet read the other 5 messages), for a number of weeks we were on duty “in the blind”. We were given no instructions at all regarding:

- How to answer
- What to say
- Who might phone
- What to ask
- Where to enter information

In a sense, had we answered, it would possibly prove worse than not picking up at all.

A hypothetical call would be something like

“Oh, hello, who are you?”

“What do you want?”

“What are you? What am I? What am I even supposed to do?”

So I think that higher up (than me) someone failed to prepare us. I did not raise this concern at the time.


Long story short, the company expected technical staff to carry out purely clerical work using defective products that many staff members had issues with (but could communicate with peers to affirm that pattern) trying to meet impossible demands like picking a call within 3 rings using defective stuff. Sometimes it would not phone or ring, sometimes it is a background process (not an actual phone!), sometimes there was insufficient memory.

At the end came a long document with a fabricated timeline of what had actually happened. Why? Because you can never assert that people above you blew it. Or that it’s their fault that faulty products are used and no instructions are available.

It’s not even clear if the above client was actually a paying client. The company was habitually announcing clients that later turned out to be ‘pre’ announcements or truly premature as nothing would ever come out of it. Giving false hopes to staff to discourage looking for other employment may seem fair, but it is still misleading. The managers were very eager to give a false impression (illusion) of getting business.

We previously shared some screenshots from the Internet Archive, demonstrating with the Wayback Machine the contents of old sites of Sirius, mentioning words like community and advertising more honestly (staff, clients etc.). Well, honesty is long gone at Sirius.

Sirius is now a minuscule company. At the moment it paints a misleading picture of who works in the company and who the company works for. We’re already in the second half of January and this still hasn’t been rectified. I happen to know that at least one client (telephony company) asked to be removed from the fake “clients” page. There were probably more, but I wasn’t a witness to that. Should Rianne and I keep asking them to remove our names from the site too? They’re not even removing our prior staff that left years ago; one of them changed jobs to work for our client.

Sirius is very fake.

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

DecorWhat Else is New

  1. Links 31/05/2023: Inkscape’s 1.3 Plans and New ARM Cortex-A55-Based Linux Chip

    Links for the day

  2. Gemini Links 31/05/2023: Personality of Software Engineers

    Links for the day

  3. Links 31/05/2023: Armbian 23.05 Release and Illegal UPC

    Links for the day

  4. IRC Proceedings: Tuesday, May 30, 2023

    IRC logs for Tuesday, May 30, 2023

  5. Gemini Protocol About to Turn 4 and It's Still Growing

    In the month of May we had zero downtime (no updates to the system or outages in the network), which means Lupa did not detect any errors such as timeouts and we’re on top of the list (the page was fixed a day or so after we wrote about it); Gemini continues to grow (chart by Botond) as we’re approaching the 4th anniversary of the protocol

  6. Links 31/05/2023: Librem Server v2, curl 8.1.2, and Kali Linux 2023.2 Release

    Links for the day

  7. Gemini Links 31/05/2023: Bayes Filter and Programming Wordle

    Links for the day

  8. [Meme] Makes No Sense for EPO (Now Connected to the EU) and Staff Pensions to be Tied to the UK After Brexit

    It seems like EPO staff is starting to have doubts about the safety of EPO pensions after Benoît Battistelli sent money to reckless gambling (EPOTIF) — a plot that’s 100% supported by António Campinos and his enablers in the Council, not to mention the European Union

  9. Working Conditions at EPO Deteriorate and Staff Inquires About Pension Rights

    Work is becoming a lot worse (not even compliant with the law!) and promises are constantly being broken, so staff is starting to chase management for answers and assurances pertaining to finances

  10. Links 30/05/2023: Orc 0.4.34 and Another Rust Crisis

    Links for the day

  11. Links 30/05/2023: Nitrux 2.8.1 and HypoPG 1.4.0

    Links for the day

  12. Gemini Links 30/05/2023: Bubble Version 3.0

    Links for the day

  13. Links 30/05/2023: LibreOffice 7.6 in Review and More Digital Restrictions (DRM) From HP

    Links for the day

  14. Gemini Links 30/05/2023: Curl Still Missing the Point?

    Links for the day

  15. IRC Proceedings: Monday, May 29, 2023

    IRC logs for Monday, May 29, 2023

  16. MS (Mark Shuttleworth) as a Microsoft Salesperson

    Canonical isn’t working for GNU/Linux or for Ubuntu; it’s working for “business partners” (WSL was all along about promoting Windows)

  17. First Speaker in Event for GNU at 40 Called for Resignation/Removal of GNU's Founder

    It’s good that the FSF prepares an event to celebrate GNU’s 40th anniversary, but readers told us that the speakers list is unsavoury, especially the first one (a key participant in the relentless campaign of defamation against the person who started both GNU and the FSF; the "FSFE" isn't even permitted to use that name)

  18. When Jokes Became 'Rude' (or Disingenuously Misinterpreted by the 'Cancel Mob')

    A new and more detailed explanation of what the wordplay around "pleasure card" actually meant

  19. Site Updates and Plans Ahead

    A quick look at or a roundup of what we've been up to, what we plan to publish in the future, what topics we shall focus on very soon, and progress moving to Alpine Linux

  20. Links 29/05/2023: Snap and PipeWire Plans as Vendor Lock-in

    Links for the day

  21. Gemini Links 29/05/2023: GNU/Linux Pains and More

    Links for the day

  22. Links 29/05/2023: Election in Fedora, Unifont 15.0.04

    Links for the day

  23. Gemini Links 29/05/2023: Rosy Crow 1.1.1 and Smolver 1.2.1 Released

    Links for the day

  24. IRC Proceedings: Sunday, May 28, 2023

    IRC logs for Sunday, May 28, 2023

  25. Daniel Stenberg Knows Almost Nothing About Gemini and He's Likely Just Protecting His Turf (HTTP/S)

    The man behind Curl, Daniel Stenberg, criticises Gemini; but it's not clear if he even bothered trying it (except very briefly) or just read some inaccurate, one-sided blurbs about it

  26. Links 29/05/2023: Videos Catchup and Gemini FUD

    Links for the day

  27. Links 28/05/2023: Linux 6.4 RC4 and MX Linux 23 Beta

    Links for the day

  28. Gemini Links 28/05/2023: Itanium Day, GNUnet DHT, and More

    Links for the day

  29. Links 28/05/2023: eGates System Collapses, More High TCO Stories (Microsoft Windows)

    Links for the day

  30. IRC Proceedings: Saturday, May 27, 2023

    IRC logs for Saturday, May 27, 2023

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts