I was confused for a second asking myself when Kroger was split into Kroger Sued and Kroger Nord.
I was confused for a second asking myself when Kroger was split into Kroger Sued and Kroger Nord.
Android supports multiple payment providers. Some banks implement their own payment provider (e.g. Sparkasse in Germany), most just rely on Google Pay (now Google Wallet). Google Wallet has strict requirements for the Play Integrity API. Because of the modifications to Android that GrapheneOS is implementing, it is not eligible to receive the required integrity attestation and thus, Google Wallet is refusing to work. Google could at any point reconsider and certify/whitlelist GrapheneOS, which would allow Google Wallet to work using GrapheneOS. Likelihood close to 0.
Any banking app implementing their own payment provider is completely independent of this decision unless it also relies on Play Integrity API attestation (or a similar mechanism).
That does not sound plausible to me. Typically, your own computer would be behind a router that is either doing NAT or has a firewall (probably the former). Any incoming traffic would be directed to the router without any chance of reaching your computer. Whatever you saw was either outgoing traffic or incoming traffic in response to connections initiated by your own computer.
Connection attempts from the FBI? Could you specify that a bit further?
home assistant, freshrss (and a few related services such as rss-bridge), nitter and piped. I tried to host libregrammar, but ran out of memory.
I am using Librera Reader. Make sure to install the F-Droid version (Librera FD) without Google Play services.
It is primarily an ebook reader that supports a variety of formats, but it is also an excellent PDF viewer. Significantly more feature-rich than any other FOSS PDF viewer for Android that I have found.