I think you mean IPV0x08

Rename the ISOs to BMP images and say they’re art instead.

It’s the other way around. Google specifically blocks Goodlgle Pay being used on GrapheneOS. I believe there’s another contactless payment app called Curve or something that works on GrapheneOS. Requires Google Play Services installed though.

I still haven’t gotten to give it a full proper go. But Toolbx is designed to assist with development on immutable OSs. Let’s you do regular package installs for all the various Dev tools into a container. Can either install your IDE into the container and run it like a regular app, or use an IDE with built-in Dev Container support.

This amount obviously includes automated emails sent on your behalf by Jira and Confluence. Of course also a tiny *Up to 400 in the fine print.

I did the exact same thing. Wouldn’t like to see it adopted due to accessibility issues. But its a neat trick.

Can you point to any vulnerabilities in its source code as evidence for this?

I’ve tried to play it through twice and haven’t really been able to get much past Act 1. Only saw hope it ended a bit though a Let’s Play stream.

I’m using Bank Australia with GrapheneOS and it works well. Does the Comm Banks builtin tap and pay work on GrapheneOS at all? Assuming they still have their own version, I haven’t been with them in a while.

That’s pretty much exactly it. Not much benefit for only one application. But I have multiple apps that all recieves notifications via UnifiedPush. My UnifiedPush client (ntfy) stays running in the background, the rest of the apps can go to sleep and get woken up if something haopens.

Is that with using UnifiedPush or the WebSocket notification method?

Signal uses Play Services for its push notifications. It does have a fallback method which maintains a connection to their servers to get message notifications. It requires changing some battery optimisation settings which might have some minor battery impacts.

Personally I’m using Molly which implements UnifiedPush for Push Notifications without Molly/Signal needing to run in the background constantly. Also swaps a few other Google dependencies (like location pins) with open source alternatives.

Having the second profile with Google Services is a good idea though. That was what I used to do before I shed my last few Google dependencies.

We all know all the cool kids are hanging out on GitHub contributing to Buttplug.io

I’ve just started using beets for organizing my collection. It’s relatively easy once you get the hang of it. Ease I suppose differs based on how organised/tagged your collection is currently.

You can install pretty much any user agent switcher extension on Firefox for Android.

I downloaded FossWallet off F-Droid last week for an annual pass I bought. It only supports Apple Passkey files, but if they offer Google Wallet they’ll usually offer that too.

They forked it

CoMaps is a recent fork of Organic Maps. So those two are pretty similar at the moment in terms of functionality. Osmand I would say has a lot more features and customisation options, but Organic/CoMaps is faster and more responsive.

Ah, misunderstood your post. I think regular Signal still supports local backup. Doubt they’ll remove it when they add this.

Switching to Molly won’t necessarily give you free cloud backups. Someone will still need to pay for the storage costs.