@prologic@twtxt.net the meta info on the top I added manually. it’s following what I have seen from some other twtxt feeds. the new parser will read them.
🧮 USERS:1 FEEDS:6 TWTS:223 BLOGS:1 ARCHIVED:23273 CACHE:9748 FOLLOWERS:8 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:222 BLOGS:1 ARCHIVED:23273 CACHE:9683 FOLLOWERS:8 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:221 BLOGS:1 ARCHIVED:23273 CACHE:9659 FOLLOWERS:8 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:220 BLOGS:1 ARCHIVED:23273 CACHE:9636 FOLLOWERS:8 FOLLOWING:31
FOLLOW: @xuu@txt.sour.is from @jlj@ctrl-c.club using twtxt/1.2.3
FOLLOW: @xuu@txt.sour.is from @adi@46.23.94.13 using twtxt/0.1.0@7098fcf
🧮 USERS:1 FEEDS:6 TWTS:216 BLOGS:1 ARCHIVED:23273 CACHE:9623 FOLLOWERS:6 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:215 BLOGS:1 ARCHIVED:23259 CACHE:9560 FOLLOWERS:6 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:214 BLOGS:1 ARCHIVED:23201 CACHE:9488 FOLLOWERS:6 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:213 BLOGS:1 ARCHIVED:23201 CACHE:9459 FOLLOWERS:6 FOLLOWING:31
FOLLOW: @stats@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@9d7b86c
🧮 USERS:1 FEEDS:6 TWTS:204 BLOGS:1 ARCHIVED:23201 CACHE:9414 FOLLOWERS:6 FOLLOWING:31
@lyse@lyse.isobeef.org @prologic@twtxt.net very curious… i worked on a very similar track. i built a spider that will trace off any follows =
comments and mentions from other users and came up with:
twters: 744
total: 52073
🧮 USERS:1 FEEDS:6 TWTS:201 BLOGS:1 ARCHIVED:21891 CACHE:7262 FOLLOWERS:6 FOLLOWING:31
Disadvantage of twtxt: less incentives to reply to people since it’s not certain they’ll ever see it. My current solution to that is to follow everybody on the we-are-twtxt and only unfollow if they twt a lot of stuff I’m not interested in
FOLLOW: @xuu@txt.sour.is from @niplav@niplav.github.io using txtnish/0.2
🧮 USERS:1 FEEDS:6 TWTS:199 BLOGS:1 ARCHIVED:21891 CACHE:7242 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:198 BLOGS:1 ARCHIVED:21891 CACHE:7237 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:197 BLOGS:1 ARCHIVED:21891 CACHE:7288 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:195 BLOGS:1 ARCHIVED:21891 CACHE:7239 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:194 BLOGS:1 ARCHIVED:21891 CACHE:7220 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:193 BLOGS:1 ARCHIVED:21874 CACHE:7129 FOLLOWERS:5 FOLLOWING:31
Umeshism: If you can follow your own ethical rules, your own ethical rules are not demanding enough.
🧮 USERS:1 FEEDS:6 TWTS:192 BLOGS:1 ARCHIVED:21874 CACHE:7108 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:191 BLOGS:1 ARCHIVED:21870 CACHE:7050 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:188 BLOGS:1 ARCHIVED:21817 CACHE:6745 FOLLOWERS:5 FOLLOWING:31
🧮 USERS:1 FEEDS:6 TWTS:185 BLOGS:1 ARCHIVED:21812 CACHE:6647 FOLLOWERS:5 FOLLOWING:30
🧮 USERS:1 FEEDS:6 TWTS:184 BLOGS:1 ARCHIVED:21812 CACHE:6441 FOLLOWERS:5 FOLLOWING:30
FOLLOW: @xuu@txt.sour.is from @lyse@lyse.isobeef.org using twtxt/1.2.3
🧮 USERS:1 FEEDS:6 TWTS:182 BLOGS:1 ARCHIVED:21812 CACHE:6424 FOLLOWERS:4 FOLLOWING:30
🧮 USERS:1 FEEDS:6 TWTS:181 BLOGS:1 ARCHIVED:21812 CACHE:6172 FOLLOWERS:4 FOLLOWING:30
🧮 USERS:1 FEEDS:6 TWTS:180 BLOGS:1 ARCHIVED:21812 CACHE:6144 FOLLOWERS:4 FOLLOWING:30
🧮 USERS:1 FEEDS:6 TWTS:173 BLOGS:1 ARCHIVED:21812 CACHE:6068 FOLLOWERS:4 FOLLOWING:29
🧮 USERS:1 FEEDS:6 TWTS:172 BLOGS:1 ARCHIVED:21812 CACHE:6104 FOLLOWERS:4 FOLLOWING:29
🧮 USERS:1 FEEDS:6 TWTS:170 BLOGS:1 ARCHIVED:21812 CACHE:6098 FOLLOWERS:4 FOLLOWING:29
🧮 USERS:1 FEEDS:6 TWTS:168 BLOGS:1 ARCHIVED:21812 CACHE:6044 FOLLOWERS:4 FOLLOWING:29
🧮 USERS:1 FEEDS:6 TWTS:167 BLOGS:1 ARCHIVED:21789 CACHE:4656 FOLLOWERS:4 FOLLOWING:29
🧮 USERS:1 FEEDS:6 TWTS:164 BLOGS:1 ARCHIVED:21789 CACHE:4645 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:157 BLOGS:1 ARCHIVED:21789 CACHE:4519 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:155 BLOGS:1 ARCHIVED:21789 CACHE:4482 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:152 BLOGS:1 ARCHIVED:21789 CACHE:4473 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:149 BLOGS:1 ARCHIVED:21789 CACHE:3307 FOLLOWERS:4 FOLLOWING:28
@prologic@twtxt.net 😁 that is me testing locally. does it notify you somehow when I follow?
🧮 USERS:1 FEEDS:6 TWTS:142 BLOGS:1 ARCHIVED:21789 CACHE:2748 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:138 BLOGS:1 ARCHIVED:21789 CACHE:2736 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:85 BLOGS:1 ARCHIVED:21789 CACHE:2498 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:80 BLOGS:1 ARCHIVED:21767 CACHE:438 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:67 BLOGS:1 ARCHIVED:19880 CACHE:947 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:63 BLOGS:1 ARCHIVED:16769 CACHE:985 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:52 BLOGS:1 ARCHIVED:16684 CACHE:973 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:50 BLOGS:1 ARCHIVED:16641 CACHE:972 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:49 BLOGS:1 ARCHIVED:16571 CACHE:971 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:48 BLOGS:1 ARCHIVED:16296 CACHE:932 FOLLOWERS:4 FOLLOWING:28
🧮 USERS:1 FEEDS:6 TWTS:45 BLOGS:1 ARCHIVED:14928 CACHE:700 FOLLOWERS:4 FOLLOWING:24
🧮 USERS:1 FEEDS:6 TWTS:41 BLOGS:0 ARCHIVED:14905 CACHE:675 FOLLOWERS:4 FOLLOWING:23
FOLLOW: @xuu@txt.sour.is from @vain@www.uninformativ.de using twtrd/latest
🧮 USERS:1 FEEDS:3 TWTS:39 BLOGS:0 ARCHIVED:8028 CACHE:504 FOLLOWERS:3 FOLLOWING:18
🧮 USERS:1 FEEDS:3 TWTS:31 BLOGS:0 ARCHIVED:3793 CACHE:418 FOLLOWERS:3 FOLLOWING:15
🧮 USERS:2 FEEDS:3 TWTS:30 BLOGS:0 ARCHIVED:3787 CACHE:413 FOLLOWERS:4 FOLLOWING:15
@prologic@twtxt.net this is a go version of Keyoxide.org that runs all server side. which is based on work from https://metacode.biz/openpgp/
OpenPGP has a part of the self signature reserved for notatinal data. which is basically a bunch of key/values.
this site tries to emulate the identity proofs of keybase but in a more decentralized/federation way.
my next steps are to have this project host WKD keys which is kinda like a self hosting of your pgp key that are also discoverable with http requests.
then to add a new notation for following other keys. where you can do a kind of web of trust.
🧮 USERS:2 FEEDS:3 TWTS:11 BLOGS:0 ARCHIVED:3542 CACHE:296 FOLLOWERS:4 FOLLOWING:16
FOLLOW: @xuu@txt.sour.is from @admin@29e5c8c72192.ngrok.io using twtxt/0.1.0@f654e6f
FOLLOW: @foo@txt.sour.is from @foo@txt.sour.is using twtxt/0.1.0@9fdcb47
FOLLOW: @xuu@txt.sour.is from @lyxal@twtxt.net using twtxt/0.1.0@9fdcb47
FOLLOW: @xuu@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@9fdcb47
🧮 USERS:1 FEEDS:3 TWTS:3 BLOGS:0 ARCHIVED:3162 CACHE:237 FOLLOWERS:1 FOLLOWING:9
FOLLOW: @twtxt@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@b62883f
Discovered some new twtxt followers by glancing at my web server logs.. Feeling so l33t now.
@mdosch@mdosch.de I thought it was a nice practice to share interesting twtxt-ers through a follow tweet
@sdk@codevoid.de you know the more I think about it, it might make sense to have it the twtxt file. It would just need to be a comment line something like “#follows sdk gopher://codevoid.de/0/tw.txt” on a single line. That way it would be easy to parse out those follows by finding the #follows.
@sdk@codevoid.de That’s an interesting thought. I Know most are text files but at one time there was someone that used a python CGI Script. That person would have had to make a script for the follows.
@freemor@freemor.homelinux.net I thought so too. Color me surprised when I surveyed my follow programmers in my dept and only 3 out 12 knew what I was talking about.
So since Mastodon was mentioned a few times, I’m trying that out. Any recommendations on people to follow?
Re: support for other protocols, it seems like twtxt would be pretty easily adapted to work over the p2p file network DAT, though it’d need client support for DAT or some way to follow people via files and sync in the background, which might be simpler for clients to support but would still require changes to most clients.
@tdemin@tdemin.github.io good points, though another that I’ve noticed is that it’s difficult to tell who in your network is actually reachable with your tweets. My HTTPS cert went unupdated for a brief while and now I have no idea who is still following me since I got it working again, so it’s difficult to tell where I can really have a conversation. A centralized service can tell who’s following who, but that’s basically impossible in twtxt.
When it comes to performance issues, I honestly think the solution is just “don’t follow so many people”. You only pull the feeds you read, and once one’s feeds are too much for the computer to handle, they’ll almost certainly have far too much content for a person to actually read.
part 3: make ‘tf’ run ‘twtxt follow “$@”’