Alaknár

Yes. It’s a system where we can create an entry for every case, monitor it, log all activity, manage who’s responsible, who needs to approve, and who owns which parts of the process, automate everything that needs automating, and - in case of an audit - present the entire lifespan of the case, from start to finish to the auditor.

No need, we have a tool for that. One that’s decidedly not email…

And you seem to think that “ticketing system” can only be used for IT incident management. It’s like you’re not aware of integrations with (or flat out specialised tools for) knowledge management systems, HR systems, CRM systems, asset management systems, and a billion others.

You still didn’t give me any example of a process you had in mind so, yeah, I agree, the discussion is pointless.

Already have provided 1 of many examples: classing. Applying a type to the communication relevant to the business

This is not an example. What type of communication? Are you classing emails? Are you classing internal documents? Are you classing marketing material? Are you classing internal comms?

To the process it could be scope, direction, decision ect. This can route, tag, extract, modify and move/copy messages automatically to target services

This description screams “use a proper ticketing system” to me but, again, I feel like I don’t have enough information about the process you’re talking about.

However jumping between apps is

A badly designed process or the wrong app.

So if someone can build an app like Outlook that has rich email, calendaring and pure depth of functionality that it has. This would be a massive barrier removal if not in my oppinion the last barrier for mass business FOSS adoption

Again, this all sounds like you guys are using the wrong tools for the job, but would need to hear more details.

So you’re advocating for slowing process, bad user experience, and duplicating shitty email functionality in every app to receive and send email limiting communications. Got it.

Yeah, if you ignore everything I said and invent your own stuff, then this is exactly right.

Yes they do. Duplicating email into other systems that doesnt have anywhere near the same functionality and flow as their dedicated email app which is designed for email is frustrating, and restricts communication

I’m still trying to wrap my head around the fact that you think that email is somehow the peak of UX.

Could you give me an example of a process that’s much better handled via API to Outlook than literally anything else?

Wtf does classing have to do with ticketing systems. It applies to records management, project management, legal case management, the list goes on. It applies to most business

Wow, these all sound like important things that should definitely not be handled via Outlook. But, again, I might be super wrong - please give me an example, because maybe we’re talking about two different things.

Oh my sweet summer child. I’ve got news for you: email is HOW business is conducted. That is not going away any time soon.

Are you from the US?

Just FYI in case you don’t know - SteamOS has changed and is now based on Arch, which means Bazzite is still fundamentally different.

I personally went with Garuda Linux for two reasons:

1. SteamOS is Arch based (so is Garuda)
2. When researching issues, 80% of the time you’ll end up on the Arch Wiki anyway. Might as well use the actual thing.

Bazzite is probably easier to use for newbies (immutable, relatively stable update windows), but in terms of “I found a guide for SteamOS online on how to get game X working”, Garuda will be much better. Also, Garuda devs included their Rani app, which helps the user take care of the OS, handling a lot of the maintenance.

Client api is responsive, fast

If it’s done right. So, just like an app.

access to local OS and local hardware

I’m already speaking for switching from Outlook with API to apps, you don’t need to sell it to me!

Severely limits access to other services which is very important when moving data.

Read this again.

You’re advocating for moving data via Outlook. Mate, I hate to break it to you, but this is peak insanity!

You have conflated User Experience with User Interface. I didnt say UI for that obvious reason

UI is integral to UX. That’s why I mentioned it.

Also: “familiar UX” makes little sense. People don’t get “familiar” with UX, the UX is either good or bad. That’s why I mentioned both.

Having to open and process the same flow of task from one app to another app breaking concentration is bad fucking UX

Here’s the thing: it shouldn’t be “teh same flow of task from one app to another”. Modern apps tend to encompass the entirety of a process.

Something as simple as classing becomes simple when the context of the conversation is very easy to get and more accurate when you dont duplicate an entire chain.

That’s what ticketing systems are for.

In general: using email for business processes must die just as much as using Excel for a “database”.

It’s not “bollocks”, it’s a fact. Lots of businesses that go cloud replace API calls with external apps. People used to do human resources management via Excel and Outlook with macros and plugins, now they use BambooHR or Workday, for instance.

Of course there will also be lots of businesses that don’t, but I haven’t seen that in the last 13 years of working in the field. And in that time I went through companies as small as 200 users to as large as 180 000 users.

That is being cut off in an anticompetitive move by Microsoft

Agreed. Kinda. Email should be email, nothing else. It’s not secure enough for anything else. If you want fancy features, get a fancy app that can do them, maybe have it send notifications to your mailbox, that’s it.

It allows for information management and automation to be verified by people with simplicity and a familiar UX

With this I don’t agree. Again, email is email - third party (or custom) software can do these things infinitely better. As for “familiar UX” - come on, it’s 2025. If someone can’t handle a new UI/UX, they shouldn’t be doing office work.

You must not be much of an enterprise admin if you don’t know that there are MDM, DLP, and IAM solutions for Linux.

I would really appreciate it if you stopped putting words in my mouth. I didn’t say these tools don’t exist, did I?

Source: I manage all of those for Linux in an enterprise environment.

Out of curiosity: which ones do you use?

Mate, I MANAGE Outlook in my enterprise environment.

Sure, I guess if you have some very specific add-ons as a requirement, it might be difficult. But these things are dying out, 99% of the time Outlook is being used only for email and nothing else. In such scenarios Thunderbird is perfectly fine.

Now, without MDM/DLP/IAM it’s literally illegal to introduce Linux in many environments. Any business handling finances MUST be compliant to regulatory standards, and those require these systems to be in place. Without those three you lose your license and literally just cannot do business anymore.

That’s a very ignorant take.

There are plenty of Outlook replacements for Windows AND Linux.

What Linux doesn’t have is IAM, MDM and DLP comparable to what Entra ID + Intune (or Active Directory + SCCM) gives you.

I wonder what must happen to roll out more Linux in the public sector

Management tools. There’s barely any IAM, DLP or MDM available for Linux, and whatever there is requires tremendous effort to manage compared to… just registering with Entra ID and Intune.

If it doesn’t require a kernel-level anti-cheat system, then yes, you can.

Uuuh… When was that? Got some examples?

Here you go: