Conversation

This Tweet was deleted by the Tweet author. Learn more
Replying to
deleted!! is there backstory I missed? I believe they have similar incentives and have made progress towards providing an example for factoring out many of the questionable google-y bits. I'm happily widevine-free in part due to their efforts.
1
Replying to
I strongly dislike their CEO and consider a fair bit of what they've done as a company to be quite problematic. I prefer avoiding contact with them over conflict. I have too much other stuff to deal with to have the bandwidth available to deal with them.
2
1
Replying to
Chromium itself doesn't come with Widevine. If you build desktop Chromium with enable_widevine=true it enables support for fetching and using it. It's not enabled by default. It has support for other implementations too. I want to have it work this way for Google services too.
1
1
Replying to
So, for example, there should be a way to configure the service to use for correcting navigating errors. It should default to not using one. If they have no intention of standardizing and documenting how this works, they should just move this proprietary Google service to Chrome.
1
1
Replying to
I want them to start designing all of these things to be configurable at build time. It should be possible to build Chromium in a way that it doesn't connect to Google services without applying any patches. Other browsers shouldn't need to patch it to use their services instead.
1
1
Replying to
Yes, I'm aware of some of this! It's why I've been investing in Brave, despite significant disagreements with the CEO. It seems very useful to have at least one group working to maintain a diffset for most of the obvious issues.