this post was submitted on 24 Nov 2025
234 points (98.8% liked)
Linux
10322 readers
821 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, if you ignore everything I said and invent your own stuff, then this is exactly right.
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?
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.
Are you from the US?
Good UX.
Already have provided 1 of many examples: classing. Applying a type to the communication relevant to the business. To the process it could be scope, direction, decision ect. This can route, tag, extract, modify and move/copy messages automatically to target services.
Just to be clear I am not advocating for building Microsoft Lotus notes (Teams), not at all. Quite the opposite.
However jumping between apps is how mistakes are made, and evidence lost from laziness or "too busy". IMO Email communications should only be handled by Outlook or a dedicated email client that has the depth of functionality for good communication. Addins provide the middleware between different products and services to integrate them. It can even be completely transparent to the user.
Bringing this back to the topic. The shift to the web only Outlook means no more BYO libraries, no more .net , no more OS api, no more COM api. These provide an enormous amount of capability for addins to leverage and provide integration. Now with website Outlook, the api is incredibly limitted and entirely controlled by Microsoft, there is no BYO libraries and connectivity and those existing web api's can and are removed at whim removing the ability to conduct business on 365.
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.
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?
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.
A badly designed process or the wrong app.
Again, this all sounds like you guys are using the wrong tools for the job, but would need to hear more details.
Im done. You have utterly no idea what you a talking about. Fundamental information management concepts are foreign to you.
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.
Great story never said that.
Go do a course in basic information management.
No need, we have a tool for that. One that's decidedly not email....
No doubt its a ticket system
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.