News for hackers. Stuff that matters.
Re:We Must Revive Gopherspace (2017) by icebraining on Saturday February 16, 2019 @11:19AM (#19179276)
HTML ain't the problem; you can build websites without tracking. If you somehow managed to pull enough users to Gopher, they'd just write Gopher Chrome and start adding new features that conveniently allow tracking into it, and gradually kill off the original protocol (see EEE). The problem is economic, and the solution must be too.
Re:We Must Revive Gopherspace (2017) by rixrax on Saturday February 16, 2019 @01:31PM (#19180095)
I’m old enough to have used gopher on vt100 terminals as an undergrad in college to try and do some ‘work’. And when http/www arrived, it didn’t take long to switch to a better mousetrap. And this wasn’t just because you could now render a gif in NCSA Mosaic on indigo workstation. Everything was just better in this new http world.

Let’s fast forward to today, yes, we’ve gone overboard all over, but then again, Gopher [i think] doesn’t come standard with TLS, it hasn’t gone through the evolution that http[s] has that makes it a robust and scalable backbone it is today.

What I’m trying to say is that we should not casually float around pipe dreams about switching to ancient tech that wasn’t that good to begin with. Yes, electric cars were a thing already in early 1900s, and we maybe took a wrong turn with combustion engine, but with Gopher, I think we should let the sleeping dogs lie, and focus on improving next version of QUIC, or even inventing something entirely new that would address many of the concerns in the article without sacrificing years of innovation since we abandoned Gopher. Heck, this new thing might as well run on TCP/70, never mind UDP appears to be the thing now[0].

[0] https://en.m.wikipedia.org/wiki/HTTP/3

Re:We Must Revive Gopherspace (2017) by ethbro on Saturday February 16, 2019 @03:15PM (#19180692)
Well said. The article conflates a content / rendering problem with a protocol solution.

A lightweight HTTP/TLS subset that severely limits client-side execution expectations would seem to accomplish the same goals.

While repurposing all the amazing tech we've built since the 1990s.

Essentially, "just pass me the bare minimum of response to make Firefox Reader View work."

... but then we wouldn't be able to serve high-value targeted ads, would we?

Re:We Must Revive Gopherspace (2017) by redahs on Saturday February 16, 2019 @03:36PM (#19180797)
If the desire is to make online content more readable, it might be worth starting with the assumption that all content downloaded from the network will be read on a black-and-white ereader device with no persistent internet connection.

This assumption might require substantially reworking the hyperlink model of the internet, so that external references to content delivered by third-parties is sharply distinguished from internal references to other pages within the same work.

Re:We Must Revive Gopherspace (2017) by ivan_ah on Saturday February 16, 2019 @10:27PM (#19182520)
Your idea of hypermedia with an offline browsing assumption is very good! Imagine an "offline archive" format that contains a document D + a pre-downloaded copy of all referred documents R1, R2, ..., Rn, along with necessary assets to render R1,R2..Rn in some useful manner (e.g. save html + main-narrative images from each page Ri, but skip everything else).

This "offline archive format" has numerous benefits: (A) Cognitive benefits of a limited/standard UI for information (e.g. "read on a black-and-white ereader device"), (B) Accessibility: standardizing on text would make life easier for people using screen readers, (C) Performance (since accessing everything on localhost), (D) async access (reaching the "edge" of the subgraph of the internet you have pre-downloaded on your localnet could be recorded and queued up for async retrieval by "opportunistic means", e.g., next time you connect to free wifi somewhere you retrieve the content and resolve those queued "HTTP promises", (E) cognitive benefits of staying on task when doing research (read the actual paper you wanted to read, instead of getting lost reading the references, and the references's references).

I'm not sure what "standard" for offline media (A) would should target... Do we allow video or not? On the one hand video has great usefulness as communication medium on the other it's very passive medium, often associated with entertainment rather than information. Hard choice if you ask me.

I'm sure such "pre-fetched HTTP" exists already of some sort, no? Or is it just not that useful if you only have "one hop" in the graph? How hard would it be to crawl/scrape 2 hops? 3 hops? I think we could have pretty good offline internet experience with a few hops. For me personally, I think async interactions with the internet limited to 3 hops would improve my focus—I'm thinking of hckrnews crawled + 3 hops of web content linked, a clone of any github repo encountered (if <10MB), and maybe doi links resolved to actual paper from sci-hub. Having access to this would be 80%+ of the daily "internet value" delivered for me, and more importantly allow me to cutoff from the useless information like news and youtube entertainment.

update: found WARC https://en.wikipedia.org/wiki/Web_ARChive http://archive-access.sourceforge.net/warc/warc_file_format-...

Re:We Must Revive Gopherspace (2017) by ethbro on Sunday February 17, 2019 @03:11PM (#19186547)
The issue is this thrashes caching at both the local and network levels, decreases overall hit rate, and doesn't scale as links-per-page increase.

How many links from any given page are ever taken? And is it worth network capacity and storage to cache any given one?

Re:We Must Revive Gopherspace (2017) by dredmorbius on Saturday February 16, 2019 @11:24PM (#19182667)
What if the Web was filesystem accessible?

https://old.reddit.com/r/dredmorbius/comments/6bgowu/what_if...

Re:We Must Revive Gopherspace (2017) by xj9 on Sunday February 17, 2019 @01:29AM (#19182986)
Re:We Must Revive Gopherspace (2017) by dredmorbius on Sunday February 17, 2019 @03:15AM (#19183302)
FYI, that's noted in the article:

Plan 9 OS and the 9P protocol

I'm carving out a subsection for this, as the concept appears to contain a number of the elements (though not all of them) mentioned above. See Wikpedia's 9P (protocol) entry for more:

In particular, 9P supports Plan 9 applications through file servers:

acme: a text editor/development environment

rio: the Plan 9 windowing system

plumber: interprocess communication

ftpfs: an FTP client which presents the files and directories on a remote FTP server in the local namespace

wikifs: a wiki editing tool which presents a remote wiki as files in the local namespace

webfs: a file server that retrieves data from URLs and presents the contents and details of responses as files in the local namespace

https://old.reddit.com/r/dredmorbius/comments/6bgowu/what_if...

Re:We Must Revive Gopherspace (2017) by codetrotter on Saturday February 16, 2019 @10:09PM (#19182464)
> Essentially, "just pass me the bare minimum of response to make Firefox Reader View work."

I wish it was possible to use a html meta tag to declare to the user-agent that it should show the content in reader view.

Then sites that only want to provide text and images and no ads etc could be implemented without any CSS at all and minimal amounts of markup and still be nice and readable on all devices thanks to user-agent reader view taking care of the presentation.

Re:We Must Revive Gopherspace (2017) by Technetium_Hat on Saturday February 16, 2019 @10:37PM (#19182543)
So you're really wishing that we had sensible default css, instead of the terrible user agent styles that we are forced to keep for compatibility.
Re:We Must Revive Gopherspace (2017) by codetrotter on Saturday February 16, 2019 @11:07PM (#19182631)
No, because that is not realistic for the exact reason you mention — that would break a lot of sites. Probably the vast majority even.

And I don’t see any real benefit in changing the defaults either. Most sites want to provide custom CSS. The point of reader view is to make simple articles consisting of text and images comfortable to read on your specific device. Device/resolution specific defaults would be at least as painful, and probably more painful, to override for every site that wants to use custom CSS.

Whereas an explicit meta tag telling the user-agent to use reader view is entirely feasible. Such a meta tag does not interfere with existing pages, requires nothing extra from sites that don’t want it, and would still fall back to something that works for all end-users whose user-agents don’t implement it (because browsers ignore meta tags they don’t understand so those browsers would render the page in the exact same way they would any unstyled page). And on top of that this theoretical meta tag would be really easy for browser vendors to implement — they parse the HTML, see the meta tag and trigger the reader view mode that they have already implemented.

Re:We Must Revive Gopherspace (2017) by redwall_hp on Sunday February 17, 2019 @12:33AM (#19182835)
The solution is to stop respecting the style tag and enforce sane defaults that the user has control over. The Web was meant to be a means of creating academic documents with fancy citations in a tree structure, not a glossy magazine delivery mechanism.
Re:We Must Revive Gopherspace (2017) by ancarda on Sunday February 17, 2019 @07:56AM (#19184236)
>just pass me the bare minimum of response to make Firefox Reader View work.

Couldn't an HTTP proxy work here? Something you run on localhost that fetches web pages, stripping them of trackers, adverts, and other undesirable stuff? Perhaps with enough development, it could even selectively strip CSS and JavaScript -- eg. it would be really nice if websites stopped shipping scrollbar hijacking / custom scrollbar code.

Re:We Must Revive Gopherspace (2017) by jancsika on Saturday February 16, 2019 @03:53PM (#19180874)
> Essentially, "just pass me the bare minimum of response to make Firefox Reader View work."

What would that constraint look like? Is animation and interaction prohibited there, for example?

Re:We Must Revive Gopherspace (2017) by ethbro on Saturday February 16, 2019 @04:11PM (#19180967)
I think the one-sentence summary would be "Content without code, and a bare minimum of formatting."

The lesson from the modern web being, if you give web developers a toolbox, they'll figure out how to build a surveillance system.

And for decades we've been creating more powerful tools (Flash/ActionScript, ActiveX, JavaScript, Wasm, etc).

The answer would seem to be that we should be far more careful what tools we allow to be used.

(Note: Not saying restrict all the web this way, but if one wanted to build parent article's wikipedia-esque info web)

Re:We Must Revive Gopherspace (2017) by pharke on Saturday February 16, 2019 @09:40PM (#19182354)
I don't think the issue is the tools available but the motivation behind their use. Until we get rid of the ad revenue model we'll be stuck with user profiling and tracking. Micropayments or some other model will have to take it's place before we see a return to the ideals we used to aspire to.
Re:We Must Revive Gopherspace (2017) by coldtea on Saturday February 16, 2019 @05:20PM (#19181310)
I'd prohibit interaction aside from clicking on links to get to the next page. As for animation, only embedded videos.

If we allow all those, it's just the modern web again.

Re:We Must Revive Gopherspace (2017) by Wowfunhappy on Saturday February 16, 2019 @05:44PM (#19181416)
If there's support for embedded assets (you mention videos, so I assume also images, etc), how do you prevent "tracking pixels" that can monitor what content is viewed per IP address?

I think it's generally useful to look at email here, where only a small subset of html—primarily photos + text—are reliably supported across clients.

Re:We Must Revive Gopherspace (2017) by coldtea on Saturday February 16, 2019 @05:56PM (#19181466)
>how do you prevent "tracking pixels" that can monitor what content is viewed per IP address?

No third party connections allowed. As for the originating server, they already know you requested the page, no?

Re:We Must Revive Gopherspace (2017) by kd5bjo on Sunday February 17, 2019 @06:11AM (#19183864)
Content addressing can help here. If every asset is identified by a cryptographic hash, the user agent is free to fetch it from any available source. In the case of images, you can hash over the rendered pixels instead of the file encoding, so all transparent 1x1 images are concise red interchangeable.

Alternatively/in addition, the user agent can treat embedded assets like textbooks do, and present them all as numbered, boxed, and captioned figures.

Re:We Must Revive Gopherspace (2017) by meruru on Saturday February 16, 2019 @05:06PM (#19181231)
If there was a way for me as a web developer to tell browsers "render this page in reader view" I would definitely use it.
Re:We Must Revive Gopherspace (2017) by crooked-v on Saturday February 16, 2019 @05:10PM (#19181260)
Just use plain output and a little bit of CSS. http://bettermotherfuckingwebsite.com
Re:We Must Revive Gopherspace (2017) by u801e on Saturday February 16, 2019 @07:58PM (#19181957)
> Black on white? How often do you see that kind of contrast in real life? Tone it down a bit

I never understood why people have a problem with normal contrast. Low contrast is hard to read.

Re:We Must Revive Gopherspace (2017) by dredmorbius on Saturday February 16, 2019 @11:26PM (#19182673)
Re:We Must Revive Gopherspace (2017) by crooked-v on Saturday February 16, 2019 @09:35PM (#19182330)
#444 on white is hardly "low contrast".
Re:We Must Revive Gopherspace (2017) by meruru on Saturday February 16, 2019 @11:30PM (#19182679)
That doesn't use the user's preferred font/line/column size and background color.
Re:We Must Revive Gopherspace (2017) by marcus_holmes on Saturday February 16, 2019 @10:43PM (#19182561)
There's a subset of crusty techies like us who would like this.

The vast teeming hordes of Kardashian fans and youtube addicts would not. They like where we are now.

Re:We Must Revive Gopherspace (2017) by samstave on Saturday February 16, 2019 @06:28PM (#19181616)
>render a gif in NCSA Mosaic on indigo workstation

You know what I would love to see is a comparison chart for all Historic SGI machines, and their MSRP from their heyday to comparable compute capabilities in modern devices.

I remember when we were moving ILM/Lucas to the Presidio - and they were throwing our massive SGI machines, which were hundreds of thousands at the time - but some of them were turned into kegerators...

Re:We Must Revive Gopherspace (2017) by chrisfinne on Saturday February 16, 2019 @11:03PM (#19182615)
I recall those times too, however I switched back to gopher because the web was click-click-crash if you were running windows or on the college unix workstations, it was click-click-hang.
Re:We Must Revive Gopherspace (2017) by bunderbunder on Saturday February 16, 2019 @12:10PM (#19179569)
Moving to another protocol, like Gopher, seems like an economic solution to me.

A parallel protocol and hypermedia format that's restricted enough to prevent tracking isn't going to attract everyone. It's going to attract the subset of users who care enough about stuff privacy to give up "rich Web" features like single page applications and animated HTML canvas elements in return.

That's not a group that's likely to start immediately demanding to to build in the features needed to create infiniscrolling Pinterest feeds. And it's also going to be a much restricted group, meaning businesses won't stand to profit much by pushing for it. So there might not be any economic incentive to do it.

At least, that's how it might be at first. If it remains a nice place to be for 5 years, I'd call it a decent run. 10, and I'd be ecstatic.

Re:We Must Revive Gopherspace (2017) by hopler on Saturday February 16, 2019 @01:09PM (#19179952)
Why not just put up a web page or forum without the features you hate? Build a search engine for non-JS pages or whatever Why do you need gopher?
Re:We Must Revive Gopherspace (2017) by EamonnMR on Saturday February 16, 2019 @04:38PM (#19181100)
Someone already did:

http://wiby.me

Re:We Must Revive Gopherspace (2017) by hedora on Saturday February 16, 2019 @01:35PM (#19180131)
You need the user agent and transpory layer to enforce privacy protections.

The modern web cannot do that.

(I’m not convinced gopher can either — I think NNTP was actually better at that — but like the thought experiment.)

Re:We Must Revive Gopherspace (2017) by arminiusreturns on Saturday February 16, 2019 @02:56PM (#19180604)
Usenet is still going strong! It's weird the looks I get from "techies" when I tell them I still use irc, usenet, and rss... and it's shameful.
Re:We Must Revive Gopherspace (2017) by dvfjsdhgfv on Saturday February 16, 2019 @03:53PM (#19180872)
Ironically, on HN you got the local equivalent in the form of downvotes.
Re:We Must Revive Gopherspace (2017) by Top5a on Sunday February 17, 2019 @05:59AM (#19183825)
The downvote/bury mechanic makes HN just as poor as SN or Reddit. If one must implement downvotes, at least provide tally, such as on Ars, rather than the default silly text fading (which one should disable).
Re:We Must Revive Gopherspace (2017) by tammer on Saturday February 16, 2019 @12:43PM (#19179772)
Precisely. This is leveraging the “network effect” that has thus far mostly been a tool of corporate profit for mass benefit.

I yearn for a future where knowledge is distributed in a practical, organizied way such as via Gopher or similar, along with tapping the full potential of email as a one-to-many, many-to-many, and many-to-one communications medium where data is distributed and address ownership is maintained.

Re:We Must Revive Gopherspace (2017) by krapp on Saturday February 16, 2019 @02:22PM (#19180422)
>I yearn for a future where knowledge is distributed in a practical, organizied way such as via Gopher or similar, along with tapping the full potential of email as a one-to-many, many-to-many, and many-to-one communications medium where data is distributed and address ownership is maintained.

We already have that, it's called the World Wide Web.

You seem to be under the impression that the popularity of the web is due to centralization by and commercialization by corporate interests, but that isn't the case. It's still entirely feasible to distribute knowledge in a "practical, organized way" using HTML and HTTP, and people do use it for things besides the three social media sites people now mistakenly believe comprise the entire web.

Re:We Must Revive Gopherspace (2017) by adrianratnapala on Saturday February 16, 2019 @08:37PM (#19182089)
I started using the Internet at a time when HTTP traffic already exceeded Gopher+FTP traffic, but not by orders of magnitude.

I'd start nearly any session with Gopher, and it would end in either some web pages or an FTP server. Gopher was the go-to because it was organised unlike the rat's nest of links you had to deal with on the web.

This wasn't really fixed until the advent of big centralised search engines (and even then, the early ones weren't worth damn).

Re:We Must Revive Gopherspace (2017) by daxfohl on Saturday February 16, 2019 @05:07PM (#19181239)
Even the internet as a whole isn't the problem. Corporations can share your data just as easily if it's from a paper form that you gave to them. It's not going to be long until cameras, drones, microphones everywhere are spying on everybody.

It'd be nice to have a quieter place like old gopher, but yeah the real increase in privacy it would bring is somewhat illusory.

Re:We Must Revive Gopherspace (2017) by petra on Saturday February 16, 2019 @11:57AM (#19179514)
Say we've built the system of economic incentives for privacy(opt-in). And managed to convince 10% of users and 50% of site owners to convert. Extremely hard.

What do users get in the end ? half of the web is still tracking them. And many of the big guys still track them.

Not enough if you ask me. That's what makes it so difficult.

So let's solve that: let's build a search engine that let me filter sites according to privacy, Ah and be perceived as good as google - because in today's world, in many jobs, you cannot give up on an information advantage.

That's kind of an impossible mission.

Re:We Must Revive Gopherspace (2017) by m-p-3 on Saturday February 16, 2019 @02:26PM (#19180449)
DuckDuckGo should implement that, or at least put a privacy indicator.
Re:We Must Revive Gopherspace (2017) by mattkevan on Saturday February 16, 2019 @06:29PM (#19181619)
They do. Their browser plugin grades sites both on the number of tracking scripts and the quality of their privacy policy.

https://duck.co/help/desktop/adding-duckduckgo-to-your-brows...

Re:We Must Revive Gopherspace (2017) by dragonwriter on Sunday February 17, 2019 @12:31PM (#19185600)
> HTML ain't the problem;

Gopher is an alternative to HTTP, not HTML. HTML can be used with gopher, and since documents served via gopher can be accessed by URLs, it's hypermedia features are usable over gopher. (But gopher is read only, unlike HTTP, so even with JS—since even though it uses URLs, HTML’s built-in form behavior presupposes HTTP and it's verbs—to do a gopher call for a form you'd only get the equivalent of GET forms.)

In principal at least; other than Lynx and an extension for Firefox, I don't think any current browser has support for Gopher, anyway.

> If you somehow managed to pull enough users to Gopher, they'd just write Gopher Chrome and start adding new features that conveniently allow tracking into it

You can do IP based tracking on any TCP/IP protocol, and if the clients have JS (or other scripting, but if you make it alternate channel for HTML, JS is the obvious choice) support and aren't a monoculture, and have differences detectable with JS, you can do client fingerprinting on top of that. Yes, even with gopher protocol alone, as long as your server can treat certain crafted requests specially.

Re:We Must Revive Gopherspace (2017) by lazyjones on Saturday February 16, 2019 @01:08PM (#19179935)
> The problem is economic, and the solution must be too.

Alright, let's talk to our representatives and ask them to consider taxing tracking and data collection.

Re:We Must Revive Gopherspace (2017) by jrmg on Saturday February 16, 2019 @01:17PM (#19180004)
Re:We Must Revive Gopherspace (2017) by TeMPOraL on Saturday February 16, 2019 @01:20PM (#19180025)
That's totally true.

But then again, the harm of advertising and surveillance capitalism is a thing. So is the focus on data hoarding, vendor lock-in, favoring prettiness over utility.

I really wish we could run a parallel web. One optimized for utility, where data and content is available in maximally useful form, where users are in control of their rendering, and are free to use whatever automation they want. Not a replacement web, just a for people who are willing to jump through some hoops in order to avoid the crap that's on the mainsteram one.

I don't know much about Gopher yet (I'm starting to learn now), but maybe such a parallel web could be developed there?

Re:We Must Revive Gopherspace (2017) by ForHackernews on Saturday February 16, 2019 @03:33PM (#19180784)
Gopher might be amenable to that. It's a much more limited protocol, and AFAIK doesn't allow inline images or any server-defined styling.
Re:We Must Revive Gopherspace (2017) by classichasclass on Saturday February 16, 2019 @04:49PM (#19181155)
Well, let's be explicit here. The wire protocol doesn't care (you can serve HTML documents from a gopher server with inline content), but gopher menus indeed don't allow those sorts of features.
Re:We Must Revive Gopherspace (2017) by icebraining on Saturday February 16, 2019 @03:30PM (#19180764)
Freenet is kind of that parallel web - decentralized, very hard to surveil, mostly made of simple HTML documents and pictures.

And nobody uses it.

Re:We Must Revive Gopherspace (2017) by ForHackernews on Monday February 18, 2019 @06:23AM (#19189980)
How is Freenet different from Tor?
Re:We Must Revive Gopherspace (2017) by icebraining on Monday February 18, 2019 @08:32AM (#19190479)
Tor follows the traditional client/server model, it just uses a few connection layers to attempt to make it harder for the server (or any listener, of course) to identify the origin of the connection. That means someone must be running that server, which means it's possible to shut it down and punish the operators, and those operators can in turn identify the clients by any means except those directly prevented by the layering model.

Freenet is a distributed content-addressed store, much like IPFS, except that rather than you directly fetching content from other users who have specifically "pinned" that content (outing you both as interested in the material), the request hops over multiple users, leaving it cached (in an encrypted form, for plausible deniability) over their machines, so that it's very hard to tell who actually requested it.

Re:We Must Revive Gopherspace (2017) by pvarangot on Sunday February 17, 2019 @12:31AM (#19182827)
Using technology to kickstart the discussion about the economical solution is not a bad idea. It would be nice to have a neutral place to discuss technology and it's slowly stopping to be a thing.
Re:We Must Revive Gopherspace (2017) by helij on Saturday February 16, 2019 @11:56AM (#19179510)
Indeed[1] You always have a choice!

[1] https://artlists.org/privacy-policy/

Re:We Must Revive Gopherspace (2017) by jrnichols on Sunday February 17, 2019 @08:19PM (#19188018)
just like RSS. text feeds weren't the problem - advertisers declaring it "stealing content" and trying to force advertisements everywhere are the problem.

usenet was also great until spam went nuts.

Re:We Must Revive Gopherspace (2017) by kleer001 on Saturday February 16, 2019 @02:26PM (#19180455)
Pay people to use Gopher? Maybe state funded.
Re:We Must Revive Gopherspace (2017) by joering2 on Saturday February 16, 2019 @12:27PM (#19179686)
> The problem is economic, and the solution must be too.

FB for example is US-based company. Last time I checked you are not forced to accept outside money, get VC rounds or go IPO.

Mark chosen to go the "American path" that is capitalism to the maximum so of course I will lose an argument over why he is trying to maximize profits. But nothing stopped him from building sponsorship agreements with i.e. fortune 500 corps, instead of building bidding platform ala Google.

I'm pretty sure if you would signup fortune 500 and have for example 500 rotating banners, it would give you enough founds to run operations and pay every employee $150,000 salary. Plus having exactly ZERO tracking cookies and ZERO malicious following you JS script. Its quite possible given FB size and reach, but again "this is America, this is business."