what are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.
what are you using to ci/cd? i dont see a travisci/circleci/etc in the repo.. i can put something together to bump the patch level on master branch merges.
-----BEGIN CRYPTUTIL ENCRYPTED MESSAGE-----
l0GwFAQpx3ed+bZlcQ+pexbynFzZOm8EI/FivGbWQ16whyTkToVv8S2GSAjrsJoT
37MdaBDpoitli/f/aP130b6O6SnK/LdHHJ1DTvWgxB14sq9b4mRtk7HvYzA=
-----END CRYPTUTIL ENCRYPTED MESSAGE-----
-----BEGIN CRYPTUTIL ENCRYPTED MESSAGE-----
l0GwFAQpx3ed+bZlcQ+pexbynFzZOm8EI/FivGbWQ16whyTkToVv8S2GSAjrsJoT
37MdaBDpoitli/f/aP130b6O6SnK/LdHHJ1DTvWgxB14sq9b4mRtk7HvYzA=
-----END CRYPTUTIL ENCRYPTED MESSAGE-----
-----BEGIN CRYPTUTIL ENCRYPTED MESSAGE-----
l0GwFAQpx3ed+bZlcQ+pexbynFzZOm8EI/FivGbWQ16whyTkToVv8S2GSAjrsJoT
37MdaBDpoitli/f/aP130b6O6SnK/LdHHJ1DTvWgxB14sq9b4mRtk7HvYzA=
-----END CRYPTUTIL ENCRYPTED MESSAGE-----
> I would need an out-of-band way to verify your public key’s fingerprint though 🤣
> I would need an out-of-band way to verify your public key’s fingerprint though 🤣
> Can we not have clients sign their own public keys before listing them on their Pod’s account?
Yeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.
> Can we not have clients sign their own public keys before listing them on their Pod’s account?
Yeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.
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>
