# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 5
# self = https://watcher.sour.is/conv/4epqdsa
movq
www.uninformativ.de
View Thread
@prologic That’s the thread, I think:

https://lists.debian.org/gopher-project/2022/10/msg00001.html

Interesting – doesn’t feel hostile to me. (These people aren’t native english speakers, maybe that’s an important factor here?) Then again, I often read the OpenBSD mailing lists and those really are “something else” … 😅 🫤

Also, Hiltjo posted links to gopher://bitreich.org/0/usr/20h/phlog/2020-06-07T18-28-23-863932.md and gopher://bitreich.org/1/scm/sacc. Apparently, the Gopher server geomyidae does have native TLS support now and there’s a couple of clients supporting it, too. I didn’t test it, though. If that works, it’d be quite a bit simpler than what Solène described in her post (the one mentioned by @mckinley – which, to be fair, predates 20h’s phlog entry from 2020).

So I don’t think that things are *that* bleak. 😊

(Is “Gopher + TLS” still “strictly Gopher”? Nah. But neither is using UTF-8 in Gopher pages and a loooooooot of people do that.)

By the way, you sparked a follow-up thread:

https://lists.debian.org/gopher-project/2022/10/msg00012.html
movq
www.uninformativ.de
View Thread
@prologic That’s the thread, I think:

https://lists.debian.org/gopher-project/2022/10/msg00001.html

Interesting – doesn’t feel hostile to me. (These people aren’t native english speakers, maybe that’s an important factor here?) Then again, I often read the OpenBSD mailing lists and those really are “something else” … 😅 🫤

Also, Hiltjo posted links to gopher://bitreich.org/0/usr/20h/phlog/2020-06-07T18-28-23-863932.md and gopher://bitreich.org/1/scm/sacc. Apparently, the Gopher server geomyidae does have native TLS support now and there’s a couple of clients supporting it, too. I didn’t test it, though. If that works, it’d be quite a bit simpler than what Solène described in her post (the one mentioned by @mckinley – which, to be fair, predates 20h’s phlog entry from 2020).

So I don’t think that things are *that* bleak. 😊

(Is “Gopher + TLS” still “strictly Gopher”? Nah. But neither is using UTF-8 in Gopher pages and a loooooooot of people do that.)

By the way, you sparked a follow-up thread:

https://lists.debian.org/gopher-project/2022/10/msg00012.html
movq
www.uninformativ.de
View Thread
@prologic That’s the thread, I think:

https://lists.debian.org/gopher-project/2022/10/msg00001.html

Interesting – doesn’t feel hostile to me. (These people aren’t native english speakers, maybe that’s an important factor here?) Then again, I often read the OpenBSD mailing lists and those really are “something else” … 😅 🫤

Also, Hiltjo posted links to gopher://bitreich.org/0/usr/20h/phlog/2020-06-07T18-28-23-863932.md and gopher://bitreich.org/1/scm/sacc. Apparently, the Gopher server geomyidae does have native TLS support now and there’s a couple of clients supporting it, too. I didn’t test it, though. If that works, it’d be quite a bit simpler than what Solène described in her post (the one mentioned by @mckinley – which, to be fair, predates 20h’s phlog entry from 2020).

So I don’t think that things are *that* bleak. 😊

(Is “Gopher + TLS” still “strictly Gopher”? Nah. But neither is using UTF-8 in Gopher pages and a loooooooot of people do that.)

By the way, you sparked a follow-up thread:

https://lists.debian.org/gopher-project/2022/10/msg00012.html
mckinley
twtxt.net
View Thread
@movq I didn't know Geomyidae supported TLS. That's a little embarrassing, I have a copy of it on my computer.

main.c, line 31:


#ifdef ENABLE_TLS
#include <tls.h>
#endif /* ENABLE_TLS */
mckinley
twtxt.net
View Thread
> Is “Gopher + TLS” still “strictly Gopher”? Nah. But neither is using UTF-8 in Gopher pages and a loooooooot of people do that.

Also, I'm the line endings for just about everything Gopher are CRLF per RFC 1436. I'd be willing to bet that a lot of hand-written gophermaps use LF.