I feel that so far in #Bitcoin, #Nostr, and the #Pears stack we’ve had a strong focus on two things:

• User facing wallets, app, and features

• And fundamental network design and implementation

However, there are drawbacks to what we’ve focused on: The fundamental network development is critical, but isn’t understood and doesn’t interact well with the end user. While the end user wallets and services often have huge trade offs and rely on third parties or custodians.

We have basically let the market for centralized companies work to bridge between these two areas of development and demographics of the community.

But as has been shown with recent arrests and the fear rippling through public service providers, I think it’s critically important that we start focusing on building tools to BE a service provider, that are as simple and easy to operate as the end user wallets have been designed.

The barrier is still too large between the end UX and the core tools of these environments.

For example, we need to think about how we can design an interface that lets anyone with a couple of BTC be a private LSP, automatically, with channel splicing, and try at lets users connect to and use them in popular wallets with nothing but a QR. This would radically change the landscape if “running a server” is as easy as we can possibly make it. This would be the key to genuine decentralization of the market and the ability to quietly make a huge variety of reliable and simple services and onboarding tools that aren’t bug, public, and easily targeted businesses.

It would open up an entirely new layer of the market that is never actually targeted and with tradition infrastructure, isn’t really possible. But the new protocols we have today change this. We need to change how we think about the architecture of the market when we have new tools that, rather than simply building the same things with new tools, allow us to completely rethink how things are built in the first place.

Recently piece from nostr:npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m is a great example. IMO, It’s time we think about UX for sovereign providers the way we’ve always thought about UX for the average user.