XMPP, Gemini, Gopher and NEX

[sjehuda]

I think that it would be good to support Gemini.

I have opened a journal site for my XMPP projects over HTTP, and today my Gemini journal has more posts that my HTTP journal.

• https://schapps.woodpeckersnest.eu/ (was intended to be the main source)
• gemini://woodpeckersnest.space/~schapps/journal.gmi (the actual main source)

NEX, which I did not try yet, might be worthy too https://nightfall.city/nex/info/specification.txt

[thp]

You can use a shell job to run text-mode clients (presumably the "CLI" ones there would work, but the "TUI" ones might not) for these protocols, no need to pack all different protocols into urlwatch.

As written a few years ago, I think it's not so much the protocols that matter, it's the content. In fact, your HTTPS-served pages are totally fine (no bloat), so no need for a special protocol and special clients.

Just fix up your journal site so that the content on the HTTPS and Gemini site are synchronised, no need to have different content over different protocols if you want to be interoperable :)

Happy to accept patches for the documentation that has recommendations for text-mode clients for Gemini, Gopher and NEX that work fine with the shell job (probably for the Advanced Topics section, which is a collection of recipes).

For Gopher, this should work (requires w3m installed):

name: Check a gopher webpage
command: w3m gopher://sdf.org

For NEX, this can work (requires netcat installed):

name: Check a NEX page
command: echo "/" | nc nex.nightfall.city 1900

But really, those newfangled "simple" protocols are perfect for command-line utilities to request a document and print it on stdout as plain text, so perfect for shell-based jobs IMHO (it also allows more choice, and doesn't require us to fixate on a specific client implementation).

[sjehuda]

Thanks!

I will definitely try it.

Actually, I did not mention XMPP.

I suppose that you, as one who is responsible for a bot framework for XMPP, are well aware of XMPP PubSub URI (XEP-0060) and also of Atom Over XMPP (XEP-0277 and XEP-0472) for publishing of content.

My projects are heavily involved with XMPP PubSub and I wouldbe glad to contribute for adding support for XMPP URI with Slixmpp.

https://git.xmpp-it.net/sch