I would expect that a llm based scraper is going to be better at parsing an email address from your instructions than some of the more inattentive people who's emails you might want to receive. So I think some of the dumber mitigation measures that still block the simple regex bots from this topic are probably a better bet now.

I have a wildcard address at my domain. The most common email addresses for spam are:

- git@mydomain.com

Presumably harvested from GitHub or gitlab

- contact@mydomain.com / admin@mydomain.com

Not actually an email address ever used, presumably people just guessing these exist from convention.

- <first name>@mydomain.com

I mean, if you know my name you can probably guess this but also this has been my primary email address for outbound email and so has ended up in marketing lists etc.

- ap@mydomain.com, finance@mydomain.com

This is a very recent trend but I've been getting emails to made up addresses like these ones quoting forged emails from myself (with various titles like CEO or CFO attached) claiming to authorize payments to other parties, usually backdated, and then asking that I process their invoice ASAP because look how long ago the CEO said it should be paid. I guess my website has ended up in some list of businesses despite being a personal site.

Ironically, the address that was in plain text in my HN profile for like 15 years gets very minimal spam.

I find articles like this a good counter to the idea that typical software used to be better in the past (usually with an appeal to an idea that people were “real programmers” in those days and anything other than C as used in the 90s is a modern extravagance)

AI can produce code that is about 70% as good as median quality code found on the internet.

I would not describe median quality C code as free from these issues

Neither does localstack to be fair.

I honestly think GitHub and AWS are the two biggest blockers to IPv6 left. Sure your public web servers might need IPv4 for a long while yet, but all these backend microservices and CI builds etc could all be v6 only, except they need to pull stuff from GitHub or certain AWS services.

It's particularly aggravating with AWS, since they charge for IPv4 addresses yet many of their services aren't IPv6 capable.

They do seem to be making progress on that: https://aws.amazon.com/new/?ams%23article-feed%23pattern-dat...

They've enabled v6 on an average of something like two services per week for the past year... but they have a lot of services.

It’s an announcement published for their followers and distributed through their own channels to those people. That it doesn’t make sense when detached from that context and put on HN to people with no knowledge of who they are seems very much irrelevant to the goals of writing the post?

I mean, I’m sure “Fortnite with infinite vbucks.apk” has a much worse malware rate than the play store, but I’m almost certain that fdroid has a lower malware rate than the play store and I honestly suspect even “random apks off github” might have a similar rate to the play store

Is that not appealing to those users _because_ its a subsidised flat rate? Like those users could go and swap to API pricing right now if they wanted to, but at API pricing they don’t want to

Right, but that just proves there's tons of pent-up demand waiting in the wings as token prices fall.

They’re literally calling dodgy boxes here by both the consumers and sellers. Look, make the case in court if you want, you might get off with a slap, and nobody’s rooting for the big bad corporation here either, but nobody is under any illusions that these are legal

Not necessarily. Any Android TV box would do, doesn't need to be a dodgy one.

Not that I would ever do such a thing, of course.