hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt

@soren@darch.dk you reach out and tell them to set a nick? Or parse the URL, and use the word right after the tilde as the nick?

@sorenpeter@darch.dk I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by all clients for display purposes.

@sorenpeter@darch.dk @bender@twtxt.net @prologic@twtxt.net Right. Also, generally speaking, if you come across a new feed URL, it’s probably either via some mention in another feed or the User-Agent in your access log. Both cases typically advertise also a display name. So, you just reuse whatever you’ve seen there.

@sorenpeter@darch.dk Here are two more cases:

• nick = subdomain: https://aelaraji.com/timeline/profile?url=https://lyse.isobeef.org/twtxt.txt -> lyse.isobeef.org
  
• nick = second level domain: https://aelaraji.com/timeline/profile?url=https://aelaraji.com/twtxt.txt -> aelaraji.com

@aelaraji@aelaraji.com domains/subdomains I think are much harder to “standardize” hmmm 🤔

@prologic@twtxt.net No I’m not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter@darch.dk already did with the nick = domain case. (unless I’m missing the point)