Comments 1 - 30 of 30 Search these comments
Each link off the main page would have its own file, that gets updated and synchronized with each post.
- Gab can be censored or taken offline
@Tenpoundbass What would be in each of these files?
Or maybe you'd be introduce to friends of people who are on the same server, because you all know the guy who is paying the $5/month. So that would be kind of social.
But html is pretty simple and people all have browsers.
- decentralization, resistant to censorship
- completely private to your friends (ssh has good privacy)
- every friend would have a local copy of everything via rsync, so the server could be easily re-created if somehow destroyed
- you can't delete anyone else's work, nor can they delete yours
- relatively easy to set up
- easy to use via web interface without ever needing a web server anywhere
- no advertising
- cheap
- no dns to pay for or to have cut off
- no ssl certificate required
- works offline! you can still view anything and create content when you're not connected, and then rsync to put/get the latest
late 90's era
I recall the bulletin board system back in the 1980s and using my Commodore 64.
Question, what if people "remove friend", will that still work due to how certificates work?
No login thing seems like it would be very confusing for many people, especially for people like me with multiple computers, i have a phone and computer and I use two different logins on both because it's hard to remember random password or transfer one to another.
we develop a Social Network Transport Protocol
Just need to figure out a way to prevent a browser which has loaded a page from the local filesystem from using the network at all. We just want to browse the files we have downloaded from the server with rsync
You are at the mercy of some Commie dirt bag, depersoning you, and demanding that your registrar, and hosting company dump you if they don't like you.
1)Facebook type apps need physical storage space and cpu cycles/electricity to run. That takes money.
The server should run only sshd and nothing else. No other ports should be open. Password login should be disabled.
A "friend request" becomes a request to the server owner (the guy paying the $5/month) to add an account with useradd, and to add the public ssh key for that account in /etc/ssh/authorized_keys.d/ Everyone's home directory would be publicly readable by all the other users on the server.
The the friend can log in with ssh and see everything in /home/* But more importantly, the friend can rsync the entire /home/ directory of that server down to a local copy, maybe ~/static/(server_owner_name)/home/
After rsync runs, to view content one could simply view that content directly from the local filesystem (say, open a movie file with VLC), or could can use a browser with a file:///path/to/index.html page which lets you see content in the familiar html format, no server necessary! That local index.html file can run javascript, and we know that javascript has the permission to write files to the same directory that its own html file is in. So to create a forum, say, one could use the html interface to write a comment, and then "save", which writes the comment as a file to the local disk.
A cron job could come along and automatically rsync that comment and any other changes to your /home/ directory on the shared server once per minute, where other people's cron jobs would be rsyncing to their laptops every minute as well.
That's basically it. What do you get?
- decentralization, resistant to censorship
- completely private to your friends (ssh has good privacy)
- every friend would have a local copy of everything via rsync, so the server could be easily re-created if somehow destroyed
- you can't delete anyone else's work, nor can they delete yours
- relatively easy to set up
- easy to use via web interface without ever needing a web server anywhere
- no advertising
- cheap, only $5/month for one guy
- no dns to pay for or to have cut off
- no ssl certificate required so it can't be cut off
- works offline! you can still view anything and create content when you're not connected, and then rsync to put/get the latest
- crazy fast to browse after each rsync is done, because all files are local
The hosting service would know what you have on your server, but if you took it a step further and actually got your own hardware, you could share any type of file you want, and no one could do anything about it. You just have to be able to trust the friends you let onto your server.