💾 Archived View for station.martinrue.com › krixano › bf0f7e55ec98446293182d8965da280d captured on 2024-08-18 at 23:12:40. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-12)
-=-=-=-=-=-=-
Found this interesting protocol that someone is currently working on: gemini://tilde.team/~aprilnightk/netamict/index.gmi
2 years ago · 👍 superfxchip
gemini://tilde.team/~aprilnightk/netamict/index.gmi
@krixano recently this space became crowded... Check this out:
https://diasp.org/posts/21598415 · 2 years ago
https://diasp.org/posts/21598415
@mfoo2 It's true that requiring the terminal introduces downsides, but not every protocol must be universal (in fact, I think it's a bad thing to have universal protocols). The point is that a protocol is designed for a particular usage so that it is efficient for that usage. For example, you can use SSH for accessing the cli on remote servers, but you wouldn't use it for things it's not intended for. To increase accessibility in these instances would mean providing content via multiple protocols. It's similar to how screen readers that read from the display are less accurate and useful than speech-first interfaces. · 2 years ago
it’s a step backwards to require a particular front end rendering technology (the terminal). On a related note the accessibility won't be as good as Gemini. so it's a no thanks from me. · 2 years ago
@kakafega I think there's not as much information on the gemini site as there is on the HFNP/NETAMICT site, which is accessible via the older HFNP browser, since the new one isn't done yet. I'm not entirely sure on how everything works, because there's other things than just sending "pre-rendered" text to a terminal, like things called "processors" that the server and client supports, and adding or removing users. Another interesting thing is pages can send blobs with the page that can then be used by these "processors".
Anyways, I think it'll be interesting to see how it develops, because I think it'll be way more than just a copy of gemini or gopher. · 2 years ago
While it seems like an interesting concept, what would it bring "better" than already existing protocols? For example, gemini brings encryption when compared with gopher (and both simplicity when compared with http), but this protocol i'm not noticing any thing it may be better 🤔 · 2 years ago
@superfxchip If you're referring to similar features that HTML also has, then yeah. But, it looks like the protocol uses something more similar to BBCode, except everything is actually rendered on the server by having the client send the terminal dimensions (width and height) and color support to the server, and then the server computes and "renders" everything for that terminal size and type and sends back what gets displayed. So the BBCode-like markup never actually gets sent to the client, it's just used as a markup language for storage prior to rendering for the user's termial. In this way, it acts almost like an intermediary or templating engine. · 2 years ago
The idea of being able to use HTML features over a terminal client really catches me. I'd love to see what more comes out of this :O · 2 years ago