User Controls
A network of forums
-
2017-08-03 at 11:20 PM UTCNirvanaNiggas
-
2017-08-04 at 1:49 AM UTCBHL
-
2017-08-04 at 3:06 AM UTCDerpaDewNet
-
2017-08-04 at 3:33 PM UTCThis could be easily accomplished by setting up identical FTP servers on multiple boxes, then using a program called FlashFXP to synchronize all the files between all the servers. When one server adds or removes a file, FlashFXP can be used to "side-transfer" the required changes to all servers simultaneously.
-
2017-08-04 at 3:55 PM UTC
-
2017-08-04 at 8:17 PM UTCDonald Trump : All talks, zero action.
-
2017-08-05 at 1:50 AM UTC
-
2017-08-20 at 6:48 AM UTCButtHole Ladies
-
2017-08-20 at 8:29 AM UTC
Originally posted by -SpectraL This could be easily accomplished by setting up identical FTP servers on multiple boxes, then using a program called FlashFXP to synchronize all the files between all the servers. When one server adds or removes a file, FlashFXP can be used to "side-transfer" the required changes to all servers simultaneously.
Solves none of the issues that have been brought up ITT. The second you can write to two servers and those writes can interact in some way (e.g. flood control exists, write to two servers within milliseconds, flood control says one write needs to fail but it can't be coordinated which). Flat file synchronization does nothing to touch this. And that doesn't even touch on the issue of distributing data necessary for user authentication. -
2017-08-20 at 8:44 AM UTC
-
2017-08-20 at 4:03 PM UTCThere would need to be some kind of key authentication system set up so that users could log into each system, without the owner of each system knowing the password. I don't know much about this though. I am going to be putting another server(HTTP and IRC) up soon though. So if anyone is interested in toying around with this idea, let me know.
-
2017-08-20 at 4:51 PM UTC
Originally posted by Lanny Solves none of the issues that have been brought up ITT. The second you can write to two servers and those writes can interact in some way (e.g. flood control exists, write to two servers within milliseconds, flood control says one write needs to fail but it can't be coordinated which). Flat file synchronization does nothing to touch this. And that doesn't even touch on the issue of distributing data necessary for user authentication.
The two servers don't interact at all. They are both slaves of the one master server, slaves which don't talk to one another. Flood control could be resolved on either slave server through write permissions. User authentication is handled from the user authentication system on the master server, and then passed through to the slave servers. -
2017-08-20 at 4:59 PM UTC
Originally posted by SBTlauien There would need to be some kind of key authentication system set up so that users could log into each system, without the owner of each system knowing the password. I don't know much about this though. I am going to be putting another server(HTTP and IRC) up soon though. So if anyone is interested in toying around with this idea, let me know.
a 3rd authentication server that users log on to that receive and encrypt datas before sending them to those two servers ???? -
2017-08-20 at 7 PM UTC
Originally posted by -SpectraL The two servers don't interact at all. They are both slaves of the one master server, slaves which don't talk to one another. Flood control could be resolved on either slave server through write permissions. User authentication is handled from the user authentication system on the master server, and then passed through to the slave servers.
As soon as you say "master server" then your system is centralized again, the most you could hope to achieve is some scalability (until auth load becomes too heavy) but there are far better options for scale. -
2017-08-20 at 7:06 PM UTCI'd suggest study the NirvanaNet node network scheme and its inner workings.
-
2017-08-20 at 7:11 PM UTChttps://en.wikipedia.org/wiki/Inter-server
In computer network protocol design, inter-server communication is an extension of the client–server model in which data are exchanged directly between servers. In some fields server-to-server (S2S) is used as an alternative, and the term inter-domain can in some cases be used interchangeably.
Protocols that have inter-server functions as well as the regular client–server communications include the following:
The domain name system (DNS), which uses an inter-server protocol for zone transfers;
The Dynamic Host Configuration Protocol (DHCP);
FXP, allowing file transfer directly between FTP servers;
The Inter-Asterisk eXchange (IAX);
InterMUD;
The IRC, an Internet chat system with an inter-server protocol allowing clients to be distributed across many servers;
The Network News Transfer Protocol (NNTP);
The Protocol for SYnchronous Conferencing (PSYC);
SIP, a signaling protocol commonly used for Voice over IP;
SILC, a secure Internet conferencing protocol;
The Extensible Messaging and Presence Protocol (XMPP, formerly named Jabber).
Some of these protocols employ multicast strategies to efficiently deliver information to multiple servers at once.
See also[edit]
Overlay network -
2017-08-20 at 7:32 PM UTCIs that supposed to be a reply to my post in any way or are you just typing random garbage at this point?
-
2017-08-20 at 8:26 PM UTCSpectraL knows less about computing than the random button on imgur. Just ignore him. He can't even keep his home address secure.
-
2017-08-20 at 8:45 PM UTC
-
2017-08-20 at 8:51 PM UTC
Originally posted by -SpectraL So, you want me to cross all the t's and dot all the i's for you?
I want you to post content that's relevant, cunt pasting some garbage from wikipedia is not relevant. Those protocols listed all depend on inter-server trust, credentialing info can be distributed across them. The same notion does not apply to a notion of a syndicated forum.
