Here's a more real-world projection of the cost and server impact - The Bandwidth Cost of AI Crawlers: What Scraping Really Costs Publishers - https://aipaypercrawl.com/articles/ai-crawler-bandwidth-cost
3,189 karma · joined December 12, 2023
Here's a more real-world projection of the cost and server impact - The Bandwidth Cost of AI Crawlers: What Scraping Really Costs Publishers - https://aipaypercrawl.com/articles/ai-crawler-bandwidth-cost
Cloudflare, Google Captcha, HCaptcha etc. are all shitty technical solutions because, as we are all discovering, it comes at the cost of our privacy (i.e. our personal data may monetise these services) and / or our computing resource and time. If current copyright laws aren't sufficient to prevent this, we have to acknowledge the system is broken. The answer could be enhancing it with some kind of Digital Millennium Copyright Act (DMCA) -like laws, but in favour of the creators against BigTech or rogue actors.
- Web-scraping and copyright law - https://www.neudata.co/blog/web-scraping-and-copyright-law
- Why DMCA Claims Against Web Scrapers Face Long Odds - https://capstonedc.com/insights/why-dmca-claims-against-web-...
> Every step subtracts a degree of sender control. Some of it passes to the user, and that is a good thing: a person deciding what is allowed to interrupt them is the channel working as it should. The rest passes to the platform, and that is the part that should concern a sender, because the platform's judgment is opaque, unappealable, and increasingly made by a model rather than by a setting the user chose.
A platform has essentially two "clients" - the user and the developer. Without both, it wouldn't exist. And it is in the interest of both that the platform should have very limited arbitrary authority over them. Nobody can deny today that the platform owners today have too much power over their users and their developers, which makes it easy for them to commercially exploit them while undermining their rights. We need regulations and standards (for interoperability, which is one of the arguments being made) to counter this.
It reminds of my first experience using macOS, as a long time Windows user. The first few months on macOS was a totally frustrating and negative experience for me - "What the ...? why does the ENTER key not open files or folders? Why is it going to 'rename' mode? Why doesn't double-clicking the title bar on a window maximise the window? Why are some windows maximised and others take their own custom width? Why is the Maximise button making apps full screen!?" - and so on.
The point is that I had become so familiar with the Windows UI, that every other OS UI suddenly seemed alien - "This is not how a UI should work on an OS". (This was also the reason that I hated Ubuntu's DE, as it tried to imitate the macOS UI I was then unfamiliar with). Familiarity means when you face a new UI, you have to spend effort to re-learn your way of thinking around a UI, which can be a frustrating experience (especially as you grow older). That effort / stress also unconsciously creates a negative impression in your mind about the UI. Both Apple and Microsoft know this and that is why they deliberately make their UI distinct and different from each other - whether it is Windows vs macOS or Windows Phone vs ios. Recently someone (a non-geek) asked me if they should buy a Macbook as they had an iPhone too. As they were a Windows user, I warned them that the macOS UI would be frustrating and to try macOS before committing to it. They did, and ultimately decided against it and chose to stick to Windows (buying a Surface Tablet).
As a former graphic designer, and an experienced Photoshop user, I only considered GIMP as a replacement when Adobe decided to make it a subscription. And just as with Windows to macOS, re-learning to use the GIMP UI was a frustrating experience because I was always thinking of "this is how it is done in Photoshop". Once you let go of that "familiarity", and are willing to actually test if the "GIMP way" is maybe better, it becomes a less frustrating experience. (All that said, while I have got used to using the GIMP tools the GIMP way, the overall GIMP layout does have a cluttered feeling and I do recommend installing Photo GIMP - it won't really make GIMP a Photoshop clone, but it will make it more "familiar" and thus easier to "re-learn" how to use it).