This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[ripe-list] Mastodon for the RIPE Community
- Previous message (by thread): [ripe-list] Mastodon for the RIPE Community
- Next message (by thread): [ripe-list] Mastodon for the RIPE Community
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sasha Romijn
sasha at reliablycoded.nl
Wed May 1 22:57:04 CEST 2024
Hello Ulka, On 25 Apr 2024, at 15:26, Ulka Athale wrote: > However, there were also suggestions that we should dip our toe in the > water. So we have started a RIPE NCC account on Mastodon that > community members can follow. We hope to connect with people and also > learn more about the Mastodon ecosystem. We can then revisit this > question at a later date once we are familiar with the platform and we > can better assess whether there is appetite for us to provide a server > for the community. Great to see RIPE NCC on Mastodon! I don’t think I commented in the community plenary, but I strongly feel that while a server for RIPE NCC’s own accounts or NCC staff can make sense, RIPE NCC should definitely not run a general Mastodon server for RIPE community members. In this way, Mastodon is in my opinion similar to mail or web hosting here: the NCC runs those things for their own operations and for things like RIPE mailing lists, but does not offer them to RIPE community members for general use. There are many other service providers that do this already, and having RIPE NCC run this adds many headaches at very little added value. Sasha
- Previous message (by thread): [ripe-list] Mastodon for the RIPE Community
- Next message (by thread): [ripe-list] Mastodon for the RIPE Community
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]