Unhosted

From I ask questions

<me> well, as I understood: the unhosted team does this:
<me> 1. define a protocol
<me> 2. rewrite some existing apps in a way so your data can be more safe (which does not bother a hacker)

<me> so, when you look at libredocs.org
<me> you can see how it works
<me> the advantage is:
<me> that the libredocs.org site is completely free available to download
<me> and also you can set it up
<me> or you just use libredocs.org as a normal user
<me> libredocs belongs to point 2
<me> as an example

<user> hum. SO what is a protocol?
<user> (i know the word but not the exact tech meaning)
<me> look at the website, there should be a link
<me> the protocol tells how the code should behave
<me> it's something like a standard
<me> so people when they program know what to call and how to call

<me> so, let's imagine you are paranoid
<me> or let's say: I am paranoid ...
<me> I could take the code programmed by the unhosted team and run everything on my own servers
<me> but I see it like this:
<me> using storages which are not on my own servers is again untrustful
<me> imagine some admin taking too easy passwords or having ulterior motives
<me> or someone blackmailing someone
<me> the disadvantage of running all on your own is:
<me> you get also more vulnerable
<me> since it is easier to hack laymen's server
<me> also: no software is safe
<me> no server is failsafe against attacks
<me> so: if someone goes online: ...
<me> expect that the data may some day end also in public (or someone's hands much before)

<user2> it's not only about security or privacy
<user2> having an open standard for storing data prevents your stuff being lost or uncompatible when companies go out of business, or sell their data, sell their apps, change everything, etc etc
<user2> when you have unhosted apps using an open protocol, you can never lose your apps, and you can always migrate your storage