Thanks for sharing the link. I'll take a peek at them and their ToS.

Or... honestly, just pay $40 for basically unlimited usage for a year from an API, then roll your own frontend.

Can you clarify, what you mean by this? Rent a VPS? Or is there a legitimately good place that'll offer "unlimited" llm api access for $40 / year (and would you have any sort of privacy with this)?

Hey, I'm glad you found the information helpful.

If you decide to use your own avb custom keys (meaning that you are the only person who can install cfw - this means that google, graphene, etc would fail to install as they aren't signed with your keys).

You can then use tools like Custota to allow you to have/distribute your OTA (over-the-air) cfw updates.

Why would you want to do this?

Well, for sometime I was running a rooted version of graphene w/ magisk (as I wanted "real" offline backups). This means that I needed to "sign" each release and the official graphene updates. The process was a bit tedious, but well documented.

The upshot of custota being installed on my device, was that I got a notification when I had a new self-signed update available... and the release/install process was entirely under my control. ...and if something borked, I could "rollback" to the previous version (tbh, nothing did bork, so I didn't actually need to try this).

Good Grief

I'm curious: How is Cryptomator better/worse than running rclone with client-side encryption?

I don't know if Calyx offers "officially" signed releases, but there appear to be users reporting that moto g84 support avb_custom_keys.

If they don't, you can create your own custom keys and sign the release yourself using ’avbroot' (linked above).

AFAIK, the only way you can reliably lock your bootloader with a custom firmware, is if the device allows you to upload new avb_custom_keys. This basically allows you change your locked bootloader to allow custom firmware from a single (signed) source (ie graphene, google, your own).

I can't say for certain, but many non-pixel phones do not support this.

So, if you were to lock your bootloader, the loader would notice that you have an "unauthorized" firmware installed and would not run it. You'd basically need to unlock the bootloader again, but I think Motorola has made this process more complicated. Meaning you might need a bootable device to do it.

As far as security: Unlocked phones are less secure. All android devices are encrypted, using a hardware key plus your pin number. When a device is locked, a "secure key" is used as the hardware key. When a device is unlocked "another key" is used. If an attacker gets a hold of your unlocked encrypted phone, they can easily get this "other hardware key" which means they already have 1/2 of the information needed to decrypt your phone.

Afterwards, the only thing protecting your unlock phone is the strength of your pin (which is trivial to brute force). On locked bootloaders, it's much more difficult, as they'd need to figure out the "secure key", in addition to your pin.

I was kinda disappointed that the article didn't offer any suggestions for how to "push back" on attestation being shoved down our throats.

...it seems governments and companies are doubling down on attestation, in the form of mandatory age verification.

So... who's going to get this money? ...I'm just askin' for a friend.

My concern would be if I could buy local games and use them in my imported console.

Can TorrentsDB be self-hosted?

I found a repo on github, but it hasn't been updated in 6 years.

I had a torx handle with a single screw driver bit attached, left over in my backpack. (So basically just a screwdriver)

Combined, it barely exceeded the maximum safety length. If I'd stored it separated, it would have been fine.

I offered to separate it, that wasn't going to work. I needed to leave one of them behind. ...as the rest of the socket set (at home) needed the torx handle, I left them with the screw driver bit.