Keeping it at the user level is way worse. That's like Robert Breedlove recommending or following Swan Bitcoin's app. How helpful is that if he's not into software?

I care about verification, about "Is this app safe to use?", about "Does it only do NIP-49 key encryption and nothing else with my key?".

Builders (or specialized DVM's) actually have the skills for this. They will not do this for free, but anyone can pay them (even in the open). And their verification can verified and they have a looooot to lose.

FOSS also helps here in bringing a level of transparency you'll never have with users.

Reply to this note

Please Login to reply.

Discussion

Seems like the same problem with apps as with users. Just because I "trust" an app doesn't mean it's qualified to recommend any other app. Neither Breedlove nor Coracle should be trusted to recommend a hardware wallet, but I would trust Wallet Scrutiny or Odell. The difference is that while businesses have more resources to make good recommendations, they also have more perverse incentives to choose recommendations that make them money.

That's why I like the idea of showing the list of people that you know that endorse/follow the target (app, podcast, mint...)

Among those people, maybe you'll find the developers you trust, maybe you'll find the podcasters you trust, depending on the use case.

The alternative is to build specified competency/recommendation events for each relevant topic/category, but who chooses the categories?

Yeah, that's the real sticky question

True.

Ideally there's a separate market of Verifier services (payed by user or builder). I just think it's smart to bootstrap that market from the dev side and not from "which users follow what apps".

It's like buying a new car and letting a mechanic that you trust do check up on it's quality.