131–140 of 211 posts
Earlier quoted context omitted.
Just put them in markdown and have compatible clients inline render an image and non compatible clients get a link.
Compare this thread with the thread about 30 years ago: http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.ht...
Is extensibility really the Pandora's box the author makes it out to be? Just because something is extensible doesn't mean it has to be extended in monstrous ways.
Earlier quoted context omitted.
Would you notice if someone changed the "f" in the middle of that onion link to an "l"?
Again, it's impossible, or should be impossible, to easily change a single character in a hash. The avalanche effect means that small changes in the input data will result in huge changes to the hash.
Earlier quoted context omitted.
HTTP supports extensibility via HTTP headers and methods. Gemini to not be evolved: * HTTP is now for interactivity, complex clients, WebGL, Webassembly, ... * Gemini is for a segregated simpler web: links and text.
There is nothing Gemini can do to prevent people from adding complexity on top of it. It's exactly how the web evolved. It did not have activex/java applets/flash/javascript at the beginning.
People here saying they'd rather use just text-only HTML, or HTML+CSS sans JS, don't understand that what attracts people to Gemini is the ease of implementation . The main quality of Gemini is that it is easy to understand and implement thus allowing normal developers to create clients and servers from scratch with minimal fuss. You can actually keep the whole spec in your head which is no longer something anyone ca…
Gemini is a bit conflicted here. It has both privacy and simplicity as design goals. But privacy (materialized by encryption) is far from simple, so much that "rolling your own crypto" is seen as a cardinal sin, and for good reason. Crypto is an arm race, constantly under attack, constantly updated, and very easy to get wrong. The argument on the Gemini website is to use a library, which is indeed the most sensible thing to do, but if you allow code you don't really understand, one might as well use a webview and call it a day.
When I was in high school, I was part of an online community that wrote graphical shells for DOS (really NTVDM) in QBasic. One of the things we all started to want was a web browser, but most of us had no idea how to write a parser, let alone deal with the complexities of HTML and JavaScript. So we created our own markup language, where each "tag" was on it's own line, with the first character indicating the type of…
Earlier quoted context omitted.
Just put them in markdown and have compatible clients inline render an image and non compatible clients get a link.
Compare this thread with the thread about 30 years ago: http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.ht...
Also Marc Andreeson's suggestion of "a general-purpose procedural graphics language within which we can embed arbitrary hyperlinks attached to icons, images, or text, or anything" before JS or HTML5 canvas arrived on the scene is interesting.
An alternative protocol that explored some of these evolutionary dead ends of the early web could be fun.
[0]http://1997.webhistory.org/www.lists/www-talk.1993q1/0209.ht...
I understand the desire to use trust-on-first-use to get rid of certificate authorities (some of the most dispicable and untrustworthy organizations around, and the largest security hole in TLS). However trust-on-first-use basically hands any long-term man-in-the-middle a complete victory. Authoritarian regimes are going to require ISPs to mitm every connection from first use, and hand over whatever data is desired t…
Is there the equivalent of a Gemini "home page" anywhere? I'm after some links.