1074 points by luu 940 days ago | 585 comments on HN
| Mild positive Editorial · v3.7· 2026-02-28 10:49:55
Summary Digital Freedom & Autonomy Advocates
This Mastodon post advocates for digital autonomy and privacy protection by criticizing Google Chrome's browser policies (Manifest v3, JPEG XL removal, Web Environment Integrity/DRM) and recommending open-source alternatives (Firefox, Epiphany). The content strongly engages Articles 12 (privacy), 19 (free expression), 18 (freedom of thought), and 21 (public participation), while using loaded language and presenting a one-sided perspective without Google's counterargument.
The problem is there are almost 0 alternatives beyond Firefox so if you don’t like their UX you’re stuck. All the “new” browsers are just chromium skins (edge, arc, etc.) Are there any real competitors building a new browser?
Webmasters should really fight back and show annoying popups when the user agent equals Chrome. These popups could nudge the user towards e g. Firefox.
Perhaps EFF.org could provide a reference implementation of such popups.
Google Will Let You Opt Out of Chrome 'Forced Login' (2018)
Remember? They tried to force everyone to login completely.
Quote from article:
The tweak was made to address a privacy uproar over the latest iteration of Google's browser, Chrome 69. Earlier versions of the browser let you log into a Google service, say Gmail, without logging into Chrome. But the tech giant decided to change that in Chrome 69, which arrived earlier this month. Signing into a Google service via the browser will now automatically log you into Chrome as well.
Expected a huge list and there's only 3 items there, and one of them, JPEG XL, is kinda moot because it didn't seem viable until recently after Safari started supporting it...
Feel that the list could have had much more substance with the addition of webUSB, webSerial and such features which Chrome just strong armed.
In the current form the list and toot don't really drive the point home...
Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE, IE wasn't an inferior browser at the beginning either. What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web thanks to its enormous market share. On IE's case, MS probably stagnated it to prevent competition against its desktop Apps business and on Google's case it's going to be in the name of data collection and ad business.
Chrome is the new IE.
But yeah, that's what you get when you don't know history.
As someone who hates Google’s behavior here, this “list” (3 whole items!) is deeply underwhelming to the point that I would say it’s some of the laziest social media activism (essentially the easiest form of activism) I’ve ever seen.
What is the excuse of all people reading this thread in agreement and still using Chrome? As I mentioned elsewhere, this is preaching to the choir. A choir of Chrome users.
Google wouldn't be so dominant if tech people like us would stop making lazy excuses to continue its hegemony. In Dante's Divina Commedia, there is a circle of hell for those too lazy to take a stance [1]. If it were written today, it would include a lot of tech workers running Chrome with uBlock enabled.
It's 2023, Safari and Firefox have been very good for a while.
--
1: in fact, in the Divina Commedia the lazy ones that can't take a stance are kept just outside of Hell, as they are so detestable not even Satan itself would want them around.
I would add their moves to put things behind codes of conduct. Not the first time I've seen them deployed purely to stifle criticism but I've never seen it done as overtly as this.
As someone working in the ad fraud detection space, Google has been hostile for quite a while. Making things extra difficult just to get more ad spend quota on their platforms. First User-Agent reduction (I agree with some points). Later making a perfect Headless automated browser that shows no difference against a real browser (making bot detection nearly impossible without captcha's). Last weeks by removing any kind of WebView signal in the browser so it makes impossible to detect between in-app traffic/fraud/Chrome Mobile. Could write a lot more about other stuff and the implications but the whole picture is not looking great.
Firefox had been underperforming during part of its life, but deep internal improvements meant those days are over. There is a huge difference in memory and CPU usage between older Firefox and the one we have today. Sadly, lots of people still think that Firefox never changed.
I did a quick memory usage test, just for having my personal anecdote and some numbers to show. The result was that Firefox uses an average of 10 MiB for each open (and active) tab. Not bad at all!
First, what I'm testing:
* Firefox 115, on Linux Mint 20.3 (which essentially is Ubuntu 20.04).
* 13 extensions installed. Some are uBlock Origin, Amazon Unsponsor, Bookmark Search Plus, DeArrow, Multi-Account Containers, Keepa, One-Click Wayback, Tree Style Tab (guys try this one out for a great vertical tab tree!).
* 90 tabs open. Tree Style Tab makes me open lots of tabs, because it is then so convenient to open/close subtrees for different topics... but I digress.
* Tabs include: 4 videogame stores, which are heavy on graphics and dynamic content. 10 shopping tabs in various shops, including Amazon. 10 YouTube videos (buffering preloaded). 14 Google Drive / Google Docs tabs (heavy on JS usage). Various documentation pages, and too many HN threads to admit.
* Firefox configured to remember all tabs when closed, and restore them when opening. Upon firstly starting, Firefox doesn't actually load the tabs. They are in suspended, inactive state, until opened for the first time.
RAM usage results:
* Cleanly started, only HN frontpage loaded: 372 MiB.
* HN frontpage and this entry opened in tabs: 386 MiB.
* Third HN tab opened: 394 MiB.
* Went through ALL 90 tabs to force them loading: 954 MiB.
Conclusion: Firefox uses around 10 MiB per loaded tab.
(The reason for this post is all those comments here and in other entries, claiming that Firefox was a resource hog for them a while ago, and that's why they nowadays are committed Chrome users. In light of recent events, we really need to collectively reduce Chrome usage numbers!)
Sounds like the thing about "ad blocker sabotage" is about replacing the Web Request API with something called declarativeNetRequest. I've been sifting through documentation but have had trouble seeing why this is any kind of a downgrade for ad blockers. Can someone explain?
- Removing "http://" from URLs. This was partially fixed several years later on Desktop, as now you can right-click the URL bar and check "Always show full URLs"
- Replacing the linear tab view on Android with a 2D grid (so the first tab is hardest to reach with your thumb), and gradually removing all the workarounds as people discovered them.
- Lack of extensions (e.g. ad blocking) on Android
- When using a bluetooth mouse on a Chromebook, the scroll wheel has been really janky for years, and it can only be temporarily fixed using "gesture_prop" in the crosh console. Not sure if this is intentional or just laziness.
I don't understand the JPEG XL frackus, but that's partly because I think the Web platform should not continue being an enormous ball of mud, with everything built into the browser with no layering.
Make a Wasm module (use SIMD and threads if you want) that can decode the format and render to an immutable canvas and then let the browser engine manage the pixels after that. Wasm is close enough to native speed now that it no longer makes sense to bake this into the native browser binary anymore.
Across the dozens of Chrome threads over the last week, I haven't seen discussion about the impact of businesses' usage of Google Workspace. I'm sure this is relevant to the discussion on moving away en masse from Chrome; I use Firefox primarily but need to use Chrome for various organizations.
There's quite a few really useful features for Workspace org admins, from blocklists and telemetry to provisioning browser extensions and adding bookmarks, and most of these features require end users to use Chrome. In fact, you can configure security policy such that end users can only use Chrome to login to their company account, and there are multiple reasons from a corporation's perspective to enforce these types of policies.
Microsoft 365 is the most dominant player, and I assume Google Workspace is second in enterprise user account management. Are there any prominent, stable open-source business cloud stacks that meaningfully compete here?
Aa long as chromium is open source and various entities are able to build and remove/modify anti-user features, i don't see a problem with alternatives being a "skin". If Google makes moves to make it difficult to modify chromium then browser maintainers will quickly migrate to other engines.
Serious question: does the concept of a webmaster still exist in 2023? Sites are developed and built in dtap, deployed by gated processes, and in many instances nobody but the deployment agents have access to the actual production servers.
Can you expand on what you mean? As it stands your questions seem in incredibly bad faith, especially considering the market share Chrome has in the browser space.
IE was absolutely hated for not evolving. I'm curious what "its own vision" was, other than "do as little as possible, while Mozilla and Opera keeps pushing forward."
Now, this is from the perspective of the web developer. I don't think IE was ever hated the same way from the end-user perspective.
Chrome is still innovating, but now end-users hate it, because it's trying to be too much. The "new IE" hat still belongs to Safari.
It was/is a very well thought-out format that had a lot of industry signalling they were willing or even enthusiastic about supporting it, which happens virtually never for new image formats. All the major browsers were working on support, many image processing pipelines were being updated.
Everyone agreed that it was not just a major improvement, but actually the best option out of all the contenders out there. Even the Chrome team. The only ones who didn't agree were the AVIF team at Google, who had developed a competing standard. Well, whoever was on that team had some pull, because not long after Chrome landed JXL support in stable and everything was about to pick up some serious pace, they suddenly landed a commit that reverted everything to do with JXL support in Chrome, and that was that.
An immense, cross-industry effort undone by internal Google politics. That's what's hostile about this situation. JXL is still limping along, but Google's unilateral reversal hurt everyone's confidence in the project but also the entire process. Apparently it doesn't matter what everyone in the world thinks is the most appropriate format. What matters is Lord Google's favour.
Safari caused me by far the most issues, back when I was doing frontend in ~2017/2018, in terms of how it complied with web standards (I wasn't as fussed at the standards it didn't support - at least I knew!) and rendered the web application I was working on across desktop, iPad and iPhone.
I spent more time chasing Safari bugs and rendering idiosyncrasies than I did dealing with IE11, frankly.
I've been a long time Firefox user, but the UI/UX has stagnated (like all browsers) for so long. I'm enjoying using Arc at the moment because it's rethinking a lot of things that bug me about the traditional browser UI paradigm but I also know that it's a trendy startup that could either: explode, decide to change features radically at the drop of a hat (pivot), or simple do something distasteful to please investors.
Extensions technically fill in the gap on the Firefox side, like Containers, but the UX is just an afterthought.
I mean it was always viable. Chrome did an opt-in experiment that no one heard of and than used it as a justification for ceasing its development. As a format it is just a win-win situation. Most of the companies that deals with images spoke for JXL. I think Google tried to push its own format in favour of JXL. So I really don't think it is moot.
IE was terrible at first. It wasn’t until Netscape started proposing dynamic HTML and making a play to take over the desktop experience that Microsoft threw itself behind making a better browser, bundling it with the operating system, and giving it away for free (Netscape was free for end users but required commercial licensing). The only point of IE was to kill Netscape, and it did. Netscape got the last laugh by open sourcing the browser, which is todays Mozilla Firefox. Mozilla was the Netscape mascot FWIW. Mission accomplished Microsoft pivoted to destroying other innovative companies and let IE languish until it was replaced by the malware browser Edge as a competitor to the malware adware browser Chrome. Fortunately Firefox, Safari, Brave, opera continue to exist.
> Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE
It wasn't because they had poor feature adoption. It was because they'd tend to adopt features in a way that's incompatible with other browsers (of the top of my head, handling of localStorage in private browsing). It was a bit of a "fuck you" to devs since you often had to do browser detection for Safari (much like you used to have to do for IE) and have special branches or polyfills for Safari.
> What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web
Apple is just as guilty of this. They crippled and bastardised a bunch of features just to push for a more native adoption (depends on how cynical you are, but some say it's for more control over device usage patterns, and some say it's for longer battery life)
It's gotten better and more aligned with other browsers now, though. But alas, I know most are just chromium clones these days
I’ve been saying this for years (on HN and elsewhere).
In my mind, there are two types of “IEs”. There is the IE that didn’t follow standards and did whatever they wanted and there is the IE that was slow to adopt new standards. Chrome is the former and Safari is the latter. Also, Safari is no where near as slow as IE was to adopt standards so I don’t find it great comparison.
Manifest v3 has been delayed and was/is pretty legitimate, I don't think most people really know wtf they're talking about when it comes to v3. JPEGXL doesn't exactly seem like that big of a deal and is now being developed again - sounds fine, Chrome went "seems like no one wants this" and then people said "we want this" and now it's being worked on. WEI isn't even properly proposed yet, it's so early.
So these 3 things aren't really that insane, WEI is easily the worst of them.
In the meantime,
a) Chrome does everything I need while providing the highest security value.
b) Mozilla won't earn me as a user until their CEO is removed
It's not laziness, I make the conscious choice to use Chrome because I think it's the best browser right now. I use Brave on Mobile and I haven't switched on my laptop yet because I haven't evaluated it.
For me it's the ecosystem. I like my desktop browser syncing with my Android browser, and I really like built in chromecast support in my browser.
I know that Firefox has a mobile version with sync, but last time I tried it, I didn't care for it. I know there have been some attempts to bring chromecast support to Firefox via extensions, but last I tried it it was very buggy. But it's been many years since I tried either of those, maybe I'll give it another shot.
I also just realized neither of these conveniences are relevant on my work laptop. Firefox is approved by my company IT and a lot of my coworkers use it. I'm going to switch today.
This is one of the ways Chrome obtained its market share. I remember years back when working at one of the biggest Flash/HTML5 game platforms at the time, we where paid serious money by Google to include a banner to switch to Chrome when we detected a different browser.
It removes the ability to run custom logic to decide whether a net request should be allowed to go through, switching Chrome to a system like Safari's where you can only declaratively specify what you would like blocked.
While Google claims it is a change they are making for security and performance, a lot of people are worried that it is actually intended to make ad blocking harder.
The biggest blocker for me has been the lack of convenient profile switching. It's an important part of my workflow to have a separate profile for home/work/other, with history, bookmarks, etc. Container tabs are not a good replacement. Worse, I get irritated with the fact that Firefox fully supports this under the hood, but seems to push back against actually implementing a convenient way to use it.
I'm currently doing my yearly attempt to switch, using the Profile Switcher extension [0]. It works well enough, but requires external software running and I fully expect it to break eventually. I also can't open external links in anything but the default profile (vs Chrome opening in the profile most recently active, a nice convenience).
Punishing users for the browser they use when it can render the site perfectly fine is so hostile. They may not even have the choice of browser installed on the machine they use.
An additional test that may be worth trying out is BrowserBench [1] Varies heavily by computer specs. My daily driver is an ancient PC running Linux still fast enough for me but my newer mini-PC's leave this old thing in the dust regardless of what browser I use.
> It's 2023, Safari and Firefox have been very good for a while.
This has not been my experience. Every once in a while I try to make the switch (to Firefox because I'm not generally a mac user, but I use safari on iOS and I'm basically resigned to its limitations)
Slow rendering is for sure a problem.
Buggy rendering is very common -- maybe the site, or maybe the browser, who knows, but anecdotally I've had a lot of bad experiences, including lost work filling out multi-page forms.
And I hate to mention it, but aesthetically I find Firefox to be very clunky and ugly.
Yes, Chrome is terrible for even more reasons than the ones shown here -- the direct integration of Google sign-on into the browser is awful, and the in-page text highlighting through (#:~:text=) is a big anti-feature (that now is being copied by the others, oh well), and after I spent so much effort trying to prune down the stupid buttons on my address bar only to find that they keep adding new, useless ones that are un-removeable ("reading panel"? why are they doing this?). But even with those things it's still the most performant and capable browser.
Google running sites poorly or broken in non chrome browsers should be on the list too. Half the time the back button only changes the url on youtube, and doesn’t go back to the previous page.
Editorial Channel
What the content says
+0.50
Article 19Freedom of Expression
High Advocacy Coverage
Editorial
+0.50
SETL
+0.32
Post is a direct exercise of freedom of opinion and expression, sharing critical views on technology policy publicly without restriction.
FW Ratio: 60%
Observable Facts
The post expresses critical opinions about Google's browser policies without editorial alteration or removal.
The post is publicly visible and accessible on the platform without paywalls or authentication.
Author is clearly identified and credited for the expression.
Inferences
The post demonstrates active exercise of freedom of expression in public discourse.
Mastodon's platform architecture explicitly supports freedom of opinion without editorial censorship.
+0.40
Article 12Privacy
High Advocacy Framing
Editorial
+0.40
SETL
+0.20
Post explicitly advocates against DRM surveillance mechanisms and supports privacy protection; directly engages Web Environment Integrity as a privacy threat.
FW Ratio: 60%
Observable Facts
Post labels Web Environment Integrity 'DRM for whole websites' and states it 'would hurt the web.'
Post critiques Manifest v3 as harming content-blocking extensions that protect user privacy.
Mastodon.social has no advertisement or commercial tracking business model.
Inferences
Advocacy framing DRM and surveillance mechanisms as harmful directly supports privacy rights protection.
Platform's design avoiding ads and tracking reflects structural alignment with privacy as a human right.
+0.30
Article 18Freedom of Thought
High Advocacy Framing
Editorial
+0.30
SETL
+0.17
Post advocates for user freedom to choose tools and platforms without coercion; endorses autonomy in technological and ideological choices.
FW Ratio: 60%
Observable Facts
Post frames browser choice as a matter of principle, appealing to readers' autonomy and judgment.
Post recommends Firefox and Epiphany as alternatives aligned with user values.
Mastodon platform design does not impose algorithmic constraints on user expression or thought.
Inferences
Advocacy for autonomous tool selection relates directly to freedom of conscience and thought.
Platform structure respecting user agency aligns with Article 18 principles.
+0.20
Article 1Freedom, Equality, Brotherhood
Medium Advocacy
Editorial
+0.20
SETL
+0.14
Post advocates for user freedom and autonomous choice in browser selection, acting with conscience about technological practices.
FW Ratio: 50%
Observable Facts
Post encourages readers to make autonomous decisions about browser use based on principle.
Mastodon facilitates community discourse where users exercise reasoned judgment.
Inferences
Advocacy for switching browsers reflects respect for users' capacity for reasoned choice.
Platform structure supporting diverse expression aligns with Article 1 principles.
+0.20
Article 20Assembly & Association
Medium Advocacy Coverage
Editorial
+0.20
SETL
0.00
Post participates in public assembly and association around technology policy; engages broader discourse community.
FW Ratio: 50%
Observable Facts
Post invites community sharing ('handy for sharing with your entourage') to organize collective response.
Mastodon platform facilitates federation and collective discourse without membership restrictions.
Inferences
The post uses the platform to organize and mobilize community discourse on public issues.
Platform structure supporting federation aligns with freedom of assembly principles.
+0.20
Article 21Political Participation
Medium Advocacy Coverage
Editorial
+0.20
SETL
+0.14
Post engages in public discourse about technology policy affecting the broader public; participates in civic debate on digital rights.
FW Ratio: 50%
Observable Facts
Post discusses Web standards, browser policy, and digital infrastructure — matters of public concern.
Post presents reasoning for a position on public policy affecting internet users globally.
Inferences
Participation in public debate about technology policy relates to Article 21 rights.
Platform accessibility supports democratic participation in public affairs.
+0.10
PreamblePreamble
Medium Advocacy
Editorial
+0.10
SETL
0.00
Post advocates for human agency and autonomy in digital choice, relating to recognizing inherent dignity.
FW Ratio: 50%
Observable Facts
The post frames browser choice as empowering users to exercise control over their digital tools.
Mastodon's open-source design reflects institutional respect for user autonomy.
Inferences
Advocacy for user choice relates to recognizing human dignity and agency.
Platform structure supporting user autonomy demonstrates alignment with dignity principles.
+0.10
Article 3Life, Liberty, Security
Low Framing
Editorial
+0.10
SETL
+0.10
Post relates digital security concerns to freedom; DRM mechanisms framed as threats to user autonomy and security.
FW Ratio: 50%
Observable Facts
Post characterizes Web Environment Integrity as a mechanism that 'would hurt the web' and threaten digital security.
Inferences
Framing DRM as a security threat relates to liberty concerns in broader digital rights discourse.
+0.10
Article 27Cultural Participation
Medium Advocacy Framing
Editorial
+0.10
SETL
0.00
Post advocates for open standards and open-source software, which relate to cultural participation and intellectual freedom.
FW Ratio: 60%
Observable Facts
Post recommends Firefox and Epiphany, both open-source browsers supporting digital culture.
Post frames JPEG XL removal as limiting technological diversity and cultural participation.
Mastodon codebase is open-source, enabling community participation in digital culture.
Inferences
Advocacy for open standards relates to cultural participation in digital society.
Open-source platform reflects commitment to intellectual and cultural freedom.
0.00
Article 29Duties to Community
Low
Editorial
0.00
SETL
ND
Post advocates individual choice and autonomy; does not directly address community duties or reasonable limitations.
FW Ratio: 50%
Observable Facts
Post frames the matter as individual user choice rather than collective responsibility.
Inferences
Content emphasizes rights over corresponding duties in community context.
-0.10
Article 11Presumption of Innocence
Medium Framing
Editorial
-0.10
SETL
-0.10
Post uses strong pejorative language ('sabotage,' 'hostile') to characterize Google's decisions without presenting their perspective or stated rationale.
FW Ratio: 60%
Observable Facts
Post describes Manifest v3 and JPEG XL changes as 'sabotage' rather than technical/business decisions.
Post does not include Google's stated justifications or defense of these policy choices.
The characterization relies on interpretive framing rather than balanced presentation.
Inferences
One-sided criticism without counterargument may limit fair representation of the dispute.
Use of 'sabotage' presumes intent without acknowledging Google's perspective on the changes.
ND
Article 2Non-Discrimination
Content does not address non-discrimination.
ND
Article 4No Slavery
Not addressed.
ND
Article 5No Torture
Not addressed.
ND
Article 6Legal Personhood
Not addressed.
ND
Article 7Equality Before Law
Not addressed.
ND
Article 8Right to Remedy
Not addressed.
ND
Article 9No Arbitrary Detention
Not addressed.
ND
Article 10Fair Hearing
Not addressed.
ND
Article 13Freedom of Movement
Not addressed.
ND
Article 14Asylum
Not addressed.
ND
Article 15Nationality
Not addressed.
ND
Article 16Marriage & Family
Not addressed.
ND
Article 17Property
Not addressed.
ND
Article 22Social Security
Not addressed.
ND
Article 23Work & Equal Pay
Not addressed.
ND
Article 24Rest & Leisure
Not addressed.
ND
Article 25Standard of Living
Not addressed.
ND
Article 26Education
Not addressed.
ND
Article 28Social & International Order
Not addressed.
ND
Article 30No Destruction of Rights
Not addressed.
Structural Channel
What the site does
+0.30
Article 12Privacy
High Advocacy Framing
Structural
+0.30
Context Modifier
ND
SETL
+0.20
Mastodon.social operates without advertising or tracking, demonstrating structural commitment to user privacy and avoiding surveillance infrastructure.
+0.30
Article 19Freedom of Expression
High Advocacy Coverage
Structural
+0.30
Context Modifier
ND
SETL
+0.32
Mastodon.social is explicitly designed to support uncensored expression; no prior editorial review or content removal barriers.
+0.20
Article 18Freedom of Thought
High Advocacy Framing
Structural
+0.20
Context Modifier
ND
SETL
+0.17
Mastodon's open design and lack of algorithmic coercion supports freedom of thought and conscience.
+0.20
Article 20Assembly & Association
Medium Advocacy Coverage
Structural
+0.20
Context Modifier
ND
SETL
0.00
Mastodon enables peaceful assembly and association through public discourse threads and community participation.
+0.10
PreamblePreamble
Medium Advocacy
Structural
+0.10
Context Modifier
ND
SETL
0.00
Mastodon platform design respects user agency and dignity through open, non-extractive architecture.
+0.10
Article 1Freedom, Equality, Brotherhood
Medium Advocacy
Structural
+0.10
Context Modifier
ND
SETL
+0.14
Platform enables users to act as free agents with conscience through open expression and community participation.
+0.10
Article 21Political Participation
Medium Advocacy Coverage
Structural
+0.10
Context Modifier
ND
SETL
+0.14
Platform enables participation in public affairs through accessible discourse channels.
+0.10
Article 27Cultural Participation
Medium Advocacy Framing
Structural
+0.10
Context Modifier
ND
SETL
0.00
Mastodon itself is open-source, demonstrating structural commitment to intellectual freedom and cultural openness.
0.00
Article 3Life, Liberty, Security
Low Framing
Structural
0.00
Context Modifier
ND
SETL
+0.10
Neutral; platform structure does not directly engage with this provision.
0.00
Article 11Presumption of Innocence
Medium Framing
Structural
0.00
Context Modifier
ND
SETL
-0.10
Neutral; platform does not structure the response.
0.00
Article 29Duties to Community
Low
Structural
0.00
Context Modifier
ND
SETL
ND
Neutral; not directly addressed.
ND
Article 2Non-Discrimination
Not evaluated.
ND
Article 4No Slavery
Not evaluated.
ND
Article 5No Torture
Not evaluated.
ND
Article 6Legal Personhood
Not evaluated.
ND
Article 7Equality Before Law
Not evaluated.
ND
Article 8Right to Remedy
Not evaluated.
ND
Article 9No Arbitrary Detention
Not evaluated.
ND
Article 10Fair Hearing
Not evaluated.
ND
Article 13Freedom of Movement
Not evaluated.
ND
Article 14Asylum
Not evaluated.
ND
Article 15Nationality
Not evaluated.
ND
Article 16Marriage & Family
Not evaluated.
ND
Article 17Property
Not evaluated.
ND
Article 22Social Security
Not evaluated.
ND
Article 23Work & Equal Pay
Not evaluated.
ND
Article 24Rest & Leisure
Not evaluated.
ND
Article 25Standard of Living
Not evaluated.
ND
Article 26Education
Not evaluated.
ND
Article 28Social & International Order
Not evaluated.
ND
Article 30No Destruction of Rights
Not evaluated.
Supplementary Signals
How this content communicates, beyond directional lean. Learn more
Describes Manifest v3 and JPEG XL removal as 'sabotage' (used twice) and 'hostile moves' — characterizing technical policy decisions with inflammatory language presupposing malicious intent.
appeal to fear
Implies Chrome is dangerous to users and the web; frames Web Environment Integrity as a threat that 'would hurt the web' and users' ability to block ads/trackers.
bandwagon
Invites readers to 'share with your entourage' to convince others to switch browsers, suggesting peer pressure as a persuasion mechanism.
build 73de264+3rh4 · deployed 2026-02-28 13:33 UTC · evaluated 2026-02-28 13:36:03 UTC
Support HN HRCB
Each evaluation uses real API credits. HN HRCB runs on donations — no ads, no paywalls.
If you find it useful, please consider helping keep it running.