$ du -h .config/twtxt/cache*.db
13M .config/twtxt/cache2.db # contains read status for each twt (very inefficient format)
7,0M .config/twtxt/cache.db # the actual cache by the original twtxt reference implementation
Yeah, wrong place for caches.
I haven't left the house, so it feels well under air conditioning. In two more hours I will call it quits from the work day, and will have to dash to the grocery to get supplies for tonight's meal (arroz con gandules). I will let you know how it truly feels out there then. :-D
For those swollen fingers, nothing better than a mildly cold shower! Oh, and paws off the keyboard! :-P
I haven't left the house, so it feels well under air conditioning. In two more hours I will call it quits from the work day, and will have to dash to the grocery to get supplies for tonight's meal (arroz con gandules). I will let you know how it truly feels out there then. :-D
For those swollen fingers, nothing better than a mildly cold shower! Oh, and paws off the keyboard! :-P
I have to read up on the twtxt registry documentation on the weekend (too tired at the moment), but it should probably be no real issue to integrate that API into yarnd.
29°C, zero wind, extremely humid, luckily the sun was behind the clouds. I'm soaking wet, sweat ran down in streams and dripped in my eyes, it burned a bit. The sky is getting a little dark, I hope the thunderstorm and rain are really arriving here later. Rain had always been finally cancelled the couple last days.
I'm gotta go cool off my fingers now, they're swollen from the heat.
24056 "prologic"
5103 "lyse"
3932 "movq"
1984 "abucci"
1876 "adi"
1633 "fastidious"
1551 "jlj"
1455 "mckinley"
1413 "offgridliving
1280 "eaplmx"
Some of those I no longer follow, or do not exist, but their wisdom remains. LOL.
24056 "prologic"
5103 "lyse"
3932 "movq"
1984 "abucci"
1876 "adi"
1633 "fastidious"
1551 "jlj"
1455 "mckinley"
1413 "offgridliving
1280 "eaplmx"
Some of those I no longer follow, or do not exist, but their wisdom remains. LOL.
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I don’t really have that in my inbox. 🤔
These are the Top 10, btw:
$ awk '/^From: / { user\n++ } END { for (u in user) { print user\n, u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I don’t really have that in my inbox. 🤔
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I don’t really have that in my inbox. 🤔
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I don’t really have that in my inbox. 🤔
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
$ du -sh ~/Mail/twt
244M /home/user/Mail/twt
But:
$ du -sh --apparent-size ~/Mail/twt
33M /home/user/Mail/twt
There are about 60k twts in there.
Regarding one-way junk: True. Looks like I mostly unfollowed those, I don’t really have that in my inbox. 🤔
These are the Top 10, btw:
$ awk '/^From: / { user[$2]++ } END { for (u in user) { print user[u], u } }' * | sort -k1rn | head -n 10
24020 "prologic"
5269 "lyse"
3928 "movq"
2285 "adi"
1985 "abucci"
1713 "mckinley"
1415 "off_grid_living"
1352 "darch"
1280 "eaplmx"
956 "bender"*
anth http://a.9srv.net/tw.txt
bender https://twtxt.net/user/bender/twtxt.txt
johanbove https://johanbove.info/twtxt.txt
ionores https://twtxt.net/user/ionores/twtxt.txt
lyse https://lyse.isobeef.org/twtxt.txt
mckinley https://twtxt.net/user/mckinley/twtxt.txt
movq https://www.uninformativ.de/twtxt.txt
prologic https://twtxt.net/user/prologic/twtxt.txt
stigatle https://yarn.stigatle.no/user/stigatle/twtxt.txt
thecanine https://twtxt.net/user/thecanine/twtxt.txt
xuu https://txt.sour.is/user/xuu/twtxt.txt
abucci https://anthony.buc.ci/user/abucci/twtxt.txt
soren https://darch.dk/twtxt.txt
aelaraji https://aelaraji.com/twtxt.txt
dbucklin https://www.davebucklin.com/twtxt.txt
falsifian https://www.falsifian.org/twtxt.txt
off_grid https://twtxt.net/user/off_grid_living/twtxt.txt
yarn_police https://twtxt.net/user/yarn_police/twtxt.txt
And the Maildir size is 212MB. What size (not followers list) is yours?
And I just realized: Mutt’s layout helps a lot. Skimming over new twts is really easy and it’s not a big loss if there are a couple of shitposts™ in my “timeline”. This is very different from Mastodon (both the default web UI and all clients I’ve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. 😅
(I mostly only follow Hashtags on Mastodon anyway. It’s more interesting that way.)
And I just realized: Mutt’s layout helps a lot. Skimming over new twts is really easy and it’s not a big loss if there are a couple of shitposts™ in my “timeline”. This is very different from Mastodon (both the default web UI and all clients I’ve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. 😅
(I mostly only follow Hashtags on Mastodon anyway. It’s more interesting that way.)
And I just realized: Mutt’s layout helps a lot. Skimming over new twts is really easy and it’s not a big loss if there are a couple of shitposts™ in my “timeline”. This is very different from Mastodon (both the default web UI and all clients I’ve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. 😅
(I mostly only follow Hashtags on Mastodon anyway. It’s more interesting that way.)
And I just realized: Mutt’s layout helps a lot. Skimming over new twts is really easy and it’s not a big loss if there are a couple of shitposts™ in my “timeline”. This is very different from Mastodon (both the default web UI and all clients I’ve tried), where the timeline is always *huge*. Posts take up a lot of space on screen. Makes me think twice if I want to follow someone or not. 😅
(I mostly only follow Hashtags on Mastodon anyway. It’s more interesting that way.)
st3wsda and it started like this:(#yqke7sq) I've been sketching out some …
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some …
This can’t be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. 😅
st3wsda and it started like this:(#yqke7sq) I've been sketching out some …
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some …
This can’t be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. 😅
st3wsda and it started like this:(#yqke7sq) I've been sketching out some …
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some …
This can’t be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. 😅
st3wsda and it started like this:(#yqke7sq) I've been sketching out some …
When fetching the feed *now*, the twt starts like this and the current twt gets the hash
6mdqxrq:(#yqke7sq) I've been sketching out some …
This can’t be avoided, really. Publishing twts and then editing them is like doing a
git push --force after rewriting the commit history. Chaos will ensue. 😅
Screenshot of Yarn.social showing duplicated headers.
Skill issues aside (since I'm willing to learn), my internet speed is a huge limitation (I have less than 1Mb Up) 🫠 Then again, there's the
Running stuff off of my RPI's SD Card 😅 that's just asking for trouble. Seriously, I should get a proper Job, at least I'll be able to afford my curiosities 🙃
Skill issues aside (since I'm willing to learn), my internet speed is a huge limitation (I have less than 1Mb Up) 🫠 Then again, there's the
Running stuff off of my RPI's SD Card 😅 that's just asking for trouble. Seriously, I should get a proper Job, at least I'll be able to afford my curiosities 🙃
Skill issues aside (since I'm willing to learn), my internet speed is a huge limitation (I have less than 1Mb Up) 🫠 Then again, there's the
Running stuff off of my RPI's SD Card 😅 that's just asking for trouble. Seriously, I should get a proper Job, at least I'll be able to afford my curiosities 🙃
> Does yarnd provide an API for finding twts? Is it similar?
No, it doesn't. But
yarns (_the search engine/crawler wrote_) seems more fitting here. It's been discussed before, the possibility of building a "Twtxt Register v1" compatible API for yarns. I _think_ a search engine + crawler + registry (_especially ones that can form a bit of a "distributed network_) are far more useful I _think_ in order to support the _actual_ decentralised Twtxt / Yarn ecosystem (_which is how I prefer to describe it_).
> Does yarnd provide an API for finding twts? Is it similar?
No, it doesn't. But
yarns (_the search engine/crawler wrote_) seems more fitting here. It's been discussed before, the possibility of building a "Twtxt Register v1" compatible API for yarns. I _think_ a search engine + crawler + registry (_especially ones that can form a bit of a "distributed network_) are far more useful I _think_ in order to support the _actual_ decentralised Twtxt / Yarn ecosystem (_which is how I prefer to describe it_).
Based on the twtxt.net web UI, it seems to be in reply to a twt by @cuaxolotl which begins "I’ve been sketching out...".
But jenny thinks the hash of that twt is 6mdqxrq. At least, there's a very twt in their feed with that hash that has the same text as appears on yarn.social (except with ' instead of ’).
Based on this, it appears jenny and yarnd disagree about the hash of the twt, or perhaps the twt was edited (though I can't see any difference, assuming ' vs ’ is just a rendering choice).
(I also noticed that https://twtxt.readthedocs.io/en/latest/user/registry.html recommends "The registries should sync each others user list by using the users endpoint". If I understood that right, registering with one should be enough to appear on others, even if they don't crawl.)
Does yarnd provide an API for finding twts? Is it similar?
yarnd certainly hasn't).
yarnd certainly hasn't).
On registries however, I think a registry is the wrong approach. I see far greater value in feed crawlers and search engines like the (_half baked one_) I built over at https://search.twtxt.net/
On registries however, I think a registry is the wrong approach. I see far greater value in feed crawlers and search engines like the (_half baked one_) I built over at https://search.twtxt.net/
Say I see a twt beginning (#hash) and I want to look up the start of the thread. Is the idea that if that twt is hosted by a a yarn.social pod, it is likely to know the thread start, so I should query that particular pod for the hash? But what if no yarn.social pods are involved?
The community seems small enough that a registry server should be able to keep up, and I can have a couple of others as backups. Or I could crawl the list of feeds followed by whoever emitted the twt that prompted my query.
I have successfully used registry servers a little bit, e.g. to find a feed that mentioned a tag I was interested in. Was even thinking of making my own, if I get bored of my too many other projects :-)
But when I tried it out on a twt from @prologic, I discovered jenny and yarn.social seem to disagree about the hash of this twt: https://twtxt.net/twt/st3wsda . jenny assigned it a hash of 6mdqxrq but the URL and prologic's reply suggest yarn.social thinks the hash is st3wsda. (And as a result, jenny --fetch-context didn't work on prologic's twt.)
YOU LIVE ON STOLEN LAND GOVERNED BY U.S. CORPORATIONS =3
<u> tag, maybe?
just needed to get out. first run since the PTC and felt great.
#running
just needed to get out. first run since the PTC and felt great.
#running
just needed to get out. first run since the PTC and felt great.
#running