Callum on Nostr: Good question. The underlying stack is called Pear which handles all the P2P (and ...
Good question.
The underlying stack is called Pear which handles all the P2P (and holepuching) tech. This is 100% open source and there are github pages for each module.
https://pears.com/
https://docs.pears.com/
https://github.com/holepunchto
The developers of Keet have expressed a firm intention to open source the Keet code too, after it exits Beta. The reason they give for not doing it now is that they want to keep control of development up to that point, and also want to build a supporting social network around Keet before it can be copied by a less principled 'competitor'. (That's me paraphrasing their motives and how I understand their thinking anyway.) I'm usually a stickler for open source but in this case, with the underlying stack being open source now and the promise to open source the Keet client later and for the reason for the delay given, I find myself ok with the situation. Everyone needs to make their own call on this though and maybe wait to see if the promise is fulfilled. I find it too intriguing and impressive a product to wait and so I'm a user now mostly just to watch progress (and experience the tech).
The underlying stack is called Pear which handles all the P2P (and holepuching) tech. This is 100% open source and there are github pages for each module.
https://pears.com/
https://docs.pears.com/
https://github.com/holepunchto
The developers of Keet have expressed a firm intention to open source the Keet code too, after it exits Beta. The reason they give for not doing it now is that they want to keep control of development up to that point, and also want to build a supporting social network around Keet before it can be copied by a less principled 'competitor'. (That's me paraphrasing their motives and how I understand their thinking anyway.) I'm usually a stickler for open source but in this case, with the underlying stack being open source now and the promise to open source the Keet client later and for the reason for the delay given, I find myself ok with the situation. Everyone needs to make their own call on this though and maybe wait to see if the promise is fulfilled. I find it too intriguing and impressive a product to wait and so I'm a user now mostly just to watch progress (and experience the tech).