disconnection

I already moved my big customers off Railway after an earlier incident this year that leaked customer data. It’s a stunningly horrible situation to not be able to cycle environment variables after such an event. I did an emergency migration to fly.io today with minimal disruption today. I’d recommend everyone to immediately migrate somewhere else ASAP so you can change environment variables. And of course never give Railway a cent more of your money.

I don't know all the details of how this was done. But I think the big advance is that LLMs can now allow people to decompile binaries who don't know what "clean-room reverse engineering" means.

IMO either it was decompiled (a tedious but not complex task to do by hand, now automated) and illegal, or properly clean-roomed and buggy slop.

If it was me doing this, I'd anonymously dump the source onto a torrent, not parade around the media.

Still waiting on a reply and the logs so I can do forensics on this incident. IMO the response from Railway should have been: "all hands on deck, red alert, worst imaginable security breach for a PaaS". Not a small yellow alert popup about a CDN misconfiguration, and saying that all affected customers have been emailed, which is demonstrably not correct.

Good that he worked it out so quick. I recently spent a day debugging email problems on Railway PaaS, because they silently closed an SMTP port without telling anyone.

I have a hierarchy of templates, where I can automatically swap out parts of the prompt based on which LLM I am using. And also have a set of benchmarking tests to compare relative performance. I treat LLMs like a commodity and keep switching between them to compare performance.

Lol, don't care; I run my own models locally .

Yup - SwiftUI is pretty immature still, so I use the latest iOS17 to get the latest features to make development simpler. For example, handling in-app purchases is hugely easier in iOS17.

oops, high-pass filter.