Yarn.social users keep mentioning me as
https://uninformativ.de/twtxt.txt, which is not correct. The
www. is missing. Is there something we can do about that or should I extend my client so that it recognizes this as “me”, too? 😅
@firstname.lastname@example.org I think this is a case of bad data. 😢 My pod in particular has a lot of bad data lying around 😢 I’m not really sure what to realistically do about it, I’ve spoken to @email@example.com a bit about this but I’m not entirely sure…
It’s obviously not me… I’m @-mentioning you correctly, hmmm
@firstname.lastname@example.org @email@example.com Same with me, I often get mentioned as either
https://lyse.isobeef.org (filename missing entirely) or even
http://lyse.isobeef.org (HTTP rather than HTTPS as an added bonus on top).
Also for some reason user agents “yarns/master@19127bf (search.twtxt.net Support: https://search.twtxt.net/support)” and “master@19127bf (+https://search.twtxt.net)” are requesting
/user/lyse/twtxt.txt on my server every hour. This path of course results in a 404. I reckon way in the past someone mentioned me wrongly and the search engine now has my broken URL in its database forever.
I have zero knowledge of this mention completion system in yarnd. I should probably take a look at it. For the search engine some manually maintained normalization rules (or alias rules or whatever you want to call it) are required to fix this. In the simplest case a blacklist would suffice. But some rewriting would have the benefit to be more user-friendly with future features, such as mention search etc.
Feels a bit like the mechanism that fills the cache predates the feed metadata extension, eh? 🤔 (I don’t remember the timeline anymore. 🥴)
@firstname.lastname@example.org It did and it was borrows code from twet initially 😆