How To: Beat the Censor

[l2k-Shadow]

Ahh true, perhaps bad design by Battle.Net? Since you can still swear at others regardless of if you are in a public channel or not?

/ignore fixes that problem.

[Barabajagal]

or /o igwhis... Nobody uses the option features, though. And no, Chriso, it was intentional.

[Chriso]

Just seems odd that swearing is only blocked in public channels though, I mean children could stumble into a private channel and get e-molested (in #sex) or e-abused.

[UserLoser]

Just seems odd that swearing is only blocked in public channels though, I mean children could stumble into a private channel and get e-molested (in #sex) or e-abused.

#sex isn't/wasn't ever a channel on battle.net

[Kp]

Censoring was not present in the original version of the software.  It was added after I had been on battle.net for several years.  I presume the decision to censor only public channels was driven by the fact that public channels are a landing zone and have no operator.  If someone is swearing in a private channel, the operator can remove that person.  If the operator refuses, the offended parties can move to a different private channel, and /whois will not allow you to follow them.  On the other hand, if you change public channels, the cursing entity can follow you easily.

[l2k-Shadow]

Just seems odd that swearing is only blocked in public channels though, I mean children could stumble into a private channel and get e-molested (in #sex) or e-abused.

#sex isn't/wasn't ever a channel on battle.net

perhaps not but

Code Select Expand


/j #sex


[Leaky]

Just seems odd that swearing is only blocked in public channels though, I mean children could stumble into a private channel and get e-molested (in #sex) or e-abused.

#sex isn't/wasn't ever a channel on battle.net

perhaps not but

Code Select Expand


/j #sex


LuLz he didn't say it was an invalid channel he meant it's not an actively used channel

[l2k-Shadow]

Just seems odd that swearing is only blocked in public channels though, I mean children could stumble into a private channel and get e-molested (in #sex) or e-abused.

#sex isn't/wasn't ever a channel on battle.net

perhaps not but

Code Select Expand


/j #sex


LuLz he didn't say it was an invalid channel he meant it's not an actively used channel

you might want to double check that information. it's full almost all the time on east.

[UserLoser]

#sex isn't valid channel

[Leaky]

Just seems odd that swearing is only blocked in public channels though, I mean children could stumble into a private channel and get e-molested (in #sex) or e-abused.

#sex isn't/wasn't ever a channel on battle.net

perhaps not but

Code Select Expand


/j #sex


LuLz he didn't say it was an invalid channel he meant it's not an actively used channel

you might want to double check that information. it's full almost all the time on east.

i did double check it see /\ userlosers' post # is filtered out of the channel name invalid channel name it is it is

[l2k-Shadow]

i was merely pointing out with my first post that /j #sex and /j sex are the same thing.

[Chriso]

Sorry habit from IRC, yeah I meant /j sex

[Barabajagal]

Sex on both west and east has always been popular, east often having 3 or more channels, with the first two often totally full. It's a bunch of idlers, with random quiet chat occasionally.

[UserLoser]

i was merely pointing out with my first post that /j #sex and /j sex are the same thing.

Not on Battle.net

[Mystical]

i was merely pointing out with my first post that /j #sex and /j sex are the same thing.

Not on Battle.net

If you use "/join #sex" or "/join sex" on starcraft client they work the same.