Yesterday I said that Nostr Nests was a Nostr client and that Corny Chat wasn't a Nostr client. When I first used Corny, it allowed Nostr login and pulled a profile picture and name. That was it. I have not used Corny since. It's been updated. A lot! Wow. It's now in alignment with Nostr Nests using multiple Nostr events and publishing them to relays. That's cool. Congratulations, @Nice and Kind Vic. Sorry I was wrong on the progress with your app. Keep building. ๐Ÿค™๐Ÿป๐Ÿ’œ๐Ÿซ‚ image

Replies (23)

Thank you Derek. With the pace of development and growth in quantity of new applications and services that have come on board over the past year it can be easy to miss the details. Also thanks to people like @elsat who seems to be working tirelessly to identify where apps are compatible and not with the nostrability tracking. Big things are in store and the next 12 to 15 months are going to be exciting times.
:P's avatar
:P 1 year ago
Dude this sarcastic congratulations card is a dick move. The only reason cornychat exists in the first place is because nostr nests was closed sourced which is the complete opposite of nostrโ€™s ethos. Nostr nests was closed source for the first 18 months and just recently became open after the new release. Corny Chat has been a grassroots movement with user feedback being implemented in real time while nests has been developed in private behind closed doors. The fact of the matter is corny chat exists because you and semisol played gate keeper and didnโ€™t take user feedback seriously. Not to mention nests completely ignored Jam systemโ€™s license agreement which clearly stated that all jam systems implementations have to be open sourced.
It's not sarcasm. Yikes. The attached image is a little funny, but nothing malicious is meant by it. It's just meant to add some levity to the situation. Again. Yikes. The original Nests that was a fork of Jam was closed, but open to anyone that wanted to contribute. Several people did contribute. This was because Semisol wanted to keep his indexer that he wrote private. This has been discussed numerous times. It was roughly a year, closer to 9 months if memory serves correctly, not 18 months that you mentioned. In January 2024 I began discussing working with Kieran and in February 2024 a brand new open source client launched. Here's the announcement that discusses the launch Gate keeper? No. I actively tried to get Semisol to work on Nests for the better part of a year and tried to get people to contribute, including Vic, but ultimately Vic did not want to work with Semisol and decided to go his own route. Ultimately it was for the best. Now I get to work with Kieran on a fully open source and Nostr first client that I've always wanted for Nests. You were there for all of this. I'm surprised you don't remember it this way. Maybe your bias is showing?
You're welcome. People getting hurt to easily and overreacting because we're not inside each other's assholes all of the time. For real. ๐Ÿคฃ๐Ÿคฃ๐Ÿคฃ Remember we discussed this last week.
Derek Ross's avatar Derek Ross
We need more the fuck you building this is the fuck I'm building.
View quoted note →
Probably. I just found out recently that an upcoming major client may not fit my definition of a client... It uses login, but doesn't publish anything, and it's more of a content scrapper. I did not know this. It's also early in development so they still have time to become more of a client and publish data.
I would only give that title to something that is interoperable or potentially interoperable with other apps. Some random spammer abusing relays as free storage isn't a real client, for example. An app can also use Nostr identities and consume Nostr data but not want to be interoperable, and I think that makes it not a client, or a partial client, but that isn't a bad thing either. We don't have to use Nostr events for things not suited for Nostr events.
๐Ÿ˜‚ maybe your bias is showing? You called out a nostr client as not a nostr client, when you donโ€™t even bother to use said client, because โ€ฆbias?
Absolutely. I'm building a non-client app with nostr login only, because I love what nostr stands for in comparison with X etc. The app follows in the same spirit as nostr: education, fun, generosity etc. But that doesn't mean I'm making all data in the app event-based. There is no need to do this in my case, it would just fill up relays and degrade the UX needlessly.
โ†‘