271–280 of 439 posts
Earlier quoted context omitted.
Wasn't there news about police officers playing music in order for videos of them triggering automated copyright/DMCA takedowns? https://www.vice.com/en/article/bvxb94/is-this-beverly-hills...
In reality it would only demonitize it for the uploader and they wouldnt get paid.
Bittorrent, switch in long-term to that. Not saying every end-user should be a seeder but there is big bittorrent community out there and everyone could help a little bit. Other options: - A kind of mirror network (it only needs to keep sure that integrity can be checked, maybe with a public key) - And while doing that why not also support compression (why not? only devs need to read it and they can run easily a deco…
Oh, but yes every user should be a seeder. Why not?
Earlier quoted context omitted.
In case anyone reading hasn't heard of it: SponsorBlock for YouTube - Skip Sponsorships - https://chrome.google.com/webstore/detail/sponsorblock-for-y...
Sponsorblock has saved me hundreds of hours from watching youtube ads and other time wasting bullshit. The devs deserve to be paid for making this awesome application.
Earlier quoted context omitted.
Is it? Seems superior to arbitrary magic numbers or headers, and God forbid full naive parsing, in most ways.
Whats wrong with storing and delivering the intended content type as metadata, whether thats headers or filesystem metadata like in Mac OS X?
At least file extension is limited and externally visible (and thus accountable) to third party behavior, which should limit the worst complexity excesses.
Is filesystem metadata actually different (theoretically) from extension? Or just data in a different format?
Extension seems a nice balance between simplicity / brevity and utility, albeit as a hint, not a commandment.
Earlier quoted context omitted.
Cloudflare caches robots.txt by default when proxied (the only .txt-file that they automatically cache), for all other content the following from their ToS probably applies: > Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited, unless purchased separately as part of a Paid Service or expressly allowed under our Supplemental Terms fo…
The TOS isn't that you can't serve plain text, it's that it shouldn't be disproportionate in volume to the cached html served.
Earlier quoted context omitted.
text/html is not text/plain but that doesn't matter: it's not a technical limitation that caused cloudflare to draw this line. it's cloudflare deciding to protect "web content" and not videos or .iso images or other things that normally are not commonly served while you browse a contemporary website and read HTML.
> it's cloudflare deciding to protect "web content" and not videos or .iso images or other things that normally are not commonly served while you browse a contemporary website and read HTML. That's false in two ways: first, text is normally served while you browse a contemporary website; second, so are images, which are explicitly called out as potentially violating this clause. Text is the only data that isn't cover…
Earlier quoted context omitted.
Actually you're missing the point. It doesn't seem like many people are condemning Cloudflare for not serving a bandwidth-heavy file for free (FTA: "CloudFlare does not allow non-enterprise users use that much traffic"). Rather what's being condemned is this nonsense customer service characterization of a text file as somehow not "web content". Easylist.txt is a data file that could just as easily be in JSON (and be…
But it's not JSON or HTML. And it's not meant for browsers. It's clearly a dataset as a text file and not meant as "web(page) content". What's nonsense about that when it's completely accurate?
And there is no reason a web app couldn't read data from a txt file instead of a json file.
Earlier quoted context omitted.
Actually you're missing the point. It doesn't seem like many people are condemning Cloudflare for not serving a bandwidth-heavy file for free (FTA: "CloudFlare does not allow non-enterprise users use that much traffic"). Rather what's being condemned is this nonsense customer service characterization of a text file as somehow not "web content". Easylist.txt is a data file that could just as easily be in JSON (and be…
But it's not JSON or HTML. And it's not meant for browsers. It's clearly a dataset as a text file and not meant as "web(page) content". What's nonsense about that when it's completely accurate?
A great opportunity right now for CloudFlare to win some goodwill and PR by helping out EasyList for free right now. But what about simply enable a firewall and show captcha or similar if the origin IP is from India and requesting that URL until the situation is under control? I did that with the free plan recently in CloudFlare in a similar situation and it worked perfectly (of course on a much smaller scale).
I can't understand their argument that a text file 'isn't a web content'; seems like a bullshit excuse.