= 27d567bc2d48d9f40e9ccc20ea370b15)
buybuydandavis comments on Turning the Technical Crank - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (134)
I've often griped about how the web X.0 is still miles behind usenet readers and even mailing list software of the 90s for forum discussions.
I saw some talk about the problem of requiring installation of an NNTP client.
Are there no reasonably sized javascript libraries that can be loaded as an in browser nntp client?
As for the Diaspora, couldn't we just link/insert the blog posts of diaspora authors and discuss?
In-browser javascript can't open TCP connections, so it can't talk to real NNTP servers. It can only use websockets, aka tcp-over-http.
If you also happen to be running an HTTP server, you can use a websocket-to-tcp bridge like websockify.
Why exactly do you want an in-browser nntp client?
A number of comments expressed that getting people to install nntp clients was probably a non-starter. A browser client is all you're going to get.
A javascript client seemed like a solution to that.
It is a non-starter, but there are ways to get the equivalent of a client in a web browser without using javascript to do it.
So what's the best solution you have for the problem?