Too bad the Nostr nest guy violated the Jam systems license and wouldn’t open source his software and teared apart a growing community.

you can talk to @semisol about that. nests was migrated and recreated in full open source glory afterwards. im sorry your butthole still hurts.

too many apps to use today lol. nests was one of the most popular apps back in the day because we needed a way to meet one another.

wait wait wait… is this true? did @Derek Ross use AI to vibe code nostr nests based on open source code, then after community grew shut it down rather than open source it? if it is, we need to know.

Before the AI tools were good enough semisol forked jam systems, users had ideas and wanted to contribute but were gate kept, that’s the origin story of corny chat

thank you.

LMAO! this is so far from the truth it's actually hilarious. wow is that what Puzzles is telling people? I unfollowed him three years ago. That would be pretty much on point for him to lie like that though.

i definitely don’t want to get in the middle of a personal conflict. it seemed out of character, so wanted to clarify

thanks <3

It was more complex and weirder than that. Derek started hosting Nostr Nests independently based on Jam software. They made some minor modifications early on, but got bigger. With our existing work together on Nostr Plebs, I agreed to help. With there UI leaving a lot to be desired, me, @TC and @Karnage worked on a UI redesign. Most of the core remained the same, with mostly some UI changes. I have been clear that Nests was based on Jam, and I have never tried to obscure that. Anyway, at this point, it was decided that a complete rewrite, fully independent from Jam was a good idea. There were too many issues with large rooms on Jam. Also, it was built with a different identity system than Nostr, which made it hard to integrate. The main reason that we, together, decided to not make it open-contribution is due to the rewrite. It would be fully open source and open contribution, and more suited than that. (Looking back, I’m not sure if that was a good choice or not. The code depended a lot on internal details to work.) Anyway, I did not have the motivation to work on the rewrite due to burn-out and personal reasons. This was not helped by the fact that our informal agreement with Derek that it was a shared project fell through, of sorts. Derek had made it clear that he treated it mostly as his own project including making unilateral decisions, and I felt like that was disrespectful to the work of me and others. Around that point I left and took a break from Nostr. I did not track what happened fully next, but I believe it was replaced by a rewrite by Kieran and then proceeded to become inactive. —— If it was ever unclear that Nests was based on Jam, I apologize for that. There was never a goal to gatekeep contributions, but more that it was simply not suitable for it due to it being designed with so many internal components. The situation was more complex than this person was solely responsible about it”. Even though I have mixed feelings about it, I will not share my personal interactions with Derek in depth out of respect for privacy.

thank you for caring enough to take the time to write all this. 👍

I appreciate your response but based off Jam’s license you shouldn’t have released the software without making the repo public to begin with. It’s in the past now and no sense of crying over split milk. The sad part is how it teared apart Nostr. After Cornychat was released clients refused to integrate it because they didn’t want to offend Derk In my opinion this is when interoperability on Nostr started going downhill. The Nostrati began scrutinizing what constituted as a Nostr client with Fiat Gaf hand waving cornychat as “Not-a-client”. Now that the Nostrati has abandoned Nostr and migrated over to X there is a chance for the surviving misfits of Nostr to regroup and try again.

I could not bring myself to work on the Nests rewrite while being exhausted, under public pressure, and other concerns. The unilateral decisions about a project I contributed to so much did not help. I forgot to mention, we held a bounty pool to be paid out to any contributors to the ground-up rewrite, that was separated. I transferred any custodied sats for this bounty I might have to Derek when I left. If I remember correctly, we also compensated both TC and Karnage out of pocket from Nostr Plebs for their work. It was however unfortunate to see Karnage’s design work go to waste.. —— I do less Nostr development now. Mostly because the AI slop takeover, and the focus on quality going downhill. I have tried to prevent that to some extent, but I have failed. (Especially on the NIPs, where my access was revoked) But, it is great to be able to work with amazing people like @Karnage and the @The Fishcake (nostr.build). I try to do the right thing. Sometimes I make mistakes.

Making it open would not have helped with interoperability, unfortunately. Jam was not designed for that, which both Nests and Corny Chat were based on. It would have been good to fully open up, but it’s gone now. There was no attempts though to “lock it down”, and it remained compatible with the base Jam software. The goal of the rewrite was to provide specifications anyone could implement to get their own fully compatible audio room. That got lost after the takeover, somehow. I attribute the downfall more to Primal and fast-moving specs, more than “scrutinizing what is a true client”.

Took a good 30m or so to write. I have also included some additional details here: View quoted note →

I don't know what stage the nest is at inside nip-29