... And the fun isn't over! Release 2.0.0 also introduces #docker containers 🎉

docker run keyoxide/keyoxide

This one is for the promise of #selfhosting and building a decentralized network of identity verification!

For more info: https://hub.docker.com/r/keyoxide/keyoxide

@keyoxide why do you need a Twitter API key? Scraping the page would seem the obvious way to go, I mean it's what Nitter does, and you already get the URL to the status, so I would think you can use a similar scraping technique, no?

@Matter this was also recently suggested by others. The idea initially was to get all proofs as similarly as possible, meaning parsing JSON data. An exception would have to be made for twitter to parse HTML content instead.

But since twitter is already an exception with api access… This might get implemented in a version soon.

I heard Nitter was using leaked API credentials, not sure if true though

@keyoxide Oh right, I confused it with how youtube-dl and newpipe work.

Another question, what measures do you think might promote a decentralized usage of Keyoxide? I think we should avoid people going to keyoxide.org as much as possible, but it's not evident to me how to go about this.

@Matter not sure about the measures yet. Making selfhosting as simple as possible is obviously key, hope today made some impact.

Agreed that keyoxide as a whole should work as a network. For now, no federation between instances whatsoever. But I'm going to explore certain directions in the near future.

Always open to suggestions and criticism! :)