what-about-design: rephrase Snikket bits

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2020-07-18 21:43:08 +02:00
parent 1d5c6cd87f
commit 02b74d13ad
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2

View file

@ -120,14 +120,14 @@ guidelines, it's that it's not the same.
Recently a solution following this design process called [Snikket] has Recently a solution following this design process called [Snikket] has
emerged. You can read about its goals [in the introduction emerged. You can read about its goals [in the introduction
article][snikket-intro] or in a [more detailed article][snikket-intro] or in a [more detailed
explanation][snikket-explanation] from the author. At the time of writing it explanation][snikket-explanation] from its author. At the time of writing it
is composed of a rebranded [Prosody] and Conversations, is entirely based on is composed of a rebranded [Prosody] and Conversations, is entirely based on
XMPP and it federates with the XMPP network, but the important part is that XMPP and federates with the XMPP network. But the important part -- and also
the goal is to provide a set of server and client(s) that works together with why it deserves a different name -- is its goal: provide a server and a (set
a common set of guildelines. of) client(s) that interoperate properly and have similar design.
Maybe you're not part of the target, in which case there might someday be a Maybe you're not part of Snikket's target, in which case there might someday
similar solution that's more adapted to your use-case. be a similar solution that's more adapted to your use-case.
For the most technical of us who understand the protocol and/or can deal with For the most technical of us who understand the protocol and/or can deal with
common design issues, it may be ok to continue using our current clients common design issues, it may be ok to continue using our current clients