💾 Archived View for rawtext.club › ~sloum › geminilist › 002799.gmi captured on 2020-10-31 at 14:47:15. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Jason McBrayer jmcbray at carcosa.net
Mon Sep 28 13:31:38 BST 2020
- - - - - - - - - - - - - - - - - - -
Sandra Snan <sandra.snan at idiomdrottning.org> writes:
"Oh, it's chill, any particular client and any particular server can use
this for ANY semantics" only makes me more concerned, since it's the
foundation for a hundred hundreds of protocols.
I strongly agree with you.
IMO, we should resist the temptation to make Gemini a general-purposeapplication platform, and the like temptation to build a general purposeapplication platform alongside it.
I prefer the idea of writing protocols that are specific to applications(or classes of applications). A protocol for email; a protocol formessage boards; a protocol for file transfer. And a proliferation ofboth clients and servers for each protocol. The use of HTTP foreverything has led to every site being an incompatible siloedapplication... I'll save the rest of the rant for a gemlog post.
-- +-----------------------------------------------------------+| Jason F. McBrayer jmcbray at carcosa.net || A flower falls, even though we love it; and a weed grows, || even though we do not love it. -- Dogen |