# 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 29
# self = https://watcher.sour.is/conv/63dtg5a
@xuu Not too happy with WKD's use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the [RFC..](https://tools.ietf.org/html/draft-koch-openpgp-webkey-service-11#.1)
@xuu Not too happy with WKD's use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the [RFC..](https://tools.ietf.org/html/draft-koch-openpgp-webkey-service-11#.1)
@xuu Not too happy with WKD's use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the [RFC..](https://tools.ietf.org/html/draft-koch-openpgp-webkey-service-11#.1)
@xuu Not too happy with WKD's use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the [RFC..](https://tools.ietf.org/html/draft-koch-openpgp-webkey-service-11#.1)
@xuu With SRV you can set what hostname to be used (and port/priority/etc)
@xuu With SRV you can set what hostname to be used (and port/priority/etc)
@xuu With SRV you can set what hostname to be used (and port/priority/etc)
@xuu With SRV you can set what hostname to be used (and port/priority/etc)
@prologic Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own. \n\nit takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
@prologic Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own. \n\nit takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
@prologic Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own.
it takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
@prologic Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own.
it takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
@prologic Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own.
it takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
@prologic looking through the drafts it looks like it actually used SRV records as recently as 2018 😵
@prologic looking through the drafts it looks like it actually used SRV records as recently as 2018 😵
@prologic looking through the drafts it looks like it actually used SRV records as recently as 2018 😵
@prologic looking through the drafts it looks like it actually used SRV records as recently as 2018 😵
@prologic the HKP is http keyserver protocol. it's what happens when you do gpg --send-keys\n\nmakes a POST to the keyserver with your pubkey.
@prologic the HKP is http keyserver protocol. it's what happens when you do gpg --send-keys
makes a POST to the keyserver with your pubkey.
@prologic the HKP is http keyserver protocol. it's what happens when you do gpg --send-keys\n\nmakes a POST to the keyserver with your pubkey.
@prologic the HKP is http keyserver protocol. it's what happens when you do gpg --send-keys
makes a POST to the keyserver with your pubkey.
@prologic the HKP is http keyserver protocol. it's what happens when you do gpg --send-keys
makes a POST to the keyserver with your pubkey.
Ahh I see. This is all to do with the GPG keyserver proto and format? I never really looked into it, but this is interesting. I _might_ maybe be convinced to write one in Go 😀
Ahh I see. This is all to do with the GPG keyserver proto and format? I never really looked into it, but this is interesting. I _might_ maybe be convinced to write one in Go 😀
Ahh I see. This is all to do with the GPG keyserver proto and format? I never really looked into it, but this is interesting. I _might_ maybe be convinced to write one in Go 😀