pushcx

Yeah. And if it's not all passwords under the account, the email should've had a list of the affected ones. Instead Dreamhost says both that they've already deleted the at risk passwords, and also that customers need to reset all passwords. Maybe when they mean "reset all" they meant "reset all [the deleted] passwords", but being so unclear about scope and remediation steps is a painful mistake.

A single sentence like, "If a password wasn't reset as of (timestamp), we don't believe it could have been at risk." would go a long way to fixing these incident comms, if that's the case.

No kudos earned. They didn't ban him, they just didn't invite him to give a keynote. Then Ruby Central put him back on stage for a RailsConf keynote q&a. It was the snowball that started rolling an ongoing avalanche of secondary crises.

Many years ago, I arrived to my half-height cubicle at a Fortune 100 company to see that my desktop PC case was ajar. I set the CRT aside, opened it, and realized that the RAM had been removed. My neighbor explained what must have happened: another employee must have needed to double their RAM from 8 to 16 MB. Requisitioning an upgrade was a weeks-long bureaucratic process that required approval by one's manager and IT, perhaps prompting a review of per-team resource allocation. Repairing a broken PC was a trivial help desk ticket; my PC was restored in an hour or two.

It wasn't obviously wrong in 2001. .pro started with a similar structure around the same time.

Having an "AI tells" linter to catch "Phrasing that reads as machine-generated rather than my voice" has a real echo of "What does God need with a starship?".

I run a site about programming that's constantly hit by people writing their first scrapers, etc. I checked the last ~10 million lines of http logs and see no instances of this. Anthropic doesn't really respect robots.txt so it's all over the logs, but not with an email address or in the form given in this github issue. This is just an odd thing you got an LLM to spit out.

The web app typically sees 10 rps and most of those don't write.

I timed it a few times.

This isn't elaborated on in the piece, but it does mention that it's written in the context of the Fermi paradox. Adding 50,000 years of technological development and a 1,000 year rebooting phase at each star system doesn't meaningfully change how long it would take life to spread when considered against the 13,500,000,000 years since stars developed.

Or it's a distinction without a difference to the site owner. Ever prod service I've run has seen significantly more abuse from human users using alias services, especially protonmail. I'm not surprised that some owners have chosen to block it entirely, given their resources, but I'd prefer to see it used as a signal in a more sophisticated system if possible.

I had wanted the same thing for a long time and jj + difftastic has satisfied me.

It's not intentional on this author's part, but this is a great example of how Google rewards people posting slop. The oldest posts on the blog read normally, the new stuff this post says it added to satisfy Google all reads like this post.