what-about-design: more rephrasing Snikket bits

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

View file

@ -117,14 +117,15 @@ guidelines, it's that it's not the same.
# What now? # What now?
Recently a solution following this design process called [Snikket] has A solution called [Snikket] following this design process has recently
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 its 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 federates with the XMPP network. But the important part -- and also XMPP and federates with the XMPP network. But the important part -- and also
why it deserves a different name -- is its goal: provide a server and a (set why it deserves a different name -- is its goal: provide a server and a (set
of) client(s) that interoperate properly and have similar design. of) client(s) that interoperate properly and have common design guidelines
that match the expected userbase.
Maybe you're not part of Snikket's target, in which case there might someday Maybe you're not part of Snikket's target, in which case there might someday
be a similar solution that's more adapted to your use-case. be a similar solution that's more adapted to your use-case.