This is ultimately just going to give them training material for how to avoid this crap. They'll have to up their game to get good code. The arms race just took another step, and if you're spending money creating or hosting this kind of content, it's not going to make up for the money you're losing by your other content getting scraped. The bottom has always been threatening to fall out of the ads paid for eyeballs, And nobody could anticipate the trigger for the downfall. Looks like we found it.
> This is ultimately just going to give them training material for how to avoid this crap.
> The arms race just took another step, and if you're spending money creating or hosting this kind of content, it's not going to make up for the money you're losing by your other content getting scraped.
So we should all just do nothing and accept the inevitable?
The README.md specifically states how to allow for nice robots to proceed unhindered. The people behind these efforts, I would imagine, don't particularly care about their sites' reputations in the cases people use LLMs for search.
The small non-profit I volunteer with finds Google ads to be surprisingly effective, and much more cost-effective than FB for what they do, so there's at least some Google search usage in the demographic that they serve.
To be clear, I mean AI is going to be the downfall of ad supported content. But let's face it. We have link farms and spam factories as a result of the ad supported content market. I think this is going to eventually do justice for users because it puts a premium on content quality that someone will want to pay a direct licensing fee to scrape for your AI bots as opposed to tricking somebody into clicking on a link and looking at an impression for something they won't buy.
So, if at the end of the day instead of clicking EVERY single link in the repository they just check it out and parse locally...... I would consider it a win.
It's super expensive for them to run this hardware. And they need the compute for other things. Everyone who's cursed open AI for going down in the middle of the day whenever they're using it to write code or do some other thing, will breathe a little easier now that there's some compute available. Wise decision, in my opinion.
Some advice I follow, and give to others: Refuse notifications by default. Only enable them when you're getting paid to see them. (slack and work email, for example count as getting paid to see them)
My version of that is to ask yourself what this app could notify you about and decide based on that.
What could a game notify you about? Nothing, probably spam. Deny.
What could a social app notify you about? Interactions with your content and profile. These are useful, allow.
What could an instant messaging app notify you about? Messages, obviously. Allow.
What could a fast food establishment app notify your about? Probably your order status if you order from the app. But it might also spam you. Allow but be prepared to turn off categories that are spammy if spam does arrive.
The web is the enemy. I have an ad blocking VPN and I use GroundNews to filter out sites that have paywalls. Between those two things, I lead a relatively sane life. But I tried looking at some of the same places on an unflitered device and man, I can't even imagine living like that. It now costs me $100/year in ad blocking/circumvention just so I don't want to kill the browser.
Is the adblocking VPN doing anything some DNS block lists on your router or device wouldn’t do?
You can’t do MITM on HTTPS anyway, so I can’t imagine they would do anything more than a $20 Pi Zero and PiHole, except for the fact that somebody else is managing it.
I mused about the idea of a version of Hypercard where you could load cards from network resources, or even just stacks. Ultimately though it would have been an even bigger security nightmare than the original Javascript. Hypercard was developed long before security was even a consideration on consumer hardware. The only thing it had was 5 different access levels, from a view only mode to full developer support.
It's as much of a fantasy as the one where Apple released a version of Hypercard for Windows 3.1 and blew Qbasic out of the water. It's a real shame Apple just chucked one of the most interesting beginner programming environments in the trash just as so many new people were getting interested in programming.
HyperLook was inspired by HyperCard and implemented for the NeWS window system in PostScript, and supported networking. I used it to implement SimCity for Unix.
SimCity, Cellular Automata, and Happy Tool for HyperLook (nee HyperNeWS (nee GoodNeWS))
HyperLook was like HyperCard for NeWS, with PostScript graphics and scripting plus networking. Here are three unique and wacky examples that plug together to show what HyperNeWS was all about, and where we could go in the future!
I don't disagree, but neither does the article. It's just talking about the fact that we previously considered anything that can't be easily and tersely written down as nearly or entirely intractable. But, as we have seen, the three body problem is not really a hum-dinger as far as the universe goes, it's not even table stakes. We need to be able to do the same kind of energy arbitrage on n-body problems that we do on 2. And now we have the beginnings of a place to toy with more complicated ideas -- since these won't fit on a blackboard.
Problems with opaque stability boundaries that observe non-liner effects are always great. Chaos theory makes it even more fun as your observation can change the outcome.
reply