# 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 16
# self = https://watcher.sour.is/conv/mfvalvq
Check out the Nex Protocol. It's designed to be even simpler than Gemini and Gopher. What do you think? Could be great to host a twtxt feed on.
@shreyan Interesting 🤔
@shreyan Interesting 🤔
@shreyan Interesting 🤔
It looks a lot like Gopher I guess?
It looks a lot like Gopher I guess?
It looks a lot like Gopher I guess?
@prologic Yup. Was very easy to get Go implementations of both a Client and a Server up and running within 10 minutes.
@shreyan The only problem is that there is no such thing as “plain text”. Is it ASCII? UTF-8? DOS or UNIX line endings? Something else?

.txt or “plain text” are ambiguous terms, I’m afraid. 🫤

Other than that, it looks neat and interesting. 😅
@shreyan The only problem is that there is no such thing as “plain text”. Is it ASCII? UTF-8? DOS or UNIX line endings? Something else?

.txt or “plain text” are ambiguous terms, I’m afraid. 🫤

Other than that, it looks neat and interesting. 😅
@shreyan The only problem is that there is no such thing as “plain text”. Is it ASCII? UTF-8? DOS or UNIX line endings? Something else?

.txt or “plain text” are ambiguous terms, I’m afraid. 🫤

Other than that, it looks neat and interesting. 😅
@shreyan and I'll be quoting a friend:

I'm all for more protocols to move away from the web but pls be original and actually useful
@yakumo_izuru Heh, it looks a little bit like a hackathon project someone might make right after discovering TCP/IP and socket programming
My Go implementation of a server, for the curious: https://github.com/ShreyanJain9/nex-server
Nex is a neat proposal of a hobbyist hypersimple 'protocol' by m15o. The community has created Browsers, proxies and content.
Nex is a neat proposal of a hobbyist hypersimple 'protocol' by m15o. The community has created Browsers, proxies and content.

I've hosted twtxt.txt files on Gemini, but I can't find an advantage for Nix if we already have HTTP 1.1 more than belonging of that niche community 🤔