Any terms that seem weird in our app ToS are there as boilerplate, we don't inject special weird things into our terms, we just ask our lawyers to make sure we are doing what is required.
You will fi...
Hi, thank you for taking the time to respond to my thoughts on the matter!
My goal is not to be dogmatic, I am ultimately a builder and I want to use the tools that will allow for people to take control of their data and allow for as much sovereignty as possible.
Thank you for clarifying the ToS situation. Given the nature of corporate control, I tend to be wary of such things, especially how Synonym is the primary driver of this project. I was worried that this reflected some aspect of the AT protocol, some hidden centralization.
I do see the amazing benefits that this architecture can provide, you really do hit all the main problems with the Nostr architecture and I want to be in the loop for all the advancements that are made.
I really do want to build with Pubky, the lack of any real homeserver implementations is definitely a turn off for the time being. I also think having to download an app is also a major point of friction that many normal folk won't want to swallow. As we have learned from Nostr, architecture is unfortunately not a selling point for most.
What is the roadmap looking like? Are there any plans to have something like NIPs or BIPs?
Once things become more fleshed out, what will standardization/specs look like?
It doesn't seem like Tether or Synonym are non-profits. How can we trust that neither party will try to assume control over the project? Yes, it is open source, but the funding is what will keep it going.
What is the business model here?
What will genuine collaboration and support with the open source community look like?
Please let me know your thoughts! I am eager to hear them. I have an app idea I have been toying with that could benefit from Pubky's architecture.
My goal is not to be dogmatic, I am ultimately a builder and I want to use the tools that will allow for people to take control of their data and allow for as much sovereignty as possible.
Thank you for clarifying the ToS situation. Given the nature of corporate control, I tend to be wary of such things, especially how Synonym is the primary driver of this project. I was worried that this reflected some aspect of the AT protocol, some hidden centralization.
I do see the amazing benefits that this architecture can provide, you really do hit all the main problems with the Nostr architecture and I want to be in the loop for all the advancements that are made.
I really do want to build with Pubky, the lack of any real homeserver implementations is definitely a turn off for the time being. I also think having to download an app is also a major point of friction that many normal folk won't want to swallow. As we have learned from Nostr, architecture is unfortunately not a selling point for most.
What is the roadmap looking like? Are there any plans to have something like NIPs or BIPs?
Once things become more fleshed out, what will standardization/specs look like?
It doesn't seem like Tether or Synonym are non-profits. How can we trust that neither party will try to assume control over the project? Yes, it is open source, but the funding is what will keep it going.
What is the business model here?
What will genuine collaboration and support with the open source community look like?
Please let me know your thoughts! I am eager to hear them. I have an app idea I have been toying with that could benefit from Pubky's architecture.
1