This is definitely better than that the copy we have in the "Create Subchannel" modal on web today.

That said, I'd like to revise this for three reasons:

1. Would be good to match the language we have in the "Create Subchannel" modal, which doesn't prefix with "Make it so"
2. Would be good to try to use language we can also use in the "Create Subchannel" modal. Granted in this case it's applied to the community root versus an arbitrary channel, so there will probably need to be some differences
3. As part of the Roles project, it will be possible for the admin to assign privileges to post in announcement channels to other roles

How about this?

Subchannel creation modal

Only admins and other admin-appointed roles can send messages in an announcement channel.

Community creation modal

This option sets the community's root channel to an announcement channel. Only admins and other admin-appointed roles can send messages in an announcement channel.

I think we should just drop the ancestry section of this modal until we have multi-keyserver support.

This could work

I feel like the best thing would be to hardcode "ashoat" as the keyserver name since that is the only keyserver we have right now. When we do have multi-keyserver support we can then come back and update this accordingly

I'd probably prefer this

It's a tradeoff between confusing users who might think it's weird to see my username there, versus misleading users who might be surprised to learn that their community is hosted on my keyserver. I think I lean towards Ginsu's suggestion, but I can see arguments for both sides

What does form do here? Searched the codebase and I can see we use it in some other places in web. I know we're not actually using the classic HTTP form functionality (sending on submit), and I vaguely recall <form> elements having some other function (outside of sending on submit), but I don't recall what that functionality is