In Body URI references

[Jonathan McHugh]

Hi Stephane,

Thanks for your interest.

Stephane Bortzmeyer <stephane@sources.org> writes:

> On Sun, Jun 13, 2021 at 03:17:35PM +0200,
>  Jonathan McHugh <indieterminacy@libre.brussels> wrote 
>> Is there a style like Bit.ly for url shortening? Which still
>> respects Gemini design principles?
>
> I don't think any URI redirector could respect Gemini design
> principles. For instance, these redirectors are a privacy issue.
>

I have no desire to redirect users.

Im thinking in terms of inline reference to unclutter a large paragraph
while still collecting the urls below a section or as a footer.

>> Would it be interesting for there to be a (de)centralised site, which
>> provides?:
>> * A dictionary of url links
>> * Appropriate hashes that can be used for publishing or client
>> (re)interpretations.
>
> WHat is exactly the problem you are trying to solve? I can imagine
> some uses for such a site but I'm not sure which you had in mind.

I would prefer to work to a standard equivalent to wikipedia
content. IMHO. Its a good expectation for managing content, irrespective
of site or service.

As an example, the HTTP wikipedia page for Gemini Protocol starts with this
paragraph
=> https://en.wikipedia.org/wiki/Gemini_(protocol)
```
The Gemini protocol is an application layer protocol for distributed hypertext information systems that provides access to simple, primarily textual documents in Gemini space. This is done with contemporary technologies such as TLS, thereby improving privacy and user agency relative to the Web. Servers run by default on port 1965. The protocol is being designed collaboratively and is not currently being standardized as an internet standard. 
```
Pasting this echews 6 uri links:
=> https://en.wikipedia.org/wiki/Application_layer
=> https://en.wikipedia.org/wiki/Hypertext
=> https://en.wikipedia.org/wiki/Gemini_space
=> https://en.wikipedia.org/wiki/Transport_Layer_Security
=> https://en.wikipedia.org/wiki/Internet_standard

Naturally these are all unternal links, which could be referenced if
needed. I expect serving ALL references as a footer bibliopgraphy is
equitable.

I do not know whether clients or users have policies for 'folding away'
cross references for obvious/queryable suggestions.

The next paragraph contains 2 internal navigation links and 2 internal citations:
```
The design is inspired by the Gopher protocol, but mandates the use of Transport Layer Security with trust on first use (TOFU)[1] and privacy-related features. It is not intended to replace Gopher or HTTP, but to co-exist with them.[2]
```
=> https://en.wikipedia.org/wiki/Internet_protocol_suite
=> https://en.wikipedia.org/wiki/Trust_on_first_use
=> https://en.wikipedia.org/wiki/Gemini_(protocol)#cite_note-1
=> https://en.wikipedia.org/wiki/Gemini_(protocol)#cite_note-faq-2

The use of [:digit:] doesnt seem to be stable for content
(intentionally) containing square brackets, such as in lua
```
x = foo[1]
```

The proxy Gopherpedia eschews internal links and citations for the
content it generates.

I have come across this repo for proxying wiki content with Gemini but I
havent come across a working service yet
=> https://github.com/pitr/wp

I dont know whether there are are successful CMS approaches for cleanly
managing links.


I have been reminising about the social bookmarking site Delicious. Id
be happy if by aggregate or by project I was capable of having more
solid references across documents and references.

I have been intrigued by the potential of Emacs' Hyperbole as a
mechanism for interpreting content and interfacing with it. Given that
it cooperate with (the Gemini client) Emacs' Elpher I would like to
think there could be utility
=> https://www.gnu.org/software/hyperbole/DEMO.html#Social-Media-Hashtags-and-Usernames

Approaches include
```
   [facebook|instagram|twitter][#@]<hashtag-or-username>
   [fb|in|tw][#@]<hashtag-or-username>
   gh#rswgnu/hyperbole/5ae3550 (if include user, must include project)
   github#hyperbole/5ae3550    (project can be given with user default)
   gh#5ae3550                  (user and project defaults are used)
   git#/hyperbole            (displays the top directory of the hyperbole repository)
   git#/hyperbole/55a1f0     (displays hyperbole git commit diff)
   git#=hactypes.el          (displays a git-versioned file regardless of directory)
   git#=master:kotl/kview.el (displays file in subdirectory from master branch)
   gt#55a1f0                 (when within a git repo, displays its commit diff)
```                   
As well as this
```
   A document id is used just like a reference citation in traditional publications but it
   actually links to the document that it references and the card catalog
   (index) entry for the document.  One can easily pass around doc ids to point
   people to appropriate documents.  For example, a mail message in response to
   a question might say, "See [Emacs-001] for examples of what Emacs can do."
```

Here is a Hyperbole mailing list thread, concerning my generation of
navigation links to anchored queries (based upon searching my
filesystem)
=> https://lists.gnu.org/archive/html/hyperbole-users/2021-05/msg00050.html

I would like to have content served to me in Elpher, with actionable
links that permit me to visit links with little fuss. If I can consume
(or create) content like wikipedia with the links but with minimal URI noise, it
would make me happy.

--
Jonathan McHugh
indieterminacy@libre.brussels