[Standards] Deprecating Privacy Lists

Vitaly Takmazov vitalyster at gmail.com
Mon Oct 12 13:54:06 UTC 2015


> who complain about specs they want not existing believe is responsible for doing this for them at no cost, and why?
Hi from 2015! There are number of options:
1) Get an existing protocol/library which is more suitable for the
task. It can be "no cost", or much cheaper than fighting with
inconsistent XMPP protocols and specs.
2) Develop protocol from scratch. It may cost developer time, but in
most cases it is still cheaper. And you still can reuse existing
ideas, specs, tools, experience, etc.
3) "Extend" XMPP without documentation and standartization, (whatsapp way)

And the counter question: who exactly these developers who want to
contribute to XMPP community "at no cost"? They already must be
interested and motivated. How existing XMPP/XSF state (inconsistent,
incomplete, absence of libraries, clients, name it) can motivate new
developer to join it?
---


More information about the Standards mailing list