ether+nick

@valorzard I recommend some good patterns:

- Use fallbacks.
- Support multiple profiles -- people are doing great with draft-cavage-12 and RFC 9421, for instance.
- Think about how your software will interact with software written by someone who never read your FEP. Will it fail gracefully, fallback to default behaviour, or crash and leak private data?
- Be compatible with the spec, and not just compatible with Mastodon.