Skip to content
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

Dynamic sites: is there value in read only dynamic sites? #13

Open
probar opened this issue Mar 20, 2014 · 3 comments
Open

Dynamic sites: is there value in read only dynamic sites? #13

probar opened this issue Mar 20, 2014 · 3 comments

Comments

@probar
Copy link
Contributor

probar commented Mar 20, 2014

It could be reasonably easy to add dynamic sites to syncnet assuming they're read only and only creator updates , using something like taffydb.

On the other hand , 2 way dynamic sites look much harder, and not supported well on btsync.

Is there any value to this use case?

@jminardi
Copy link
Owner

What do you mean by 2 way dynamic sites? Syncnet supports the first usecase you described above. Since I am the only one that holds the read/write secret for my site I can make changes and they are pushed out to anyone else with the site.

I think it would be hard to get Syncnet to serve a page like facebook however, where updates come from multiple 3rd parties.

@probar
Copy link
Contributor Author

probar commented Mar 21, 2014

2 way communication might be easily possible in a limited way: if the hoster site isn't blocked for a user ,he can send data to it , and users that hoster site is blocked only see results from others.

@probar
Copy link
Contributor Author

probar commented Mar 22, 2014

I think there might be a solution:

  1. At site creation - creation of an extra shared folder that's writable, to files with limited size, and sharing it's write secret with syncnets who surf the site. That folder will serve as shared memory.

2.When each user want to write data to a site, he writes it to file name "user_public_key.txt" what he wants to write, and encrypts and signs the data with private_key.

3.Syncnet of site creator decrypts and validates data on said directory, uses it (with server logic applied somehow) and deletes it.

I think this could work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants