@evelyn @ralf also there are existing standards that define these web of trust assertions, so could just use that. Not sure what you're referring to with the whims of twitter users?

@evelyn @ralf well your local server could provide their own assertions, I was just using mastodon.social as an example here. You probably wouldn't display assertions from other servers.

@evelyn @ralf Mastodon servers could even start configuring their web of trust, which could then be displayed. You could show "Whistleblower Support is verified by Independent Whistleblowers Intl which is verified by the Dutch govt which is trusted by Mastodon.social"

@evelyn @ralf the website is the best description I've found of VC, but is commercial. VC could be used for any type of claim (not just ID cards and stuff). For example, a whistleblower support org could give out VCs to whistleblowers that says "Whistleblower Help Foundation verifies that the person that owns @[email protected] has worked at the DOD as an Analyst" or whatever. Using the VC format Mastodon could then display that nicely and help users understand whether or not to trust this claim.

@evelyn @ralf not sure how this is much different from the existing domain name ownership verification that Mastodon already does.
There are plenty good reasons to have verified claims integrated into the platform. Verified Credentials allows federating (decentralizing) the verification. Seems perfect for Mastodon?

@randomdude @ralf @fraunora I think it's an important step in a web of trust usecase. I've been considering building some very simple OSS backend for issuing these for common "blue check" usecases, along with some Web Components (or similar) to display them.