ydant

As a workaround, /btw will force it to answer based solely on context and isn't allowed tool calls

Interesting perspective.

Though, I'd argue it should be 18 years free by their math. They lump a subset of leisure activities into another category as if those are beyond your easy control.

Commuting, working, grooming, etc - sure, you could optimize those, but it's harder to deviate from the norm. But TV/video games? Doesn't seem like the same discussion.

This is a fun blast from the past. One of my first real programming experiences was working as a (the) programmer on a MUD and I remember learning about this technique somewhere (I think just reading about how forking worked) and then figuring out how to implement it on our MUD.

It felt absolutely magical to be able to hot deploy changes without kicking everyone off of the server - but felt even more magical to have gotten it to work.

The MUD community was a fun early introduction to open source. People (many of them probably "kids" like I was at the time) sharing various patches and features. It felt so cool to release something and have other people use it and provide feedback. Like the author says - at some point the MUD itself became a lot less interesting than the programming.

Redirects to Pixel watch for Android user agents.

That has the problem of opening up an attack where the attacker requests the sign-in link, the person receiving the link blindly clicks it, and the attacker now has access.

People blindly click links all the time. It would have a low success rate, but would be more than 0%.

I can't tell yet if I'll actually end up using this in practice, but it's pretty well implemented.

The memo is stored as another email in the "Memos" folder as a reply to the message being memoed, so the data will be backed up naturally by any email backup and does show up, in a sort-of-awkward way, in other non-Fastmail mail clients.

In the Fastmail client, the memo shows up, highlighted, in the message list before the normal message snippet, and at the top of the message when you edit the message.

Seems pretty well thought-out.

It's just an anecdote, but from my one-time experience the 90 days restriction isn't a hard restriction with TMobile. Service worked fine for 5 months for a family member abroad (in a single country) with no issues or messaging from TMobile about an overstay - although this was on a family plan with other phones in the US for the majority of that time.

I'll absolutely reference an issue number in a comment (with some context comments as well) in cases where it makes sense.

Sometimes you need to go back and read through a lot of context understanding why a block of code does what it does, and it's a lot more efficient for the rest of the time to have a quick reference to the full explanation rather than pages of comments giving that context.

Thanks for the hint about `--intent-to-add` / `-N`.

There's constantly new things to learn about git. I use `git add -p` extensively, but never thought to check for an option like that.

Re: T-Mobile - On United you can just set your laptop user agent to a mobile one and sign on with your phone number. Works fine for both the short period and full flight options.

Your "join" page is a little UX uncomfortable. Middle click doesn't work for the description or apply link (just loads the whole join page again), and the apply expands/embeds the greenhouse.io page (in a narrow column) instead of opening it in a new window.