From fa9ab1b807eac29a42baa83e0659f4fc8f28bfd7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Thu, 3 Oct 2019 10:01:43 +0200 Subject: [PATCH] Stockholm sprint: Remove commas and use periods. Thanks lool0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- content/posts/stockholm-sprint.md | 50 +++++++++++++++---------------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/content/posts/stockholm-sprint.md b/content/posts/stockholm-sprint.md index 0a5fddc..73efb9c 100644 --- a/content/posts/stockholm-sprint.md +++ b/content/posts/stockholm-sprint.md @@ -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