@afelia.bsky.social oder dem einen halt beides

Wir brauchen unverzüglich einen Parteispendendeckel.

Musk soll 276 Millionen Dollar...

Im September brannte eine Station des Internetanbieters Starlink in Polen. Nun gab es Festnahmen in Baden-Württemberg und Berlin. Polen geht von Sabotage durch Russland aus. https://taz.de/!6221272

Because it’s okay if you’re a man, but . . .

#Trump appointee #KimberlyGuilfoyle, the #US ambassador to Greece, has been asked to #resign from her post after coming under severe criticism over allegations she has engaged in improper & possibly illegal conduct before & during her tenure in Athens, new Trump press sec Katie Zacharia said Tuesday.

Not that I have any love for crazy-lips-Guilfoyle.

#law #corruption
https://apnews.com/live/trump-midterm-elections-news-updates-10-13-2026?utm_source=app&utm_medium=iOS_share&utm_campaign=more_message

https://www.europesays.com/de/1346658/ Experten warnen vor Grauzonen: 16-Jährige in Köln von Roboter sexuell belästigt – Teenager unter Verdacht #AktuelleNachrichten #AktuelleNews #ARD #DE #Deutschland #DieEU #Germany #Headlines #Jugend #Köln #Nachrichten #News #Newsdesk #Schlagzeilen

Trump's diesel ceasefire plans aren't working.

RE: https://bsky.app/profile/did:plc:opq5phhuquxppobexcp2cm4y/post/3mxrbwhqhbf2z

Grundrechteschutz abbauen: Grün-schwarze Regierung Baden-Württemberg plant massive Kürzungen beim Landesbeauftragten für Datenschutz und Informationsfreiheit https://www.baden-wuerttemberg.datenschutz.de/einsparungen-lfdi-verstossen-gegen-unionsrecht/

@HistoPol @retrocomputing @Goodlucksil Aurora Store is an alternative frontend to the Play Store and Neo Store is an alternative frontend to F-Droid. Those aren't separate stores themselves. There's no reason to use both F-Droid and Neo Store.

Android Auto works well on GrapheneOS and there hasn't been any recent update improving it. It's necessary to give Android Auto wired or wireless access to use it via the sandboxed Google Play configuration menu:

https://grapheneos.org/usage#android-auto

@HistoPol @retrocomputing @Goodlucksil There's no recommendation to install apps in a secondary user. There's a common misconception by people who wrongly believe it works the same way as a desktop OS about this. Apps running in the main user do not receive any extra access and are not any less sandboxed. Apps do not need to be put into dedicated profiles to be sandboxed. Using multiple profiles is useful but people should generally start with the 2 available nested profiles for convenience.

@Disreputable_Craftsman Apps configuring their Play Store listing to require the Play Integrity API are largely doing so based on not understanding what it does. Those apps still run fine on GrapheneOS and can still be installed on it by using an alternate install method than the sandboxed Play Store.

There's a per-app exploit protection compatibility mode toggle for apps with memory corruption and other bugs making them incompatible with added exploit protections.

@Disreputable_Craftsman The vast majority of Android apps work fine on GrapheneOS. It currently has better compatibility than it ever has in the past. It's getting better.

The only substantial remaining incompatible apps are banking and government apps using the Play Integrity API. GrapheneOS shows a Play Integrity API usage notification to end users when apps use it. Many of the apps using it don't disallow using GrapheneOS based on the result.

@Disreputable_Craftsman Nothing is changing about GrapheneOS support for Pixels. Those will be supported until after end-of-life as has always been made clear from the beginning. Our site documents the minimum support time for each of the supported devices. There hasn't been any post from us implying otherwise.

We've made it entirely clear those will continue to be supported and also that we'll add support for new Pixels meeting our requirements.

@HistoPol @retrocomputing @Goodlucksil @Tutanota The vast majority of Android apps work fine on GrapheneOS. It currently has better compatibility than it ever has in the past. It's getting better.

The only substantial remaining incompatible apps are banking and government apps using the Play Integrity API. GrapheneOS shows a Play Integrity API usage notification to end users when apps use it. Many of the apps using it don't disallow using GrapheneOS based on the result.

@HistoPol @retrocomputing @Goodlucksil @Tutanota Apps configuring their Play Store listing to require the Play Integrity API are largely doing so based on not understanding what it does. Those apps still run fine on GrapheneOS and can still be installed on it by using an alternate install method than the sandboxed Play Store.

There's a per-app exploit protection compatibility mode toggle for apps with memory corruption and other bugs making them incompatible with added exploit protections.

@HistoPol @retrocomputing @Goodlucksil @Tutanota Nothing is changing about GrapheneOS support for Pixels. Those will be supported until after end-of-life as has always been made clear from the beginning. Our site documents the minimum support time for each of the supported devices. There hasn't been any post from us implying otherwise.

We've made it entirely clear those will continue to be supported and also that we'll add support for new Pixels meeting our requirements.

@HistoPol @GrapheneOS @marcellinusme @retrocomputing @Goodlucksil @Tutanota didn't notice what you're describing 🤔. Lately I just noticed a lot of updates from app installed through Aurora Store. Very interested about what will be of our old Pixels... are they going not to be supported at all by Graphene?

@GrapheneOS Keep on keepin' on! Writing from a GrapheneOS'ed Pixel 7 Pro and planning to switch to whatever allows me using GrapheneOS whenever support onnthis device might run out or the device itself breaks. 👍🙏👏

@marcellinusme @retrocomputing @Goodlucksil @Tutanota Android OEMs have months of early access to Android Security Bulletin patches and are allowed to ship those patches early. We're the only platform shipping all of these patches early. We strongly disagree with this system and are advocating against it but we massively benefit from it. We get to ship the Android Security Bulletin patches months before they're publicly available. We're far ahead of the Pixel OS on those patches, not behind it.

@marcellinusme @retrocomputing @Goodlucksil @Tutanota No, it's you who is spreading misinformation to promote highly insecure and non-private products from Murena.

/e/ and Murena devices have years of delays for privacy and security updates along with not having anything close to current standard privacy and security protections.

GrapheneOS has an OEM partnership with Motorola and they have upcoming devices with official support for it which will have greatly improved updates and security.

@retrocomputing @marcellinusme @Goodlucksil @Tutanota /e/ is a poorly maintained fork of LineageOS reducing privacy and security patches/protections far more than LineageOS compared to AOSP. It takes years to ship full patches despite misleading users. It also adds many privacy invasive services.

More information:

https://eylenburg.github.io/android_comparison.htm

https://codeberg.org/divested-mobile/divestos-website/raw/commit/c7447de50bc8fadd20a30d4cbf1dcd8cf14805a0/static/misc/e.txt

https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private

Two examples of Murena pushing anti-privacy propaganda:

https://x.com/GrapheneOS/status/2040887784253141142

https://clubic.com/actualite-604786-murena-e-os-interview.html