Oddbean new post about | logout
▲ ▼
Zapstore | 6 months ago (raw) | root | parent | reply | flag +2 
 During the bootstrap phase only this nsec is signing releases but I'm building tools for developers to sign their own. 

Since there is no centralized source of truth anyone can claim an app is theirs, hence the importance of the social graph to establish trust and weed out scammers
▲ ▼
elsat | 6 months ago (raw) | root | parent | reply | flag +2 
 I think this is a novel approach that does not exist on centralized appstore or play store. For instance @sommerfeld can submit an app repo for @Zapstore consideration, and review. 

Placeholder feature request: 

https://github.com/zapstore/zapstore/issues/13
▲ ▼
sommerfeld | 6 months ago (raw) | root | parent | reply | flag 
 Doesn't that still depend on zap.store repo maintainers approving a PR? Still centralized
▲ ▼
sommerfeld | 6 months ago (raw) | root | parent | reply | flag 
 Nevemind elsat, I misread your proposal!
▲ ▼
elsat | 6 months ago (raw) | root | parent | reply | flag 
 Correct. There could/should be some way to bug devs to take ownership. 

You can have slower, app dev owned growth, or faster zap.store curation. 

Even with the latter nostr WOT lends social credibility, unlike traditional appstores.
▲ ▼
sommerfeld | 6 months ago (raw) | root | parent | reply | flag +2 
 But it would be cool to also include apps where their devs don't know/care about nostr.

I was thinking of something like the Arch User Repository (AUR) where users submit packages that are not theirs and it's up to other users whether they trust it or not.
▲ ▼
elsat | 6 months ago (raw) | root | parent | reply | flag +1 
 > But it would be cool to also include apps where their devs don't know/care about nostr.


This is the default during bootstrap. It will be curious to track how dev ownership trends overt time.
▲ ▼
Zapstore | 6 months ago (raw) | root | parent | reply | flag +2 
 This will 100% be the case when we open up for users to choose their relays. Step by step