bboard hyperpithole gate
 (DIR) Menu
 (DIR) Section <GOPHER>
 (DIR) Forward
 (DIR) Backward
       Thread[.post]: 36.2
       TACKER:  yeti (yeti)
       SUBJECT: .. How you were using the Internet in the 90's?
       DATE:    23-Jan-22 22:04:14
       HOST:    sdf
       
       Browsers were not broken back then.  Using ftp: and gopher: URLs was 
       completely normal.  The early web neither had GIFs nor tables.  Complicated 
       layouts like tables needed to be hand set in <pre>...</pre>.  When GIF 
       krept in, we did already smell that this will be the beginning of the end.
       
       But <table> really made life easier.  \o/
       
       I think the small web should fight browsers being crippling more and more.  
       It won't take long and they will be single protocoll network enabled 
       pagers only.
       
       The browser was invented to be one frontend to many protocols.  Diversity 
       was builtin from the earliest days.  This has to return!
       
       
       Small web?
       
       Don't fight http/html.  Http is easy to implement, even an Arduino can do 
       this.  It may transprt more then just html pages.
       
       Fight for browsers that keep up diversity.  Elinks, Emacs, Dillo (easily 
       extendable) probably aren't the only candidates that are worth being 
       mentioned here.
       
       [ SCROLL (F)ORWARD, (B)ACKWARD - (Q)UIT ] FORWARD
       extendable) probably aren't the only candidates that are worth being 
       mentioned here.
       
       http://yeti.freeshell.org/tmp/20220122-194852__emacs_appetiser.png
       
       Fight big-$$$ browsers that now even kick out ftp: and you can bet, if not 
       seeing opposition, even http: will not live long any more.
       
       Gopher, Gemini, Spartan?  Make them visible.  I dislike Gemini because it 
       forces TLS over an incapable markup.  That doesn't fit well together and 
       serves a niche between gopher and http/html that IMO does not exist in the 
       first place.  Spartan is Gemini markup over a plaintext protocol.  I think 
       that fits better between the other two.
       
       
       New web?
       
       I think the way to connect should be rethought.  Currently we have the 
       protocol and the filytype/markup.  Cleartext vs TLS should be a choice 
       everywhere.  Make URLs have an own component for the kind of tunnel to 
       establish between server and client and strip cryptography from the 
       protocol part.
       
       
       Ok.
       Enough.
       ...for now.
       
       
       
       <GOPHER.36.2/18>(165)[ <ENTER> follow thread, (R)EPLY, (F)LAG or (Q)UIT ]