PDA

View Full Version : Forbiddances for client side protocol extensions?


Lastwebpage
07-08-2008, 10:25 PM
Hello,
the XEPs describe some standards that a client can support or not, some of them must or should supported. Okay.

But what about extensions from a client which are not defined in the XEP but is similar to existing XEP, are this "allowed"?

In this particular case I speak about an "extension" for MUCs.
XEP-118 define a standard to send and receive information about the music which an user hear at the moment. That's fine. I can see this info when I want it, if I don't want to see it, that's okay too, I can disable this display. :)

But now a client think: "hmmh, not all servers support XEP-118, therefore I post my music info with another way". For example post this music info directly in the MUC as a message.

I speak not about the fact that in my opinion messages like this are spam, I speak about the possibility for a client to not use a already defined XEP, but use another way, especially if the other users can't disable the receiving of things like this.
( on second thoughts I can imagine some other situations with the same problem, not only in MUCs)

Are there somewhere any rules about this?

Peter Fl.

stpeter
07-12-2008, 02:47 AM
What's the problem?

If you don't like those messages being sent through a MUC room, don't join the room. If you're a room admin, ban the user. Or use the MUC feature of disallowing certain payloads.

Same thing for sending music via presence -- remove the person from your roster if you're a regular user, disable the person's account if you're a server admin, etc.

XEPs can't solve deployment problems and abuses like this.

/psa

Lastwebpage
07-12-2008, 03:13 AM
I was not sure about this, maybe I overlooked somewhere the sentence "other ways should not used" or something similar in the XEP docus. ;)

Peter