GrapheneOS version 2023080700 released:
https://grapheneos.org/releases#2023080700
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/6792-grapheneos-version-2023080700-released
Bah joined the ascii skeleton emoji hellthread via nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 now I can't scroll my replies ๐
This donation method mostly has no fees on our end. The only exception is a 4.14 USD fee for SWIFT wire transfers within the US as opposed to ACH payments which are free to receive. ACH is usually free/cheap on sender side so use ACH rather than sending a domestic wire transfer.
It's now possible to donate to the non-profit GrapheneOS Foundation via bank transfers in the EU/SEPA, UK, US, Australia, New Zealand, Canada, Hungary, Singapore and Turkey. International wire transfers from elsewhere are not currently a supported option.
We've added support for Litecoin donations to the non-profit GrapheneOS Foundation via a Bech32 (Segwit) address:
Trying out Nostr.Wine as my first paid relay. The speed difference is night and day in conjunction with #Amethyst.
Be good to hear from others on their paid relay preferences and why?
#GrowNostr
New Article on PrivSec.dev
https://privsec.dev/posts/knowledge/setting-up-mta-sts-with-a-custom-domain-on-proton-mail/
Vanadium doesn't have any internal options being based on Chromium.
To make use of SOCKS5 you need to use a VPN with the option in their app or use an app which uses the VPN API to run a SOCKS5 proxy.
I had one knocking about a family member left me with other electrical bits and pieces. Saw the video and dug it out.
Wished I'd done it and owned one sooner. Never been much of a Sony gamer.
I entirely blame Modern Vintage Gamer for this. ๐ฎ๐น๏ธ
#PSP #PSP1000 #Sony #Sega #StreetsOfRage2 #PSPunk
Keep me in the loop ๐๐
Not that weird. It does happen and is a common symptomatic precursor to hardware failure.
If it happens and you can't turn the device on (Pixel 5th Gen and < ) and you plug your phone into a PC and see Qualcomm HS-USB QD-Loader 9008 or similar then the device is dead.
If you use a 6th Gen > Tensor device this won't happen.
If you see these with more regularity and can grab a bug report (SETTINGS>SYSTEM>DEVELOPER OPTIONS>BUG REPORT>INTERACTIVE) and then make yourself known in our Matrix support room, we can look into it further.
Thankyou it would be appreciated and gratefully recieved.
Thanks for tagging me Chris, I am indeed a community moderator for the project. You can find me across our Matrix, Twitter/X, Discuss Forum and doing community outreach here on Nostr.
Happy to assist how I can Garrett, that is, if our warm, welcoming, and incredibly helpful broader user base doesn't beat me to the punch. ๐๐
Hi there, please let me know your issues and feedback, happy to listen.
Also Android Open Source Project is a Linux distribution, as is GrapheneOS. A substantial portion of our work is on the Linux kernel. We've made significant upstream contributions to the Linux kernel project with the bugs we've found, patches we've provided and code review.
An operating system doesn't need to use systemd, glibc, gcc/binutils, pipewire/pulseaudio, Wayland/X11, GNOME/KDE, etc. to be Linux. Linux is a kernel.
Thanks for listing GrapheneOS there but to emphasise the differences between it and the others...
GrapheneOS and CalyxOS/LineageOS are much different. GrapheneOS is a hardened OS with substantial privacy and security improvements:
https://grapheneos.org/features
CalyxOS/LineageOS are not hardened OS, substantially reduces security. CalyxOS recently went 2 months not shipping standard security patches.
Compatibility with Android apps on GrapheneOS is also much different. GrapheneOS provides our sandboxed Google Play compatibility layer:
https://grapheneos.org/usage#sandboxed-google-play
Can run the vast majority of Play Store apps on GrapheneOS, but not CalyxOS/LineageOS with the problematic microG approach.
GrapheneOS also doesn't require any CLI (Command Line Interface) knpwledge and helps protect users from bricking their devices by using our simple click through web installer process:
https://grapheneos.org/install/web
CalyxOS is closer to LineageOS they both share the same issue above and they both always use multiple Google services too while giving them privileged access even if users don't use microG. It would be wrong to imply they don't use Google services. microG is of course an implementation of Google services. GrapheneOS doesn't use Google services by default.
To clarify further they always use Google services even without microG. They use Google for connectivity checks, network time, attestation key provisioning, SUPL, DNS fallback (LineageOS only), PSDS (Pixel 6 and 7), eSIM activation and more enabled by default.
https://blog.privacyguides.org/2022/04/21/grapheneos-or-calyxos/ is a 3rd party article explaining some of the substantial differences between GrapheneOS and CalyxOS. It's a common misconception that they're similar. CalyxOS is far more similar to LineageOS than GrapheneOS. There are many other alternate OSes available.
https://privsec.dev/posts/android/choosing-your-android-based-operating-system/ is another article about privacy and security differences between alternative Android-based operating systems.
If you have any questions/feedback though you know where I am, always happy to hear. Take care.
Regards the Pinephone:
Pinephone has no secure element. Lacks secure element features deeply integrated into Android Open Source Project such as the hardware keystore, disk encryption key derivation throttling and insider attack resistance for the secure element. GrapheneOS makes even more use of it.
Pinephone has almost none of the expected hardware security features. It has an insecure SoC configuration, no secure element, no capability of providing Wi-Fi anonymity, no possibility of providing proper security support due to the chosen components and further problems.
Pinephone is not open hardware and doesn't have open firmware despite many misleading claims about it. There's no open source baseband firmware available but rather an open source OS for loading proprietary baseband firmware.
The Pinephone baseband with the open firmware is really no more open source than a mainstream Android phone with an open source rild and other services in the OS. It's presented as a breakthrough and unique feature but what's being replaced doesn't exist on a mainstream phone.
GrapheneOS priority is avoiding the device being compromised in the first place. Pinephone has very poor hardware, firmware and software security. Radio firmware can't be kept properly updated. Operating systems for it lack modern security model with proper sandboxing and MAC/MLS, etc.
We're unwilling to make substantial security sacrifices to have broader hardware support which is why we focus on Pixels. Pixels offer far better security than other Android phones and the Pinephone offers far worse security than a typical Android phone which is why for example we can't support it.
Thanks for listing GrapheneOS there but to emphasise the differences between it and the others...
GrapheneOS and CalyxOS/LineageOS are much different. GrapheneOS is a hardened OS with substantial privacy and security improvements:
https://grapheneos.org/features
CalyxOS/LineageOS are not hardened OS, substantially reduces security. CalyxOS recently went 2 months not shipping standard security patches.
Compatibility with Android apps on GrapheneOS is also much different. GrapheneOS provides our sandboxed Google Play compatibility layer:
https://grapheneos.org/usage#sandboxed-google-play
Can run the vast majority of Play Store apps on GrapheneOS, but not CalyxOS/LineageOS with the problematic microG approach.
GrapheneOS also doesn't require any CLI (Command Line Interface) knpwledge and helps protect users from bricking their devices by using our simple click through web installer process:
https://grapheneos.org/install/web
CalyxOS is closer to LineageOS they both share the same issue above and they both always use multiple Google services too while giving them privileged access even if users don't use microG. It would be wrong to imply they don't use Google services. microG is of course an implementation of Google services. GrapheneOS doesn't use Google services by default.
To clarify further they always use Google services even without microG. They use Google for connectivity checks, network time, attestation key provisioning, SUPL, DNS fallback (LineageOS only), PSDS (Pixel 6 and 7), eSIM activation and more enabled by default.
https://blog.privacyguides.org/2022/04/21/grapheneos-or-calyxos/ is a 3rd party article explaining some of the substantial differences between GrapheneOS and CalyxOS. It's a common misconception that they're similar. CalyxOS is far more similar to LineageOS than GrapheneOS. There are many other alternate OSes available.
https://privsec.dev/posts/android/choosing-your-android-based-operating-system/ is another article about privacy and security differences between alternative Android-based operating systems.
If you have any questions/feedback though you know where I am, always happy to hear. Take care.
Ahh security patches, condoms of code. ๐
We have contributed to Florisboard with the prospect of including it in the future however it is still far from production ready as it stands but watch this space when it is.
I am holding all lightning donations from Nostr in the interim.
Thankyou ๐ nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 ๐ฃ๏ธ๐ข
#Humble
Oof being referred to as an account. By all means check my verified links here on Nostr and ask in the GrapheneOS Matrix Community:
GrapheneOS Community https://matrix.to/#/#community:grapheneos.org