backlinks and other shenanigans

Re-thinking previous strategies I had for building software within gemini-space has made me choose decentralized ideas. Since gemini-space is very spread out and full of ideas and things, but none are streamlined, it feels odd to re-develop every single thing many many times. For instance comments on gemlogs. Therefore I guess decentralization has these immediate advantages:

• less maintenance
• scalability
• adaptability
• extendability

and these disadvantages, which I can understand when someone argues that they don't want to deal with them:

• the need to agree on protocols and information structure
• increased amount of requests on servers

Finally I did come up with a pattern that I find quite simple to support:

The Backlink Project

The general outline is, instead of signing up and writing a comment text on a gemlog, a response to an article, any social interaction, every "site" provides a backlink URL. Then the URL is submitted there, and with that backlink something can happen. Show a link to it, include the content, partially or fully, scan for hierarchies, etc.

=> Read up on the Backlink Project

Titan

Previously I logged into my server, navigated into the correct folder, booted up vim and started to type. Then I started up vim locally, finished typing and then scp'ed the file up to my server. Both are quite tedious and well, some places I can write content don't necessarily have my ssh keys lying around, but they do have certificates.

Implementation of the titan protocol was easier than I expected. At least after implementing my own gemini server from scratch. It's a great addition, I feel.

To fully reflect on how well titan does and whether I want to keep using it I probably need to run it for a few weeks. I'll report back then.