# type = bot and optionally # retention = N so that feeds like @tiktok work like they did before, and... Updated some internal metrics in yarnd to be IMO "better", with queue depth, queue time and last processing time for feeds.
$ bat https://twtxt.net/twt/edgwjcq | jq '.subject'
"(#yarnd)"
hahahahaha ๐คฃ Does your client allow you to do this or what? ๐ค
jenny, tt or any other client where fetches are driven by user interactions of invoking the app. What do we call this type of client? Hmmm ๐ค Then I can tell who uses yarnd because they are "seen" more frequently ๐คฃ
I'll think about doing this too, but I have to do it carefully so as not to cost too much in terms of resources or performance...
- Drift into Failure: From Hunting Broken Components to Understanding Complex Systems by Sidney Dekker (2011)
- Engineering a Safer World by Nancy Leveson (2011)
The former I haven't read. The later I haven't finished reading ๐
- asynchronous evolution
- drift into failure
yarnd: pods establish cryptographic identities, exchange signed /info and /twt payloads with signature verification, ensuring authenticity, integrity, and spoof-proof identity validation across the distributed network.
cacher branch? ๐ค It is recommended you take a full backup of you pod beforehand, just in case. Keen to get this branch merged and to cut a new release finally after >2 years ๐คฃ
yarnd ๐คฃ Nice! ๐
twtxt.net feels very clear of late hmmm ๐ง This is good right? ๐
. in nicknames and then expect to be able to to end a mention with a . ๐คฆโโ๏ธ
sqlite> select count(distinct(nick)) from twters where nick like '%.%';
count(distinct(nick)) = 5
sqlite> select distinct(nick) from twters where nick like '%.%';
nick = @marado@ciberlandia.pt
nick = eapl.me
nick = eapl.mx
nick = grumpygordie.great-site.net
nick = @chyrp.doesnm.cc
. (_period_) in their # nick ๐คฃ tbh I _think_ nick(s) should have rules of what they can and cannot be comprised of. i.e: no punctuation ๐คฆโโ๏ธ
> as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.
I _think_ this is because we probably need to start thinking about three different aspects to the ecosystem and document them out:
- Specifications (_as they are now_)
- Server recommendations (_e.g: Timeline, yarnd, etc_)
- Client recommendations (_e.g: jenny, tt, tt2, twet, etc_)
> what is twtxt for you?
For me Twtxt is just the underlying format that Yarn.social builds upon ๐