Subnostr

The problems with everyone working with NIPs as permanent PRs is that

* people keep starting new PRs to cover the same topic, rather than joining in the working group that already exists

* without a NIP ever being merged or listed, there's no reference point, for newcomers

* the NIP never reaches a frozen state, as you leave the PR discussion and come back and files have been added and whatnot, and it's like, At which point in this PR thread did I implement this NIP?

* there are almost 600 PRs, already, and Nostr is still relatively small

* some PRs do actually get merged, but there's no clear criteria or schedule for merging, so it just looks like favoritism

* all of Nostr's use cases are documented and discussed primarily on GitHub, which is embarrassing for a communications protocol (i.e. "the developers of Nostr don't want to use on Nostr")

Reply to this note

Please Login to reply.

Discussion

The Beave 11mo ago

This is the worst kind of nepotistic idiocy for a protocol that is supposed to be anything but nepotistic idiocy.

GTFO of github. Seriously.

🤬

nostr:nevent1qqsw9cfgl7ug3kp47ytu6r87e9094ntrtjf3g8l7sw7em7rdwqxd3gqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7q3ql5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqsxpqqqqqqz0rnsn5

Niel Liesmons 11mo ago

That last point keeps surprising me.

"But I don't want my git stuff in tHe FeEd" 🤦‍♂️

Silberengel 11mo ago

Yes, it's bizarre. Entire feed is dev talk, anyway. 🤣

Niel Liesmons 11mo ago

Yup, two blindspots:

1️⃣ 80% of conversations (as distinct from the influencor-worship-one-directional messages) are dev talk already. Except on global of course, there it's Babylon all day, every day.

2️⃣ tHe FeEd is a terribly blunt tool for navigating a multi-content, multi-community connected web of data.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 11mo ago

that last point is a glaring pain point for anyone who understands what the purpose of nostr actually is

Niel Liesmons 11mo ago

It's still hard for me to understand why this wouldn't be the first thing you'd build on this protocol, with 80% devs.

Niel Liesmons 11mo ago

gitworkshop needs competition, tons of it

Colby Serpa 11mo ago

Oh don’t worry… we’re cookin👨‍🍳

Niel Liesmons 11mo ago

Good.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 11mo ago

i'm of the opinion that the thing that makes the difference will not just be in capabilities but architecture

a simpler way of talking about things tends to make them easier to code

but maybe i'm weird like this, being a #golang #gopher for the last 8 years everything gets tighter and simpler at the same time... even in my own code i tend to net reduce the amount of code after a certain point with a project

worse is better, simpler takes a lot more work

Silberengel 11mo ago

Yeah, we moved to work on Alexandria, partly because the gitstuff field was incredibly crowded, and now it's like

Niel Liesmons 11mo ago

It's the one use case where all the solo-devs don't have to break their head all day on what UI/UX the normies would like. Non capisco 🤌

Silberengel 11mo ago

The problem is that solo devs are all GitHub junkies.

Silberengel 11mo ago

I bet we were the few ones thinking of a serious alternative because we're used to using other gitservers at work, so we don't give a crap about GitHub.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 11mo ago

been running my own gitea and on and off using gitlab for years

Daniel Wigton 11mo ago

Not true! I have my own git server in my basement that only I can access. Is that better or worse?

Niel Liesmons 11mo ago

For now, I'm unfortunately way better at making this meme than at making Ngit work. So yeah... hypocrite until I learn that stuff.

Silberengel 11mo ago

The important information to know is that GitHub is just a layer on top of a gitserver, and the main parts we use are the patches and the issues, which we have in gitstuff events.

You could keep GitHub as a remote NIP repo and everyone could have their own repo clone and decide, by themselves, which patches they pull. That would end the need to grovel to the repo owners, to get a NIP merged. More-popular patches would be pulled by more people, even if the GitHub repo owners don't like it.

The people you actively work with would tend to have patches that you are more-likely to see, which eliminates the need we've developed to go off and have topic-chatrooms, so that you can finally talk with the people interested in a Nostr topic on Nostr.

But whatever.

We haven't ever gotten any use out of the NIP repo. Only grief. Over and over, nothing but grief and time wasted that we coulda spent developing and shitposting.