horsebridge

> "We should crack down on industrial-scale distillation operations" I'd prefer if there was a crack down on industrial-scale scraping. Maybe even reimbursement for the problems it has caused (some nasty AWS bills, tons of man-hours spent on preventing new nasty AWS bills, etc).

With such a wide set of goals, this won't go far. They are limiting themselves to people that agree with all of that.

Stock images only have okay pricing (per image) if you use some sort of decently sized subscription. Anyone that only needs a few images are unfortunately screwed.

Got any suggestions for this situation (invasion of Ukraine)?

Anybody running a site with data that is useful for AI will learn how horrible bytedance is.

I don't really have any problem with ROCm these days, although I only use system packages. It used to be quite wonky though, and I've totally given up on custom ROCm installs.

I'm part of a smaller shop. GCP didn't even bother responding to us when we tried to contact sales, which is why we're at AWS.

I don't really agree about that "frobnicate" deal. If you messed up when you added a parameter to "frobnicate", you'll get "Hi, you broke frobnicate, please fix it. It's causing issues.".

You break it, you fix it, including the troubleshooting.

Well, it has been an Incredible Journey.

https://ourincrediblejourney.tumblr.com/

Lists like these would be better with some more explanations for the less obvious bullet points. For instance, when/why would an email have multiple From addresses?

Was it this [1] program?

[1] https://archive.org/details/thegpa