further idea (No need to publish this) \u002D the following is pure gold if you think about it.\u000a\u000aWould a API access be possible? If so, did you ever thought about the abillity for people running communities (Insta, FB, Circle, Tribe, YT, Heartbeat, Discord...) woudl love the idea about their community members getting an email for \u0022community internal\u0022 comms \u002D secured? \u000a\u000aBriefly:\u000a\u000a1. Add API or at least, email creation by incoming webhook and send back the confirmation to the originator or simply team with Heartbeat and community platforms alike.\u000a\u000a2. User signs up with the community but the community creates a free email account based on the users chosen namespace\u000a\u000a3. community internal newsletter and alike are sent encrypted within the community using your system\u000a\u000a4. users learn they now got a free and secure email that is getting more and more secure the more people are using it.\u000a\u000a5. If user leaves community there must be an option to keep/delete namespace and block it for 36 month or so to avoid abuse.

Question

further idea (No need to publish this) \u002D the following is pure gold if you think about it.\u000a\u000aWould a API access be possible? If so, did you ever thought about the abillity for people running communities (Insta, FB, Circle, Tribe,  YT, Heartbeat, Discord...) woudl love the idea about their community members getting an email for \u0022community internal\u0022 comms \u002D secured? \u000a\u000aBriefly:\u000a\u000a1.  Add API or at least, email creation by incoming webhook and send back the confirmation to the originator or simply team with Heartbeat and community platforms alike.\u000a\u000a2. User signs up with the community but the community creates  a free email account based on the users chosen namespace\u000a\u000a3. community internal newsletter and alike are sent encrypted within the community using your system\u000a\u000a4. users learn they now got a free and secure email that is getting more and more secure the more people are using it.\u000a\u000a5. If user leaves community there must be an option to keep/delete namespace and block it for 36 month or so to avoid abuse.

Youri_Telios · Answer

Another1,\u000a\u000aI will try to respond to all of your questions/comments in this one reply. Please let me know I miss anything.\u000a\u000a1. A couple of users have brought up the desire for us to have API that our users can leverage. A lot of our tech is open source and though there is a lot of content out there already that could help accomplish some of this thing, it hasn\u0027t been organized in a way that would perform the function describe. All this to say, that is an idea we are open to but it may be a little bit before we can get around to it.\u000a\u000a2\u002D5. I think I am following the use case you are laying out and it brings some very interesting idea, I can\u0027t say we had explored quite so specifically for this use case. We built Telios as a protocol, as such the majority of the tech is open source. It is conceivable that one could use the technology we created and organize it in the way you are describing. Not sure that Telios will get around to exploring that use case anytime soon but it certainly leaves me with a lot to think about.\u000a\u000aOn your earlier comment about a family plan, that is something I have actually thought about and am really excited to get to a point where we can explore that a bit more. I have young kids myself and more and more I think about how to keep them safe and their privacy protected. I think Telios could evolve to cover a lot of those use cases. I encourage you to keep following our growth and evolution and to keep contributing great ideas as you have done today.\u000a\u000aThank you very much for taking the time to share your opinion.

Lifetime Access to PieSync

Share Lifetime Access to PieSync

Related questions