Nice to see the #EU #DigitalMarketsAct start to influence #BigTech's approach to their restrictive policies: looks like #Google is reconsidering allowing #ChromeOS users to install APKs outside of #GooglePlay. That gives users the freedom to use other app sources like #FDroid, easily debug apps, and more.
* https://issuetracker.google.com/issues/206353953#comment69
* https://bugs.chromium.org/p/chromium/issues/detail?id=1401666#c31
Let's keep the pressure on them so they follow through!
Nice to see the #EU #DigitalMarketsAct start to influence #BigTech's approach to their restrictive policies: looks like #Google is reconsidering allowing #ChromeOS users to install APKs outside of #GooglePlay. That gives users the freedom to use other app sources like #FDroid, easily debug apps, and more.
* https://issuetracker.google.com/issues/206353953#comment69
* https://bugs.chromium.org/p/chromium/issues/detail?id=1401666#c31
Let's keep the pressure on them so they follow through!
The main #Jitsi public instance https://meet.jit.si is now requiring logging in with a Google, Facebook or GitHub account in order to create new rooms. https://jitsi.org/blog/authentication-on-meet-jit-si/
Apparently they feel that there was too much abuse of their terms of service, but they do not give any details at all.
Are you at #CCCamp23? Come join us this Friday 14:00 local time at ChaosZone for a casual F-Droid community meetup!
https://events.ccc.de/camp/2023/hub/camp23/en/event/f-droid-community-meetup/
@fdroidorg meetup at #chaoszone @ #cccamp23 right now!
@kgbvax TRUST. Yes, that's the key.
With CLOSED source you need to trust the dev, ans solely the dev (unless there were audits).
With FOSS, everyone (technically capable of) can review/audit the source. At F-Droid, that is done: many eyes on the code, many mechanisms cross-checking it. True, not every line and every minute, but it's done.
Knowing the dev behind it then is only needed to put blame – and THAT is not what F-Droid stand for
Unlike Google, F-Droid does not force developers to publicize their name or address information.
We understand that people have many reasons to develop under another name than their legal one and to keep their personal information private. And that what matters is the trust between user and developer, not private details of their lives.
For more information on how we designed F-Droid to protect your privacy, see https://f-droid.org/2022/02/28/no-user-accounts-by-design.html.
#Mozilla has published its position on the "Web Environment Integrity API" proposal put forward by the #Google #Chrome team.
First paragraph: "Mozilla opposes this proposal because it contradicts our principles and vision for the Web."
https://github.com/mozilla/standards-positions/issues/852#issuecomment-1648820747
'Ada & Zangemann - A tale of software, skateboards, and raspberry ice cream' book reading
☑️ FrOSCon 2023
🗓️ 6 August
⏰ 10 h
📍HS7
💻 https://programm.froscon.org/2023/events/2986.html
"#Google's newest proposed web standard is... #DRM?" -- Google is proposing yet another user-hostile feature and aims to make it an web standard called "Web Environment Integrity API". This lets websites confirm the browser has limitations on what it can do, going against #UserFreedom. The #IETF internet standard RFC 8890 declares "The Internet Is For End Users". Google's API circumvents that.
Thanks to Ron Amadeo for his a concise, cutting analysis:
https://arstechnica.com/gadgets/2023/07/googles-web-integrity-api-sounds-like-drm-for-the-web/
Looks like the latest release of #FDroid, v1.17.0, does not get flagged by #Google, at least in the #Android 14 emulator. I heard some reports that v1.16.4 also isn't flagged. I don't really know why its flagging F-Droid then. v1.16.4 has an unchanged #targetSdkVersion, but v1.17.0 has it bumped to 28. I have found no way to get info on why they are flagging the app, just this silly "unsafe" warning screen. Is F-Droid being flagged by Google Play Protect on your devices? Please let me know.
What to do about the lack of #DataSkills?
In the iTalks series organised by our iLab, 🔟 experts on #DataLiteracy discussed it with almost 7⃣0⃣0⃣ participants from public sector, academia, and civil society! 👩💻
Missed it? Check the slides & recordings 👉 https://europa.eu/!x98WfB
On the other hand, #MLS includes "Group Integrity", which means that all members in a group see the same state. This means all members see the same list of members, same message transcript, same message order, etc. #Signal Protocol does not guarantee Group Integrity. I think this is an important property, but I wonder how much this was actually abused in the real world with other protocols? 3/
One big concern I have about #MLS over something like #Signal Protocol is that it makes it so the cost of sending a message to a group of 10 is about the same as sending to a group of 1000 or more. This is the opposite of how physical social interaction works, it is much more effort to speak in front of large groups. This gives advantage to spam, disinfo, trolling, etc. as compared to protocols where the cost linearly increases as the number of users in the group increases. 2/
#MLS Messaging Layer Security has just been officially standardized by the #IETF, this is a great new development, especially in combination with standard protocols like #Matrix and #XMPP. https://blog.phnx.im/rfc-9420-mls/ 1/
A decade ago, #AmnestyInternational did some extensive UX work on #panic buttons using the power button. They used 10 presses as their trigger, and still got far too many false positives. Their conclusion was power button triggers were not workable. #GuardianProject reached a similar conclusion back then. I guess #Google missed that research: they shipped #Android with a 5-press trigger, and now emergency services numbers are receiving record numbers of false calls:
https://arstechnica.com/gadgets/2023/06/uk-police-blame-android-for-record-number-of-false-emergency-calls/
Gathering technical details of unpatched vulns is dangerous, no matter who is doing it. The #EU Cyber Resilience Act should avoid making this a requirement, it will not make us safer.
More info in the blog post:
https://guardianproject.info/2023/06/11/eu-should-not-require-sharing-unpatched-vulnerabilities/
1/5 🚨The final EU Parliament position on #AIAct is here 🚨
Some wins for #FundamentalRights but also missed opportunities to protect and empower people.
Read our statement: https://edri.org/our-work/eu-parliament-plenary-ban-of-public-facial-recognition-human-rights-gaps-ai-act/
1/4🔎#Google's harmful tracking ads business is now officially under investigation in Europe.
🚨In preliminarily findings, @EU_Commission confirms: since at least 2014, Google has abused its dominance in the #AdTech market - harming people, online journalism and competitors.
https://ec.europa.eu/commission/presscorner/detail/en/ip_23_3207
4/4 The @EU_Commission findings against Google make clear once again that the harm done by the #surveillance ads business cannot effectively be remedied unless we put an end to it 🙅♀️
https://edri.org/our-work/surveillance-based-advertising-an-industry-broken-by-design-and-by-default/
People, apps and code you can trust