One of the issues I had with HackerNews was that the front page was dominated by articles from major publications that imo were often written by journalists out of their depth. I think having a filter by domain feature would help users avoid certain publications that they know they won't enjoy reading.

While browsing through the Tildes documentation, I stumbled across this in the Technical Goals section:

Tildes is a website. Your phone already has an app for using it—it's your browser.

Tildes will have a full-featured API, so I definitely don't want to discourage mobile apps overall, but the primary interface for using the site on mobile should remain as the website. That means that mobile users will get access to updates at exactly the same time as desktop ones, and full functionality should always be available on both.

This got me thinking. Despite Tildes preferring mobile browsers over an app, is there still a chance for one? I usually avoid using websites on mobile unless I must, as mobile websites generally don't have the full functionality of the website. Labelling comments 'Exemplary' and 'Malice' on mobile is an example of what doesn't work (there's more), and it's usually very unresponsive for some of the things that still do work. Also, there aren't any notifications on mobile websites and some people, me included, have cumbersome browsers that make the feel of using the website slow and laborious.

Another thing is, if the app has no chance of happening, could Tildes get desktop notifications? I usually like to respond to replies to my topics and comments as quickly as possible and I'm not a fan of the whole 'constant login to check my notifications' thing. Email notifications aren't possible because of Tildes' privacy belief.

I've read a few novels, I think an excellent short novel is Elevation by Stephen King. It's not what you'd expect from a Stephen King novel (no horror elements), but it's a great read. I can't say too much without spoiling it, but here's the blurb:

The latest from legendary master storyteller Stephen King, a riveting, extraordinarily eerie, and moving story about a man whose mysterious affliction brings a small town together—a timely, upbeat tale about finding common ground despite deep-rooted differences.

It starts off a little slow, but give it a little bit of time. It's readable in an afternoon, I think I spent 5 or so hours reading it.

I was telling someone about a psychology book I'm reading at the moment. Intending to read it themselves they messaged me later to ask for the title. And I felt a bit unsettled at sharing it!

Whilst it's interesting and I'm enjoying it, I doubt I'll remember its lessons or claims in a year or two. Which got me thinking about books that I read years ago which still help me understand the world.

So I thought I'd make a post asking which books other users still found helpful year(s) later.

tldr; share books that are:

• Non-fiction (or at least serious fiction).
• First read over a year ago.
• Have been helpful to you multiple times since.

It's somewhat of an unspoken rule on Reddit that replying to a comment that's more than a day old is a faux pas. The conversation naturally settles within that period – or, less often, within two days. After that, the only appropriate thing is to either reference the conversation, or quote parts of the comments in relation to a similar issue in another post.

On Hubski, conversations could go on for days. It's explicitly stated in the guidelines that it's completely okay to reply to a comment of any age. I've never seen a year-old "revival" do any good, but the fact that it isn't prohibited or frowned upon adds no burden to the user.

How does Tildes handle this? Is there an unwritten rule already? Should there be a written one? What would be the factors?

Today's Feb 13. I've found a post from Feb 2 that was on a subject of interest of mine, where comments were insightful, but I feel like not all questions that need to be asked have been. Surely I won't go about creating another topic just to revive the conversation against only my own commentary to show for it.

There's also the matter of important, (semi)official topics on Tildes. Suppose a new issue arises that concerns an earlier public discussion held, say, half a year ago. It's a minor issue, but one that requires a discussion to settle. Does one comment on the old official topic, or does one create a new topic for this purpose?

One of the people in an IRC channel I frequent pointed out a site I've been building uses CDNs that are IPv4 only. I never realized this, I just assumed every major provider had deployed IPv6. Oh, how very wrong I was. A quick check of some major (to me) sites shows a shocking lack of IPv6, including:

• Bootstrap (stackpath.bootstrapcdn.com)
• Discord
• FontAwesome (use.fontawesome.com)
• GitHub/GitHub pages
• GitLab/GitLab pages (self-hosted supports IPv6, but officially hosted GitLab only supports IPv4 due to Azure limitations)
• jQuery, IF you use code.jquery.com (some tutorials use ajax.googleapis.com, which does have IPv6, but an unfortunate amount use code.jquery.com, including the getting started page for Bootstrap)
• Parts of Amazon/AWS (Amazon is IPv4 only, some of AWS is IPv4 only, including S3)
• Reddit
• Stack Overflow/Exchange/etc
• Twitter

An honorable mention goes to Angular's websites because the websites themselves are IPv4 only but the libraries are hosted on ajax.googleapis.com, which is IPv6 accessible. I checked npm, PyPI, RubyGems, and Tildes, and they all support IPv6.

I can understand why companies like Amazon have partial support (upgrading can be a PITA if you're a cloud service provider with uptime requirements), but then you have services like Discord (launched in 2015 with no obligation to maintain service) that only support IPv4. At the very least, I'd expect CDNs referenced by thousands (if not millions) of webpages to be on IPv6 by now.

Am I missing something? CDNs are pretty static, it's just a matter of choosing one that supports IPv6, you don't even need to update your application if you just change the DNS entries.