@hcf that's just wrong and you know that.

• If this was the case they'd not facilitate any #eMail whatsoever!
  • They do it to facilitate a #toxic #LockIn to their #Apps and #WebMail at the cost of #interoperability, #Accessibility and #Privacy !

For example, if "#Security" was a real issue, they'd host their #IMAP+#SMTP access exclusively over @torproject / #Tor because #OnionServices are using fully-encrypted connections in a self-authenticating adress spaces.

• They don't because that isn't the issue, and I'm not talking about the Server-to-Server - Connectivity, which is INHERENTLY AND UNFIXABLE INSECURE WITH EVERY EMAIL PROVIDER unless they don't allow actual cross-provider eMails (or restrict it to very few, selected competitiors with spechally negotiated connectivity [i.e. #VPN|s], which to my knowledge NONE of the commercial providers do)…

I brought up @monocles because they at least don't lie to customers and are honest about security & privacy!

• If your "#security" relies on someone else risking jailtime, then you should IMHO get additional time for being "criminally incompetent" and "putting others at risk'…

@case2tv @dans_root @earthnewstech

#sarcasm #commentary #ITsec #InfoSec #OpSec #ComSec

@benno Not transitioning assumes that the continued Pain and Suffering is less great short, middle and longterm than any migration.

• Which is in many cases just #EscalatingCommitment with very few nieche exceptions...

I consider any #LockIn, espechally *toxic Lock-In as described a big problem that needs to be dealt with at some point.

• Cuz it's either #mismanagment or a systemic issue that needs to be fixed!

If one cannot even consider a slow, step-wise migration then obviously the pain and suffering of said #CCSS is not high enough as push factor because #FLOSS has all the pull factors it'll even have...

• Sounds harsh, but that's my observation and experience as #IT #Sysadmin who migrated several clients/employers away from multiple CCSS to FLOSS options...