Keyoxide @keyoxide@fosstodon.org

@haru I understand… Sorry about the PHP-NodeJS switch, I did it because it will help me with future development of other parts of a "keyoxide ecosystem" 🙂 but I still miss PHP sometimes 😉

guess we need a new PHP client!

@haru thank you 😊 it is my privilege to have people invest their valuable time in my project!

This is peculiar: I did recently switch to a different QR library that is npm-able… Have you tried running "npm install" again?

@haru that's a great trick, I will update the guide with this. Thank you!

@neb @airgoa indeed, just "encrypt the message", no account or info needed, but you'll have to send it to the person yourself, using email or chat.

@ghil going good so far? Any services you would like to see implemented?

@haru it is indeed being generated on the fly, so an iframe should do the trick!

Keyoxide doesn't send emails though. So the idea is people can read the email address from the profile page and use it with their email client? Yes, that should work

@wizzwizz4 @b0undarybreaker thanks for the mention 🤗 and yeah, working on a replacement for the identity part of keybase!

https://keyoxide.org

@nathand This part is quite significant!

"proof" tells Keyoxide that this notation is going to be a proof!

Unfortunately, "proof" is not a notation type defined in the spec and must therefore, as per spec, be complemented by a domain name.

In this case, the creator of these pgp-based decentralized proofs @wiktor used his domain as he should have. This means now that, as long as "proof" notation aren't incorporated into the official spec, we keep the original domain for all proofs.

👀 @codeberg

Great feeling to start the monday with a release 🎉 2.2.0!

If you know SEMVER, you know it's going to be more than just fixes 😋

#keyoxide now verifies proofs for #gitea and #gitlab!! It also supports the Onion-Location header if you have a keyoxide instance hosted on the #tor
network!

Thanks so much to @supernova and @dusansimic for their contributions!

https://codeberg.org/keyoxide/web/releases/tag/2.2.0

#pgp #gpg #identity

@jpvanacken

- keybase has proprietary servers that hold the private keys of their users (private keys should never be uploaded)
- zoom is a video conference platform that is easy to hack (zoombombing) and has admitted shutting down a conference at the request of the Chinese government
- zoom acquires keybase

@erAck This is strange, direct URLs are definitely supported. What is your WKD id?

@beli3ver I'm working on a way to display avatars stored inside the key, that would be the ultimate decentralized solution IMO.

@beli3ver completely agree, in fact, libravatar is what I used when I started the project. The main reason I switched was long loading times for the avatars.

But the fact gravatar is used instead of libravatar still doesn't feel right. I'll do a few more tests with libravatar, if it's more stable now, I'll switch.

Thanks for the suggestion, couldn't agree more!

@Avalon awesome, glad to see more and more identity proofs out there!