@lyse How does `tt` handle feeds with multiple sources for the same “nick”? 🤔

@prologic (#kjjdgua) I just use a different nick for different URLs. :-D The thing is that I'm still using the reference `twtxt` implementation under the hood, so there's no way around.

…e (#kjjdgua) Yeah `yarnd` is too. But maybe we _shoudl_ change this? It's probably client specific though? I _think_ there's a difference between the set of specs that form a set of valid and useful f…

…gic (#kjjdgua) The only real stable and unique thing is the feed URL (if we ignore moving to other servers for now). So ideally a URL is mapped to a nick but not the other way around. At least not in …

…gic (#kjjdgua) If I'm not mistaken the twtxt spec doesn't mention anything that nicks must be unique. It also doesn't claim the oppsite. Only the implemention makes the assumption, that nicks are uniq…

…gic (#kjjdgua) Maybe we need a third entity here to reason about nicks and URLs. For now call it the identity. If a nick resolves to multiple URLs, is it the same feed? Same as in by the same author o…

…#kjjdgua) With so many new pods podding up right now it would make sense to have a standard for identity consisting of a (optional?) nick and the URL to the actual feed. it is already visual present o…

@lyse (#kjjdgua) Agreed a list here is better and a simple change 👌

…#kjjdgua) Also turns out at least on `yarnd` you can follow a "person" who _might_ have multiple feeds like @adi and @old_adi (_as long as you name them differently, as the mapping here is `nick -> ur…

@prologic (#kjjdgua) Yeah I found that out just before by adding his twtxt.net feed as "adi2"