I’d recommend Rubble’s talk: https://youtu.be/B6YQQC5Q_5g?t=10140
I also really enjoyed #[6]​ talk: https://youtu.be/B6YQQC5Q_5g?t=5045
Discussion
In that one now! 👆👆
Nice to hear some challenges identified for nostr. Sometimes I feel like you get attacked for saying anything against the common narratives
💯
I think being able to have an open minded discussion about it is critical for Nostr over time 🫂
Lots of stuff to figure out🤙 Nostr is vastly different than it was a year ago and that is because of people building together and figuring out what works and what doesn’t work. Open discussion is cruicial and that’s one of the most awesome thing about the nostr community.
Nicely said 🤙
You’re right about that. Building together and figure out together is critical. If no one is critical is hard to move forward in the right direction.
Nostr will bring in more blog style content and needs discord style communities
We’re going to display both the short posts event type 3, and the longer event type 30023 for longer form texts with markdown formatting in the same feed.
The confusing part is going to be in posting where we will need to communicate to users that if they use markdown then not all clients will display their content.
So if there is markdown it will be considered long form, or does the user control the type (via the client)?
Not exactly. The way it works is that if it’s an event type 3, you shouldn’t use markdown and if it’s event type 30023 you can use markdown. The lengths of the two message types are the same.
Personally I would rather have a field on event type 3 that said formatting. But my understanding is that #[7]​ didn’t want markdown showing up in the primary tweet like messages so the support was relegated to a secondary event type.
Clients choose which message types they support. Relays can also choose which they’ll host.
Right, I was asking how the type is set, does a user have to know about types? Or if they use markdown it becomes the long form type?
Event type is set with all messages, the text ones we’re using here are type 3… but there are a ton of others. It’s set upon writing and signing the messages.
Habla.news is a good example of a nostr app that uses longer form events vs the normal type 3.
For discord I think we need private groups. I think the p2panda implementation of MLS (message layer security) will work.
We need to have a prototype and with it a NIP. Once we get group encryption we can get pretty good privacy. 🥀
Yes me too. There is a saying “Bitcoin is for enemies “…. Is nostr the same? Everyone is welcome? But also everyone is welcome to criticize and attack? I like #[3]​ perspective that we need more tools to help non-technical people, non-bitcoin people feel welcome and comfortable.
I agree, and the fact that we can have this open discussion here and now is showcasing that Nostr is moving in a positive direction. On the other hand, there is still a long way to go
Will sport teams and corporations be welcome here? How will we filter but also keep it open? How block bots and spam?
Important questions!! Time will tell 🤙
