# 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 33
# self = https://watcher.sour.is/conv/bai3sla
@adi Looks good :) I will give mkws a go soon
@lazarus 🤩! What website? Would be cool it's a good fit for you! Let me know how it goes!
@lazarus 🤩! What website? Would be cool it's a good fit for you! Let me know how it goes!
@adi It will be a basic social profile site similar to examples listed on mkws, and with at least a yarn pod :)
I'm a dummy, so I might need some help when I get around to it!
@adi It will be a basic social profile site similar to examples listed on mkws, and with at least a yarn pod :)\n\nI'm a dummy, so I might need some help when I get around to it!
@lazarus Right now you need to only host a twtxt.txt file like this one and an avatar.png like this one sorry @movq I used you as an example 😂 As you can see @movq doesn't even run a Yarn.social pod actually (yarnd); but nonetheless he is part of the network at large because that's what we've built upon, Also note the metadata at the top of his feed, this is also important 👌
@lazarus Right now you need to only host a twtxt.txt file like this one and an avatar.png like this one sorry @movq I used you as an example 😂 As you can see @movq doesn't even run a Yarn.social pod actually (yarnd); but nonetheless he is part of the network at large because that's what we've built upon, Also note the metadata at the top of his feed, this is also important 👌
@prologic @movq How can you specify your handle? Do other sites recognise it depending where the twtxt.txt is located?\n\ne.g. Can I host a pod publicly at yarn.domain.tld but have the yarn handle just as\n @username@domain.tld instead of @username@yarn.domain.tld \n\nI mean, from the perspective of everyone else.\nI realise the profile will still be viewable at yarn.domain.tld/user/username
@prologic @movq How can you specify your handle? Do other sites recognise it depending where the twtxt.txt is located?
e.g. Can I host a pod publicly at yarn.domain.tld but have the yarn handle just as
@username@domain.tld instead of @username@yarn.domain.tld
I mean, from the perspective of everyone else.
I realise the profile will still be viewable at yarn.domain.tld/user/username
@lazarus In plain twtxt, none of this is really specified. 😢 That part of the protocol is not so great. In plain twtxt, *my followers* must configure that the URL https://www.uninformativ.de/twtxt.txt belongs to the username “movq”. So it has to be done manually. 😢 That being said, you can put a # nick = foobar at the top of your feed and *some* clients will pick it up and show this as your nick. All the @username@yarn.domain.tld stuff that you see in Yarn.social is actually just a Yarn convention – maybe @prologic can tell you more about how exactly that works. 🙂
@lazarus In plain twtxt, none of this is really specified. 😢 That part of the protocol is not so great. In plain twtxt, *my followers* must configure that the URL https://www.uninformativ.de/twtxt.txt belongs to the username “movq”. So it has to be done manually. 😢 That being said, you can put a # nick = foobar at the top of your feed and *some* clients will pick it up and show this as your nick. All the @username@yarn.domain.tld stuff that you see in Yarn.social is actually just a Yarn convention – maybe @prologic can tell you more about how exactly that works. 🙂
@lazarus In plain twtxt, none of this is really specified. 😢 That part of the protocol is not so great. In plain twtxt, *my followers* must configure that the URL https://www.uninformativ.de/twtxt.txt belongs to the username “movq”. So it has to be done manually. 😢 That being said, you can put a # nick = foobar at the top of your feed and *some* clients will pick it up and show this as your nick. All the @username@yarn.domain.tld stuff that you see in Yarn.social is actually just a Yarn convention – maybe @prologic can tell you more about how exactly that works. 🙂
@lazarus Hmmm no only the former is supported
@lazarus Hmmm no only the former is supported
@prologic So it works for @lyse and @movq because they are just hosting a twtxt file and not a pod? They can still have landing page for their website and have their handle at the domain.tld level this way.
It's not a big issue for me, was just wondering if it were possible to make use of a .well-known in nginx.
@prologic So it works for @lyse and @movq because they are just hosting a twtxt file and not a pod? They can still have landing page for their website and have their handle at the domain.tld level this way.\n\nIt's not a big issue for me, was just wondering if it were possible to make use of a .well-known in nginx.
@lyse @lazarus I think the .well-known stuff is just convention right? 🤔
@lyse @lazarus I think the .well-known stuff is just convention right? 🤔
@lyse @prologic For example I have currently running a Matrix server here https://ix.social/ with the following
r {
server_name ix.social;
...
location /.well-known/matrix/server {
return 200 '{ "m.server": "syn.ix.social:443"}';
...
}
location /.well-known/matrix/client {
return 200 '{"m.homeserver": {"base_url": "https://syn.ix.social:443"}}';
...
This allows the user handle to be username@ix.social instead of username@syn.ix.social where Synapse is running.
@lyse @prologic For example I have currently running a Matrix server here https://ix.social/ with the following\n\nserver {\n server_name ix.social;\n\t...\n location /.well-known/matrix/server {\n return 200 '{ "m.server": "syn.ix.social:443"}';\n\t...\n }\n location /.well-known/matrix/client {\n return 200 '{"m.homeserver": {"base_url": "https://syn.ix.social:443"}}';\n \t...\n\nThis allows the user handle to be username@ix.social instead of username@syn.ix.social where Synapse is running.
@lazarus @prologic This wellknown mechanism seems like a nice thing. But I only know it from OIDC and Let's Encrypt. I personally don't care so much about these "handles". Twtxt just says, you need a public file and a nick, that's all. As @movq pointed out, some clients understand # nick = foobar comments in the feed. So, not sure, what the wellknown here would actually bring new to the plate. Rewriting URLs definitely breaks twtxt mentions, that's for sure.