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

xmpp-sprint: Reword and finish Objectives section

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2018-08-30 00:50:54 +01:00
parent 82da6c4089
commit 7e5f749387
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2
1 changed files with 18 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
content/posts/xmpp-sprint.md
View file

@ -60,34 +60,40 @@ And remotely:
## Objectives ## Objectives
In retrospective, _User Experience_ seems to fit the ambiance of the sprint We started the sprint with a short standup, to discuss ideas gathered during
(**badly said**), and is generally a theme that comes back regularly within the previous weeks online, and to narrow the focus to a few feasible items.
the community lately. At this point it became clear that User Experience (UX) would be an important
topic during the weekend, as it is also within the XMPP community of late.
At the beginning of the sprint, here is roughly what we planned to work on: Here is roughly what was mentioned, and what we planned to work on:
1. Bookmarks: Sync [Private XML](https://xmpp.org/extensions/xep-0049.html) 1. Bookmarks: Sync [Private XML](https://xmpp.org/extensions/xep-0049.html)
bookmarks with [PEP](https://xmpp.org/extensions/xep-0048.html) ones. bookmarks with [PEP](https://xmpp.org/extensions/xep-0048.html) ones.
XMPP has different standard places to store bookmarks, and this has often XMPP has different standard places to store bookmarks, and this has often
proven to be a painful experience to the user, when using different clients proven to be a painful experience to the user, when using different clients
for examle. The objective here was to transparently synchronize both for examle. The objective here was to transparently synchronize both
stores, so that the user gets an overall nicer experience. stores, so that the user gets an overall nicer experience.
2. [Message Attaching](https://xmpp.org/extensions/xep-0367.html) 2. [Message Attaching](https://xmpp.org/extensions/xep-0367.html) and
**TDB** Reactions.
Message Attaching defines a way by which one can indicate that a message is
semantically related "attached" to an earlier message in the discussion.
This can be useful for reactions, for example, or even for previews of
links.
3. [In-Band Registration](https://xmpp.org/extensions/xep-0077.html) in 3. [In-Band Registration](https://xmpp.org/extensions/xep-0077.html) in
clients that don't support it, namely dino and poezio. clients that don't support it, namely dino and poezio.
In-Band Registration is a mechanism that allows clients to provide an In-Band Registration is a mechanism that allows clients to provide an
interface to create accounts on servers that allow it. This way the user interface to create accounts on servers that allow it. This way the user
doesn't have to go through multiple hops to start chatting with their doesn't have to go through multiple hops to start chatting with their
friends. friends.
4. Reactions 5. [Consistent color generation](https://xmpp.org/extensions/xep-0392.html).
**TBD**
5. [Consistent color generation](https://xmpp.org/extensions/xep-0392.html)
This specification aims at providing algorithms that will be used to This specification aims at providing algorithms that will be used to
generate deterministic colors, so that they stay consistent across clients, generate deterministic colors, so that they stay consistent across clients,
and thus help with recognition, for nicknames in groupchats, for example. and thus help with recognition, for nicknames in groupchats, for example.
5. [Hats](https://xmpp.org/extensions/xep-0317.html) 5. [Hats](https://xmpp.org/extensions/xep-0317.html).
Hats are **TBD** Hats allow for customised roles and affiliations in chatrooms, an extension
of the usual roles and affiliations. They can be used a regular "titles"
that are displayed to other users, (e.g., "Teacher", "Student", "Developer
of XYZ"), but can also carry permission information.
![Hard working developers](xmpp-sprint-1.jpg) ![Hard working developers](xmpp-sprint-1.jpg)