Just assume you are.

Oh geez…

The only true solution to this is cryptographically signed identities.

One method is identity verification tied to a public key, which can be done with claims aggregation (I am X on GitHub, and Y on LinkedIn, and Z on my national ID, etc), but this removes anonymous use.

Another is a central resource to verify a user’s key is a real human, where only one entity controls the identity verification. While this allows pseudo anonymous use, it also requires everyone to trust one individilual entity, and that has other risks.

We’ve been discussing this with FedID a lot, lately.

I really want to build an ESP32 remote and hub combo with a community-owned device database. I have the know-how, but alas, not the time.

Still using Rufus? Ventoy is the way of the future. One USB, hundreds of ISOs.

Edit: Seems I was unaware of some potential risks with the binary blobs pre-built in Ventoy. No threat has been found, but there are supply-chain concerns. It appears there is a fork where someone is cleaning up the build process.

Maybe, but not based on the sign. That’s a standard trucker joke about waiting for pumps.

Ahhh yes very very true. Also a great addition.

True, I went through that phase as well. It usually came with a side of insecurity. Just happy to have grown in more than just age.

Having grown up in a conservative household in a red state (US), and having thought this as I transitioned away to more liberal stances as I learned more about the world, I have to say: Spot on. I was an uninformed idiot.

Exactly. I don’t think they’d ever go down this road, but the big players like Samsung have agreements in place where they will continue to get access to main or some trunk. No reason they couldn’t change license and require all players to do the same thing, though O doubt that would happen given the massive security PR implications. So many Android devices would end up with vulnerabilities, tarnishing the image.

And are limited to highly trained routes. There’s a reason you only see them in specific neighborhoods of specific cities.

It’s an Apache license with a contributor agreement. At any point they could close source. People could fork from it at that point, but any new features/updates/breaking changed from then out would be behind the scenes. There’s no GPL poison pill in this one, I’m afraid.

Note: I don’t at all expect this extreme of a direction.

Click bait headline.

Next post:

“Why do people respond to a message that doesn’t need a response when they could just send an emoji?”

Thanks Fennec I use, I haven’t tried Mull yet. Sounds dumb but I’m constantly looking for Android FF forks so I can use them for other profiles. Really wish mobile FF would get proper profile support.

What do you use on Mobile?

How so? If Graphene is based off a release branch, there shouldn’t be change in timing. Sure, maybe a little for inspection, but as far as I know Graphene isn’t based off main anyway.

Depends on how much they contribute back. Graphene has a history of contributing to AOSP, so it will make things more difficult for that, but not really for the ROM development itself. I’m not sure how Lineage is structured these days.

This is not at all a summary of the article. They’re moving to trunk-based dev to reduce merge conflicts coming in from the public on AOSP.

I don’t like it, because those few devs who contribute to AOSP without an agreement currently will have lagging code, but what you describe is just plain wrong. Is it possible? Sure. But it always has been, that doesn’t mean that’s what is happening.

Nice. I went Sibor with the CNC kit for an… odd reason? It needs to survive repetitive van transport.