{"thread":{"id":"44700","subject":"some updates for public-inbox readers","startedAt":"2016-12-14T08:00:31Z","lastAt":"2016-12-14T08:00:31Z","messageCount":1,"participants":["Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"307739","messageId":"20161214075903.GA22774@dcvr","threadId":"44700","inReplyTo":null,"subject":"some updates for public-inbox readers","fromName":"Eric Wong","fromEmail":"e@80x24.org","sentAt":"2016-12-14T07:59:03Z","receivedAt":"2016-12-14T08:00:31Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"First, bad news:\n\nThere's been some hardware problems the past week or so and a\nfew minutes of scattered downtime and high latency as a result.\nHopefully no lost messages, as SMTP should retry.\n\nGetting things migrated to different hardware in a few\nminutes, so maybe the new hardware will have fewer gremlins\n(but we could always end up with more gremlins...)\n\nTo encourage independently-run mirrors and decentralization:\nI will never guarantee the continued availability of any\nservice I run.\n\n\nThe (maybe) good news:\n\nI'm probably a day or so away from deploying RFC 4685 support\nfor threading the Atom feeds at\nhttp://hjrcffqmbrq6wope.onion/git/new.atom\nhttp://czquwvybam4bgbro.onion/git/new.atom\nhttps://public-inbox.org/git/new.atom\n\nThe implementation is here:\nhttp://hjrcffqmbrq6wope.onion/meta/20161213023330.6104-1-e@80x24.org/\nhttp://czquwvybam4bgbro.onion/meta/20161213023330.6104-1-e@80x24.org/\nhttps://public-inbox.org/meta/20161213023330.6104-1-e@80x24.org/\n\nBut I'm not sure if there's any widely-used feed readers capable\nof doing proper threading like a good mail/news client can, yet.\nPerhaps this will be a step to get feed reader authors\nto implement threading support (and find bugs in my generator!).\n\nI don't believe this feature will break existing feed readers;\nat least not the command-line ones I've tried.  But maybe it\ndoes and I'll have to put threading in a different endpoint\n(that would hurt cache hit rates :<)\n\n\nI'll also increase the size of the feed from the measly 25\nentries to something more at some point....  Hopefully it won't\ncause somebody's feed reader to fall over when the feed grows; but\n25 entries is not enough for higher-traffic lists, and a recent\nchange means buffering big feeds for slow clients is now bounded\nto one message (instead of potentially using all space):\nhttp://hjrcffqmbrq6wope.onion/meta/20161203015045.9398-1-e@80x24.org/\nhttp://czquwvybam4bgbro.onion/meta/20161203015045.9398-1-e@80x24.org/\nhttps://public-inbox.org/meta/20161203015045.9398-1-e@80x24.org/\n\n\nAnyways, if you always want to be up-to-date; don't feel bad\nabout hammering the Atom feed every few seconds, or even running\n\"git fetch\" every minute.  The servers can handle it; and we'll\nfind out if they don't!\n\nAnd of course you can also clone the code:\n\n\tgit clone http://hjrcffqmbrq6wope.onion/public-inbox\n\tgit clone https://public-inbox.org/\n\nand run everything yourself off your list subscription\n(Maybe it's near time to do a proper release;\n I guess the project is 10% \"complete\" at this point)\n\nTor hidden service mirrors remain on different (better) hardware\nand networks, and have historically higher reliability:\n\n        http://czquwvybam4bgbro.onion/git/\n        http://hjrcffqmbrq6wope.onion/git/\n        nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git\n        nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git\n\nBut it's winter and storms are coming...\n"}]}