💾 Archived View for rawtext.club › ~sloum › geminilist › 007184.gmi captured on 2024-03-21 at 16:00:28. Gemini links have been rewritten to link to archived content

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

Not always online capsules

Jonathan McHugh indieterminacy at libre.brussels

Wed Sep 22 12:39:13 BST 2021

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

Carsten,

I havent touched DNS properly, is this aspect easy to look into.

Could public-inbox serve as an alternative approach?=

https://public-inbox.org/README

Traditional mailing lists use the "push" model.  For readers,that requires commitment to subscribe and effort to unsubscribe.New readers may also have difficulty following existingdiscussions if archives do not expose Message-ID and Referencesheaders.  List server admins are also burdened with deliveryfailures.

public-inbox uses the "pull" model.  Casual readers mayfollow the list via NNTP, IMAP, Atom feed or HTML archives.

If a reader loses interest, they simply stop following.

Since we use git, mirrors are easy-to-setup, and lists areeasy-to-relocate to different mail addresses without losingor splitting archives.

_Anybody_ may also setup a delivery-only mailing list server toreplay a public-inbox git archive to subscribers via SMTP.```

====================Jonathan McHughindieterminacy at libre.brussels

September 22, 2021 12:33 PM, "Carsten Strotmann" <carsten at strotmann.de> wrote:

> Hi,
> 
> On 22 Sep 2021, at 11:36, Alice wrote:
> 
>
>
> There are registrar that disallow txt records? Lot of other services
>
>
> (gitlab pages comes to mind for example) requires user to set TXT
>
>
> records.
>
> 
>
> Also SPF and dkim require TXT records - and these are needed for 
> anyone who wants email at their
>
> own domain.
>
> 
>
> My registrar hides TXT records under an "Advanced" tab, but it's 
> available.
> 
> when using TXT records (which might not be the best choice for this function), they should be
> stored at a well-known subdomain.
> 
> The DNS currently has the problem that too many applications try to store information in TXT
> records on the base domain name, that creates all kinds of operational issues for the DNS service
> and for the applications.
> 
> For example take a look at "dig microsoft.com txt" or "dig twitter.com txt". Storing more TXT
> records at that place will make the situation worse.
> 
> A well-know subdomain for Gemini parameter information could be something like
> 
> _gemini_parameter.domain.tld. TXT "online-start=090000" "online-end=220000" "language=en"
> 
> Another (maybe technically better) alternative could be the new SVCB "Service binding and parameter
> specification via the DNS" record: <https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https>
> 
> Greetings
> 
> Carsten