OF requires strict government issued ID verification in some jurisdictions. Patreon does not, at least in the US.

That should be your deciding factor already. No one should have their privacy invaded just to send you a few bucks a month.

What do you mean? RPCS3 is an excellent emulator. It's not completely hardware accurate, almost no 3D emulator is, but it's still pretty good.

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?

Bro...

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!

You also can't open two spreadsheets that have the same filename. I'm sure that's led to a helpdesk call or two.

I don't need or want replication of my private projects to a peer to peer network. That's just extra bandwidth to and from my server, and bandwidth can be expensive. I already replicate my code to two different places I control, and that's enough for me.

I'm not sure who Radicle is for, but I don't think the casual hobbyist looking to self host something like Forgejo would benefit at all from Radicle.

Loading the source code for Radicle on Radicle also seems fairly slow. It seems this distributed nature comes at a speed tradeoff.

With the whole Yuzu thing going on, I can see some benefit to Radicle for high profile projects that may be subject to a takedown. In that respect, it's a bit like "Tor for Git."

I suspect that over time, pirate projects and other blatantly illegal activities will make use of Radicle for anti-takedown reasons. But to me, these two projects solve two different problems, for two different audiences, and are not really comparable.

Edit: There is already enough controversy surrounding Radicle, that, if I were someone looking to host a takedown-resistant, anonymous code repository, I would probably be better served hosting an anonymous Forgejo instance on a set of anonymous Njalla domains and VPSes. The blockchain aspect was already a bit odd, and what I'm now seeing from Radicle does not exactly inspire confidence. I don't think I'll ever use this.

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.

A bit too late for that now. Once they killed Inbox I just migrated everything to ProtonMail. Don't even use my Gmail address anymore.

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.