The better thing is probably to pull the desired nick from metadata comments, but not everyone has it and usage frequency is still interesting on its own.
#b2t4avq
xandkar
@xandkar.net
Follow
Block / Report User
If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!
You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.
@xandkar does not follow you (they may not see your replies!)
Recent Twts
Recent twts from xandkar
#b2t4avq
Updated and renamed peer set files: https://xandkar.net/twtxt/peers/ The superset is all.txt and the verified subset is downloaded-and-parsed.txt
#vvdje7a
Tracking current/correct nicks was getting confusing, so I added a nick usage frequency count pass to the crawler, which also corrects a URL’s nick to the one most-frequently mentioned for that URL. The collected nick data per (encoded) URL is here: https://xandkar.net/twtxt/nicks/seen/
#k7i5tna
@movq@www.uninformativ.de logrotate feels like the right solution. Just need the client support and a convention for where to host the archives.
#uucw4ja
Added deduping by URI, which trimmed the unverified set to 1244 and verified to 583: https://xandkar.net/twtxt/ . Still more refining to do, but it’s starting to look more reasonable now. H/T: @lyse@lyse.isobeef.org
#m2y32la
(#thttegq) Added my current peer set files here: https://xandkar.net/twtxt/
#z7omtvq
(#thttegq) Perhaps because I’m not limiting to just twtxt.net? I seeded with initial peers manually and from there keep spidering out to mentions. Also, there may still be dupes which differ only in nick and/or some alias URI that leads to the same place - need to design a de-dupping pass…
#oer7htq
(#thttegq) If a peer’s URI is downloaded with 200 and at least one message is parsed from it - a peer gets the “verified” badge.
#i3zniqq
Hey @prologic@twtxt.net! Been busy with work and family and what not. How’s it going? Also see my previous message.
#sfpei3q
Sorry if I missed replying to you. Besides time constraints, my client is currentl stupid and does not accumulate messages - if you trimmed your timeline - I lost the trimmed messages forever. I might work on improving this over the winter vacation.
#mcjcp4a
Finally added validation to discovered peers! The list of now-VERIFIED, discovered peers, with at least one valid message is now at 703 (out of the 1449 unverified - a lot of garbage mentions are out there). https://xandkar.net/twtxt/peers.txt
#thttegq