Technology

59605 readers

3434 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

600

Google.com pages found to have access to hidden Chrome API allowing hardware info such as CPU usage to be viewed (simonwillison.net)

submitted 4 months ago by dantheclamman@lemmy.world to c/technology@lemmy.world

33 comments fedilink hide all child comments

h/t @simon@simonwillison.net https://fedi.simonwillison.net/@simon/112757810519145581

you are viewing a single comment's thread
view the rest of the comments

[–] xavier666@lemm.ee 3 points 4 months ago (2 children)

You can fork it, fix it, do whatever you want with the code, but on the main chromium repo they rarely accept PRs from random contributors

This needs to be discussed more by the community.

I can kind of understand what's happening. They want to have complete control over what goes in an out of Chromium. Some PM is probably overseeing the PRs, and if some PR hinders their ability to collect data, that PR gets rejected. Mighty fine project this is. Other forks probably don't have the resources to go through all the commits issued by Google and just accept them as it is. They just makes the changes to suit their own agenda. All the more reason for people to switch to Firefox

I wonder how Ungoogled Chromium is affected by all this.

[–] infeeeee@lemm.ee 5 points 4 months ago

I don't know what needs to be discussed. Everyone owns their code, every project has some kind of hierarchy. Chromium is a project started by google, so Alphabet Inc. has a final word in any decisions. Similarly Linus Torvalds has a final say in Linux kernel development, and Lennart Poettering in systemd. That's how it always worked, and I think it's good enough.

What you can do is, you can hard fork a project, than you can have a final say there. This is actually how chromium's engine started: its Blink engine is the fork of Apple's webkit engine which is again a fork of Kde's khtml engine.

Ungoogled chromium is not a hard fork it's just a list of patches: https://github.com/ungoogled-software/ungoogled-chromium They can override google's decisions this way, but the more thing they patch the more thing they have to maintain, more work, and more things can break with each update. Afaik it's similar how all other chromium based browsers work.

Everyone said this for years now. If you care about the freedom of internet (caring about your privacy is secondary) you shouldn't use chromium based browsers. Stop using it now.

[–] conciselyverbose@sh.itjust.works 1 points 4 months ago (1 children)

Open source doesn't mean they have to accept community input. The rights you're granted are the right to take their code and alter it for your own project, or redistribute it, not direct it.

A lot of corporate owned open source projects choose not to accept third party contributions at all (or at least without giving them actual ownership), because if they own the entire codebase, they can sell different licenses to businesses that may not like some restriction of the open source license.

[–] xavier666@lemm.ee 1 points 4 months ago

I prefer the VS Code approach. The entire codebase is open but owned by Microsoft. But because of the MIT licence, the community has made VSCodium. Microsoft does not interfere with VSCodium (AFAIK). This I think is a good model.