@fwam @fosserytech
a) I don't let anyone police my toots. #DealWithIt!
b) IDK what kind of files you use but I've never had issues with #OpenDocument and the only.issues I ever had were caused by #MicrosoftOffice and/or #OOXML.

@fwam @fosserytech nah.

#LibreOffice works fine.
I jist refuse to accept #OOXML bloat and expect either #PDF-Forms or #OpenDocument.

Canonical and IBM Are Turning Ubuntu and Fedora into Microsoft Windows
http://techrights.org/2023/07/09/corporate-distros/
#novell #novell_suse #suse_linux #open_suse #mono #ooxml #moonlight #microsoft #gnu #linux #foss #analysis

Sorry to whomever posted this that missed the boost, but it took a while to read, take off my glasses, rub my eyes, put em back on, reread it, shake my head back and forth, spend a bit letting it swirl around my noggin and now I cant find the original toot.

Every Signature is Broken: On the Insecurity of #Microsoft #Office #OOXML Signatures

#InSecurity

https://www.usenix.org/conference/usenixsecurity23/presentation/rohlmann

@hllizi @mspro doch, gibt es...

Z.B. auch als #Sabotage [#OOXML] gegen offene Standards [#OpenDocument]...
https://en.wikipedia.org/wiki/Embrace%2C_extend%2C_and_extinguish

@atomicpoet @Joseph @nus yeah, but only because they failed to force it upon everyone else.

Had they supported the #InternetExploder [cuz it literally is a cyberjihadist towards open standards!] on #macOS and released it for other #Unix-alike OSes like #Linux, they'd have the same chokehold on the #web as they have with their shitty #Office365 / #MicrosoftOffice #Bloatware and it's horribly bad #OOXML files!

God, I hate #Windows based from my own experience!

This brings back memories of the big #ODF v #OOXML format wars: „Every Signature is Broken: On the Insecurity of Microsoft Office’s OOXML Signatures“ https://www.usenix.org/conference/usenixsecurity23/presentation/rohlmann

@mvsde you mean "be thankful it's not a shitty #OOXML #DOCX" because German Govt IT sucks ass!

@mar I REFUSE TO USE SHITTY #OOXML AND FORCE SENDERS TO USE #PDF OR IF IT'S AN ACTUAL FORM, A PDF FORM...

@erk @encthenet Well, whilst #ISO, #DIN, #ANSI & Co. only take existing standards and reward them with their blessing, I think they should mandate those to be truly open.

For example I'd cnsider the acceptance of #OOXML to be the biggest Mistake of ISO since not only did they already accepted #OpenDocument as superior option, but at >6.000 (!!!) pages "specification" it's practically impossible to implement OOXML by anyone but #Microsoft.

@dc8wan der #OOXML-Schrott gehört IMHO verboten und stattdessen flächendeckend #SigG & #SigVO gepushed und eMail mit wahlweise S/MIME und/oder PGPG/MIME - Ende-zu-Ende - Verschlüsselung bei Behörden, Organisationen und Unternehmen vorgeschrieben!

@danilo who the f**k uses proprietary #SingleVendor / #SingleProvider formats like that?

Next thing you gonna try to tell me people prefer #OOXML over #OpenDocument and nut because they're shitty #TechIlliterates...

@berkough @fuchsiii same as with Xorg or any massively functional software.

Would I love it if everyone obly used #Markdown, #YADL & #TSV's for work?
Hell yeah.

But I also understand that WYSIWYG-Editors are important, so I'm not gonna advocate for banning LibreOffice, as unlike Microsoft they don't champion bloated trash like #OOXML & use toxic LockIn to chain users on their GDPR & BDSG noncompliant Govware...

@edv_nachrichten man könnte ja auch konsequent #OOXML & #Windows verweigern - ist billiger und effizienter.

@libreoffice personally, I refuse to use #OOXML as well as any #proprietary and/or #SingleVendor / #SinglePeovider solution.

@atomicpoet @rberger Both should've never existed in the first place.

#Silverlight - like #Flash - deservedly died as all #proprietary #rentseeking technology should!

I sincerely hope proprietary shit like #MAPI & #OOXML will soon die out with #Win32 / #Win64 / #WinRT APIs.

Because the only sustainable tech is FLOSS...

@sindastra
I'd try #LibreOffice that can import #OOXML #docx (and old binary #doc) and export to #PDF. Even on #Mac :mastocheeky:

@Andres @survey Well, @libreoffice works fine if you don't have to deal with bs like #OOXML which noone should use since #OpenDocument works fine on #MicrosoftOffice.

Not to mention @collabora's @CollaboraOffice is included with several hosters and if you feel fancy you can even #SelfHost it on your own metal, VMs or some (virtual) box from a provider of your choice.

Or checkout #OpenXChange.

@mcepl @ProfessorCode @survey noone should use #OOXML.

It's purposefully designed to be unimplementable by anyone but #Microsoft (similar to #Exchange's #MAPI protocol) and inherently worse than #OpenDocument due to being > 6.000 pages of legacy bloatware down to Office 4.2 bugs.

@msw And that's how we get bloated shit like #OOXML that NOONE SHOULD EVER USE - PERIOD!
https://en.wikipedia.org/wiki/Office_Open_XML

Espechally when #OpenDocument is the superior format that is without #bloat and with a specification that anyone but Microsoft can even implement!
https://en.wikipedia.org/wiki/OpenDocument