The guy you were replying to is saying "People hate GrapheneOS because it requires a Pixel," they were not saying "everyone in the world should be using a Pixel" as you seem to have mistaken.
You're getting very fired up and heated in the comments here... maybe take a break?
This was the first thing that came up in a search. Looks like there's a few sizes too:
https://meowspace.biz/product/meowspace-microchip-system/
It looks pretty pricey, but considering microchip pet doors on their own cost about that much, this seems like a cheaper option than DIYing some contraption involving a microchip pet door.
Look around for this kind of stuff OP! It exists!
It doesn't seem like the Lemmy API provides any way to tell if a remote instance has downvotes disabled or not.
This doesn't solve the problem of sending Threads a copy of absolutely every bit of activity that happens on the instance. If I'm on an instance that federates with Threads, even if I put them out of sight/out of mind, they still get a copy of everything I do. A lot of people are on the fediverse for privacy reasons, yet here we are with people begging to hand Facebook this data on a silver platter.
"But why hide information that's public? They could just scrape it."
Yes, they could. But a real-time feed of activity is more complete, easier to manage, and doesn't require them to go and build a scraping tool just for this.
If I don't want Threads to have any of my data sent to them, I should be able to choose without needing to leave an instance I've been on for potentially years.
I'm really not a fan of when features are teased as "coming to Android 14." There is absolutely no shot this gets upstreamed to AOSP.
Reading between the lines in the article, this is going to end up in an update to Google's launcher app, or maybe their wallpaper app. At most, their closed source flavor of SystemUI.
But for the growing number of us compiling AOSP from source and using it to get away from Google's spying, it's disingenuous to keep advertising these features as "coming to Android 14."
Heck - if this feature makes it in any of the apps like I said it might, then there's really no reason to lock it to Android 14. It could easily run on Android 12 and 13. But it won't, because Google wants you to buy a new phone.
Been running CalyxOS for 3 years. Compile it myself from source with some extra tweaks and such. I've even got a nice build server going that automatically compiles builds monthly and pushes updates to my phone via OTAs. It was a little work to get set up, but now it doesn't feel any different from the stock Android experience.
It started because I was tired of all the unchecked spying Google does, and I wanted to get away from that. But now I can never go back to "regular" Android, because the vendor bloat in "stock" ROMs is incessant, and I am maintaining patches for quite a few features Google has either removed, or never supported in the first place (2-button navigation, AM/PM clock, automatic call recording).
Honestly, there hasn't been any drawbacks. The phone works perfectly, calls are fine, it runs great, and I haven't needed Google Play Services for basically anything. My banking app still works. I don't use Google Pay so I don't really care that it doesn't work. Android wearOS doesn't work, but at this point Google has dropped the ball so severely, I don't have the motivation to bother with a smartwatch.
Most of my paid apps continue to work without patches, and I get them from Aurora Store. For the ones that don't work, I just patch them myself to remove the license checks. I paid for them, so I should be able to use them regardless of what ROM I use.
Liftoff is a pretty popular app and it doesn't have DM support either.
I don't see anyone talking about CrossCode, but it's such an amazing game. And it's on sale right now!
https://store.steampowered.com/app/368340/CrossCode/
Profound story, excellent sound design, amazing soundtrack, insanely well designed combat system. It's just an incredible game. It has more content, depth, and attention to detail than most AAA games these days.
If you're picking it up, get the DLC as well! It's not just DLC, it's the conclusion of the game's story!
It's caused by Lemmy-UI's websockets client. It does weird stuff like this when the site is under heavy load (we broke Lemmy!)
It's being removed in Lemmy 0.18 and being replaced with a more stable http client. No word on when that will release, but it looks like progress is being made fast.
Sources:
https://github.com/LemmyNet/lemmy/issues/3008#issuecomment-1588120660
https://github.com/LemmyNet/lemmy-ui/commit/2b1af707c3df6126b3e6890106c03c60ad49b1be
I did. The benefits as I see them:
If you don't want to open this and solder a chip, then no, you can't do what you want.
The closest you can get is to enable AutoRCM, which will cause the Switch to always boot into recovery mode and accept a payload. This skips the need to use a jig in the Joy-Con rail, but you still need to inject a payload. And because recovery mode is just a black screen, you don't have any visual feedback to know if the Switch is actually in recovery mode, or if the battery is just dead.
Your best option is to just boot into whatever OS you use most, then make it a habit to keep it charged enough to not shut down.