rtorrent with unbound to mitigate the UI hangs from DNS lookups (serve-expired = true). The rtorrent config file is extremely hacky and every time I have to muck with it I wonder it why a friendlier interface to libtorrent hasn't overtaken it. But it gets the job done.
I tried Transmission for a while, but it seemed to stall arbitrarily (maybe requiring restarting?) and I couldn't figure out what the problem was. I know it's a popular option, it just didn't work for me, in the time I wanted to spend on setting it up.
I was scratching my head trying to figure out what curl has to do with rtorrent. But now I'm realizing that it could indeed be using libcurl as torrents use HTTP every place they use DNS.
But still I like to run a recursive resolver locally (rather than using a well known public resolver), and part of the problem is that I was getting SERVFAIL responses due to bits of the lookup getting dropped or taking too long (high latency VPN). So unbound fixes that, for rtorrent as well as other software running on the same machine. But maybe next time I visit that aspect of my setup, I'll look into making a Nix derivation for rtorrent with c-ares.
Oh interesting! I'm subscribed to my replies via hnreplies.com, and your replies come through as just `* * *`, and I could swear I've seen it on the actual site before. Like maybe people were reserving their reply slot or something.
Ah, that must be hnreplies behavior. I've never seen that on HN itself.
It could have something to do with me having delay=5 in my profile settings? (This setting makes it so it takes 5 minutes for a comment to show up publicly, in case one wants to reconsider)
FYI, that feature makes the comment completely invisible on pages where it would otherwise show up in the basic HN web interface (no asterisks or anything). But it appears that if I go to the URL comment directly from a non-logged-in browser, it does show the three asterisks. So it looks like hnstatus becomes aware of the new comment (probably just enumerating IDs?), and can see its parent but but can't read the content.
(I edited this comment based on investigation I did while this comment was in its delay period)