@clacke@evan Whee! I was one of the first people on identi.ca, and had a habit of sniping the post IDs with round numbers. I ended up getting most of them, but it looks like 10,000,000 was the only which survived on archive.org.
If you're making a video and you say "without further ado", you probably already have too much ado, and you should have reduced the amount of ado in your video to begin with.
@malwaretech "We won't give you a description of what you want to know because we wouldn't put what you want to know in the description anyway" is certainly a take.
"Uhh Ryan, aren't those french fried onions? And aren't you allergic to onions?"
It's a big "it's complicated", but basically french fried onions are one of the few exceptions where it's safe to eat and I actually will eat. (Putting onion powder in dishes is the other exception.)
My family cookbook is painfully 1980s, but oh my is this hot dog quiche so awesome. And OMFG FOOD HACK, that crust is actually a tube of crescent roll dough.
@ryanc I swear, literally everyone (including myself) have their own "came across Dan Kaminsky by chance, we hit it off and decided to do this cool project together" story.
Also, I'm pretty sure I remember 2004 specifically, just from the year alone: Alexis Park, in the tent, he did voice-over-negative-TTL-DNS?
@cwebber The original social media training set was taken from a single day of Twitter's tweets, back when Twitter was small enough you could go to them and ask "hey, can I have all your tweets, for science?" and they were like "sure, here you go!"
That day happened to be Canada Day, so he talked about it a lot in the early days.
@cwebber My favorite part was he had buffer overflow issues which were never fully resolved, so if his brain got too large, the responses would slowly start mutating from lovable wacky hijinx to literal gibberish. The solution was to kill the brain and re-train him.
Hi, my name's Ryan and I'm a cybersecurity consultant with Mars Corp. I'm sure you've seen today's massive supply chain breach, and I'd just like mention that had the maintainer been supplied with a Snickers bar from us, they would have had the energy to resist the social engineering attack and
@lnxw37a2 The assistance aspect didn't seem to slow down the overall experience for me, but yeah, the 1 or 2 employees always seemed to be helping people, so if you happened to need help yourself, it was often a small wait.
This may be lessened here in California because CA does not allow for alcohol purchases in self-checkout (which is moderately stupid), so the employees aren't doing ID check lockout overrides for people buying beer.
Checkout at the Walmart in town used to be great. There was a corral of 15 self checkout stations, manned by one or two employees. There was usually a line, but it always moved fast because it was nearly impossible for individual slow customers to slow it down for everyone.
This was far too convenient and efficient, so naturally they replaced it with multiple lines of 4 stations, each manned by one employee. (1/3)
If you do Kubernetes work and don't yet know about the management program `k9s` (curses GUI), it's an eye-opener. Kubernetes has been a primary part of my job for a few years, but I would hate finding/doing things with `kubectl`.
I learned about `k9s` back in September and it was a "where have you been all my life" moment. It's good for doing the occasional manual task, but even better for visualizing the state of a cluster at a human level.