WTFFFFFF🥶🥶🥶🥶🥶🥶🥶🥶

@fiatjaf I think njump relay need to both implement and respect NIP-70 and NIP-62. Since it collects data over the network, people need to opt out for it. For their whole pubkey or just one event. I know people who tried to delete their notes from njump, they even asked me and I sent direct nak requests for them but they still find their event on njump. This is really really important. I know all these stuff can be gamed by bad actors collecting everything and do nothing about it, but we need to respect this as much as possible specifically in clients like njump where people try to find something first.

در نوشتاری باستانی («چامه هرمزگان») نوشته شده است: «پرستش‌گاه‌ها ویران شدند…؛ تازیان [عرب‌های اسلام‌گرای] ستمکار، روستاهای پیرامون شهر را با خود شهر، یکسان [نابود] کردند؛ زنان و دختران را به اسیری گرفتند و آزادمردان در خون خود غلتیدند…».

Stay humble, stack ideas.

NIP-51 bookmarks need to support categories or collections somehow. If I'm bookmarking a post, I may want to put this post between some specific section like ideas, buy list, vacation or something like that. It can be done using a new addressable event for bookmarks, or just adding a new value at the end of `e` tags for bookmark events which will be counted as category or collection name.

I was thinking about age verification on social media. This is not good because we don't want to do KYC and age verification, but meanwhile the child safety is important. The solution as we know is to expect the parents to take care about this. I believe we need a set of nostr clients that are for child's. They can support good protection about unknown keys and let the parents to have control over contents show to them and relays they use, somehow. Even some relays can focus on this topic. Meanwhile when they have a space as social media, we have an opportunity to teach them what is Nostr, why it even exists, why free speech matters and more in a gamified way. What do you think? 🤔

@npub1kpt9...nhmz is suggesting a way to get follower counts, filter out spams or even get suggestions to follow or see. If we get an standard interface to it, clients can behave it like a Blossom server or a relay. You can just use a public/private (self-host) / paid Vertex server and then your client will use it to filter spams, show follower counts (don't need heavy queries, and you can self host if you don't trust), and get content and profile suggestions. I think that standard interface is its DVM now. HTTP/WebSocket interfaces can help too. If people are going to finish DVMs (I don't know the current state).

About followers in the Nostr: View quoted note →

https://npub1hu47u55pzjw8cdg0t5f2uvh4znrcvnl3pqz3st6p0pfcctzzzqrsplc46u.nsite.lol Just published latest version of @Raxva 🪽 website on Nostr. URL is too long. Soon I'll do some stuff to make a shorter one. 🥶 #nsite