Time to ditch vanilla FireFox for LibreWolf (https://librewolf.net/).
Read the whole blog post. Didn't see any explanation why suddenly $5,800/month are needed. How's that number justified? It's not clear.
Accrescent depends completely on donations to run. Today we share a significant update in our new blog post on the future of Accrescent: https://blog.accrescent.app/posts/the-future-of-accrescent/.
New releases of Accrescent and our developer console are also out, with Android 16 updates and Material 3 changes. Check them out!
https://github.com/accrescent/accrescent/releases/tag/0.26.0
https://github.com/accrescent/parcelo/releases/tag/0.12.0
https://github.com/accrescent/console/releases/tag/0.12.0
#security #privacy #accrescent #android #appstre
Read the whole blog post. Didn't see any explanation why suddenly $5,800/month are needed. How's that number justified? It's not clear.
Wait, so any app on Android with network access can just open a localhost port and then a browser script can share all your private browsing data via that port? Even on GrapheneOS? How is that not restricted?? What's stopping your banking apps or "sandboxed" Google Play store from doing this and tracking everything?
https://www.theregister.com/2025/06/03/meta_pauses_android_tracking_tech/
#privacy #grapheneos #infosec
FUD. old news. already fixed in GOS
Nice!! Additionally, I lnow some NGOs prefer one bigger yearly payment to several smaller ones due to administrative costs then taking up much less off the donation! Maybe worthwile to switch to donating to one org per month 60€? :-)
FUD
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqmnwqngttz2xxpt8znsk565sl4q9mvtdere5mtp4l3622gel3e40segalsa Agreed! I stuck to the stock one for years, but decided to give this one a try.
I don't allow the launcher to lock the screen, I just use the power button. I personally don't feel comfortable giving an app that level of access. It's likely that the app isn't built to accommodate the 2-factor fingerprint, so it defaults to the passphrase.
Thank you Josh! I actually found a relevant issue just after posting: https://github.com/jrpie/launcher/issues/65
That's fine! :)
Locking via double tap just seemed super cool and handy!
#Android #FOSS launcher:
I just have to recommend #μLauncher to EVERYONE! My whole smartphone experience is a million times better when using it!
https://launcher.jrpie.de/#idea
When using this launcher, there are basically no more icons on the homescreen. Widgets are allowed. Apps are now launched through gestures or through a search that automatically launches an app when it becomes the sole search result.
For me personally this is a gamechanger since I actually just open the app that I want to check in that moment. Often I think "let me check xy" then I take my phone, get distracted, open z instead of xy to see "what's up" lol. This way there is no distraction.
I would also say that it slightly enhances #privacy against shoulder-surfing, not giving away info about installed apps when the homescreen is open.
Thanks to nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq8l99sgsv6cy3099hdem9yuawq89cjqtnx4v46j449jrwp8y0tekqz84caj for the recommendation through his newsletter!
I never used another launcher on GrapheneOS because I never felt it added anything above the default one. But this one... is AMAZING!!
I wonder though; if I allow the launcher to lock the screen (meaning I make it an admin app) I cannot unlock the phone with GrapheneOS's 2FA unlock (which is fingerprint followed by PIN) but have to enter my long primary passphrase each time (due to some "work policy" I never set according to the lock screen's info banner). Any hint on how to change that?
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqmnwqngttz2xxpt8znsk565sl4q9mvtdere5mtp4l3622gel3e40segalsa You can enable auto-locking and also configure the Private Space to go back to rest when it''s locked. Auto-locking isn't supported for Private Space in secondary users yet since there's no Android implementation and we need to implement it post-Android-16.
Thanks for your explanation! I indeed forgot to originally mention that I was talking about the issue when being in a secondary profile. Cheers! :-)
GrapheneOS version 2025052800 released:
https://grapheneos.org/releases#2025052800
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/22776-grapheneos-version-2025052800-released
#GrapheneOS #privacy #security
On that version, if the browser in private space plays a video and you lock your phone (which locks the space) you can still play the video's sound from the lock screen. Since you have to "verify it's you" to access the browser in private space again I feel like you should not be able to play the video's audio from the lock screen if the audio originates from a browser in a private space.
I noticed that some settings from the parent profile are ignored inside the private space, e.g. keyboard presses make a sound in the private space when they are set not to in the parent profile.
Today we're launching Mullvad VPN loader - a new application for installing the Mullvad VPN desktop app on Windows and macOS which is both fast and secure.
Read more here: https://mullvad.net/blog/launching-mullvad-vpn-loader
You write: "Mullvad VPN loader downloads and starts the latest Mullvad VPN app installer" and then the loader "automatically verifies the integrity and authenticity of the downloaded app [i.e., the installer]".
Doesn't this simply regress the problem of verifying the integrity and authenticity of the installer to that of the loader? What's the advantage for the user of using the loader compared to directly downloading the installer in terms of verification if the user has to verify one application anyway?
Google makes Android development private, will continue open source releases
Discussion: https://news.ycombinator.com/item?id=43485950
#android #google
Will this negatively affect GrapheneOS in any way nostr:nprofile1qqstnr0dfn4w5grepk7t8sc5qp5jqzwnf3lejf7zs6p44xdhfqd9cgspzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcnv0md0?
What's from Obsidian is not open source?
FUD at its best. Du hast zufällig vergessen zu erwähnen, dass Carlsons Handy sehr wahrscheinlich schlicht kompromittiert war; wenn das OS nicht mehr vertrauenwürdig ist, ist völlig egal, welche App man nutzt. Lass mal dein lächerliches Signal bashing und Threema Fangirl Gehabe.
FUD at its best. Dass Signal US clouds nutzt, ist nicht ideal. Aber:
1. Signal erhebt gar nicht erst beweisbar so gut wie keine Metadaten.
2. Welche Server nutzt Threema? Welche Metadaten schickt der Client? Woher weißt du das?
Dein Fangirl Gehabe ist so lächerlich.
Mal wieder ein völlig aus dem Sachzusammenhang gerissenes Zitat, um raunend irgendeinen Unsinn zu implizieren. FUD at its best.
Regarding the latter aspect: nothing really beats Pixel devices running GrapheneOS when it comes to security (and also privacy, even if that's not the project's primary focus). Building on GrapheneOS then FLOSS apps (and ideally no social media :)
Klassiche FUD Strategie; ein paywalled Artikel (broken link sowieso) und ein Screenshot, der von meinem kleinem Neffen in Photoshop gemacht sein könnte, werden genutzt, um in bester fanboy-Manier den eigenen einzig wahren Messenger anzupreisen und eine andere sichere und private FOSS Alternative in den Dreck zu ziehen.
-> FUD, fear mongering, wertloser Content.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqmnwqngttz2xxpt8znsk565sl4q9mvtdere5mtp4l3622gel3e40segalsa There's a new release of Android every month. It has monthly, quarterly and yearly releases. Android 15 QPR1 was released in December, then the first monthly update of QPR1 in January, the 2nd in February and now QPR2 in March, etc. 15 is an older release of the OS and there were releases beyond it before QPR1 too.
I understand! Thanks a lot for your explanation! :)
"Android 15 is an older release of Android" because the most current QPR is treated as the most current Android?
Thank you for this little accessible explanation! I still have problems grasping which Android update (where I mean "update" in a very general sense) means whar exactly. There are so many, the ASP, AOSP releases, Pixel specific ones... a comprehensive table would be so helpful!
Also don't have a Google account. I literally visit a random jitsi instance in a clean browser w/out any history cache and can start a jitsi meeting.