I3 Testing Server

[Adam]

Thrown up an i3 router for people testing their i3 clients and code:

Name: *KellyTest
IP: 144.139.132.92   
Port: 9000

Server Logs are at: https://www.themud.org/~i3router/router-testing/

Note address and ports may change to get up2date details see:
https://www.themud.org/imc2i3-routers.php

[kriton]

Has there been any progress on a decentralized Intermud 4 protocol? 

I've been thinking about how I would go about it myself (and whether I could make it backwards compatible with I3).

[Adam]

Has there been any progress on a decentralized Intermud 4 protocol? 

I've been thinking about how I would go about it myself (and whether I could make it backwards compatible with I3).

One could simply rewrite Intermud2 and simply add an announce server and the extra packet types we use on I3:
I2 required each mud to know about the other muds on the network to function so basically to connect you needed to know at least one other mud that knew of one other mud and you communicate your mud list and eventually know about all the muds. but to get people to move to I4 you'd need to hold their hand and spoon feed them everything they needed otherwise they would still just connect to it with an i3 client haha

[kriton]

I am not very familiar with Intermud-2.  I cannot find good documentation and the implementations I have seen kinda gross me out.  Is there an implementation guide somewhere?

[silenus]

I think the old intermud-2 protocol had a problem with multiple muds not being consistent on things like what muds were connected to a given channel and what not. I think no one analyzed the protocol to make sure that consistency is guaranteed. Not sure there was ever a specification document or design document of some sort.

[Adam]

Intermud2 never had a "good" implementation it was dropped in favor of IMC2 and I3 as they were both more stable and get the job done.

if anything id simply look at extending the I3 protocol to support encrypted TELLS and Channel Messages, but its probably overkill