[Standards-JIG] MUC (JEP-45) privacy & control

Trejkaz trejkaz at trypticon.org
Mon Apr 17 22:01:18 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 18/04/2006, at 04:36 AM, Ian Paterson wrote:

>>> In general the solution to this sort of problem is not to
>>> reduce functionality, but rather to move the filtering to the
>>> server. In this case, perhaps it could be moved to the MUC
>>> component.
>>
>> Yes. If MUC servers implemented that feature then people
>> would have the same possibility to block as they do with
>> nonanonymous rooms.
>
> Sorry Trejkaz, what I meant by that was:
>
> "Yes you're right, servers are the right place to block. Although,  
> even
> if MUC servers implemented that feature, they would not be able to  
> block
> any more messages than a client can already block from nonanonymous
> rooms."

Correct.  Filtering on the MUC service would simplify the situation  
for non-anonymous rooms also, making filtering essentially just as  
easy no matter what kind of room it is since the client would no  
longer need to track nick changes, even on non-anonymous rooms.

TX

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFERBA2uMe8iwN+6nMRApTuAJ4uCpxwP54t4sEcDaaLLLbUQ7shmgCfVlAy
PWXft2KVvJu7P3baEWSTuUs=
=ZON8
-----END PGP SIGNATURE-----



More information about the Standards mailing list