Tootfinder

Opt-in global Mastodon full text search. Join the index!

@andres4ny@social.ridetrans.it
2026-10-10 02:05:38

You know people say things like, "Even if Trump isn't a Russian asset, there's nothing he'd be doing differently if he was."?
There's a similar thing for Chromium. Even if #Chromium isn't actively and officially hostile to downstream packagers and distributions, it's hard to say what they'd be doing differently if they were. There are people there…

> so the rest of this email covers the current state of affairs, and what might be done by the community to continue compiling Chromium. I hope that Chromium, Crubit, and the rest of the OSS community can together identify the best way to proceed here. If upstream genuinely wants to collaborate with the community, a good start would be not treating downstreams as an afterthought. We need to unbundle, we need to compile natively on architectures that Google only cross-compiles for, and we need …
@michabbb@social.vivaldi.net
2026-09-13 01:27:44

⚡ Projects keep a target's traffic, browser state, cookies, notes and results together, and survive between prompts
🎯 A persistent managed #Chromium session lets agents browse authenticated applications while cookies and site storage survive restarts

@andres4ny@social.ridetrans.it
2026-09-08 23:06:40

So, upstream #chromium just switched to a release cycle of every *2 weeks* for a new milestone release. It used to be 1 month.
If you're using chromium in #debian stable/oldstable, don't expect any kind of stability any more.

@andres4ny@social.ridetrans.it
2026-07-24 06:08:18

Fuck you #Google, I'm not doing two #chromium security updates per week. You people are high. It typically takes half a day for chromium build because these people are incapable of using system libraries and want to bundle an entire OS into a browser.