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

Stockholm sprint: Remove commas and use periods. Thanks lool0

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2019-10-03 10:01:43 +02:00
parent af9dd8c720
commit fa9ab1b807
1 changed files with 25 additions and 25 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
content/posts/stockholm-sprint.md
View file

@ -28,11 +28,10 @@ storage][bookmarks-pep1]. Not so long after the Cambridge sprint last year,
Daniel submitted a [conversion XEP][bookmarks-conversion] to facilitate client
behaviour and thus user experience.
This new specification also uses PEP as storage, but it brings a few
improvement to the table, specifically because it splits updates to the
bookmark storage into per entry operations instead of updating the whole
storage at once. This allows for finer grained handling in clients, and
prevents some race conditions.
This new specification also uses PEP as storage but it brings a few
improvements to the table. It splits updates to the bookmark storage into per
entry operations instead of updating the whole storage at once. This allows
for finer grained handling in clients and prevents some race conditions.
The XEP came up with its share of challenges that some of us attempted to fix
in a [pull request][bookmarks-PR-835] that has been submitted and is now
@ -61,28 +60,29 @@ available for adventurous services operators.
### New landing page
Roel and I worked on an idea that came up at the UX sprint in Brussels in
January, to have a landing page for new users that would recommend a specific
server depending on different factors that would be gathered automatically for
the most part (if not all). This is more or less similar to other portals like
[joinmastodon][joinmastodon], or [nextcloud sign-up process][nextcloud-signup].
January to have a landing page for new users. This page would recommend a
specific server depending on different factors that would be gathered
automatically for the most part (if not all). This is more or less similar to
other portals like [joinmastodon][joinmastodon], or [nextcloud sign-up
process][nextcloud-signup].
Building up the website isn't the hardest part, what is hard is finding ways
Building up the website isn't the hardest part. What is hard is finding ways
to convey to the user what "federation" or "public network" mean. Roel teaches
in Interaction Design, and so he was a great help over the weekend. We came up
with a narrative for the project, and a sketch for a sign-in flow.
in Interaction Design and was a great help over the weekend. We came up with a
narrative for the project and a sketch for a sign-in flow.
The project is far from being over, this is only the tip of the iceberg. Lots
of work needs to be done with the "stakeholders", that is mainly users and
server operators.
To know what server to recommend to users, we need to first get a list a
To know what server to recommend to users we first need to get a list a
servers we are confident about and willing to recommend. This would mandate
discussing with server operators to get feedback on a required "feature set"
and policies. All this would then be fed into usability testing sessions for
users to validate all of it. After that, we would need lots of promotion around
it, and that's also going to take a significant amount of effort.
users to validate all of it. After that, we would need lots of promotion
around it and that's also going to take a significant amount of effort.
While I am excited about all this, I don't think diving in head first is a
While I am excited about all this I don't think diving in head first is a
good strategy and I would rather take it slow.
[joinmastodon]: https://joinmastodon.org
@ -92,23 +92,23 @@ good strategy and I would rather take it slow.
Pulkomando has been working on implementing IBR support in [Renga][Renga], and
reported with Link Mauve issues to server implementations that weren't
respecting the specification. The issue in prosody has been fixed, and one has
respecting the specification. The issue in prosody has been fixed and one has
been opened [for ejabberd][IBR_ejabberd].
Larma tackled issues with bot bridging, where for example with
[matterbridge][matterbridge], users of the bridged network are displayed as
talking through the bot. This could be improved UI-wise, but requires some
groundwork and spawned [discussions][MUC_thread] about the groupchat protocol
in some specific cases.
Larma tackled issues with bot bridging where users of bridged networks are
displayed as talking through the bot. This happens for example with
[matterbridge][matterbridge]. This could be improved UI-wise but requires
some groundwork and spawned [discussions][MUC_thread] about the groupchat
protocol in some specific cases.
Fiaxh spent some time improving the empty placeholder for no opened
conversations in Dino. Here is a preview:
![Dino no-conversations placeholder screen](../dino-no-conversations-placeholder.png)
Other people worked on Jingle File Transfer interoperability and narrowed down
the cause of a somewhat old issue [in gajim][FT_gajim], and also discovered
an issue with the epoll backend [in prosody][FT_prosody], and another [in
Other people worked on Jingle File Transfer interoperability. They narrowed
down the cause of a somewhat old issue [in gajim][FT_gajim], discovered an
issue with the epoll backend [in prosody][FT_prosody], and another [in
dino][FT_dino].
[Renga]: https://github.com/HaikuArchives/Renga