Explore and implement non-public twitter verification

[Kailai-Wang]

Context

At present, we require users to post the verification message as a public tweet. This can be a bit weird (imagine your friend suddenly posted a line of hex strings on twitter...).

Shall we provide a way to verify it privately? E.g. oauth + bot
Shall we allow users to decide on the verification method? (publicly or privately)

cc @kaylawangnow @jonalvarezz

---

✔️ Please set appropriate labels and assignees if applicable.

[jonalvarezz]

That'd be fantastic if we can support both.

Technically speaking, how would the private verification work? Would it still happen in the Enclave?

[Kailai-Wang]

That'd be fantastic if we can support both.

Technically speaking, how would the private verification work? Would it still happen in the Enclave?

We would need to host a service for oauth verification I believe.
Ideally this service can be put into enclave, but maybe not in the first step.

[github-actions]

❗ This issue is stale because it has been open for 60 days with no activity.
Please take proper action against it.
@litentry/parachain