The pay-per-crawl thing, is about them thinking ahead about post-AI business/revenue models.
The way AI happened, it removed a big chunk of revenue from news companies, blogs, etc. Because lots of people go to AI instead of reaching the actual 3rd party website.
AI currently gets the content for free from the 3rd party websites, but they have revenue from their users.
So Cloudflare is proposing that AI companies should be paying for their crawling. Cloudflare's solution would give the lost revenue back where it belongs, just through a different mechanism.
The ugly side of the story is that this was already an existing solution, and open source, called L402.org.
Cloudflare wants to be the first to take a piece of the pie, but also instead of using the open source version, they forked it internally and published it as their own service, which is cloudflare specific.
To be completely fair, the l402 requires you to solve the payment mechanism itself, which for Cloudflare is easy because they already deal with payments.
comment about the linked blog post: he replaced Proton Drive with Synology, which is kinda cheating (comparing apples to apple trees). Also he did not include a cloud drive in his pricing calculations, which is also cheating...
Anyway, for anyone actually looking for good cloud drive hosting, without any BS: rsync.net (you encrypt on your side before sending anything. I use Vorta with them).
Also the same server can be used by multiple (trursted) users, like family members etc.
or the complete opposite. Very skilled people with a lot of experience in a specific project. I am like that too at my current job. I've REALLY tried to use AI but it has always slowed me down in the end. AI is only speeding me up in very specific and isolated things, tangent to the main product development.
exactly... people happily use software from Nazis (not that DHH is one) without knowing. The only difference is that DHH openly writes about his opinions (its called free speech).
Good luck to anyone wanting only ideologically compatible software. They'll end up with pretty much nothing left to use.
Same applies to companies that produce goods. It's a never ending hole.
At some point, every person who says the words "free" and "speech" consecutively (especially in such a smarmy, snotty way), needs to understand that it's not a shield from criticism nor an obligation to continued association. I'm really tired of hearing about the concept from people who don't, evidently, understand what it actually means but just want to use it as an "you have to accept me and what I say no matter what" bludgeon.
I also got ChatGPT vibes... all this repetition of "why it matters" and all the lists, and going back and forth between contradictions...
It's even sadder to me that the author says this is not GPT. I believe them. Which means we have reached a point where the style of how ChatGPT writes has made its way into our sub-conscious...
but we do... 4 years after Rust, we got a first glimpse at Zig. Even today, there's a lot of people that believe that Zig would have been a better choice for the Linux kernel than Rust.
And the answer to "why now" is quite simple - Because of the whole Rust in kernel debate, people started scrutinizing the situation.
Then Zig people should be the focus of “this kids and their new shiny” criticism, not Rust.
People who become aware of something only when it’s being used by something huge also aren’t early adopters either. Rust has already been in the Windows kernel for years at this point, with none of this consternation.
I think you're misunderstanding the purpose of hateoas.
If we jump down to the bolts and nuts, let's say on a json API, it's about including extra attributes/fields in your json response that contain links and information of how to continue. These attributes have to be blended with your other real attributes.
For example if you just created a resource with a POST endpoint, you can include a link to GET the freshly created resource ("_fetch"), a link to delete it ("_delete"), a link to list all resources of the same collection ("_list"), etc...
Then the client application is supposed to automatically discover the API's functionality. In case of a UI, it's supposed to automatically discover the API's functionality and build a presentation layer on the fly, which the user can see and use. From our example above, the UI codebase would never have a "delete" resource button, it would have a generic button which would be created and placed on the UI based on the _delete field coming back from the API
The pay-per-crawl thing, is about them thinking ahead about post-AI business/revenue models.
The way AI happened, it removed a big chunk of revenue from news companies, blogs, etc. Because lots of people go to AI instead of reaching the actual 3rd party website.
AI currently gets the content for free from the 3rd party websites, but they have revenue from their users.
So Cloudflare is proposing that AI companies should be paying for their crawling. Cloudflare's solution would give the lost revenue back where it belongs, just through a different mechanism.
The ugly side of the story is that this was already an existing solution, and open source, called L402.org.
Cloudflare wants to be the first to take a piece of the pie, but also instead of using the open source version, they forked it internally and published it as their own service, which is cloudflare specific.
To be completely fair, the l402 requires you to solve the payment mechanism itself, which for Cloudflare is easy because they already deal with payments.
reply