pep/blog.bouah.net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

what-about-design: Don't turn around

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2020-07-20 14:22:14 +02:00
parent 74cf6dee43
commit 5d787c84c7
1 changed files with 1 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
content/posts/what-about-design.md
View file

@ -2,20 +2,9 @@
title: "What about design?" title: "What about design?"
date: 2020-07-14T01:32:25+02:00 date: 2020-07-14T01:32:25+02:00
draft: true draft: true
summary: |
Who around here hasn't heard about the tragic and inevitable death of XMPP?
It's a pretty common topic in the community and around, often started by
users of XMPP themselves missing this or that feature in one or multiple
specific implementations, or users of alternative solutions. In a way this
is my own version of why XMPP is doomed (or isn't).
tags: [XMPP, Design] tags: [XMPP, Design]
--- ---
<p style="font-size: 0.9em"><em>Explicit disclaimer: This viewpoint -- as any
other article on this blog -- is a work in progress, and I'm happy to debate
it and listen to constructive feedback.</em></p>
Who around here hasn't heard about the tragic and inevitable death of XMPP Who around here hasn't heard about the tragic and inevitable death of XMPP
(eXtensible Messaging and Presence Protocol)? It's a pretty common topic in (eXtensible Messaging and Presence Protocol)? It's a pretty common topic in
the community and around, often started by users of XMPP themselves missing the community and around, often started by users of XMPP themselves missing
@ -143,11 +132,7 @@ be a similar solution that's more adapted to your use-case.
For the more technical of us who understand the protocol and/or can deal with For the more technical of us who understand the protocol and/or can deal with
less unified designs, it may be ok to continue using our current applications less unified designs, it may be ok to continue using our current applications
and work around these issues ourselves. For the mass audiences I believe this and work around these issues ourselves. For the mass audiences I believe this
is not an option. You may take this with a pinch of salt as it is as a is not an option.
developer that I am saying this to you.
I guess the only thing left to figure out now is [network
effect][network-effect]…
[Conversations]: https://conversations.im [Conversations]: https://conversations.im
[Dino]: https://dino.im [Dino]: https://dino.im
@ -157,7 +142,6 @@ effect][network-effect]…
[Snikket]: https://snikket.org [Snikket]: https://snikket.org
[snikket-intro]: https://blog.prosody.im/introducing-snikket/ [snikket-intro]: https://blog.prosody.im/introducing-snikket/
[snikket-explanation]: https://www.reddit.com/r/xmpp/comments/f0el07/can_someone_explain_to_me_whats_the_point_of/fgto5h0/ [snikket-explanation]: https://www.reddit.com/r/xmpp/comments/f0el07/can_someone_explain_to_me_whats_the_point_of/fgto5h0/
[network-effect]: https://en.wikipedia.org/wiki/Network_effect
# So why (not) XMPP? # So why (not) XMPP?
@ -171,5 +155,3 @@ I want decentralization and standardization to prevent users from being locked
in closed -- often also proprietary -- silos such as WhatsApp, Hangouts, in closed -- often also proprietary -- silos such as WhatsApp, Hangouts,
Slack, MS Teams, or even Signal. And I want extensibility to prevent being Slack, MS Teams, or even Signal. And I want extensibility to prevent being
stuck in the past and adapt to the people's needs. stuck in the past and adapt to the people's needs.
As a developer if I get to use XMPP, great, otherwise I'll learn.