"Our new developer identity requirements are designed to protect users and developers from bad actors, not to limit choice."

https://support.google.com/android-developer-console/answer/16561738

"Giving up our values in the name of security is to lose the battle in advance."

Christopher Pike, Star Trek Discover, s02e09

#SofwareFreedom #OpenStandards #VendorNeutralOS #OrganisationalIntegrity

@gaghyogi49

Understanding Android developer verification - Android Developer Console Help

To better protect users from repeat offenders, we are adding another layer of security called developer verification. This will help make app installation safer by preventing the spread of malware and

In essence it goes back to #OpenStandards and #Interoperability.

@david_chisnall

Why open standards are extremely beneficial to end users - TDF Community Blog

Whenever I talk to other technology users — including CTOs, CSOs and ICT managers, who in theory should have a certain level of expertise — I realise that most of them never consider standards when using applications, devices or websites. Users just want everything to work, but they don’t realise the fundamental role that standards, especially open standards, play in making this happen. Open standards actually offer users a significant advantage over the proprietary solutions they use every day. An open standard is a publicly available set of rules that govern how technology works. Anyone can use, develop or improve them. Examples include HTML for websites, USB for devices and PDF for documents. (And of course, the Open Document Format – ODF – as used by LibreOffice.) These are not owned by any company, and therefore benefit end users. That’s why they’re important to you. 1. You are not tied in Open standards reduce vendor lock-in. This means that users are not forced to use a single product or ecosystem from a single company to have control over their data and tools. For example, documents saved in an open format can be managed with multiple applications. If you change your

TDF Community Blog
The philosophy behind ODF: openness, freedom and control - TDF Community Blog

File formats are not usually the subject of philosophical debate because most users just want to open, save and share documents without any problems. However, the Open Document Format (ODF) is based on concepts that are much more important to users than might initially seem the case. ODF is not just a technical standard, but also a statement of openness, user freedom, and control over digital information. Understanding this philosophy helps to explain why ODF exists, why it is still important, and why it is often cited as a reference in conversations about digital rights and long-term access. In short, ODF is an open standard for office documents such as text files, spreadsheets and presentations, and it is the native format of LibreOffice. Unlike Microsoft Office and Microsoft 365 files, which use a proprietary format developed in secret in Redmond and controlled by Microsoft, ODF is developed and maintained through a completely transparent process. This may seem like a technical detail, but it is an important fact that determines everything else. Openness: no one owns your documents The principle behind ODF is openness. The complete specifications are available to the public, and anyone can read, implement or create software based

TDF Community Blog
Is anyone working on this? Should we start?
Thoughts from the Fediverse?
#OpenStandards #Interoperability #BusinessTools

@jpmens #TLDR: relying on it is a horrible idea, when GSO-based SATCOM with high elevation is way less prone to it.

#WhatsMissing are #LowCost & #OpenSourceHardware #SatelliteModems & cheap #BUCs for #OpenStandards like #DVBRCS

Östereich #DIDit ! Habt ihr wirklich #DUTgemacht, finden wir!

Hier wird gut gezeigt, dass der Abschied von Abhängigkeiten von Microsoft & Co gut möglich ist. Mit Open Source, @nextcloud statt M365 und dem Umzug ganzer Ministerien. So schnell wird aus einer EU-Deklaration zur Digitalen Souveränität eine unbedingt fortzusetzende Praxis. 🚀💪

https://www.golem.de/news/abschied-von-microsoft-und-vmware-oesterreichs-roadmap-zur-digitalen-souveraenitaet-2601-204331.html

@Golemde

#OpenSource #DigitaleSouveränität #EU #FOSS #PublicMoneyPublicCode #OpenStandards #Digitalpolitik #GovTech #Europa

Abschied von Microsoft und VMware: Österreichs Roadmap zur digitalen Souveränität - Golem.de

Österreich ist nicht gerade für Softwareinnovationen bekannt. Nun führt es aber eine Initiative für mehr digitale Souveränität in der EU an.

Golem.de

🔒 Encrypted RCS spotted in iOS 26.3 beta. 📱
Mentions of end‑to‑end encryption via carrier settings suggest Apple may enable secure RCS messaging soon—finally bridging iOS & Android text security. 🔐

Still, carriers must adopt the GSMA’s Universal Profile 3.x before users see cross‑platform E2EE in action. 🌐

🔗 https://www.privacyguides.org/news/2026/01/13/encrypted-rcs-spotted-in-ios-26-3-beta/

#TechNews #Privacy #Encryption #Apple #RCS #Google #iOS #Android #Messaging #Security #OpenStandards #UserRights #DataProtection #Interoperability #E2EE

Encrypted RCS Spotted in iOS 26.3 Beta

Mention of the long-awaited RCS end-to-end encryption (E2EE) support in the iOS 26.3 beta was spotted by Tiion-X83 on X via a carrier bundle setting that would let carriers enable E2EE for RCS messaging.

Privacy Guides

@Setanta that's brilliant! I think you are spot on. Especially in the case of FHIR, the context, and much of the meaning is lost.

As we discuss this more, it's becoming apparent that the EMR vendors' business model provide incentive to keep our data in silos. The switching cost of changing EMRs today is enormous. With a robust open standard for data, we would be one step closer to being able to easily move data and plug in a different EMR for a far lower cost. #opensource #openstandards