Let me put it this way...

They made zero effort to not leave this impression with me. They just wanted me to go away, so I did.

Do you think people hear about a project you are working on and make a NIP to stiffle you?

I can relate to where you might be coming from. I was working on a tool for quite a while and then a draft NIP dropped with a basic reference implemenation, which caused a bunch of rework if I wantednto be compatible.

I don't think anyone was trying to stiffle me but just wanted to see some progress in a problem space so had a go and opened a nip to start the discussion.

Staking out a new space doesn't work because they drop everything to front-run you with a NIP and then they start changing the NIP.

That's why their stuff stays buggy and they constantly implement new features. They need the implementation as an excuse for the NIP and the changes to the NIP. If a NIP isn't backward-compatible, all the better. Everyone else's product immediately becomes unusable and it takes them a while to catch up again, so they lose users.

Strategic advantage of a monopolist preemptively controlling other people's design.

That's why I call them "Nostrsoft".

my relay is already storing multiple versions, because deleting is racy and it's more stable to not delete the events but just show the newest one

no coincidence a bunch of people over the last idk whole time of this protocol talking about losing their metadata... won't happen if there is relays keeping multiple versions and not deleting

Ok, TIL.

But I don't know how to apply this ... with these refs available do I have to configure them as in the screenshot or can I use them meaningfully without an extra config, too?

$ git fetch

$ git ls-remote | grep merge-requests/604

From git@gitlab.com:walletscrutiny/walletScrutinyCom.git

80139aed030bb303682865d74cf4204c41b760fe refs/merge-requests/604/head

70affc2f1b0a2cb73a35992d5357d272704fe5c8 refs/merge-requests/604/merge

$ git checkout origin/merge-requests/604

error: pathspec 'origin/merge-requests/604' did not match any file(s) known to git

So I can $ git checkout 80139aed030bb303682865d74cf4204c41b760fe

HEAD is now at 80139aed03 Third batch of _desktop wallet reviews and images

but as gitlab allows me to push to the respective branch, I'd really like to have a branch and not just a revision. So I #askNostr?

it didn't restore your profile very well, i can't see it on my relays currently (nostr.wine nostr.land)

yes, this "replaceable events" thing in the protocol needs some work IMO

the hamster wheels will tick over duly thinking about this because i'm not happy with this part of the protocol, i think that "replaceable" should mean that the old versions are retained and there needs to be a way to request old versions

yeah, funny thing... in the code i work from it's horribly written, i've fixed most of it but finding a solution for this versioning issue would be cool af

it didn't restore your profile very well, i can't see it on my relays currently (nostr.wine nostr.land)

yes, this "replaceable events" thing in the protocol needs some work IMO

the hamster wheels will tick over duly thinking about this because i'm not happy with this part of the protocol, i think that "replaceable" should mean that the old versions are retained and there needs to be a way to request old versions

yeah, funny thing... in the code i work from it's horribly written, i've fixed most of it but finding a solution for this versioning issue would be cool af

🤔 I wonder if that's because I no longer write to those two relays... Do you use any others?

Yeah, I did that, but still follow the same low number of people (I used to follow 1000+)

Apparently that didn't restore my follows, though...

How can we create repository management and contribution UX using nostr which compete with Github without replicating the 'cathedral' qualities?

philosophically, nostr aligns more with the 'bazaar' model.

GitHub doesn't allow a project owner to block PRs. You can spam any public project with PRs. And people use it to file issues where the issue tracker is not public.

Lets improve on that in NIP34 💪

It seems natural to me to document Nostr with Nostr. People can use their WoT and notes that "like" or "star" other notes, to add weight to one version or another.

Organic curation.