💾 Archived View for rawtext.club › ~sloum › geminilist › 006906.gmi captured on 2023-11-14 at 09:00:15. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Decentralized content creation and linking

gemproj at suckless.anonaddy.com gemproj at suckless.anonaddy.com

Mon Jul 12 20:58:49 BST 2021

- - - - - - - - - - - - - - - - - - -

For Gemini, we could do something more basic. Gemini capsules could

expose an endpoint; this can be parsed from a page in a manner similar

to the gmnisub approach, by matching a string on a page. Perhaps a

Gemini hyperlink to an input form with the text "Submit a backlink"?

Making this multilingual could take a while.

The "manual" approach would be having a user navigate to "Submit a

backlink" somewhere on a gempost to share a backlink via input form; a

backend can check out the source page and look for a backlink. If one is

found, the Gemlog "builder" can add these backlinks to a "Mentions"

section. An automatic approach could have a Gemlog "builder"

automatically check each linked page for a "Submit a backlink" URL (or

any of its translations) and auto-submit backlinks.

I think I get the gist. It's more of an opt-in approach than what Isuggested.The biggest problem with this is, imho, that you exclude all the staticsite generators. They can't participate. And that's a problem, because youcan easily get a simple gemlog without any scripting backend, but you can'tget a proper scripting backend without a server. Ideally I'd love toinclude the static generators to at least be able to comment.

At the same time I think your solution works better. Is easier toimplement. And if you can just put up something like: <domain>/<path to thelog entry>/backlink?<link to the comment> it'll be almost automatic tocomment on existing posts. Then you should review the backlinks you getbefore you put them there, but it's simple, effective, just needs people tohop on board :)

On Mon, Jul 12, 2021 at 8:32 PM Rohan Kumar 'seirdy at seirdy.one'<gemproj+seirdy=seirdy.one at suckless.anonaddy.com> wrote:

This email was sent to gemproj at suckless.anonaddy.com from

seirdy at seirdy.one and has been forwarded by AnonAddy.

To deactivate this alias copy and paste the url below into your web

browser.

https://app.anonaddy.com/deactivate/84c97fb7-dd72-4688-b653-188215324c2a?signature=e4cd6fabb5144657ed72ac3c56cde019ecccfe366af0b08968536f9080c11eba

-----

On Mon, Jul 12, 2021 at 03:54:36PM +0000, gemproj at suckless.anonaddy.com

wrote:

For instance you write a log entry with <topic>, post it on antenna

(gemini://warmedal.se/~antenna/) and when someone posts another log entry

with a title Re: <topic> your server collects it, parses the first text

segment it finds until EOF or headline and puts it under your original

log.

Or just adds a link to this response post.

Additional features can be that you have a comment INPUT that takes a url

to the response, or scanning multiple aggregators.

I think something resembling the Web's Webmentions would be a good

start. With Webmentions, you write a comment on Webpage A on your own

website, Webpage B that has a backlink to Webpage A. You then send a

Webmention either automatically or manually; doing so manually is quite

trivial:

curl -d source="webpage B URL" dest="webpage A URL" "link to website A's

webmention endpoint"

Where the link to Webpage A's Webmention endpoint is in a <link> tag of

the <head>. A daemon receives the Webmention, downloads Webpage B, and

checks it for the backlink to Webpage A. If one exists, it accepts the

Webmention.

I have this setup for my static Web site https://seirdy.one/; Hugo pulls

in Webmentions from my self-hosted endpoint for each page. Some people

also have an input form on their pages for submitting backlinks as

Webmentions.