I don't love that a company that owns this solution. That's a centralized failure/leak point. Maybe it would be a good way to onboard less techy users to Nostr or at least expose them to the ecosystem?

What are the privacy implicatons of this though? This one app has your logins for three/four different accounts inclyding your nsec? I just don't know if privacy-focused users would ever go for something like this.

I'm personally happy with Nostr and I don't much care for the other platforms. I try to onboard people onto Nostr if I can but that's a slow process.

nostr:nevent1qqs2pzgjgze6yq8kga2m794tzjcvzzsw6sdjlhxcklxsdna97j76y0qpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctczyqxsvjqtp3hrhc7f5xn96lntcgy3yf74t06vwlhtvqmm5amkcvqwcqcyqqqqqqgkvljd7

Reply to this note

Please Login to reply.

Discussion

For now I think I'm fine with that. Centralized points will have their struggles maintaining features, and raw, signer-client-relay model can only get so smooth IMO. I still think much of the work of larger clients will still be heavily server dependent for a given app. This will likely lead to some soft-forks for optimization and such.

I think I'm okay with a few big-funded clients, because, while they have influence, they will still rely on the network to a point. The issue may be the pressure a big client puts on relay operators/developers, maybe load or feature set.

I think nostr will be as decentralized as the revenue source is. I think of it as a funnel, clients are user-facing applications and therefore have the most work and easiest revenue generation. However they depend on "public" infrastructure. So, clients now have the responsibility of UX. Incentivizing clients to in-house manage their own relays and therefor feature sets their user's want.

Nothing is stopping a client developer from hosting their own paid relays locked to their client app, walling off their network. To be honest I think were going to see that more, especially around content moderation. Fork a client, stand up your own relays, lock client to your relays. Closed and branded social media network.

Nope, not crazy.

I don't have to lock relays with Biblestr, as I'll be filtering based upon labels (manual curation), and the sorts of clients we build will only have a default, not a lockin, but I could imagine someone doing that.

I think it's a weaker business model and won't last for anything other than niche products or highly private groups, tho. Even private groups would be better with encryption instead of lockin.

Lockins drive users up the wall and would encourage forking.