# 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 21
# self = https://watcher.sour.is/conv/pgrkgwq
prologic
twtxt.net
View Thread
Glossary - yarn - Mills

Trying to define a gloosary of terms for Yarn.social, feedback welcome πŸ€—
prologic
twtxt.net
View Thread
Glossary - yarn - Mills

Trying to define a gloosary of terms for Yarn.social, feedback welcome πŸ€—
darch
twtxt.net
View Thread
- l would loose the twt and just call it a post and Root post
- Call a conversation for a conversation or thread instead of inventing new words like yarn - I like the name Yarn for the software, but i would use normal words in the UI etc.
- This is a Post box, so Post box should be called Input box, Post form or maybe Compose form
fastidious
arrakis.netbros.com
View Thread
@darch to define Yarn, and set it apart, those aren’t good recommendations. A single post on Yarn is called a twt. A bunch of replies to a twt is called a yarn (not capitalised). Any given twt, but a top one, can be forked into a separate yarn. The compose form has been called a post box (for now).

We are not naming things following a semantic web. We are inventing, or adapting, new terms.
prologic
twtxt.net
View Thread
@fastidious I'm with David on this one sorry @darch πŸ‘Œ The point is we actually are making a point of difference here really in many ways. So we should be clear on what those differences are. They happen to also relate to the underlying "tech" too, or "file format / spec" that is used too. πŸ‘Œ
prologic
twtxt.net
View Thread
@fastidious I'm with David on this one sorry @darch πŸ‘Œ The point is we actually are making a point of difference here really in many ways. So we should be clear on what those differences are. They happen to also relate to the underlying "tech" too, or "file format / spec" that is used too. πŸ‘Œ
darch
twtxt.net
View Thread
yes I agree we should define Yarn, but what we are building is not that special to the end users, who I images will just be confused about what twt, yarn, thooth etc. are. compare to using familiar words like post and tread. Tread also binds nicly with the yarn as a overall concept :)
For the technical layer, then yes, we should have a vocabulary that can be closer to the "metal", but not in the UI
prologic
twtxt.net
View Thread
@darch Yes but what about "Tweet" and "Twitter". "Google". ALl these things have become common language over time time. None of these were every in any "standard dictionary" or "language" until they were created. So I don't _really_ quite agree with you here. We _should_ use Yarn and Twt as terms because there are aspects of what we've created that are strong differentiators.
prologic
twtxt.net
View Thread
@darch Yes but what about "Tweet" and "Twitter". "Google". ALl these things have become common language over time time. None of these were every in any "standard dictionary" or "language" until they were created. So I don't _really_ quite agree with you here. We _should_ use Yarn and Twt as terms because there are aspects of what we've created that are strong differentiators.
prologic
twtxt.net
View Thread
For example:

- Yarns are short-lived and deliberately fall off the "Active Cache" on purpose.
- Yarn.social (_the platform and pods_) are difficult to abuse.
- The ecosystem is decentralised twtxt and yarnd is distributed.

And so forth... There are a few other properties, but I won't list them all here...
prologic
twtxt.net
View Thread
For example:

- Yarns are short-lived and deliberately fall off the "Active Cache" on purpose.
- Yarn.social (_the platform and pods_) are difficult to abuse.
- The ecosystem is decentralised twtxt and yarnd is distributed.

And so forth... There are a few other properties, but I won't list them all here...
prologic
twtxt.net
View Thread
And btw... Just to illustrate the point about "Yarn"

=> LMGTFY - Let Me Google That For You

I _realize_ it's not as common in non-English speaking countries, but that's okay πŸ˜… I _doubt_ "Google" was but here we are today, it's a household term, it's a verb, etc πŸ‘Œ=
prologic
twtxt.net
View Thread
And btw... Just to illustrate the point about "Yarn"

=> LMGTFY - Let Me Google That For You

I _realize_ it's not as common in non-English speaking countries, but that's okay πŸ˜… I _doubt_ "Google" was but here we are today, it's a household term, it's a verb, etc πŸ‘Œ=
darch
twtxt.net
View Thread
@prologic we also say to google stuff in Danish, so it's not a all uncommon outside the anglosphere. I just want to keep things simple and familiar to new users and not having a barrier of slang to overcome.

So is the idea with the Glossary to be technical documentation or what features are called in the end-user exposed UI?
prologic
twtxt.net
View Thread
@darch I understand πŸ€—

> So is the idea with the Glossary to be technical documentation or what features are called in the end-user exposed UI?

No I literally hacked it up this evening because @ullarah suggested (_rightfully so_) that we should have some kind if definition of terms we used. Which I agreed with πŸ‘Œ Nothing in the WIki is really public facing in the sense of the word -- more geared towards Developers, Contributors and Poderators (_another term we seem to be using lately_) really. Keep on Yarn'n πŸ˜…
prologic
twtxt.net
View Thread
@darch I understand πŸ€—

> So is the idea with the Glossary to be technical documentation or what features are called in the end-user exposed UI?

No I literally hacked it up this evening because @ullarah suggested (_rightfully so_) that we should have some kind if definition of terms we used. Which I agreed with πŸ‘Œ Nothing in the WIki is really public facing in the sense of the word -- more geared towards Developers, Contributors and Poderators (_another term we seem to be using lately_) really. Keep on Yarn'n πŸ˜…
lyse
lyse.isobeef.org
View Thread
@prologic So in my opinion it's very problematic that "yarn" names both a "single twt" and a whole "twt conversation". That's not very helpful to distinguish between both.
fastidious
arrakis.netbros.com
View Thread
@lyse I agree about yarn, and its usage for both, single and conversation. I rather keep twt for a singular entry, and yarn for a collection of twts on a related topic (aka conversation).
lyse
lyse.isobeef.org
View Thread
@fastidious Exactly, that's been also my "yarn" usage I think.
prologic
twtxt.net
View Thread
That's fine πŸ‘Œ
prologic
twtxt.net
View Thread
That's fine πŸ‘Œ