fmstrat

Honestly, this is one of the scariest parts. This is how you set back a civilization, much less a country.

Wow, all the down votes. Youngin’s don’t know what they’re missing. Classic film.

@SecondaryAnnetagonist@lemmy.blahaj.zone @Atomicbunnies@lemmy.dbzer0.com

While I wholeheartedly agree this is “meh” compared to everything else, this isn’t nothing.

If you were to try to get a job with even basic security clearance for a site in the US, and it came up that you were hacking at 19 years old, you would not move forward.

It’s a fact-based merit that under normal circumstances would result in termination if it was found to have not been disclosed previously. So pointing it out is still important.

All that being said, disclosure is the key. If it was disclosed, it’s a judgment call, and, well…

Also, @Eheran@lemmy.world

And contribute if you can’t.

For non-programmers: Yes, reporting bugs, writing docs, and answering questions is contributing.

Edit: Fun story, the best contributor I ever had was someone who randomly reproduced reported bugs and filled in the details about how they did it.

Just assume you are.

Oh geez…

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.

Ahhh yes very very true. Also a great addition.

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.

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.