💾 Archived View for rawtext.club › ~sloum › geminilist › 005817.gmi captured on 2024-02-05 at 11:06:42. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Vasco Costa vasco.costa at gmx.com
Mon Mar 1 17:20:17 GMT 2021
- - - - - - - - - - - - - - - - - - -
First of all my apologies if this has already been discussed before.
After a long time consuming gemlogs by subscribing to gemini pages thatcomply with the widely adopted subscription convention described here:
gemini://gemini.circumlunar.space/docs/companion/subscription.gmi
I can't help but notice that at their core, email and usenet show asimilar pattern to index.gmi files inside gemlog folders when presentingan index of messages to the user, perhaps with the exception that theyalso show a from address, in addition to a date and a subject.
Does anyone think it would be useful to have a gemnet folder inside ourcapsules, in a similar fashion to gemlog, using the same subscriptionconvention as mentioned above, but perhaps adding a "from" field likethis:
/gemnet/index.gmi:
=
hello_gemnet!.gmi 2021-03-01 - Hello gemnet! - gluon=
another_message.gmi 2021-03-02 - Another message - gluon=
one_more_message.gmi 2021-03-03 - One more message - gluon=
re:and_now_a_reply.gmi 2021-03-03 - Re: And now a reply - gluon=
re:and_now_a_reply_2.gmi 2021-03-03 - Re: And now a reply - gluon=
re:and_now_a_reply_3.gmi 2021-03-03 - Re: And now a reply - gluon
That renders as usual:
2021-03-01 - Hello gemnet! - gluon2021-03-02 - Another message - gluon2021-03-03 - One more message - gluon2021-03-03 - Re: And now a reply - gluon2021-03-03 - Re: And now a reply - gluon2021-03-03 - Re: And now a reply - gluon
This looks like a very simple way to post messages and replies in a"semi-distrubuted" way, making use of Gemini as the underlying transportmechanism. Distributed in the sense that messages would live only withinthe server of each author.
Then, anyone interested in the messages of a particular author wouldmake use of clients that allow YYYY-MM-DD subscriptions or run localaggregators with such feeds to be able to see the messages. Postingmessages or replies would be elegantly the same as posting a gemlogentry, using whatever mechanism you already use for that. That said,specialised clients could also easily be developed to make use of thisconvention and allow an interface more similar to an email/usenetclient if desired.
One further convenience of this "network architecture" is that SPAM iseasily avoided, since that by design, you need to opt-in to any person'sfeed and you won't see the messages of anyone you haven't subscribed to.Think of a killfile from usenet but in reverse.
I mentioned a separate folder called gemnet, but in reality gemlogs areso generic that we could use them as they are. After all, any gemlogpost could be a message itself. Using the current gemlog folders wouldeven make it very easy to reply to gemlog posts, something many peopleoften feel the need to. However, maybe this approach would create toomuch SPAM, so I think having a separate gemnet folder is morereasonable?
I guess that's it. Once again sorry if this makes no sense at all, orhas already been discussed. On the other hand, if you resonate with theconcept, I'm willing to create my own gemnet and subscribe to anyone whodoes the same. We could experiment communicating using Gemini this way.
--Vasco Costa
AKA gluon. Enthusiastic about computers, motorsports, science,technology, travelling and TV series. Yes I'm a bit of a geek.
Gemini: gemini://gluonspace.com/