It's early days for Zapstore so there are still single points of failure:

1) single hardcoded apps relay

2) few hardcoded social relays (profiles and social notes)

3) single hardcoded web of trust service

The app relay has two different risk profiles:

- for developer-signed apps: censorship risk, just like with any regular nostr relay

- for external apps signed by Zapstore (the ones picked up by our indexer): censorship and man in the middle attack risks.

My goal for the first half of 2025 is to fix or mitigate these issues:

1) offer app relay management, prepare for community-based relays, and another distinct app relay for external apps; as well as working on some additional form of app vouching, either by users or vendors

2) use all social relays with outbox model

3) offer WoT DVM management to choose your preferred provider

In an ideal world, all developers self-sign their apps. To get there we have to keep hustling and make the best product possible, and work hard on our outreach, to entice more and more developers to join.

Just like a better Twitter won't fix social media, no centralized app store, no matter how well intentioned, will be able to fix app distribution at a global scale.

Reply to this note

Please Login to reply.

Discussion

From what you've posted, one big problem with Fdroid is governance. Would you agree? Governance is hard to do well. What are your ideas for how to do it well?

Which governance?

Our goal is to provide tools to remove middlemen or minimize trust in them.

Governance of the project.

How you make decisions, long term goals, short term goals, what features you decide to add to your app, what if any marketing you do, and so on.

When a project is small, you might think that governance is unnecessary, everything is obvious. Then the project grows, more people come in, there are disagreements, different points of view, perhaps even malicious actors, and you don't have a working system in place to resolve all that, a system for making decisions.

From what you've said, Fdroid is making mistakes. But there is no way for you to influence them to fix the mistakes. They have bad governance. The bigger the project, the less you need to think about technical details (because you'll have other devs to do it) and the more you have to think about big picture items, including good ways to make decisions.

Honestly I don't know. Why do I need a system for making decisions? I just make them. Zapstore is not a democracy.

If F-Droid is a dumpster fire and they don't listen, use something else.

The beauty of OSS and open protocols is that anyone is free to fork AND take users data if they don't feel their opinion is being taken into account.

We need sourcestr

What does this mean?