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] Routine Monitoring of Source Address Validation Deployment by Operators
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Keith Mitchell
ripe at keithmitchell.co.uk
Tue Apr 30 15:20:43 CEST 2024
On 4/29/24 05:57, Ulka Athale wrote: > We had two main questions with setting up our presence on Mastodon - > whether we should run our own server, and whether this should be > open to the community. Running our own server offers some benefits > like greater control and the ability to set our own moderation > policies. This, of course, comes with the need for RIPE NCC staff to > invest time and effort in maintaining this server We set up our own community/open Mastodon instance <https://mastodns.net> at DNS-OARC, and found both that running this is fairly low-maintenance, and also that there are readily available mastodon-as-a-service providers out there that can make it easier. The OARC community is rather smaller than the RIPE one, however, so it's possible that moderation and AUP etc issues may be more significant than ours. Overall we've found running our own server to be a positive so far, and it's good to see RIPE having a Fediverse presence. Keith
- Previous message (by thread): [ripe-list] Mastodon for the RIPE Community
- Next message (by thread): [ripe-list] Routine Monitoring of Source Address Validation Deployment by Operators
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]