Screw that.
Ad blocking is under attack
361–370 of 598 posts
Re: Ad blocking is under attack
#362Earlier quoted context omitted.
Which results every single time in choosing option C: the browser back button.
I always enable ads on a URL if it asks me to (provided they don't over advertise/have spammy advertisements), kind of already feel shitty about what is effectively stealing content for free so those notices just make me conscious of the guilt. I wonder how others rationalize blocking ads and not subscribing either but still feeling entitled to access the content.
If you put something on the web, and you want me to pay for it, put up a paywall. If you want to instead serve ads, don't expect me to read them (or load them, even). My bandwidth, my decision.
Re: Ad blocking is under attack
#363Github should have protected easylist from this bullshit DMCA request, here it is on github : https://github.com/github/dmca/blob/ff44d37f62d772bfec5fd432... Github is the culprit here.
Why should Github take on unlimited liability for someone else's code? If a judge agrees that blocking this anti-circumvention technology is illegal (something the DMCA does prohibit), and Github had refused to take it down (which means they don't get safe harbor), then Github is the first-party that is liable for distributing that illegal technology, probably many millions of times. When you start taking statutory f…
This is what should have happened:
1. Github is served with a DMCA Takedown notice
2. Github validates that the notice is valid
3. Github takes down the $FILE or $REPO
4. Owner of the Repo contacts Github
5. Github notifies the owner of the repo that it was a DMCA takedown
6. Owner of the repo provides Github with the Counter-notice.
7. Github restores access to the taken down $FILE or $REPO
At this point the party issuing takedown must sue the owner of the repo. It cannot go after Github. It also cannot take down the content again using DMCA to github.Re: Ad blocking is under attack
#364Re: Ad blocking is under attack
#365Re: Ad blocking is under attack
#366Just encode the list of urls with htmlentities, base64, rot13, whatever. Then the DMCA can't be used to attack it. Edit: Disagree? Please comment. It's attackable via the DMCA because the word/brand is in the file in it's copyrighted form. If you encode it such that it isn't in that form, it's protected from that approach.
which is the ASCII _encoding_ of the forbidden string.
Just because these bits are an EBCDIC cp500 encoding of that string doesn't make it less forbidden than an ASCII encoding:
0b100001100b101001000b100101010b100000110b101000110b100010010b100101100b100101010b100000010b100100110b100000110b100100110b100000010b100101000b10010110b100000110b100101100b10010100
Here's how I made both.. shows reasonably (IMO) that encoding is.. nothing.
> ''.join(bin(c) for c in 'functionalclam.com'.encode('ascii'))
> # vs this:
> ''.join(bin(c) for c in 'functionalclam.com'.encode('cp500'))Re: Ad blocking is under attack
#367Does github offer the ability to host repositories in other legal jurisdictions than the US?
Re: Ad blocking is under attack
#368Does github offer the ability to host repositories in other legal jurisdictions than the US?
Re: Ad blocking is under attack
#369Does github offer the ability to host repositories in other legal jurisdictions than the US?
Re: Ad blocking is under attack
#370Earlier quoted context omitted.
It's their fault for delivering data they want restricted. I'm under no obligation to make every HTTP request they want me to or execute any untrusted JavaScript. Nor am I obligated to render their HTML as intended. If they want these things then they need every user to enter onto a binding contract agreeing to those terms.
This argument really gets old. Morally you know what you're doing. Most people would be fine blocking the big dozen or so of the most offensive ad networks but this extreme approach (especially when the publisher is trying to offer you choices) just comes off as ridiculous.