# 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 28
# self = https://watcher.sour.is/conv/qcq7rrq
I _think_ I've pondered this idea before and entertained the idea with y'all.... What if we combined Twtxt and IRC together and integrate them together into the yarnd backend? Conversations would become transparent IRC channels and you could interact with either via Twtxt on your feed(s) or via IRC or both. Private messages would then be possible too via normal IRC facilities. Yarn.social pods would become inter-connected by design and form a "network". Crazy idea? :D
I _think_ I've pondered this idea before and entertained the idea with y'all.... What if we combined Twtxt and IRC together and integrate them together into the yarnd backend? Conversations would become transparent IRC channels and you could interact with either via Twtxt on your feed(s) or via IRC or both. Private messages would then be possible too via normal IRC facilities. Yarn.social pods would become inter-connected by design and form a "network". Crazy idea? :D
@prologic Not crazy. Just trying to wrap my head around the implications. Does it scale? Sounds like, over time, it wouldn't look like a typical IRC server; which doesn't mean that the protocol can't handle it, of course.
@jlj Yeah good questions. Not sure about how it would scale to be honest, but the inter-connections would become sports I guess.
@jlj Yeah good questions. Not sure about how it would scale to be honest, but the inter-connections would become sports I guess.
@prologic You would be building an IRC client. 😛
@prologic You would be building an IRC client. 😛
@adi No not quite. It'd be an IRC server too, but it would also have interesting qualities that would resemble IRC services as well.
@adi No not quite. It'd be an IRC server too, but it would also have interesting qualities that would resemble IRC services as well.
@prologic But not quite IRC as @jlj put it, that would be a problem.
@prologic But not quite IRC as @jlj put it, that would be a problem.
> Sounds like, over time, it wouldn’t look like a typical IRC server

He's right. It wouldn't. If you joined a pod's irc endpoint that's all you'd be an anonymous participant. Although... There's no reason the IRC endpoint couldn't enforce SASL auth requiring an account on the pod in the first place. I'm not sure either of you see what I'm seeing as a potential marrying of the two mediums 🤔
> Sounds like, over time, it wouldn’t look like a typical IRC server\n\nHe's right. It wouldn't. If you joined a pod's irc endpoint that's all you'd be an anonymous participant. Although... There's no reason the IRC endpoint couldn't enforce SASL auth requiring an account on the pod in the first place. I'm not sure either of you see what I'm seeing as a potential marrying of the two mediums 🤔
> Sounds like, over time, it wouldn’t look like a typical IRC server

He's right. It wouldn't. If you joined a pod's irc endpoint that's all you'd be an anonymous participant. Although... There's no reason the IRC endpoint couldn't enforce SASL auth requiring an account on the pod in the first place. I'm not sure either of you see what I'm seeing as a potential marrying of the two mediums 🤔
Maybe... It has something to do with the number of times I've written IRC servers and services before. e.g: https://git.mills.io/prologic/eris
Maybe... It has something to do with the number of times I've written IRC servers and services before. e.g: https://git.mills.io/prologic/eris
@prologic I would like to see some basic features rolled out before inventing new stuff. Like getting a search engine up and running, so we can build filtering features for improving the UI and UX.
Also the flow/speed of conversation (the social act, not the yarn-feature) on twtxt vs. IRC is radically different. IRC is ephemeral chatting and twtxt is microbloging at its cores.
@prologic I would like to see some basic features rolled out before inventing new stuff. Like getting a search engine up and running, so we can build filtering features for improving the UI and UX.\nAlso the flow/speed of conversation (the social act, not the yarn-feature) on twtxt vs. IRC is radically different. IRC is ephemeral chatting and twtxt is microbloging at its cores.
@darch Yeah you’re right actually 😂 Thanks for being the voice of reason 🤗
@darch Yeah you’re right actually 😂 Thanks for being the voice of reason 🤗
@prologic @darch @xjix What's that homebrew tw.txt/yarn pod you're writing? Is that another server than yarnd?
@prologic @darch @xjix What's that homebrew tw.txt/yarn pod you're writing? Is that another server than yarnd?
@adi Shat do you mean? 🤔
@adi Shat do you mean? 🤔
@prologic You are welcome :)
@prologic @darch Ha ha. Yeah, a good point, indeed. :-)
@xjix @darch @prologic Just examined your source code, pretty cool, will have to dig in tho. Used https://www.marmaladefoo.com/pages/geminaut to get there. Maybe you might consider taking a look at my static site generator https://mkws.sh/
@xjix @darch @prologic Just examined your source code, pretty cool, will have to dig in tho. Used https://www.marmaladefoo.com/pages/geminaut to get there. Maybe you might consider taking a look at my static site generator https://mkws.sh/