Hello,
Alan, I think the best usage would be one suggested by Mark Stevens.
Only post actually relevant notifications. definition to be elaborated.
The fediverse is full of bots already, but they usually try to post
useful and wanted information, not just automatic results from some
verbose automatic machine.
You could discuss the utility of a bot that post a cat picture every
hour, but people actually want this.
The result of automated build? Why not, but with a purpose.
I'm not sure the fediverse is a good message bus. All bits posted on it
are info made for human consumption. If too many irrelevant information
is posted, it will bloat the whole thing. And if people dont like it,
the instance you use to post these messages will be quickly be
defederated by everyone (like qoto is already) and you will end up
"screaming alone in the dark" without anyone being able to listen to
you. Also circumventing these bans to maintain federation is an
extremely bad move.
Thats why nuttx may not actually want to use the fediverse in that
particular manner. it would be counterproductive.
Thats why I also suggested RSS as an alternative, since people have to
voluntarily subscribe to these, and no one else will be annoyed. Several
feeds can be set up, like every notification, only failures, per arch,
per board, it's only a sql request away. I might also use it, eg, to
know about the stm32h7 build status.
The fediverse does not allow that much fine filtering of notifications
without setting up multiple bots that will spam even more. RSS is
actually better in that case.
A nuttx fediverse presence would be cool (on fosstodon?), but I think it
would be better if that was a news feed and development info managed by
people, rather than just automated build status output.
Sebastien
On 12/31/24 12:13, Mark Stevens wrote:
I’ve been thinking about this for a few days and one thing spring out to me, if
some consider the email notifications of build results to be spam (due to the
number of notifications and frequency) then we should think about addressing
the spam aspect first before we look at the delivery method.
The risk you run with bulk messages be it email, RSS, Mastodon etc is that
people ignore it if they cannot get the information that is useful to them and
crucially, get to that information easily.
From my perspective I would be wanting concise information from the build
system. Preferably information that is targeted to my needs / requirements.
It seems to me that we already have this, the NuttX dashboard. Once you have
the summary then you can drill into the detail if necessary.
Alan - I believe you can restrict the servers that a Mastodon instance shares
information with so this would restrict the spam to the rest of the fediverse
if you set the share list to empty.
Regards,
Mark
-------------------------------------------
Mark Stevens
Blog: blog.mark-stevens.co.uk
On 31 Dec 2024, at 08:19, Alan C. Assis <acas...@gmail.com> wrote:
Hi Sebastien,
I think you raised a legitime (and important) concern.
Who could tell us if this usage of the fediverse is fine or not?
Maybe some optimization could be done to avoid sending too many messages.
BR,
Alan
On Sat, Dec 28, 2024 at 6:31 PM Sebastien Lorquet <sebast...@lorquet.fr
<mailto:sebast...@lorquet.fr>> wrote:
Hi,
You know me I'm not an easy person.
If the solution to being spammed by email notifications is to instead spam the
fediverse, then this is a Very Bad Idea (c)
The solution is instead to reduce the number of useless notifications so your
emails looks less like spam. eg buils successes should probably not notify, or
in a synthetic way once a day. Less notifications is always good for humans.
Better concentration, less distraction.
I have nothing against you building a mastodon instance for nuttx developers,
obviously. But please make sure you dont spam the federated network with
thousands of build notifications. If anyone else over there has a negative
opinion about receiving notification spam, I'm not going to defend the
initiative.
The fediverse is a happy nerdy place full of very nice *people*. It's not
twitter bis. It's not a place that will widely welcome bot generated build logs
and meaningless errors messages all day long.
Why not use RSS instead? This means only people actually interested by these
logs will get them. This is why RSS was invented, so anyone can choose what
info they receive. its pull model avoids spamming shared spaces, natively.
Please think about this once again.
Sebastien
On 12/28/24 21:19, Lee, Lup Yuen wrote:
We’re on a 50 km overnight hike. NuttX Build Farm runs non-stop all day, all
night. Continuously compiling over 1,000 NuttX Targets.
Can we be 100% sure that NuttX is OK? Without getting spammed by Alert Emails
all night? In this article: Mastodon becomes a fun new way to broadcast NuttX
Alerts in real time. We shall…
(1) Install our Mastodon Server with Docker Compose (or Rancher Desktop)
(2) Create a Bot User for pushing Mastodon Alerts
(3) Which will work Without Outgoing Email
(4) We fetch the NuttX Builds from Prometheus Database
(5) Post the NuttX Build via Mastodon API
(6) Our Mastodon Server will have No Local Users
(7) But will gladly accept all Fediverse Users!
Check out the article: https://lupyuen.org/articles/mastodon.html
<mastodon-flow-small.jpg>
Lup
