# 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 18
# self = https://watcher.sour.is/conv/2xsbljq
@prologic uh... how can I view all posts from account? as example from @news I can see only one recent post
@nexeq This is not possible at this time, due to deliberate / on-purpose design decision. cc @mutefall Plese help me explain this to our new friend 😅
@nexeq This is not possible at this time, due to deliberate / on-purpose design decision. cc @mutefall Plese help me explain this to our new friend 😅
@prologic i may need to write a document on this.

@nexeq there's a couple of ways to look at this. first your feed is what you make it. based on whom you follow. there's also this concept which i don't think has been officially named, but the idea is the a timeline such as in a timeseries moves along as life does. thus what you see today may not be here next week
@nexeq given lightweight nature of yarnd and the twtxt protocol in general relying on a text file and a cache layer, a poderator who would desire to have n(x) timeline (i.e. all tweets from 2017 to today) would have to invest heavily in infrastructure and the protocol twtxt and client yarnd would have to be redesigned from the ground up.

now that being said, let's say there's a post that turns into a yarn and people respond to it frequently it may be more prevalent and show up in your feed if you are indeed engaged in said yarn.
@nexeq thus you can consider the feed of tweets pseudo-ephemeral in nature in that as time progresses so do does content.

i hope this makes some sense. at first i didn't understand it until i read the techspec and tore apart the client code then it was a this is brilliant moment.

there's quite a bit of philosophical thought that goes into how things work here. this is not twitter, and that's by design.
@mutefall Thank you for your thoughts on this and your write-ups! 👌 I couldn't have said any of this better myself, and I _really_ wanted someone else's unbiased perspective on this as they've gone through it. Thanks! 🙇‍♂️

I will reiterate that many of the design decisions made are in fact quite deliberate and philosophical in nature and learn towards "how do we make a better more human social media" and "how do we make it as real and down to earth" as possible, "more human" friendly.
@mutefall Thank you for your thoughts on this and your write-ups! 👌 I couldn't have said any of this better myself, and I _really_ wanted someone else's unbiased perspective on this as they've gone through it. Thanks! 🙇‍♂️

I will reiterate that many of the design decisions made are in fact quite deliberate and philosophical in nature and learn towards "how do we make a better more human social media" and "how do we make it as real and down to earth" as possible, "more human" friendly.
@prologic

there's an ancillary note to take into consideration. post-arpa days (1987..1994) if one wanted, one could reach the end of the internet. in those days backhauls were t1 and the data contained within the internet could be held on a hard drive.

twtxt/yarn in general allows me to reach the end. at least for the day. there's no infinite feeds to overwhelm the visitor which in my view is quite nice compared to the endless pit that is the current state of the web.

we are very very small. but we are profoundly capable of very very big things. --hawking
@mutefall This is also well said ! 👌 I like it, and you're absolutely right. Under no circumstances will we ever fall into the gawd awful trap of "timeline manipulation" beyond sorting by time and hash or rendering as trees (as is the case in some clients already).

Not only should there be an end, the "system" should forget as we "humans" do. Yes we will bring in builtin search to yarnd so you _can_ search the archives if you want to, but that _should_ be your choice to do so, sort of like:

> Hmm, let me think about that for a minute and try to remember!
@mutefall This is also well said ! 👌 I like it, and you're absolutely right. Under no circumstances will we ever fall into the gawd awful trap of "timeline manipulation" beyond sorting by time and hash or rendering as trees (as is the case in some clients already).

Not only should there be an end, the "system" should forget as we "humans" do. Yes we will bring in builtin search to yarnd so you _can_ search the archives if you want to, but that _should_ be your choice to do so, sort of like:

> Hmm, let me think about that for a minute and try to remember!
I should also add to this Yarn that there is a long-list of things to avoid that are "hard lines" in terms of what Yarn.social is, what it should be and what it will be (the specs, the ecosystem, etc):

- It should be hard to abuse
- no one person's opinion is more important than another (top heavy posters, popular people, people in so-called "positions of power", etc)
- it should be your choice to post an opinions or share an idea or thought (not the other way around)
I should also add to this Yarn that there is a long-list of things to avoid that are "hard lines" in terms of what Yarn.social is, what it should be and what it will be (the specs, the ecosystem, etc):

- It should be hard to abuse
- no one person's opinion is more important than another (top heavy posters, popular people, people in so-called "positions of power", etc)
- it should be your choice to post an opinions or share an idea or thought (not the other way around)
and of course the obvious:

- it should be decentralised
- it should be easily self-hostable
- it should be easy to operate
- it should be easy to use

and above all:

- there shall never be any tracking of user data or user behaviour
- there shall be no advertising whatsoever
- there shall be no corporate or political interests or influence

Yarn.social should remain free (as in beer), open source, open and transparent.

I _hope_ it remains this way as we continue to grow! 🤞
and of course the obvious:

- it should be decentralised
- it should be easily self-hostable
- it should be easy to operate
- it should be easy to use

and above all:

- there shall never be any tracking of user data or user behaviour
- there shall be no advertising whatsoever
- there shall be no corporate or political interests or influence

Yarn.social should remain free (as in beer), open source, open and transparent.

I _hope_ it remains this way as we continue to grow! 🤞
This is a very direct and understandable answer to the question, from both of you. At risk of irony, I think one of you should copy this thread and host it somewhere permanently so we can reference it later. I would, but I wasn't involved in the conversation.
@mckinley It's okay, one just need to bookmark the Root Twt. Since all Twts and Yarns are content-addressable, it is not hard to bring this back up 👌
@mckinley It's okay, one just need to bookmark the Root Twt. Since all Twts and Yarns are content-addressable, it is not hard to bring this back up 👌