Comment P2P needs to take the lead (Score 1) 363
Facebook's progression of privacy has been apparent with its constant policy changes. I've been working my 'solution' to this for about about 6 months called Clusters.
It used Flash/HTML5 with Adobe's stratus service as a back-end for the P2P connection. It only works with when the computer is on, obviously. To get around that limitation the user can choose to have others who are approved to view the content, to also save it locally in an encrypted database and share it when the original users is offline. The content owner can set what and how long the content is allowed to be distributed via another's machine. With each user deciding how much space to allot for saving others data.
The users can create multiple GUIDs to be used for segmenting permissions. So one person can have a family/friends network that has X permissions and a work network that has Y permissions. Each submission can be shared with one or many GUIDs. I'd also like to have plugins for Twitter and Facebook as they are good services but not "the" answer.
This effectively turns your friends into the servers for a private network. With users responsible for their own network. The connection web server only a map of GUIDs to the current stratus IDs. No personal information is saved on the server nor a way to retrieve a stratusID without knowing the GUID. Personal data is saved on one's own machine and can choose which groups can have what information. Users can opt-in for an openID login to store their GUIDs on the main web server so they can access the network from any computer or web terminal.
The display interface is all HTML5 web-standards complicate and using Flash to augment HTMLs shortcoming like VoIP, webcam and P2P. Flash's power has always been to rapidly add new features to browsers without having to worry about end-users installing another plugin and thats where it should stay. Flash is the China to HTML's UN; both have benefits. Also the central web server should be minimized as much as possible. The web server should only be used for sending the stratusIDs to approved users, store GUIDs online for those who opt-in and registering new plugins/themes/skins.
If any slashdotters are interested in turning this into an open source project, have ideas or pessimistic comments; speak up.
It used Flash/HTML5 with Adobe's stratus service as a back-end for the P2P connection. It only works with when the computer is on, obviously. To get around that limitation the user can choose to have others who are approved to view the content, to also save it locally in an encrypted database and share it when the original users is offline. The content owner can set what and how long the content is allowed to be distributed via another's machine. With each user deciding how much space to allot for saving others data.
The users can create multiple GUIDs to be used for segmenting permissions. So one person can have a family/friends network that has X permissions and a work network that has Y permissions. Each submission can be shared with one or many GUIDs. I'd also like to have plugins for Twitter and Facebook as they are good services but not "the" answer.
This effectively turns your friends into the servers for a private network. With users responsible for their own network. The connection web server only a map of GUIDs to the current stratus IDs. No personal information is saved on the server nor a way to retrieve a stratusID without knowing the GUID. Personal data is saved on one's own machine and can choose which groups can have what information. Users can opt-in for an openID login to store their GUIDs on the main web server so they can access the network from any computer or web terminal.
The display interface is all HTML5 web-standards complicate and using Flash to augment HTMLs shortcoming like VoIP, webcam and P2P. Flash's power has always been to rapidly add new features to browsers without having to worry about end-users installing another plugin and thats where it should stay. Flash is the China to HTML's UN; both have benefits. Also the central web server should be minimized as much as possible. The web server should only be used for sending the stratusIDs to approved users, store GUIDs online for those who opt-in and registering new plugins/themes/skins.
If any slashdotters are interested in turning this into an open source project, have ideas or pessimistic comments; speak up.
