@acalarch @GossiTheDog Most of the people involved have 'day jobs' and not all employers are necessarily supportive. Some people asked to have time to first discuss what's happening with their employer before their name is public.

Especially as we're already seeing people presume that because someone involved with the Foundation works for Employer X it must mean Employer X is backing the Foundation - which is not safe to assume. So there is some concern about blowback on employers causing problems for the individual.

People are participating as individuals, not corporate representatives. As people are comfortable being named they'll be added to the FAQ entry.

(This is MegaZone. F5 is not officially involved, but supports employees working on initiatives outside of F5. They're aware of what I'm doing - our CEO commented on my LinkedIn post about being part of this.)

@Quinn9282 @jerry But yeah, looking at the raw data coming in, it looks like user-embedded HTML is delivered as a payload and rendered in-browser, so if Mastodon is looking in the raw payload it isn't going to validate it. Honestly, just getting verification to work isn't enough to look for other hosting solutions, so this account will remain unverified until some future time when the site might move or a new verification system is rolled out.

Shame we can't verify via a DNS TXT record. It was a snap to do that for other accounts. But for now humans can see the site links to this account if they want to check for themselves.

@christopherkunz We'll probably be sharing some names soon, we're confirming who is comfortable being named - events this week rushed things a bit. Most of us have 'day jobs' and we don't want to cause problems for anyone by outing them unless they're ready.

I don't care myself - I'm @megazone Though I'm not the only one who will always be behind this account. I already outed myself elsewhere as participating. I thought we should have an official account here and others agreed, so I made one.