Re: [111attendees] So, what are jabber scribes actually doing, these days?

"Carlos M. Martinez" <> Wed, 28 July 2021 18:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52A613A1B6E for <>; Wed, 28 Jul 2021 11:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TQXsJIGPlGXO for <>; Wed, 28 Jul 2021 11:37:06 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0FACB3A1B6B for <>; Wed, 28 Jul 2021 11:37:05 -0700 (PDT)
Received: by with SMTP id q17-20020a17090a2e11b02901757deaf2c8so5589295pjd.0 for <>; Wed, 28 Jul 2021 11:37:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=FkXzVQcYWAmrZAjJXnA66noY1yQ9JOLjQdBUfx0S3UM=; b=huXJaQu3gHMYF6Mx8S81J3vRGlmzuKZ4L0m5TuCrmvTK6DUVYOdlBES7ZxuUa1UCxR RdyXGQCybbUzszFDV5/3HIVVV71UXVJ6eMkUbg8Wf/l7cKKufX23v0frJt3841ze4k23 AB65845fZU/uFsFIrMHpiVfeHRKsi2l94YQYBsaZvvkPLneKTALNm68pN+WrQNaqbGAW 2v0zUgbLmYdMe5a5zp4Gd+KH0tmzhRqBX9WAaq0JZF2PpMmeh32pzgnMW48Ca9qx1JJ1 d6rTi0Iy2ZKUw9sEfy+N0Ig1914A9UPsLDF5DQwX9wzG7J2/gsHxKnVJvT+dLiNaVvxw yGww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=FkXzVQcYWAmrZAjJXnA66noY1yQ9JOLjQdBUfx0S3UM=; b=RBQyBggXsJwN0PjGBFi9XuJYMgD8mCnjp/fccHaqPZbREFbuyUPdVFRF0zxezVYOsV CIMapGItLJnHIa0nAH2b4ySzLmyD/wcudd7H21IYZ4b/PtnBjLbs5/EAVlpPkFk5/3WS JDxdPR+mVhQXXZJfYRTLSQgouesVEFi4qEUW8XxCi9LqLLtVsss4FsInunfKXx7UwBAm STJFa0ZJMxAM7HbiCcBh0aWOGKI7Hkhr0yQ/BMBVgLrFbNhNERWPYuR00xV4yZpeq4Ej hpALJSD/tUghJXrXgmzDlTxa+xRmx159omLkCa09OOZUK5MBOEF6bK5dKKT49busF+qo BaYg==
X-Gm-Message-State: AOAM532gPCOZi0Zlq/2uFbS3ToyFcHtYD+F+2b7rcDrwQnLvWMaapew/ vpzt28WsbwaZR3+Q/QdtSaA=
X-Google-Smtp-Source: ABdhPJwt/pmdP/6KRWO3CUNq1iTvxNp/3VwXgr5ZYVZJc7Hif13yzySKs1LBGp1TCtE4cTZVo/bxuw==
X-Received: by 2002:a62:64c8:0:b029:3a3:b7fe:ee67 with SMTP id y191-20020a6264c80000b02903a3b7feee67mr1222054pfb.40.1627497424473; Wed, 28 Jul 2021 11:37:04 -0700 (PDT)
Received: from [] ([2800:a4:29b3:c00:b50c:207f:3dac:3cea]) by with ESMTPSA id p3sm6838992pjt.0.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jul 2021 11:37:03 -0700 (PDT)
From: "Carlos M. Martinez" <>
To: Spencer Dawkins at IETF <>
Cc: Sean Turner <>,
Date: Wed, 28 Jul 2021 15:37:00 -0300
X-Mailer: MailMate (2.0BETAr6151)
Message-ID: <>
In-Reply-To: <>
References: <> <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"; markup="markdown"
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [111attendees] So, what are jabber scribes actually doing, these days?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Jul 2021 18:37:09 -0000


On 28 Jul 2021, at 14:12, Spencer Dawkins at IETF wrote:

> I wonder if the people I've talked to who are reluctant to install a 
> jabber client, or forbidden by their IT people from installing a 
> jabber client, would have the same problem with downloading the Slack 
> client. I have very little experience with the Slack web interface, 
> but wonder if it would be usable enough for us to point people toward 
> it. 

Slack's web interface is perfectly usable and fully featured. In fact 
the Slack "app" is nothing more than the web interface bottled inside 
this scourge of the Earth called Electron.

For those who don't know me, I work for LACNIC. As a data point, for 
those interested, I've run a 1500 member Slack workspace for LACNIC 34 
with little or no issues. I only had to kick out a couple of misbehaving 

I did the same thing for LACNIC 35 using Discord and the experience in 
general was much better. We are sticking to Discord for LACNIC 36. Not 
only it is actually free (we only paid 100 usd for a bot that adds some 
controls and some integrations) but the features are actually more 
geared to a conference or informal gathering and feels less "corporate" 
than Slack.

Nothing wrong with Slack, we actually de-commissioned our Jabber server 
2 years ago and moved the staff to Slack, but my recommendation for a 
conference is Discord.