Ulka Athale <[email protected]> wrote: > Dear all, > At the last RIPE Meeting, I presented at the RIPE Community Plenary on > Mastodon, asking if the RIPE NCC should run a server that would be open > to community members. The presentation is at: > https://ripe87.ripe.net/archives/video/1251/
> The feedback we got was that this was not something we should do, or at
> least not right away. The main concerns were about the work involved
> and the difficulties in moderating a public server.
> Given this
> feedback, and considering the costs and maintenance required from our
> technical staff, we will not provide a server this year.
Good. I see no reason for RIPE to run a server accessible to members.
(RIPE doesn't offer SMTP/IMAP either)
> 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
Good, but there was also a suggestion that RIPE operate a server that was
restricted to staff/management only. RIPE does operate SMTP for ripe.net.
(SMTP is ultimate original decentralized system)
> 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.
> If you’re already on Mastodon, you can follow us at:
> https://mastodon.social/@ripencc.
I've followed.
I would RIPE to consider if continued presence on twitter is ethical.
What criteria would you consider in this decision?
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
-- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ripe-list
