Post 9hdMfRhKjefUpLWGaO by gcupc@catgirl.science
 (DIR) More posts by gcupc@catgirl.science
 (DIR) Post #9hdMfRhKjefUpLWGaO by gcupc@catgirl.science
       2019-04-09T13:18:16.034660Z
       
       1 likes, 1 repeats
       
       Here’s a thing I wrote on SSB in answer to a question about why I was more excited about #gopher currently than #ssb.Okay…it seems to me that both the SSB community and the Gopher community see problems with the way the web has gone, and are addressing different problems in different ways.For Gopher, the Original Sin is complexity, especially the way the web has turned into a platform for running JavaScript applications, but also the way it’s impossible, for example, to write a browser engine from scratch given how much there is to support. The new gopher community is writing blogs and textfiles and just getting stuff out there. To the extent stuff is commented on and shared, it’s using other protocols. Partly on the web (esp. the fediverse), but also on NNTP (!). But there are links between phlogs and some interaction goes on that way.For SSB, the Original Sin is centralization, so everyone gets to own their own data instead of it being owned by Big Data. But SSB is enormously complex. A Gopher hole is a directory tree of text files served by a server that’s simple enough that you could roll your own in shell script in an afternoon. An SSB feed is… a cryptographic append-only log of messages shared over a gossip protocol implemented in node.js? And I’m also just not feeling the community, which is a lot more YMMV and subjective.Honestly, I’m kind of excited about #NNTP lately, too.