|Subject:||Re: [Social-discuss] Which framework?|
|Date:||Sun, 28 Mar 2010 12:04:40 -0400|
|User-agent:||Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:220.127.116.11) Gecko/20100227 Thunderbird/3.0.3|
On 3/28/10 10:59 AM, Adrian Thurston wrote:
Hello GNU-Social,I agree entirely. Do you think that the PHP install should be something that only the person hosting it should have access to (i.e. everyone goes to 127.0.0.1, and it is nothing more than a quick and convenient way to interface with the GNU Social install), or that everyone should, in essence, have their own GNU Social "site"?
My idea is that everyone can have this sort of "backbone" application running on their computer (perhaps in Python or C). This application handles all the "behind-the-scenes" interactions between GNU Social installs, through XMPP or another (perhaps original) protocol.
Users can (optionally) install the PHP frontend to an (Apache?) server. This PHP frontend loads data from the backend, and displays it to only one user - the person who installed the PHP frontend. Generally, this PHP frontend will only accessed from the computer it was installed on (127.0.01), but the user can also get at it from other locations (work, school, vacation, etc.) by typing in the IP address of the computer the PHP install is running on.
It could be compared to our current email system: you don't log in to your friends' email accounts to send them emails - you log in to your own email account, and send them emails. The browser frontend is nothing more than a convenience.
|[Prev in Thread]||Current Thread||[Next in Thread]|