matchboxbananasynergy
banner
mbananasynergy.bsky.social
matchboxbananasynergy
@mbananasynergy.bsky.social
Community manager @GrapheneOS. Mod for a few open-source projects. This is a personal account and the hot takes you'll find here are exclusively my own.

#grapheneos #mollyim #accrescent
We cannot say which OEM it is at this point. It'll be announced when we can.
September 3, 2025 at 7:09 PM
It's been more than that, and in those years, there have been no other devices meet our requirements. We're currently working with an OEM to have some of their future devices support GrapheneOS. They're implementing what we need. We can't cut corners, we'll just support OEMs who want to do the work.
September 3, 2025 at 7:07 PM
You're calling GrapheneOS corrupt for having clearly defined standards and sticking to them, but not companies that make software and hardware that is marketed as private and secure while being neither? It's very weird.
September 3, 2025 at 7:02 PM
This is an extremely weird thing to say. We've made it extremely clear why we currently support the devices we do, and we have also made it clear why we can't support the other devices people usually talk to us about. We're working on supporting other devices, but we won't cut corners doing it.
September 3, 2025 at 7:01 PM
This kind of thought process and purity tests almost always leads people to worse outcomes where they're much worse off than they could've otherwise been, such as with devices with horrible security/privacy practices that don't receive basic patches or have gaping holes.
September 3, 2025 at 7:00 PM
Privacy is not synonymous with "avoid Google". You can use things Google has made and have privacy. There are specific things that make e.g. Brave a better choice than other non-Chromium based browsers, or Pixels a better device for building an alternative OS.
September 3, 2025 at 6:59 PM
Reposted by matchboxbananasynergy
Things were a bit different with Android this time, likely due to a functionality vs security trade-off that made it harder to address the issue in AOSP. Going forward, we'll continue reporting to Google but jointly disclose to GrapheneOS for any future Android-related issues.
July 23, 2025 at 12:25 AM
Disable non-proxied UDP is the most secure/private option.
June 3, 2025 at 4:20 PM
GrapheneOS currently supports all devices that meet the project's criteria. We would love to be able to support more devices, and would be open to do so if a device meeting our requirements is made. You can see our hardware requirements at grapheneos.org/faq#future-d....
GrapheneOS Frequently Asked Questions
Answers to frequently asked questions about GrapheneOS.
grapheneos.org
March 31, 2025 at 10:07 PM
Reposted by matchboxbananasynergy
For an idea of what we're looking for, see the 10Gbps options at tempest.net/dedicated-se... with 64GB memory. They're also willing to give us a significant discount, which other major providers haven't offered. Tempest is currently IPv4-only though, which isn't ideal for our usage.
Premium Dedicated Server Hosting | Tempest Hosting
Experience fast, reliable, and secure hosting with Tempest. Choose from a range of dedicated servers and game servers such as Rust, CSGO, Gmod, and more! 24/7 support available.
tempest.net
March 31, 2025 at 9:13 PM
Reposted by matchboxbananasynergy
We've made 2 attempts at talking to OVH about offering us something different than their publicly available products which hasn't gone anywhere. We likely need to move this part of our infrastructure to 1 or 2 other providers with unmetered 10Gbps dedicated servers like Tempest.
March 31, 2025 at 8:48 PM