15 ms·
gemini:// space
- prepperdev 6y agoGemini is a cool piece of simple tech. I had a genuine pleasure reading the spec: https://gemini.circumlunar.space/docs/specification.html https://gemini.circumlunar.space/docs/specification.html I've entertained an idea to build a set of tools for contemporary development (version control, code review, CI, etc) which would only speak Gemini. That would be both the UI and the API. Blockers came fast: * no way to upload anything that exceeds 1024 bytes, * escaping is subtly broken and so it would be impossible to review code written in Python or Markdown (triple quotes) * No text editing capabilities, pretty much. Which is fine: Gemini is great because it's restricted. It's nearly impossible to abuse. It will find its users, even if it would not be me.
- Arnavion 6y agoThe one thing that puts me off the most is the limit of two levels of headings. (There are three, but you need one for the page title, and it would be awkward to reuse the "title" heading level for "section" headings. Even if you got over this awkwardness, three levels is still annoyingly constraining.)
- dancek 6y agoIMHO you could just use # Page title # 1. First heading and go from there. The format is meant to be human-understandable, not machine-readable. But your point is a good one, and made me wonder how the documentation of Gemini itself handles the issue. And behold, the Gemini FAQ [0] itself has the first level 1 heading as ## 1. Overview and the second one as # 2. Protocol design That's really disturbing once you notice, but I'd wager that hundreds of people have read the page and not noticed. [0]: https://proxy.vulpes.one/gemini/gemini.circumlunar.space/docs/faq.gmi https://proxy.vulpes.one/gemini/gemini.circumlunar.space/doc...
- Arnavion 6y ago>IMHO you could just use [...] and go from there. The format is meant to be human-understandable, not machine-readable. I disagree that it's not meant to be machine-readable. Accessibility clients rely on heading levels to infer sections and subsections. HTML has `<section>`, but a Gemini client only has heading levels to go by. But anyway, that's why I said it'd be "awkward", not "impossible", to reuse the title heading level for section headings. The rich-text Gemini client as well as the human user reading the raw file have to special-case that the first `#` is the page title and not equivalent to other `#` in the file. And like I said, even once you get over that awkwardness, three levels is still very limiting. I'm looking at a markdown documentation file right now that has five levels of headings. That's with one unique level for the page title, so even if it were to reuse the title heading level for the section headings it would still require four levels of headings. >And behold, the Gemini FAQ [0] itself has [...] Ha, I didn't know about that one. I had noticed in the past that the homepage [1] uses a unique level for the title, but the specs page [2] does not because it can't afford to. [1]: https://portal.mozz.us/gemini/gemini.circumlunar.space/?raw=1 https://portal.mozz.us/gemini/gemini.circumlunar.space/?raw=... [2]: https://portal.mozz.us/gemini/gemini.circumlunar.space/docs/specification.gmi?raw=1 https://portal.mozz.us/gemini/gemini.circumlunar.space/docs/...
- Semiapies 6y agoI also noticed a few cases of trying to use markdown emphasis on the docs. If you can't even write the platform docs without having to work around your markup system, maybe don't go on about how the spec will never need updating.
- spwhitton 6y agoYes, this really bothers me too. Title, sections, subsections and subsubsections is not too much sectioning.
- tjalfi 6y agoI would argue that being limited to two levels is a feature. Here's a related quote[0] from Edward Tufte. "Dr Spock's Baby Care is a best-selling owner's manual for the most complicated 'product' imaginable -- and it only has two levels of headings. You people have 8 levels of hierarchy and I haven't even stopped counting yet. No wonder you think it's complicated." [0] http://web.archive.org/web/20080610092329/http://blogs.sun.com/MartinHardee/entry/tufte_story_answerbook http://web.archive.org/web/20080610092329/http://blogs.sun.c...
- Freak_NL 6y agoFrom https://gemini.circumlunar.space/docs/faq.html https://gemini.circumlunar.space/docs/faq.html: > Of course, it is possible to serve Markdown over Gemini. The inclusion of a text/markdown Media type in the response header will allow more advanced clients to support it. So not as the default markup language, but available.
- prepperdev 6y agoWhat I meant is having markdown pieces within code regions in a text/gemini doc. Imagine a code review tool that tries to show a diff as text/gemini.
- b3kart 6y agoThat’s just not the kind of use-case the protocol has been designed for. Think “documents”, not “tools”.
- deleted 6y ago[deleted]
- dancek 6y agoTrue, text/gemini is not really suitable for UIs. I did write a wiki engine where the editing is done with sed commands and all responses are text/gemini. It works but people used to modern web apps are not going to love the UX. You can serve other mimetypes over gemini (the protocol). That's useful for some use cases (eg. ansi.hrtk.in serves modem download emulated versions of ANSI art; requires a streaming-capable client). But all in all, Gemini tries hard to not be an application platform. These exercises in stretching the limits are fun and IIRC have also guided the development of the spec. But the focus of the project is on text-based content.
- makeworld 6y ago> triple quotes Just to clarify, triple quotes work fine in gemtext. It's triple backticks that start and end preformatted sections. So only a line that exactly starts with triple backticks can't really be shown properly. Everything else can.
- agumonkey 6y agoTried using gopher back, I like frugal but it's a tad too bare.. interesting nonetheless. Ultra light for sure.
- Aeolun 6y agoI think the idea that Gemini cannot be extended is a bit silly. Clearly it can be, it’s just not inherent in the specification that it will.
- spwhitton 6y agoThey've tried to make it really difficult, though -- for example, how there is only one type of request. Extending text/gemini is more feasible indeed.
- jl6 6y agoThe author is 100% right about the effect of having formally designated spaces for things that you would think could happily exist as informal subspaces of a wider environment. Cold engineering logic drove us to see that everything is just bytes and so everything can be served over HTTP. The same logic is used in the retail world to optimize away culture and quirk and nuance and difference: everything is just a product, so everything can be sold in just one superstore. I see the small Internet movement as not just about nostalgia (although it’s definitely a little bit about nostalgia), but about countering monoculture by prioritising things other than efficiency. Gemini doesn’t need to be extensible because if you want to do something different, you can use a different tool and they can happily coexist, because the objective is not to achieve a winner-takes-all network effect victory.
- krapp 6y ago>Cold engineering logic drove us to see that everything is just bytes and so everything can be served over HTTP. >The same logic is used in the retail world to optimize away culture and quirk and nuance and difference: everything is just a product, so everything can be sold in just one superstore. That seems an odd aspersion to cast on a protocol that gave Hacker News the culture and quirk and nuance and difference of the early web it's so nostalgic for.
- andai 6y agoThere's a great FAQ which explains the motivation behind the project and behind the design decisions: https://gemini.circumlunar.space/docs/faq.html https://gemini.circumlunar.space/docs/faq.html
- kristopolous 6y agoBrowsing via a remote session (https://gemini.circumlunar.space/clients.html https://gemini.circumlunar.space/clients.html) is classic. Telnetting to a machine that had a text web browser was a real thing back in the early 90s Someone is either old or has done some serious homework (maybe both). Good job. Note: also, since people who don't know what they're talking about occasionally seem to want to challenge me on early (pre-1996 or so) web history here's some references: Page 500 from the 1994 "The Internet Complete Reference" by Harley Hahn: http://9ol.es/1994-internet-book.jpg http://9ol.es/1994-internet-book.jpg (info: http://9ol.es/1994-copyright.jpg http://9ol.es/1994-copyright.jpg) Page 272 from the 1993 "The Online Users Encyclopedia" by Bernard Aboba: http://9ol.es/1993-internet-book.jpg http://9ol.es/1993-internet-book.jpg (info: http://9ol.es/1993-copyright.jpg http://9ol.es/1993-copyright.jpg)
- julius 6y agoI like how it removes noise for the reader. Links cannot simply be put whereever the author pleases. Links have to be put on their own line. (and the browser can neatly indicate to you which links are same-domain, other-domain, other-protocol)
- gerikson 6y agoI hate not being able to integrate links in running text - it's been a feature of the web since the start, having to awkwardly add "see this link:" followed by a newline everywhere would drive me mad.
- betwixthewires 6y agoI felt that way at first, but when I started to understand the reasoning behind it (explained in the Gemini space FAQ and counties meta articles, which is a lot of Gemini documents) it makes perfect sense. When you're reading a document, it is to enjoy information. Whether that's learning, recreational reading of fiction, or whatever, a subtle part of the experience is the structure of the document. It gives you context and helps maintain a flow of thought. A reference to an external document should be plain as day and stand out. It should not bleed into any other part of the document. This might sound like an over rationalization, but to get an idea for this, imagine if footnotes or references were tossed in using parentheses wherever they were referenced. The structure of the document is important, sometimes as important as the content.
- Karunamon 6y agoI've found that the lack of good footnote handling in Gemini is a real pain in the rear. Consider footnotes in a book, you see the superscript 1 or the star or the cross and you know you glance towards the bottom of the page for that content, then jump back to where you were. On books, in dense text, you can put your finger on your current location, look to the bottom of the page, read that content, then pick up where you left off. On a screen it's harder, since going to "the bottom" involves n pages of text to be scrolled by. If I hit [End], I don't know how many [Pgup] to hit to go back. I can hit [Pgdn] a few times and count mentally (which sucks, and takes me out of the flow), but due to the way text is flowed, reversing with an equal number of [Pgup]s will usually wind up taking me somewhere above or below where I started. This disorientation is not desirable. Inline footnotes on most rich text sites usually have a link directly to the footnote, and then a back link which jumps to where the note was referenced. This is the best of both worlds. I'm on board with most of the Gemini limitations, but I see this being a no-brainer addition to the protocol if not a sane client.
- Mediterraneo10 6y agoI really like the idea of having a more bare-bones text-only web, but I can't get onboard with Gemini until it offers the same support for screenreaders as HTML. (For example, an equivalent of span lang=XX tags is missing, so if you quote a foreign-language word(s) in your text, you can't let screenreaders know what language to read it in). The visually impaired should not be second-class citizens in any new internet community.
- senkora 6y agoI would argue that that complexity should be handled by the screenreader through heuristics rather than the .gemini format itself, based on the desire to keep basic clients very simple (~100 loc). But that’s a really good point!
- Mediterraneo10 6y agoHeuristics might work for longer text where the sample is large enough to uniquely identify the language, but for single words there is not enough information. If I write "coin" in my text, for example, am I using an English word, French word, or Irish word? The pronunciation varies drastically, and screenreaders have to know what to say.
- mlyle 6y agoHumans need to know what to read, though, too, right? Obviously humans are a bit better at contextual clues, but.. the information has to be there for a human user to make the distinction.
- Mediterraneo10 6y agoSure. A quoted foreign word might (but not always) appear in some context where any reader will know how to read it. However, for the time being, computers won't, and a screenreader won't manage without adequate semantic tagging.
- contravariant 6y ago
- Thorentis 6y agoJust a meta-comment, but is this blog meant to be stream-of-consciousness? I found the prose very hard to read, and the phrasing to be quite jarring. Possibly too many commas or separate phrases?
- MrYellowP 6y ago> I now have a games console at home for the first time in some years, which I bought in response to the ongoing pandemic, and one thing that I have noticed is that using it feels like being offline in a way that playing games on a regular computer never would. I agree with you. The structure of his thoughts could use some improvement.
- deleted 6y ago[deleted]
- oneeyedpigeon 6y agoObviously take this with a pinch of salt, but it's the first piece of writing I've seen achieve a 'post-graduate' readability rating on Hemingway.
- spwhitton 6y agoSorry to put you through that! I normally go back and edit my blog posts at least a little bit, but I wasn't very happy with this one, so I didn't bother. I didn't expect it to have a readership beyond whoever happened to look at planet.debian.org yesterday.
- Ambolia 6y agoReally nice project, seems like some keys to open up the internet again would be: - Decoupling of data (articles, videos, ...) from platforms. - Decoupling authorship claims from platforms - Decoupling online identities from platforms. - Decoupling of user networks from platforms. - Distributed archiving, some years ago if you had an article/manifesto or whatever on Napster or any other P2P system it was trivial to find it again anytime you wanted, now dead blogs, videos disappearing from Youtube, or broken links to Twitter are the norm. You have to archive stuff yourself or hope somebody did it. - Related to decoupling user networks from platforms, it would be nice to decouple comment sections from platforms and from the articles themselves too. People could comment the same article in different curated comment sections with different moderation policies using their own decoupled online identity. - Create decentralized networked chains of trust (could help revitalize some scientific communities too). Seems like very interesting things going on with projects like gemini, Urbit, IPFS, still on the early stages and only usable by power-users, but hopefully they will keep growing.
- wwn_se 6y agoSomething like rss or similar so aggregation can happen client side
- bandie91 6y agoi strongly agree with these points. let me add some more: - decouple documents from the transport layer: many web vulnerabilities and complexity are due to the strong connection between http and html - decouple documents from styling: every document should be legible with any stylsheet (bring back 'userstyle'), cut back css features which lead to nasty things like keylogging via css, transparenting elements for clickjacking, hide text to manipulate clipboard, etc.
- cabalamat 6y ago> gemini, Urbit, IPFS There could be a distributed blogging/wiki platform where the articles are all written in Gemini markup (or maybe Markdown) and hosted over IPFS.
- spwhitton 6y ago
- ryannevius 6y agoAre there any other protocols that have similar aims? I love the idea of a "corner" of the web that is reminiscent of the plain markup/pre-JS days, and occasionally use w3m to get a taste of it.
- Minor49er 6y agoI'm not sure about protocols, but I've been browsing Neocities lately. There are thousands of sites. Many of them are a satisfactory throwback for my tastes: https://neocities.org/browse https://neocities.org/browse
- h_anna_h 6y agoI don't understand why the gemini people don't just use http 1.0 (+ host) with html (or plaintext/markdown/whatever even, without js/css). Seems like a case of NIH to me. Don't get me wrong, I am not against "reinventing the wheel" for a toy project or to learn but gemini seems to have become more popular than just that. If someone is really tired of the modern web I would suggest to them a distributed alternative rather than this.
- prepperdev 6y agoThis is covered by their FAQ: https://gemini.circumlunar.space/docs/faq.html https://gemini.circumlunar.space/docs/faq.html, Section 2.5 "Why not just use a subset of HTTP and HTML?"
- h_anna_h 6y agoI do not buy it. Just use gemini:// rather than https:// https:// to refer to that specific subset of https + html. Maybe also add a header to the server response that says x-gemini: true or whatever. > It's difficult or even impossible to deactivate support for all the unwanted features in mainstream browsers Just do not use mainstream browsers then. Make your own like you do for gemini. They address it a bit later with: > Writing a dumbed down web browser which gracefully ignores all the unwanted features is much harder than writing a Gemini client from scratch And I will disagree on this part, http 1.0 is actually easier to implement than the gemini protocol. > Even if you did it, you'd have a very difficult time discovering the minuscule fraction of websites it could render. Except gemini browsers render even less websites right now. It seems to me that the gemini developers can't really think outside the box. This is further proven by their dependence on things like TCP, TLS, and DNS.
- rakoo 6y agogemini isn't trying to reinvent the web, to make it P2P or serverless or whatever; it's just reusing the ideas of gopher and the web but going in another direction. It doesn't try to replace the web. From this point of view it makes total sense to reuse TCP, TLS and DNS, because they're not trying to replace them. > Maybe also add a header to the server response that says x-gemini: true or whatever. That would require adding headers, which means extension is possible, and that's explicitely something gemini doesn't want. I believe it makes sense in the goals gemini wants to achieve. > And I will disagree on this part, http 1.0 is actually easier to implement than the gemini protocol. HTTP 1.0 still has multiple headers and multiple verbs. It's actually closer to HTTP 0.9. Yes, you can say "don't use those" but at some point it's good to refresh the spec and see what is and what isn't needed. Moreover HTTP is just HTTP, Gemini is transfer + encryption + client identification (through client certificates); the latter is still the wild west for the HTTP world, there is no clear set of "best practices" in this domain
- alexwennerberg 6y agoGemini is fantastic. For anyone interested in experimenting with it without setting up a server, I've been working on a simple Gemini site builder that works over HTTP and serves the content via Gemini and HTTP proxy: https://flounder.online/ https://flounder.online/ In my view, Gemini's bare-bones text format is its killer feature. Non-technical users have been able to easily write Gemtext based on a few examples and a bit of experimentation. This gets users away from WSIWYG without forcing them to learn something as complex as HTML. And unlike Markdown, it is clearly-specified, universal, and doesn't compile to anything else. Many people criticize Gemini for lacking this or that feature, and being basically useless for "practical" applications. I wrote an blog post about this: https://alex.flounder.online/gemlog/2021-01-08-useless.gmi https://alex.flounder.online/gemlog/2021-01-08-useless.gmi
- mattowen_uk 6y agoBeyond using TLS for the connections, I struggle to understand what Gemini offers over Gopher. Gopher's document type is bare bones text also. Gopher is an open standard also. There's many clients and servers for many platforms, and it's easy to implement. I've been subscribed to the Gemini mailing list for a while now, and browse the conversations on it (it's very active), and I'm still yet to be convinced it's a viable alternative to the web that will gain any traction outside of it's core hobbyist user base.
- alexwennerberg 6y agoI don't come to Gemini from the Gopher community, but the advantages are listed in section 2.2 of the FAQ: https://gemini.circumlunar.space/docs/faq.html https://gemini.circumlunar.space/docs/faq.html
- h_anna_h 6y ago> No other "alt web" technology approaches the internet with such extreme and radical skepticism Except hypercore/dat, ipfs, freenet, tor, i2p, gnunet, ...
- 6y ago
- michaelanckaert 6y agoI've been diving head first into the Gemini space this weekend and discovered some really great content. It takes me back to web of the early 2000's where you had websites with manually curated content (webrings! link rolls!) instead of corporate milked content aggregators. Combined with my love for minimalistic websites (hello http://motherfuckingwebsite.com/ http://motherfuckingwebsite.com/) I find Gemini a perfect small web to enjoy. I've even started updating my static site generator to update both HTML and Gemini output.
- eternalban 6y ago> discovered some really great content. I just downloaded Lagrange and ended up here: gemini://cbrews.xyz/literature/the-castle-of-otranto.gmi It does remind of early web surfing(my ref is 90s).
- michaelanckaert 6y agoThanks for the nice link :)
- michaelanckaert 6y agoAn interesting tool is the Gemini portal over at https://portal.mozz.us/gemini/mozz.us/ https://portal.mozz.us/gemini/mozz.us/ This allows you to browse Gemini space through a classic Web browser.
- deleted 6y ago[deleted]
- zimbatm 6y agoI respect the sentiment of starting from scratch to get rid of technical debt. The protocol is not very different than HTTP/0.9, with hindsight applied. That being said, the protocol interaction model is essentially the same as HTTP. There is another road where browsers get support for the text/gemini content-type but still talk HTTP only. It doesn't fix everything but it has the advantage of allowing normal users to participate in it.
- bovermyer 6y agoI found this quote on a gemlog by Alex Wennerberg: > Gemini's obscurity and lack of utility means that there are no analytics, no metrics, no ways to go viral, to monetize people's attention, build a career or even a minimally-functional web platform. No sane business would build on top of Gemini, and that is exactly why it is capable of having the character that it does. I like this sentiment.
- gioscarab 6y agoYou should try to run gemini over PJON https://github.com/gioblu/PJON https://github.com/gioblu/PJON that could really change the game.
- fallat 6y agohttp://len.falken.ink/web/perceived-relations-between-gopher-gemini-and-http.txt http://len.falken.ink/web/perceived-relations-between-gopher...
- FrozenVoid 6y agoGemini appeals to the 'console-only' aesthetic, I won't bet on it replacing the everyday web, but it can be used to construct an alternative 'Internet for the terminal'-type experience: lightweight news, libraries, etc accessed from shell scripts(which is plain text vs web scripts that strip html cruft to get real content). The only thing i dislike is the poor choice of the name, which clashes with millions of sites about horoscopes.
- betwixthewires 6y agoIt goes beyond the console asthetic, it becomes about functionality for the user. I think it could very much replace the majority of the web over time, or something like it could. I'm not just being naive about something I have a pet fascination for here either. Imagine the internet in the year 2121. Do you really think that people looking to read an article about such and such that happened today are going to tolerate your abysmal theme design, constant requests to sign up to your newsletter interrupting their absorption of knowledge (or propaganda), nested dropdowns, account requirements, just to read your take on current events? Will the excuse "how else are we supposed to get paid" be an industry standard in 100 years, when the internet is as integral to the human experience as spoken language? A big reason we tolerate all the cruft is because the world has just recently left the phase where the internet is just a novelty. The internet was experienced inside of 1 application, the web browser, and that is very clunky. We are already leaving that behind with people demanding a separate app for every type of interaction they have online. The day will come where, when someone just wants to read something, they'll expect just that, and there will be millions, possibly billions, of people willing to deliver that for them. If your goal is to get your message out there (or your ideas into someone else's head), you're going to face a lot of competition, and your audience might not have the time and patience to deal with any more than they asked for.
- trap_chateau 6y agoWhile I think gemini is a cool 'hideout' on the web, it seems a lot of content served over gemini is also served over http. Does anyone know of any message boards like The Midnight Pub[1] that are served over gemini only? After some browsing, I couldn't find any. [1] https://midnight.pub/ https://midnight.pub/ gemini://midnight.pub/
- fgaz 6y agoI'm hosting a very simple one at gemini://gemini-textboard.fgaz.me but it's mostly just a demo for my gemini Haskell libraries: https://sr.ht/~fgaz/haskell-gemini/ https://sr.ht/~fgaz/haskell-gemini/ Another one I know of is gemini://geddit.glv.one/
- ufmace 6y agoThat's kind of the trouble with Gemini now. Since you can't send significant amounts of text to the server, you can't really make a message board kind of thing in pure Gemini. The content submission has to be done via HTTP or a terminal interface to the server. But then, if HTTP is the simplest and most secure way to allow posters to make submissions, then is there really a point to allowing the messages to be read over Gemini? Might as well make a simple HTTP layout and have the whole thing run over HTTP.
- krapp 6y ago>That's kind of the trouble with Gemini now. Since you can't send significant amounts of text to the server, you can't really make a message board kind of thing in pure Gemini. Given the aggressive anti-complexity stance of Gemini, isn't that supposed to be a feature? A messageboard isn't a static text document, it doesn't belong there.
- ufmace 6y agoIt's on the protocol designers and promoters to determine what it ends up being of course. It seems like a bit of a mismatch to me right now. The client cert support as the exclusive way to identify users is a really cool feature of the protocol IMO, but it doesn't seem like it's very useful without dynamically rendered pages. It's certainly possible to do dynamically rendered pages now, but they're also of much more limited use without the ability to send complex data to the server using the same protocol.
- ilaksh 6y agoIf I understand correctly they insist on no re-use of connections. That one makes no sense to me and guarantees any compliant client will be slow. So people will make "fast clients" that just ignore that rule.
- annadane 6y agoIt's a sad indictment on the tech industry that so many of you are just dismissive of Gemini
- ufmace 6y agoI've been messing with Gemini some off and on. A little unsure about what to build given the limitations. It seems to expect the user to use direct SSH access to servers for anything that would normally involve sending more than trivial amounts of data to the server. The most interesting part IMO is the restriction to use user-managed TLS client certs as the exclusive way to identify a user. Nice way to both securely manage user identity without clumsy passwords and all of the issues they bring, and easily allow the user to have zero, one, or many identities and switch among them anytime they feel like it. Eliminating cookies and other such things in favor of it eliminates third-party tracking and puts the user in charge of who knows who they are and when. I don't know if Gemini itself has a big future beyond a niche circle of bloggers. I would like to see the client cert feature be widely adopted within HTTP though. Maybe, among other things, Gemini can also be a lab to test out ideas that might make the mainstream web a better place too.
- EamonnMR 6y agoI keep getting pulled toward the small internet by various forces, but I never seem to find the center of it, the place where the good content starts. I want to find the good phlogs and the secret message boards. I've connected to modern day BBSs and could never get used to the keyboard layout. What am I missing?
- betwixthewires 6y agoThere's no center to it. Each obscure protocol or space is a separate small internet, only connected by the people that participate. Gemini has quite a bit of good content, if you like to read without feeling the need to weigh in or interact, when the mood strikes you.
- tenebrisalietum 6y ago> Gemini is one technological piece in attempts to make a version of the Internet which is healthier for humans – the so-called “small Internet” movement – and maybe there will be new ideas about how the small Internet should be which would benefit from a new version of the Gemini specification. So it seems risky to lock-in to one version. If there are better ideas or fundamentals on which to build the root of another space, then what the Gemini is protocol is saying is that -- make your own protocol and name it something different. I don't think it's risky to lock-in to the Gemini protocol because: It's very minimal, so A) clients should be minimal as well, and B) Gemini documents are human readable without a client. So if Gemini doesn't work out, your *.gmi files will hardly be useless blobs of tags.
- badsectoracula 6y agoMy main annoyance for gemini not having http is that i do not want to run a VPS. My (web) site is running on shared hosting where keeping (or not) software up to date, keeping up with the latest and greatest way Gmail breaks email and any other admin-level stuff i handled by someone else (and also it is cheaper) - i just upload a bunch of static HTML files and anything else i need to share and leave it at that. If Gemini used http 1.0 (like others mentioned) it'd work out of the box - not just for me, but for everybody else. But the custom protocol pretty much requires a VPS and that opens a can of worms i'm not interested in opening again. FWIW i used to have my own "gopherhole" but since that one also needs a custom server, i dropped it after i switched from VPS to shared hosting. I still have the client i wrote though[0] and considered making a Gemini one at some point but the fact that i can't make my own site does hamper things a bit (and TBH i haven't updated the Gopher client for years either). [0] http://runtimeterror.com/tools/gopher/ http://runtimeterror.com/tools/gopher/
- bullen 6y agoThis is the equivalent to creating a new programming language instead of just using C syntax with the C++ compiler. HTTP/1.1 is our final network protocol, just accept it. Just like Java is the final serverside programming language. JSON is the final data container. Everything else is completely stupid, indefinitely. Also: Make your own crypto! Xo But if Firefox and Chrome bans HTTP/1.1 (which means they will be obsolete) AND gemini adds chunking (without which it is meaningless) AND port 1965 is opened in every firewall on the globe; I might actually consider switching to gemini/v0.14.4 on my app server!
- betwixthewires 6y agoOn the last paragraph in the article (criticism of the lack of extensibility of the protocol), Gemini itself is a protocol largely designed to improve on the modern shortcomings of the gopher protocol, so if ever Gemini were to fall short of the demands of the type of people that use protocols like this, the solution is right under your nose: make a new protocol. I'm a big fan of Gemini. I think the philosophy around light document delivery over the internet is very important. And the lack of extensibility is a core part of that, Gemini cannot be everything to everyone, by design. And no protocol should, I personally find the idea that http is used to deliver news articles and web apps to be a bit ridiculous, the protocol was extended well beyond what it was intended, and I can find no reason for this other than that people don't like typing different things on the left side of the "://", if they ever even type that part at all. Imagine an internet where people routinely use different protocols (and know about it), how much cleaner the experience would be.
- ashkankiani 6y agoI like the idea, but not the approach.