Die, die again.
Die, die again.
I know it sounds intimidating, but the install page walks you through the process step by step. As long as the browser can see your phone, you can flash it with a few button clicks.
Yeah, there’s a bit of a barrier. But getting it actually installed is a breeze. Chromium browser that supports WebUSB is all you need to get it flashed.
Yup. That and tap to pay made me flash stock back. But I wouldnt count our going back someday.
Kind of? It’s only supported on Pixel devices currently. I think a closer comparison to Cyanogen is LineageOS, since Lineage is literally a fork of Cyanogen after the original maintainers closed up shop. Lineage is more akin to AOSP/the stock Android experience, whereas Graphene has been hardened a bit more than your typical Android release to lend itself to a more privacy-centric experience. Tap to pay and Android auto don’t work on Graphene which broke it for me at the time, but I would consider going back despite that if Topics can’t easily be disabled on Android 13/14.
My student loans paid off.
If you don’t use tap to pay and can muscle your way through documentation, GrapheneOS is easily installable on all relatively current Pixel devices. But yeah, I’m not a fan either and as long as I’m on Android, that might tip me back again to using Graphene instead of stock Android.
What do you use as a torrenting client? Most popular ones give you the ability to choose a specific interface over which it will allow incoming/outgoing connections to other peers. Your ProtonVPN should have its own interface you can select from your client. That should make it much less likely for that to happen again if Proton crashes, since if Proton crashes, that network interface disconnects.
The NIC thing was more for if you were using a VPN. You can lock down your client to just use the virtual NIC your VPN client creates, so that’s always recommended when setting up your client.
What is your toreenting “signal chain”, so to say? Normally when you download things through qBittorrent, are you generally running bare? Do you use a VPN? Is your torrent client configured to use a specific NIC? If so, is that NIC active and passing traffic? There are so many variables that play into this.
Collision avoidance is an automated system built into all commercial planes. These “near misses” aren’t actually that close. Go look up TCAS and you’ll see what margins they work with.
Tuya was also supposedly reworking their API/integration to allow for local control, though idk if that ever happened.
Depending on the hardware, you could totally allow access to port 53 via a firewall rule. Unifi does this transparently if you configure a DNS server running on a vlan other than the one you’re connected to.
Tbh no clue. Never saw it again, never heard about it again haha.
It’s still their community for which they were the administrators. Don’t like their administrative decisions? Don’t use their instance. Then you aren’t beholden to their guidelines but still get to participate in communities resident to that home server.
You pay their legal fees in full, then, if someone comes after them because of the content make available via their site. Or host your own instance and stop bitching.
Shouldn’t this account be flagged as a bot account? Or am I missing the marker that says it is?
Yet another reason I’m glad I run my own instance and can make those decisions for myself.
Not enough for it to matter to Apple, and that’s all that matters. Let the bigots jump ship. Then let Google do the same with Android and leave them with nowhere else to go.