@gcrkrause PHP backend! It used to by my go-to server language and I hadn't spent enough time with NodeJS yet to fully commit to it when I started Keyoxide. With additional tools and libraries in mind, porting to NodeJS early on will allow faster development in the future.
@keyoxide I kind of critical regarding nodejs, also php runs on every shared webhoster. so I am not sure if thats a good development, but who am i to bring critic? ;)
@gcrkrause I am a big fan of PHP. Really am! It's most likely my inexperience with big PHP projects but I didn't like the way I had set it up and just didn't want to imagine what it would turn into if left to grown.
NodeJS gives me nicer dependencies for the use-case.
Another determining factor is that I am also developing other related tools with NodeJS. Sharing the same code between them is going to be a life saver.
@gcrkrause in the end, all I'm trying to promote is decentralized identity. Keyoxide is just an implementation. Perhaps we'll see better PHP implementations in the future 🤗
@keyoxide Jeah, thats a good point. Having a implementation without spending hours on it is a nice thing...
@gcrkrause haha no worries, your original message didn't make me think otherwise! Thank you for your enthusiasm 🤗
@keyoxide unsolicited suggestion: at least in the FAQ it would be good to answer what are the main real world scenarios in which you would use keyoxide?
That being said, most project use npm due to many dependencies and ensuring quality
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.