Actually on second thoughts... I _think_ the "following" system is fine the way it is. A mapping of `alias` to `url`. I'm now following @eldersnake from three different sources 🤣
matched #jgi4ypa score:12.5 Search by:
matched #jgi4ypa score:12.5 Search by:
(#jgi4ypa) I'm basically doing it like this:
```
$ curl -qso - https://twtxt.net/~prologic/twtxt.txt | grep '^# follow.*eldersnake'
# follow = eldersnake@twtxt.net https://twtxt.net/user/eldersnake/twtxt.txt
# follow = eldersnake@we.loveprivacy.club https://we.loveprivacy.club/user/eldersnake/twtxt.txt
# follow = eldersnake@yarn.andrewjvpowell.com https://yarn.andrewjvpowell.com/user/eldersnake/twtxt.txt
```
So I _think_ just prompting the user to rename a conflicting feed to another alias is probably fine....
matched #jyuyoya score:12.5 Search by:
Search by 1 tags:
(#jgi4ypa) In the meantime I can automatically create the keys for aliases to be `@nick@domain` so there is less chance of collision in the first place, improving the overall user experience.
matched #niaujfa score:12.5 Search by:
Search by 1 tags:
(#jgi4ypa) I like it! Less work to refactor, I'm sure, and also Just Works. As you say, a prompt or something at least is probably all that is needed.
matched #e44hriq score:12.5 Search by:
Search by 1 tags:
@eldersnake (#jgi4ypa) Yup ☺️
matched #pormxwq score:12.5 Search by: