-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
comparison to iris.to #23
Comments
Well, we don't have any money and all the (many) interested parties are working on other things to pay the bills, including myself, so development is very slow. We have clients that work, but they're buggy so that's sad. About Iris, I guess I'll add a section. It is similar in some aspects, but there are two major differences (although you shouldn't believe me as I don't know enough about it):
|
Thank you for your prompt reply and helpful clarifications. I did a little bit of research on it and came to similar conclusions. Iris is really cool, but I think Nostr is more what I am interested in. Given the taproot/schnorr upgrade, the use of schnorr signatures in Nostr was smart too I think! I will figure out how to join the Telegram channel soon. |
@fiatjaf is anyone actually running a nostr relay right now at the moment such that https://nostr.com sort of works? |
Hey @VzxPLnHqr, come chat on https://t.me/nostr_protocol about these topics. |
I do not yet have a telegram account, otherwise I would post this in there. Have you seen https://iris.to ? (seems to also be created by bitcoiners). I would like to know your thoughts as to why nostr is or will be better. Or perhaps they are quite similar in underlying design?
P.S. How close is nostr to being usable for bootstrapping itself? In other words, when will the primary support / dev channel for nostr being administered on nostr itself rather than Telegram?
The text was updated successfully, but these errors were encountered: