Tim Aksu retweeted
Impressive preemptive defense here from @Railway noted in their incident write-up.
Folks should be less harsh and more appreciative of good work like this in these times - the eMudhra situation by comparison shows the consequence of total negligence, but Railway had >98% safe.
Tim Aksu retweeted
The preliminary report related to the October 21st Security Incident is now available.
blog.railway.com/p/prelimina…
It’s more of a signal of how badly shit has hit the fan that they need to do this. Think of how crazy it would be if Google was like “yeah you might see Steve log into your account while we fix this but, don’t worry!” Haha
Tim Aksu retweeted
An urgent notice from the Railway team
blog.railway.com/p/security-…
I’m finding it hard to stop the LLM from meddling with engine or framework level code it might have access to to side step quirks/bugs/issues in user land code
The web demos both hang on “Starting the engine…”, may want to investigate as this was my first real impression of the project and it’s just broken!
Tim Aksu retweeted
Ever since I got into gaming in the early 90's I've dreamed of one very specific game. I searched high and low, but the idea was simply too complex, too original. Surely no developer could ever conceive of it...
Thanks, Unity. At last I can make a corridor shooter set in space.
Tim Aksu retweeted
nobody talks about the psychological damage of watching something you spent 10 years learning become a prompt
Tim Aksu retweeted
Here's part 2 of my mini-series on memory management. It looks specifically at memory paging, linear allocators, and how different layouts of the same data can significantly effect physical use.
youtu.be/7mYWbTgEGb8
