spiffytech / Brian Cottingham

I got sized at a jeweler. Are your sizes different from that?

Definitely!

The solution I've heard:

On the email form, include a hidden password input. Password managers will fill it. After confirming the user needs a password login, show the prefilled field. User only needs one trip to the password manager.

Every time I play / skip tracks when I find a new album.

I swear it's not on purpose!

Excited to see the new built-ins! I think the JS ecosystem will be better off for getting a solid standard library.

There exist clients who will demand the entire website for their dog grooming service be wrapped in <sensitive> so no one can copy it 🙁

Or companies will lock down internal comms to keep employees from building papertrails.

My gut reaction is it'll see more abuse than legit use until its removed.

No, I don't think I have.

They're a useful idea since they're foundational for building data structures (but I don't do much of that either), and it's useful to have the notion of "this record can point to another record, in a chain even".

But I too feel like they're overemphasized in CS classes.

Most of the time I use Shazam, it's to identify an artist I want to avoid hearing ever again.

An episode of the Spacetrawler comic, featuring a sci-fi bathroom full of appliances who are eager to help a man relieve himself.

Spacetrawler

I am indescribably delighted to see a Look Around You reference in the wild.

It's a fantastic show. I regularly want to quote "Write that down", or "Thanks, foo. Thfoo.", but sadly no one in my life would understand.

Today I have several layers of protection against this specific risk:

- I use tmux locally, which clearly labels SSH sessions
- I install a shell prompt on every server which includes the hostname
- I install molly-guard, which makes me type out the hostname before a shutdown will go through.

I typed 'shutdown' into an SSH session instead of a local shell.

This took down the 200+ websites we hosted for our agency clients.

Back in 2006, recovery meant filing a support ticket for a Rackspace employee to go push the power button on our server while I sat around feeling anxious.

Overall I'm quite happy with how it went. The bsky integration was relatively easy, and felt like it was built to do exactly what I was trying to do.

I also went a step further and automatically synced my bsky follows <-> RSS reader subscriptions, rather than having to manually add RSS feeds for people I want to follow.

I was able to skip caching because bsky gives me everything I need in a single feed query per author, so I can't get any more efficient while serving fresh data.

bsky has a firehose I could have used to detect new content, but for now I just refetch when I get a request from my RSS reader.

Except for how there's no official way to turn a post ID into a link to the bsky website, and the maintainers think that's kind of a philosophically invalid ask in the first place, so you have to chop up the at:// URI string. Feels hacky.

One you know what kind of record you're holding, the data structures are straightforward and intuitive. The data needs minimal postprocessing.

This makes common things things a little clunky to use, but that's the only big negative I had with the API. Otherwise it was a smooth experience.

Strangely, the lib includes TypeScript type definitions, but values aren't type-annotated. You have to already know a value's type and cast it. Then you get types for all of its immediate properties. Except for child properties whose types can vary, which you (again) have to know & cast.

My bsky -> RSS project seems to be all set. Took about 2 evenings of work to build it and iron out all the kinks.
I'll give their API a B+. I did everything with just four API calls: log in, get follows, get author profile, get author feed. Very easy, especially with the official Node.js library.

Made it into bsky thanks to a generous invite from @madeofmistake.bsky.social!