Notices

1. Tsundoku Psychohazard (enkiv2@eldritch.cafe)'s status on Tuesday, 16-Apr-2019 17:28:20 CEST Tsundoku Psychohazard

   Pondering what's inbetween Gopher and the web gopher://zaibatsu.circumlunar.space:70/0/~solderpunk/phlog/pondering-whats-inbetween-gopher-and-the-web.txt

   • Ekaitz Zárraga 👹 repeated this.
   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Wednesday, 17-Apr-2019 11:02:10 CEST Ekaitz Zárraga 👹

     in reply to

     @enkiv2 I thought about a similar thing few time ago. When I was working on a personal project called Cicoria I understood the blog-oriented web as a subset of HTML-like documents. In my case I chose Markdown for the PoC because there are implementations of it.
     This kind of markups are easy to read in raw (and easy to render richly if you want) and they reduce the traffic needed drastically.
     I also designed a catalog based site style and then I was introduced to gopher and its menus and wtf?

   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Wednesday, 17-Apr-2019 11:02:19 CEST Ekaitz Zárraga 👹

     in reply to

     @enkiv2 It was all invented.

   • Ekaitz Zárraga 👹 (ekaitz_zarraga@mastodon.social)'s status on Wednesday, 17-Apr-2019 11:30:49 CEST Ekaitz Zárraga 👹

     in reply to

     @enkiv2 To be fair with myself, my idea was to implement different ways to get the documents, not only like Gopher menus where there's only one hostname-selector-port triplet, I was thinking on a protocol-id pair per protocol implemented.
     That'd make the client choose the protocol it prefers.

     The only thing I needed to solve is the spread of the catalog itself. :)