News for hackers. Stuff that matters.
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.