_______________________________________________Thanx for the discord.
That’s the the only useful step forward in this discussion unless the remit of TTF is cleared.
Von: Evan Leibovitch via At-Large <at-large@icann.org>
[…]
But that's perfectly OK. Creating an ALAC shared space is trivial to do. If a consensus of people simply goes there and starts chatting, then that's it. No permission, no approval.
Just watch. Here is an ALAC Discord server, complete with voice capabilities and subgroups for every RALO and a few committees, ready to use IMMEDIATELY. Feel free to try it right now:
https://discord.gg/94Q2wFFM
The only next step necessary is for people to start using it. No cost ever to users or to the Discord server administrators.
And if the consensus is that people here don't want to use it? Fine, while unpopulated it's as easy to dissolve as it was to make. Signal, WhatsApp, and Telegram all await as alternatives.
The TTF was formed as an ALAC committee, not an ICANN one. Any restraints it imposes on itself to require ICANN blessings are of its own, voluntary, absolutely unnecessary, design.
- Evan
ttf mailing list -- ttf@icann.org
To unsubscribe send an email to ttf-leave@icann.org
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.