Notices by Gianmarco Gargiulo (gianmarcogg03@mastodon.uno)

€9000 to go and 32 hours left. We can do this, #Fediverse! We can get this beyond the 75K if we really try!

@gabriel I'm working with some friends on an alternative from scratch to all of these as we are discontent as much as you are about them. No guarantees, especially since we just started, but we want to reach a sensible amount of features that's comparable to Telegram, Discord and even Mumble, all in one native desktop app (and possibly a mobile client in the future).

@privateger @alina that's the Google Firebase logo.

@FediTips @voxel maybe you're right, the Wikipedia article on the Signal Foundation says Acton is chairman of the foundation since 2018 and interim CEO of the Signal company since 2022.

https://en.wikipedia.org/wiki/Signal_Foundation

@voxel @FediTips Wikipedia says the Signal Foundation was originally funded by Brian Acton, co-founder of WhatsApp. So yeah, that statement was incorrect, even though I still agree it's better to be wary of centralized platforms.

https://en.wikipedia.org/wiki/Signal_(software)

@raccoon @Suiseiseki @GrapheneOS read this: https://grapheneos.social/@GrapheneOS/114671630177160997.

It's important to get an experimental release out quickly to begin extensive public testing. There are usually many issues found in testing. For a yearly release, we usually get out an experimental release in a day, an Alpha channel release in 2 days and need 4-6 more releases.

Our speculation about this is that a result of Google losing a US antitrust case and likely losing several more soon, they're preparing for Android and Chrome being split into separate companies. If Android gets split off, they want to retain Pixels.

https://www.nytimes.com/2025/04/21/technology/google-search-remedies-hearing.html

We've made a lot of progress on porting to Android 16 already. If things hadn't been made harder for us, we would likely be able to publish an experimental release tomorrow and quickly get a release into the Alpha and then Beta channels to start ironing out the bugs in the port.

Having our own devices meeting our hardware requirements (https://grapheneos.org/faq#future-devices) would reduce the time pressure to migrate to new releases and could be used to obtain early access ourselves. Based on talks with OEMs, paying for what we need will cost millions of dollars.

@GrapheneOS Do you believe changes that current changes might be preparing for would be necessary in the event of a breakup, or are these changes intended to soften the blow of a breakup to Google at the cost of third parties?

We're hard at work on getting the port to Android 16 done but there's a large amount of additional work we weren't expecting. It can be expected to take longer than our usual ports due to the conscription issue combined with this. It's not good, but we have to deal with it.

We don't understand why these changes were made and it's a major turn in the wrong direction. Google is in the process of losing multiple antitrust cases in the US. Android and Chrome being split into separate companies has been requested by the DOJ. They may be preparing for it.

Unfortunately, Android has made changes which will make it much harder for us to port to Android 16 and future releases. It will also make adding support for new Pixels much more difficult. We're likely going to need to focus on making GrapheneOS devices sooner than we expected.

We did far more preparation for Android 16 than we've ever done for any previous yearly release. Since we weren't able to obtain OEM partner access, we did extensive reverse engineering of the upcoming changes. Developers also practiced by redoing previous quarterly/yearly ports.

In May, we began preparing to port to Android 16 despite our most active senior developer responsible for leading OS development being unavailable (https://grapheneos.social/@GrapheneOS/114359660453627718). Android 16 launched today and porting is going to be significantly more difficult than we were expecting.

@rooneymcnibnug Sorry, I don't have any context here, and I'm not seeing anything on their site/Discourse/Mastodon. Could you elaborate/link?

For those calling new #IOS #design direction Frutiger #Aero and comparing it with Windows 7: it's just not. It's merely a cheap imitation. Windows 7 style had rich iconography utilizing unique shapes, perspective trick, variety of colors & effects. This is absent here.

🧵 1/2

@verge mostly ass, not even much of an evolution from the previous one, definitely not as much as iOS 6 to 7 and OS X Mavericks to Yosemite.

@redstrate that's so neat!