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

sprint-lyon: Remove some more commas

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2019-07-19 17:16:20 +02:00
parent 4b66ebdf9b
commit ec05053d91
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
content/posts/sprint-lyon.md
View file

@ -58,7 +58,7 @@ client authors present at the sprint wrote a DOAP file for their client.
### Reactions
Some time ago, [Movim][Movim] [implemented reactions][Movim_Reactions] using
Some time ago [Movim][Movim] [implemented reactions][Movim_Reactions] using
the [Message Attaching][XEP_0367] specification. [Dino][Dino] developers felt
that the situation could be improved, especially some issues with
non-supporting clients, and started working on a new specification a few weeks
@ -87,11 +87,11 @@ this weekend.
It mandates that [MUC][XEP_0045] components provide a stable and unique id
that is attributed per room per user (bare real JID). This is especially useful
semi-anonymous rooms, where it is usually not possible to ensure messages are
semi-anonymous rooms where it is usually not possible to ensure messages are
coming from the same participant between rejoins.
Some clients are talking about requiring occupant-id for features like Last
Message Correction, or Reactions, in semi-anonymous rooms.
Message Correction or Reactions in semi-anonymous rooms.
A [prosody module][Prosody-occupant-id] is now available and is usable with the
current release (0.11) or trunk.
@ -119,7 +119,7 @@ xmpp-parsers got a new [release][xmpp-parsers-0.14], fixing
I'd like to thank [Wisolv][Wisolv] again for hosting us this weekend.
Next month, members of the community will be present at [FrosCon][FrosCon] at
Next month members of the community will be present at [FrosCon][FrosCon] at
the XMPP booth, and at [CCCamp2019][Camp]. See our [events page][Events] for
more information about future events!