the link under recent posts here https://verdagon.dev/home 404s, as it links to https://verdagon.dev/blog/valen-memory-safety instead of https://verdagon.dev/blog/valen-group-borrowing . Interstingly this shows the page is hosted on Firebase, which is a bit unexpected for a static blog

Should be fixed now, thanks!

> they just don't need the data anymore.

Thats the wording of GDPR.. that you should delete data after you dont need it anymore for the original purpose..

Unfortunately, it seems noone is enforcing it enough.

What approach did you take with AI to make it discover an edge? Give the AI autonomy to search for edges itself and build e.g. a backtest it can use to confirm, or narrow it done with research (possibly AI) and then investigate specific approaches with AI? Or in other words, how autonomous was the AI in finding that edge?

AI couldn't really find any edges large enough to be worthwhile risk- and tax-adjusted. It's mostly me thinking of edge ideas that aren't on the internet and AI testing the hypotheses, building and battle-testing the infra, building risk models, implementing risk controls, monitoring it 24/7 for out-of-distribution behavior with several circuit breakers, etc.

going on a bit of a tangent here - some discussion there seems to be imply that AI bots mostly use IPv4s, which makes sense to me given that they are probably bots hosted by some cloud. Whereas IPv6 may be more organic traffic from e.g. mobile users (not in this case probably)... which made me think if at some point IPv6 may at some point win against IPv4 just because its more organic traffic (i.e. not from big tech cloud), leading to pages blocking IPv4? Just speculation on my side

The hardest-to-mitigate bot traffic tends to come from residential proxies, and most residential connections are still v4-only.

However, it is also easy to get large numbers of v6 addresses cheaply.

My residential ISP doesn't support IPv6 at all. If a site is ipv6 only, I can't reach it unless I use a VPN.

This is weird, every VPS I've rented in the last 8 years had IPv6, and some didn't even had IPv4.

If a problematic bot is on any mainstream VPS it will just get shut down.

How would I shut down a bot on Digital Ocean making over a million requests a day?

Send an email to the Digitalocean abuse email with the time ranges and origin IPs.

I did this with OVH, never got any response.

abuse@ contacts never send responses (though some send acknowledgements) because they don't want to give any details about their abuse process.

I also enjoyed it. Something about the writing really made me enjoy it, it was so different from the llm text i read all day long