What I really dread is having to use something like the Postgres mailing list, which is painful with conversations split between multiple pages and block quote formatted so it takes mental effort to even figure out what's the previous message and what's the reply. I'm not familiar with gmane and am young enough not to have been a heavy newsgroup user.
You think it takes mental effort to read proper quotes, e.g. in https://www.postgresql.org/message-id/CANP8%2BjKvbe2jwOzUMGo...?
That's proper quoting style. It's incredibly readable, much more than the top-posting scourge we must deal with on so many mailing lists.
Partially offtopic. The very page at http://home.gmane.org/2016/08/29/next-steps-gmane/ is much better with JS turned off: JS loads the Raleway font which at the given size and color (#666) is too thin and not contrasted enough to be readable. I have to zoom in many times before it gets OK. The default Arial is much easier on the eyes. Raleway is not that bad on my tablet, maybe because of a higher DPI (8.4" at about 2500x1600 vs 15" at 1920x1080) or because it's AMOLED. Not bad but not good enough. Arial wins even there. With a color of #222 or darker Raleway starts the be readable, but still worse than Arial.
The current one definitely suffers from the second system effect. I also avoid it and actively search for other locations with the same content.
Maybe I'm nostalgic but I really miss the newsgroups that focused on just the messages, and could be consumed by any client, stored offline, searched, etc.
I don't see anything nostalgic about that, there's value in the benefits you list and rightfully associate to application-layer protocols.
A few months ago I stumbled upon a good article that praised them too, over today's "HTTP for everything", but I'm sadly unable to find it in my bookmarks. Anyway; more than anything, it lauded the interoperability that comes with those protocols.
I'm sending email from Thunderbird, and can reply minutes later from my iPad, and follow-up/search my archive at work from Outlook or Mail.app. Transmission merrily talks to uTorrent or Deluge or rTorrent. My windows box reads video files from a Samba share.
What now? Apps interfaces are at worst totally obscure (Skype), or at best exchange readable but undocumented JSON/XML over HTTP(S). Put differently: had email been designed & implemented today, we would hardly enjoy the same interoperability. There seems to be little interest around designing new protocols (and maybe little help coming from languages/libraries too?). IRC v3 ( http://ircv3.net/ ) comes to mind, but it's pretty niche. Anyway, I'm ranting. Can anyone complement from experience trying to do such protocol design/implementation today and the challenges associated with it?
Not enough people make new running-on-TCP or running-on-UDP protocols because new protocols are hard to design, they don't work with the one application where everyone spends 70+% of their time (the web browser), and they probably get blocked on a middlebox except if you use port 80 or 443 and fake being HTTP anyway. For all but very specialized use-cases, vomiting blobs of JSON (or if you want to feel extra good, some custom binary serialization format like protobuf or Thrift or Cap'nProto or MessagePack) across HTTP endpoints is pretty okay.
QUIC is a secure transport protocol (subsuming most of the features of TCP and TLS) that runs on top of UDP (because they wanted to craft a 'better' TCP, and the only other not-blocked-by-default transport protocol is UDP).
Since Google pushed it into Android Chrome, I cannot log-in into our customers WLAN infrastructure on Android 4.3 only with 4.4+ devices, not even by disabling it via the flags menu.
And some of our devices are on 4.3 and now need to make use of HSDA for network access.
All of them are slower and less usable than navigating the messages via Thunderbird, or similar client.
What directors? I couldn't figure out from the post who Martin Danko is or who he works for.
The company I work of is actually owned by a series of individual holding companies, each one hold some percentage of the shares in the operating company. The holding companies mainly exists to protect the owners from bankruptcy.
And thanks again to Lars for his years of service.
It's also an archive of the above. This archive functionality is in common with Google Groups.
See the 'About' page .
> As part of the agreement, we have received the INN spool with all the articles but none of the code that drives the site.
https://github.com/larsmagne/reticule for the NNTP gateway,
gwene (in perl) for the rss parts.
I don't have a problem with self-promotion, but if you're more interested in supporting Gmane than in promoting Baqqer, it shouldn't really matter if the donation is via Baqqer, Gratipay, Patreon, a Bitcoin address, or even just a PayPal donation link.
Just a member of the HN community trying to help out how I can. :)
Edit: According to your resume you've been a contributor to Gratipay.