I have an idea of using something like SRV records where they can define weighted url endpoints to reach.
I have an idea of using something like SRV records where they can define weighted url endpoints to reach.
also how set in stone is using user+url? vs user@domain? the latter would mean the url could change without invalidating the hash.
o
type Twt interface {
\tTwter() Twter
\tText() string
\tMarkdownText() string
\tCreated() time.Time
...
}
o
type Twt interface {
Twter() Twter
Text() string
MarkdownText() string
Created() time.Time
...
}
o
type Twt interface {
Twter() Twter
Text() string
MarkdownText() string
Created() time.Time
...
}
o
type Twt interface {
\tTwter() Twter
\tText() string
\tMarkdownText() string
\tCreated() time.Time
...
}
It seems a bit wonky that it imports from your packages in some places. I'm guessing that's some legacy bits that need updates?
It seems a bit wonky that it imports from your packages in some places. I'm guessing that's some legacy bits that need updates?
Kinda wish [types.Twt](https://github.com/jointwt/twtxt/blob/master/types/twt.go#
Kinda wish [types.Twt](https://github.com/jointwt/twtxt/blob/master/types/twt.go#
are there some users that use alternative protos for twtxt? like ftp/gopher/dnsfs 🤔
are there some users that use alternative protos for twtxt? like ftp/gopher/dnsfs 🤔
avatar: would be the user could put their gravatar/libravatar image url like https://key.sour.is/avatar/01bc6186d015218c23dec55447e502e669ca4c61c7566dfcaa1cac256108dff0
avatar: would be the user could put their gravatar/libravatar image url like https://key.sour.is/avatar/01bc6186d015218c23dec55447e502e669ca4c61c7566dfcaa1cac256108dff0
avatar: field that pointed to where the avatar image is located it can be almost all self contained.
avatar: field that pointed to where the avatar image is located it can be almost all self contained.
gpg --send-keysmakes a POST to the keyserver with your pubkey.
gpg --send-keysmakes a POST to the keyserver with your pubkey.
gpg --send-keys\n\nmakes a POST to the keyserver with your pubkey.
it takes an email@address.com hashes the part before the @ and turns it into
[openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
it takes an email@address.com hashes the part before the @ and turns it into
[openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
[openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>
> That way at least we can form some kind of cryptographic “identity” without having to involve the users that much, it just works™
i like some of the work that keys.pub is doing with ed25519 crypto keys with something like that.
> That way at least we can form some kind of cryptographic “identity” without having to involve the users that much, it just works™
i like some of the work that keys.pub is doing with ed25519 crypto keys with something like that.
OpenPGP has a part of the self signature reserved for notatinal data. which is basically a bunch of key/values.
this site tries to emulate the identity proofs of keybase but in a more decentralized/federation way.
my next steps are to have this project host WKD keys which is kinda like a self hosting of your pgp key that are also discoverable with http requests.
then to add a new notation for following other keys. where you can do a kind of web of trust.
OpenPGP has a part of the self signature reserved for notatinal data. which is basically a bunch of key/values.
this site tries to emulate the identity proofs of keybase but in a more decentralized/federation way.
my next steps are to have this project host WKD keys which is kinda like a self hosting of your pgp key that are also discoverable with http requests.
then to add a new notation for following other keys. where you can do a kind of web of trust.
\n
[Verifying my OpenPGP key: openpgp4fpr:20AE2F310A74EA7CEC3AE69F8B3B0604F164E04F]
[Veriying my OpenPGP key: openpgp4fpr:20AE2F310A74EA7CEC3AE69F8B3B0604F164E04F]