Live data from Hacker News

Mozilla hit with takedown request for anti-paywall addons

github.com

1–10 of 405 posts

Re: Mozilla hit with takedown request for anti-paywall addons

#4

here we go -- gearing up to the decade of censorship 2020 and beyond . . . between this and the EU link sharing tax, I am beginning to wonder if the internet really is the last bastion to freedom of speech

Huh? This is a plugin that was removed from the plugin directories.

Re: Mozilla hit with takedown request for anti-paywall addons

#5
This breaks the social contract of the web. If you publish on the web (over HTTP) using HTML (with or without css+js) then you respect the concept of a User-Agent that renders the content on behalf of the user. If you wish to get around this then create another file format and protocol and application/plugin to do so — one that enforces the DRM for the owner. Don’t take agency away from User-Agent.

Re: Mozilla hit with takedown request for anti-paywall addons

#6

here we go -- gearing up to the decade of censorship 2020 and beyond . . . between this and the EU link sharing tax, I am beginning to wonder if the internet really is the last bastion to freedom of speech

Of course it isn't any different in that respect (control by state actors) than any other communication medium.

Expecting otherwise is odd.

Re: Mozilla hit with takedown request for anti-paywall addons

#7
post #4

here we go -- gearing up to the decade of censorship 2020 and beyond . . . between this and the EU link sharing tax, I am beginning to wonder if the internet really is the last bastion to freedom of speech

Huh? This is a plugin that was removed from the plugin directories.

Yeah, just like you would remove a website from a websites "directory" or better just not display a website that breaks the law or better block it at ISP level! Welcome great firewall! Who said this is censorship?

Re: Mozilla hit with takedown request for anti-paywall addons

#10

This breaks the social contract of the web. If you publish on the web (over HTTP) using HTML (with or without css+js) then you respect the concept of a User-Agent that renders the content on behalf of the user. If you wish to get around this then create another file format and protocol and application/plugin to do so — one that enforces the DRM for the owner. Don’t take agency away from User-Agent.

Would you make the same point for an extension that allows users to easily participate in DDOS attacks?

Edit: the link, for the willfully dense, is that some protocol specification does not imply its users’ acceptance of any and all (ab)uses possible. It’s completely different only in that you like one but not the other.

Post reply on HN