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.
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.
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.
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?
You should post this over on one of the Self Hosted communities. I’m sure they would appreciate this as well.
And that usage is still fine and actively used in those kinds of industries. But OP is just being edgy.
I try to catch and release, specifically larger flies (been having a flesh fly problem recently) because it’s just less cleanup.
I’ve never been able to execute that successfully. Also not as easy to do when they’re on a vertical surface or the ceiling.
Yes, and I’ve done that too, but I’ve also had a number of them fly away as the cup closed in on them, even when the cup isn’t moving quickly.
Instinctively, I doubt it. But they can pick up on the air moving around from you trying to swat at it, which is why it’s such a pain in the ass to capture to release or kill one. They are able to tell well before they’re captured/caught that something is coming for them.
This BU blog entry from 2012 gives a lot of interesting information on the many ways they are able to evade us.
My left ear loves this video.