WinMX Opennap Discrimination?

[Josh]

Just thought this was odd, I downloaded the servers.wsx list from the open nap page in the tutorials, and one of them that didn't connect showed this.

[White Stripes]

lol

well... it is their server...

[]-[êll.Ôñ.ËÀR'][']-[.]

hehehehe yea they are free to do as they wish ..... this should go in the winmx lite section ....  you sure its not one of your own servers josh? 

[Josh]

hehehehe yea they are free to do as they wish ..... this should go in the winmx lite section ....  you sure its not one of your own servers josh? 

The only servers I added were the ones from the winmxworld list.


And anyways, they didn't even know how to use the correct form of "your".

[Bluehaze]

Greetings,

Just wanted to say that I have often gotten the same message Josh saw when trying to connect to ShadowNet. As Stripes seemed to suggest, an operator of a server will set their own conditions, whether it seems right to someone or not. But the operator of ShadowNet is not too much of a stickler on his own rules. I sometimes am allowed to connect to ShadowNet in spite of my "uncool client"! TheNet, spica.sytes.net used to do much the same, but has been kinder to WinMX lately.

When you connect, check the /motd in server messages for this net. The operator has a rule, "no kanji...try English!" If you try the chat tab and get the list of chatroom for this net, you will find two rooms, both German language! Not too much of a sticklier for his own rules, this operator!

[GhostShip]

The difference betweek Kanji and English is in the character set supported, Japanese (Kanji) characters take two bytes to display and both Deutsch and English take 1.  I dont think the Server operator is racist in any way but merely trying to ensure their system remains stable as its likely its not configured to show the 2 byte characters correctly. 

[White Stripes]

could write your own opennap client josh (if you havent already)... theres something to keep the creative coding going

[Bluehaze]

Yes, Josh! I hope you will consider Stripes' idea, a new opennap client - a cool one! Slavanap server was updated, I believe, less than a year ago, so opennap is not dead yet! Maybe you could breathe more life into it. Please consider!

[Forested665]

o.o salavnap without the (at the time) major ram consumption.... interesting.
new open nap client would be interesting... whatever happened to lobster wasnt it supposed to add support for wpn chat rooms?

[GhostShip]

Lopster at one time did used to support WinMX but this was before the encryption was changed and the main WPN network was in operation, if you google for WinMX Protocol one of the old links is shown with the older style of encryption that is no longer used.

[Forested665]

coolies. i didnt know there was an intermediate stage. i remember seeing a post somewhere about the frontcode wsx as this was a nap client in the beggining what was it gatornap?

[Forested665]

- removed -

[GhostShip]

You talk as though we can afford to make enemies Bacon. In all the time I have been on WinMX we have always done our best to work in co-operation with Opennap Server operators not go out of our way to annoy them, both they and most WinMX users know why Opennap servers often prefer other clients to our favourite one, but as long as we all do our best to minimise causing problems while we are a guest on their networks then all is fine, but we must never go out of our way to wave a red flag at them, no one wins from such activity.

[Forested665]

- removed -

[White Stripes]

been nice to know what was 'removed' O.o

[GhostShip]

Bacon has removed his own posts, its not something we like here unless there is a real good reason to do such a thing.

I think on this note now would be a good time to close this unhelpful thread.