Untitled

This is a solid idea IMO, but maybe use Rootstock instead of etherum? I’m told we’re Bitcoin maxis here 🌚

It shows up in my feeds and notifications on Ditto.

https://fevela.me/ has a toggle button.

I’ve been doing it when I don’t want my replies to show up in people’s feeds, but I don’t know how effective that is.

Voting? That sounds like a recipe for disaster.

Facts

Once we can deal with adding and removing members, then we can create a system around publishing NIPs that people can vote on. And maybe we can also recreate nations from scratch too.

This is what I thought too, but after attending the recent conferences I observed that the people wish for a higher level of coordination.

I’m doing some research into building a decentralized public groups. I’m calling it a “fellowship”. People vote to add and remove people from the group. I’ve been reading about DAOs on Ethereum and also looking at the idea of a multisig “treasury UTXO” on Bitcoin that members can spend at 2/3 to redefine the list of members.

God damn you kind 1111 replied to a kind 1. 👏🔥 Fucking based. I didn’t even read your post yet just appreciating that fact, hang on

https://github.com/nostr-protocol/registry-of-kinds

I agree, I think standards can be written anywhere, we don’t need a standard for writing standards. They can be in a website, a note, an article, they can be an implementation that everybody copies.

The NIPs repo has served the purpose of having people share ideas and get in agreement about them before implementing, but that can be done elsewhere.

The stressful parts of the standardization process aren’t going away ever, and trying to do your own thing and let others copy later can be good but can also be pretty bad for everybody, it depends.

In general I think some protocol designs are much better than others, by a huge margin, and that doesn’t correlate with the people who make the better products. Also if someone has had the thought in their mind of making something as an open standard rather than a proprietary API that person is already much better qualified to writing that standard than someone who doesn’t care at all and isn’t even reading this note. But exceptions exist.

I like this approach. Significant effort goes into curating NIPs, I’d like to be able to delegate my ‘view’ of the NIPs to a committee and publish variations for specific NIPs. This way my overall view doesnt go stale. I’d also like to inspect other people’s view, particilar their explicit variations.

yes, like nostr nsec bunker support across more OSes. Android is there.

some friendship for a shared cause seems to be fragmenting 💜

salty

Neither flat nor centralized. I think hierarchies of committes, each with their own reputation is probably the way to go.

Broader adoption fixes this.

Just make your client sick af don’t argue with autists on GitHub, if your client gets users other clients will follow

Wasting so much time trying to make 100 clients interoperable for the same 12 users is useless

What kind of results?

Results.

What qualities must the center of the ecosystem have, and what qualities must the remainder of the ecosystem have, for the center to be respected?

What is the best model of coordination? We can recreate GitHub on Nostr with its hierarchy. Or we can use the Wikifreedia model. But actually instead of a NIPs registry maybe we need a kinds registry.

Who is this godlike figure? Our savior 🙏

That’s exactly how the nips repo works. Anyone can publish a “draft spec” via PR, and those can be refined and merged into the “core” after sufficient buy in from the community. I’m not saying it’s ideal, but it is not a terrible model and currently better than e.g. nostrhub.io, although I know @npub1...cd26p is planning to update that.

A healthy ecosystem needs a respected center.

Not because people are forced to follow it.

Because coordination has value.

And if that center stops serving the ecosystem, people can fork and build something else.

As Bruce Lee put it:

“Do not cling to partiality, however fantastic—see things from totality. When the totality is taken apart it is no longer total. All the pieces of a car that has been taken apart are there, but it is no longer a car and cannot function to its nature.”

That seems relevant.

A form of WOT then.

Anyone can build whatever they want. Anyone can publish a spec.

But not all ideas are equal.

Some improve interoperability.
Some improve adoption.
Some create a better experience for users.

The ecosystem should be able to identify and promote those efforts while still leaving room for experimentation.

Linux has countless distributions.

It also has a kernel.

Experimentation belongs at the edges.

The core should be standardized, documented, and promoted.

Otherwise every new user inherits the complexity.

Nostr.com seems like a natural place for that, @npub1...n8avm. A well-documented—and promoted—center of gravity benefits everyone.

Nostr has plenty of hammers. The missing piece is getting everyone to hit the same nail.

The ecosystem already has plenty of standards. The challenge is getting enough apps to implement the same ones in compatible ways so the experience feels consistent no matter which client a user chooses.

yes, more NIP synergies