# 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 13
# self = https://watcher.sour.is/conv/ooxps7q
So... Here's a thought...

> If [Matrix] is built on a decentralised/distributed event syncing and a basic model of "Room"

And:

> IRC is a centralised text based protocols with client to server and server to server networking and a basic model of "Channels" and "Users"

Then:

> Yarn.social can build a "Chat" system based on the already existing and established decentralised/distributed syncing of feeds with a model of well umm feeds

🤔 🤣
So... Here's a thought...

> If [Matrix] is built on a decentralised/distributed event syncing and a basic model of "Room"

And:

> IRC is a centralised text based protocols with client to server and server to server networking and a basic model of "Channels" and "Users"

Then:

> Yarn.social can build a "Chat" system based on the already existing and established decentralised/distributed syncing of feeds with a model of well umm feeds

🤔 🤣
@prologic I mean, sure, so long as it's fully e2ee and private (Yarn and feeds in general tend to be public...) 😄
@caesar That is true (public), that's by design, we're very open about that. Transparency. microBlogging and sharing your thoughts and opinions is the same as full blogging on your website. It _should_ be open and transparent.

However if we get get Encrypted Feeds off the ground (needs people to help contribute to the spec!) who knows? 🤷‍♂️ Maybe it'll open other other interesting possibilities? 🤔
@caesar That is true (public), that's by design, we're very open about that. Transparency. microBlogging and sharing your thoughts and opinions is the same as full blogging on your website. It _should_ be open and transparent.

However if we get get Encrypted Feeds off the ground (needs people to help contribute to the spec!) who knows? 🤷‍♂️ Maybe it'll open other other interesting possibilities? 🤔
@prologic I think it would be nice to have p2p entangled yarn would be nice. And with entangled I mean encrypted. "Entangled Yarns" how does that sound?
@carsten It's certainly a possibility. Folks like @xuu @david and I are in support of this. It requires more eyes on the spec though to make sure we don't royally fuck it up security-wise. Once we complete the spec, someone will have to build implementations for it 👌
@carsten It's certainly a possibility. Folks like @xuu @david and I are in support of this. It requires more eyes on the spec though to make sure we don't royally fuck it up security-wise. Once we complete the spec, someone will have to build implementations for it 👌
Why do we need to build chat into yarn? Can't you just run a matrix server and yarn pod on the same domain and be done with it?
@darch That's my approach, yep 👍 – but I can also see @prologic's argument that Matrix is over-engineered and current servers are resource hogs and (arguably) hard to get set up...
@darch I understand where you're coming from, but we're not doing anything drastic, but we _should_ remain open to ideas and improvements, especially encrypted feeds. The _only_ problem that can arise is that messaging can open up a can of worms and consume the project. That's the risk, and we have to weight up the risks/benefits to the project and community overall 🤗
@darch I understand where you're coming from, but we're not doing anything drastic, but we _should_ remain open to ideas and improvements, especially encrypted feeds. The _only_ problem that can arise is that messaging can open up a can of worms and consume the project. That's the risk, and we have to weight up the risks/benefits to the project and community overall 🤗
@prologic The existence of XEP-0277 doesn't make XMPP a good platform for microblogging. Likewise, I don't think twtxt will make a good chat system. What if yarnd and a separate federated chat server could (optionally) share account information so your Yarn account credentials are used for a Matrix or XMPP account on the same server?