{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
- 2y ·
-
Public·
-
friend.camp
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
Funny thing: I was going to set up some meetings at work this morning to talk with, you know, actual experts on content and identity verification to see if we can come up with some tools to AID rather than SUPPLANT the already rather good and decentralized system we have. (For example, your employer might literally just be unwilling to add a rel=me for you for baroque IT reasons. So how do we make that easier for them? Etc)
Anyway I'm still gonna do this
@darius Apparently qualified.
"come for facts, stay for snark, & wear a mask | immigrant | husband + dad | equity advocate | recovering healthtech exec/entrepreneur | infosec researcher | anesthesiologist | nerd 🤓
JOINED
Nov 03, 2022"
Man that whole idea sure does have strong "I just came in from Twitter and what this decentralized network needs is some SERIOUS CENTRALIZATION" energy. And lo and behold its creator has an account created a week and a half ago.
Kudos to him for a super fast solution to a problem he sees, I guess, but...
@darius @rysiek The obvious "other solution" is, at least for smaller instances, to run your own verification service, and let other users trust or not trust that verification. It all really depends a lot on what you're trying to verify and why - is it equivalence with AFK identity, or affiliation with certain groups, or being the actual beneficiary of a fundraiser or Patreon, and so on
> "well you can just buy any old domain name and pretend to be whatever org you want"
And then that's how he came to buy Fedified.org and pretend to be whoever he wanted.