# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 11
# self = https://watcher.sour.is/conv/gc55n3a
@eapl.me A way to have a more bluesky'ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN
So instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
@eapl.me A way to have a more bluesky'ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN
So instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
@eapl.me A way to have a more bluesky'ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN
So instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
@eapl.me A way to have a more bluesky'ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN
So instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
I'm just having a similar issue with a podcast I just uploaded on Castopod (which supports ActivityPub).
My first thought was creating a subdomain with the name of the podcast mordiscos.eapl.me
Then I watched that the software allows many podcasts in the same domain, so I had to pick a handle:
https://mordiscos.eapl.me/@podcast
So now I have @podcast@mordiscos.eapl.me when this one is 'more correct' @mordiscos@podcast.eapl.me or it could even be @mordiscos.eapl.me
I wasn't aware of all that when I setup Castopod (documentation might improve a lot, IMO)
My point here is that it's something important to think from the start, otherwise is painful to change if it's already being used like that.
I'm just having a similar issue with a podcast I just uploaded on Castopod (which supports ActivityPub).
My first thought was creating a subdomain with the name of the podcast mordiscos.eapl.me
Then I watched that the software allows many podcasts in the same domain, so I had to pick a handle:
https://mordiscos.eapl.me/@podcast
So now I have @podcast@mordiscos.eapl.me when this one is 'more correct' @mordiscos@podcast.eapl.me or it could even be @mordiscos.eapl.me
I wasn't aware of all that when I setup Castopod (documentation might improve a lot, IMO)
My point here is that it's something important to think from the start, otherwise is painful to change if it's already being used like that.
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?
It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as **@domain.tld** instead of **@domain.tld@domain.tld**
For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as **@domain.tld**
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?
It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as **@domain.tld** instead of **@domain.tld@domain.tld**
For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as **@domain.tld**
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?
It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as **@domain.tld** instead of **@domain.tld@domain.tld**
For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as **@domain.tld**
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?
It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as **@domain.tld** instead of **@domain.tld@domain.tld**
For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as **@domain.tld**