Favorited Chrome to limit full ad blocking extensions to enterprise users by 9to5Google
Google’s Chrome is not a browser, it’s advertisement delivery software. Adtech after all is where their profit is. This is incompatible with Doc Searls‘ Castle doctrine of browsers, so Chrome isn’t fit for purpose.
image by Matthew Oliphant, license CC BY ND
Google shared that Chrome’s current ad blocking capabilities for extensions will soon be restricted to enterprise users. SEC filing: “New and existing technologies could affect our ability to customize ads and/or could block ads online, which would harm our business.”
9to5Google
pi-hole.net
Keep fighting
@jeannie @ton Unlikely, as Chromium is open-source, such a move wouldn’t be accepted by others using that code in their browsers. There has already been pushback from Vivaldi, Opera and Brave over the changes to WebExtensions that would cripple ad blockers.
“Chrome isn’t fit for purpose” should be enough to stop using it
I have an installation of Chrome which is used exclusively for browser testing, auditing with Lighthouse – although https://web.dev does a lot of the same things now, from any browser – or the very rare occaision I need to use Google search for something (I’ll load any relevant results in FF). I’ve not signed in to Chrome either, so it *should* all be decoupled from my other web activity.
@bradenslen @jeannie @AlanRalph @ton I don’t know the internal power/politics/governance model of Chromium, but having been a part of a couple of “build a similar/competitive thing on the same codebase that’s sponsored by BigCo” OSS projects, it’s almost always “the management of the company who employs most of the developers makes the decisions” when there is a dominant company and/or a company that originally developed the software/sponsored the OSS project. This can even be true in an OSS project with real governance, just because of pure numbers (a company employing more people to work on a project is going to end up with more people in leadership roles because there are more of them to choose from)….
It was Mozilla Corp calling the shots over what went into Gecko (and of course the Firefox UI/UX). It was Sun (and then Oracle) dictating the design, features, and direction of OpenOffice.org—so much so that the Linux distros, who employed the greatest number of non-Sun developers, created their own fork, LibreOffice (with a slightly better name 😉 and a non-profit and true community governance to steer it) and left IBM to pick up the scraps of OOo as Apache OpenOffice. And, in fact, that Apple was driving the direction of WebKit was what brought us Chromium in the first place; Google wanted to architect things differently and focus on different areas, so they forked (they already maintained an internal fork because of the V8 JS engine and some other stuff, so this relieved some of that maintenance burden and let Opera join in).
So—and again, I don’t know how governance, and, really, power, works in Chromium, nor at what code level these changes will be made, though it certainly seems like they’d be to the shared underlying code—it doesn’t seem likely to me that the other contributor-companies to Chromium will be able to sway this decision on Google’s part, at least not without some sort of significant external pressure.
Alternatively, they could possibly patch that feature back in (if the changes are small and non-invasive—which they might be, since Google still plans to let enterprise-Chrome use them) in their own builds, and maintain that forever. Or they could all band together (especially if they get Microsoft) and fork Chromium themselves—but unless they can commit significant resources, a fork of a fork is not promising, and the reason the smaller browser developers chose Chromium in the first place was in part to have a (modern, fast, etc) browser engine without having to dedicate the resources to building and maintaining it all themselves.
Sorry for the length (and especially the gloomy outlook) but thought you might find my perspective/“expertise” of interest…
@smokey Wow, really sorry for the length. I knew it was long from scrolling in the tiny reply box, but not that long until after seeing the posted version…
Pleased to see that my step last week to fix my RSS feed so it shows my words first, not what I’m reacting to, actually has the hoped for effect.
My feed goes to my micro.blog account, and there my own words are shown now first too. A post in this new form yesterday created a nice conversation involving 4 others on micro.blog. That would not have happened had my post started and ended with “Read: some url”.
@smokey Your expertise is interesting. I’ve heard that Google calls the shots for Chromium from other sources as well. All this makes me continue to wonder how long other browsers can continue to use Chromium and how hard it would be for them to jump ship and convert to FF’s engine or Webkit?
Aside: Microsoft has been reaching out to Linux dev’s for help porting MS Edge over to Linux. I find that interesting and confusing since as a Linux user, Edge would be one of the last browsers I’d choose. Odd strategy.
Don’t worry about length. Your post was interesting and enlightening. I always wondered how and why LibreOffice came about.
cc. @ton @jeannie @AllenRalph
@smokey While a bit of a read indeed, I appreciate the “inside look” perspective of FOSS and had suspected this, but confirmation of first hand experience is educational and enlightening. Thank you.
//@ton @bradenslen @alanralph
@jeannie You’re welcome; glad you found it useful.
@bradenslen I think that WebKit would be superficially similar (since Chromium forked from it), but a lot, if not all, of the “application layer” stuff (as opposed to the “web rendering and lower layers”) won’t be the same, since that’s the most visible place that Chrome differentiated itself. I also don’t know what the WebKit cross-platform situation is these days (there used to be people who built apps with it on Linux and Windows, but I haven’t kept up), so…. Firefox would be an entirely different thing (although I think they share some of the extension APIs with Chrome, but the big stuff of how you build a browser on top of the platform will be completely different). There are no good options for the other Chromium-based browsers.
As for Microsoft, they apparently love Linux now 😉 But it does seem like an odd choice.
The birth of LibreOffice (and the subsequent rotting of the original project) was very interesting to watch; that’s got to be one of history’s better forks.
@smokey I believe GNOME web aka Epiphany is based on WebKit. Seen it installed as the default on a few distros lately. Which is encouraging, though it’s not quite as common as Firefox yet from what I’ve seen.
@smokey WebKit does not seem to be extensively used cross platform anymore. The only active project that comes readily to mind is Gnome Web browser (aka Epiphany) on Linux. I know Gnome Web is being adapted for small screen use for the new Puri.sm Libre 5 Linux smartphone as default, so maybe other Linux smartphone makers will pick it up as well.
@mcg it’s forks all the way down.
@PeacheyMcKeitch @mcg Yup. (I didn’t mention that fork because it arose in a different manner than the others.)
@bradenslen Ah, I’d forgotten Epiphany switched from Gecko to WebKit; IIRC, they started that about the same time we were considering the fate of Camino (which says something about the relative states/(un)friendlinesses of Gecko and WebKit at that time).
Quotebacks have been mentioned in various corners of the IndieWeb a lot in the past few weeks. As it was launched as a Chrome plugin, I didn’t try it out (Chrome is an unpalatable ad delivery vehicle imo). Now however there is a Firefox Quotebacks plugin, Tom Critchlow announced.
As Tom says, Quotebacks are meant to reduce friction in quoting other blogs/sites/sources, and if that increases the number and length of distributed conversations I’m all for it.
How is it different from a block-quote? It isn’t actually, under the hood it is still a block-quote. It’s just styled differently, and the browser plugin makes it very easy to capture everything you need and paste it into your blog-editor. The quoteback you see above is a html block-quote in the source:
While reading you can select text and in Firefox press alt s, and the plugin will pop-up. It allows you to add / edit things, and then copy the html encoded quote to your clipboard, to paste into your blog editor.
I like the easy ‘quote, copy, paste’ flow and having it look nice. I do think that the styling, which mimicks how e.g. Tweets are embedded in websites, may sometimes however actually break the flow of a blogpost, where a block-quote is more like a highlight in the pace and rhythm of a text, while a quoteback is presented as an embed, a different thing separate from the text. In fact I mostly actively dislike the embedded tweets in e.g. ‘news’ articles. There it feels like a way of not having to write an actual article or story, resulting in ‘news’ items along the basic template of “X said something, Twitter wasn’t having it” (With the article often stating the content of a tweet in its text, and then embedding the tweet below it, repeat 12 times. Voila, ‘journalism’ done.) It’s an additional visual amplification, easy on the eyes yes and instantly recognisable as a visual pointer to elsewhere, that probably isn’t always warranted, and may even reduce attention to the post the quote is used in. That would then decrease the level of distributed conversation, not increase it as intended.
Of course it is entirely possible to use the quoteback plugin, and not having the visual style of embedding applied. Below is the exact same quoteback as above, but with the
class="quoteback"removed, reverting it back to a regular block-quotes (but keeping the link to the source and comments you may have added). Alternatively you can also delete the script element that provides the styling information for the quoteback. (I do exactly the same with Flickr embeds)I’ll experiment for a while to see how it works for me in practice. I’ve put the script that styles the embed on my own domain, so I can also fiddle a bit with the styling if I want.