This will be a hugely unpopular thing, however...
The premise of attaching a nominal cost to a previously free service in order to combat abuse is exactly what I did with the @haveibeenpwned API keys 4 years ago: https://t.co/rMXWlTF9Fk
This stopped abuse dead. Not a little bit, not mostly, but 100%. The reason wasn't that there was no longer an ROI for abusers, rather it was because you had to stump up a credit card that could be traced back to you. Combine that with Stripe doing a very good job of identifying fraudulent use of cards (our dispute rate is 0.01% for the last 6 months) and it's now very unattractive to do nasty stuff with the service.
Clearly, they're not going to make any money out of a $1 annual fee (and for now, that's only new users in 2 countries anyway). I've no doubt based on my own experiences that it'll put a massive dent in abuse originating from those markets, I'm just not sure how much it will piss off their user base. Or how much it will matter.
@mitsuhiko It would be nice if https://t.co/UcxjIbcsJf could force authors to follow semver more diligently. Or at least show them some warning about violations. I am tired of seeing crates that bring breaking changes on minor version update.
@simonw@random_walker@MParakhin@langchain
We've just updated our paper on (indirect) prompt injection. At least 50%+ more content, including real-world demonstrations and way more threats. Check it out on Arxiv:
https://t.co/x1UclXE565
@TwistyCB@twone2 Thanks! It seems I wasn't attentive enough :)
Also tried to find different parts of the picture in google/yandex/bing, but just missed the right match. Now I see it.
@bayer_julia@quiztime Given the fact that picture contains 60+ round pieces in horizontal lines, I think this is rather that Beverly Hills clothing store, because the facade of Berlin store doesn't contain 60 pieces horizontally in any of its parts https://t.co/1Dx0XuTOta