I really appreciate you taking the time to bring me up to date and explain some of the processes and the rationale behind them. Unfortunately, I am not following your logic and the dashboard interface and functionality do not seem to follow that logic either. [See attached screenshot]
For starters, your scenario of someone (a stranger?!) scrolling through someone else’s feed to get their blockstack ID and send them Bitcoin is far fetched at best. “People would have no other way to get your Blockstack ID otherwise” - yes, they can simply message you and ask you for it. Once again, it goes back down to basic privacy. It is great if someone who, for whatever bizarre reason, doesn’t want to send you a DM on Twitter but wants to track you down on Blockstack and send you Bitcoin can find you. However, for most people it simply opens them up to creeps, stalkers and hackers. You wouldn’t post your mobile number or home address publicly for anyone to access. It completely undermines the whole point of building a trusted ID online.
Second, in regards to “it not being possible to store your verification status” so users must scroll through your old tweets to verify you themselves. That is both extremely poor UX but also entirely undermines the point of having a Blockstack ID with social verification built in.
The green circles show how the current Blockstack ID saves your social media handle. I have blacked out my Facebook and Twitter ones, but they are there. It can be contrasted to the ‘empty’ Github of Hackernews account.
The blue circles show that once a handle has been entered, there are to options: Verified or Unverified. This can also be contrasted the ‘empty’ +1 and star standard display.
Finally, the orange circle shows how there is a computation that aggregates the sum of your ‘verified’ or ‘unverified’ accounts.
My two accounts were briefly Verified before I deleted the tweets. My entire argument is that the Verified logic should be changed from “Verified: Current Post Content (ongoing)” to “Verified: Post Content Match (Yes/No), Timestamp it, Reset Yes/No field every X period requiring new verification”.
You are correct in that I am thinking from an App Developer and User perspective. That is how I see the ecosystem will grow: new users will be attracted to the App and the ecosystem will grow around the App. If the verification system is broken, they will simply go away. People do not need Blockstack to send Bitcoin, and it may only be a lot further down the line that people will seek each other out to engage though Blockstack. At the moment there is no shortage of fully developed engagement and payment options (centralised and crypto).
Most importantly, changing the verification requirement does not mean that users that want to broadcast their IDs to the world and promote the ecosystem that way can’t do it. They most certainly can still post and leave it up. It simply means that now the user has the choice to maintain it up or delete it.