@libravatar WKD on the other hand is just a simple file hosted on a server, accessible by a predictable URL. No need to install a WKD server or set any DNS records.
This is an attempt to lower barriers of entry. Do you happen to know if there's any work in this direction?
@libravatar reading the API documentation, I think libravatar's federated approach is not entirely what I was looking for.
It's great considering the alternative!
But every request still needs to be processed by a libravatar server, right? So the end-user must set DNS records and host a server implementation, correct?
@libravatar are you aware of WKD? Just in case, it's a standard for putting cryptographic keys on personal servers behind a URL that can be computed based on the identifier. So knowing just the identifier "email@example.com", you can easily download bob's key from his server on domain.tld
No need for a centralized service.
Do you happen to know if there's a similar thing for avatars? If you have a personal server, you can easily store an image there
There had been an earlier libravatar issue and at that moment, I had to put it on hold because of (poor) code design choices I had made 😐
With the Keyoxide 3.0.0 rewrite, this is now feasible. We must give key holders the choice of avatar provider. But I wouldn't mind setting defaults that favor decentralized options!
@michael yeah we tried making it standard but no luck.
As for the CLI, JS is indeed not an optimal choice but they're all stepping stones. When you're not a multimillion company, you need a few more of those.
Though at this moment not my highest priority, the CLI will also be rewritten, likely in rust
Here's what a new #keyoxide profile page looks like: https://keyoxide.org/hkp/9f0048ac0b23301e1f77e994909f6bd6f80f485d
Also, have a look at @keyoxide fediverse account, it now shows a fancy green tick next to the Keyoxide profile link ✅
So excited to announce Keyoxide version 3.0.0 🎉
This update was worth the wait, with a (much needed 😎) redesign that is cleaner and more consistent that before.
Now also featuring server-side rendering! So not only pretty darn fast, but also parseable by Mastodon! Keyoxide links in Mastodon bio with a ✅ for everyone 🤩
Thank all for your support. Here's to taking our online identity back from Big Tech!
I finally took the time to setup my #keyoxide profile. You can find it here: https://keyoxide.org/1B4C9964EAC751738E730E900A5E70481D920E7C Thanks to @yarmo for creating that awesome piece of software.
@finlaydag33k sorry for my delayed reply! Yes, this is possible, though we haven't tested this yet. I'd love to test this out with you.
@heii indeed, it now is.
I wanted to thank you for your message last night (for Europeans), after reading I immediately restarted the proxy server and that fixed it.
Interestingly, the health status of the proxy server showed no issue 🤔 unsure how it failed!
@ben no such thing as a dumb question.
Currently not, but that is a good idea! One that I, to be quite frank, had never considered and now find ridiculously obvious. Easy enough to implement, will do so soon!
- yes, one needs advanced tech skills and this is not ideal
- the website is too vague on defining certain concepts
- we need apps/gui and an android app should work with openkeychain
I am currently working on a big overhaul of the website and the information it displays. Within months, I hope to release an android app that does most of the basic functions.
I'll post updates as soon as something is ready :)
Yes, they patched it, but I still don't like #Keybase, also because it was (partially) bought by #Zoom. I use the decentralized solution @keyoxide for this and yes it is more complex but you only do this once and then you have it. Apart from that there should now be a #shell #script for it.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.