Nostr Web Client

Vivek

facdaf1ce758bdf04cdf1a1fa32a3564a608d4abc2481a286ffc178f86953ef0

Maker of kanbanstr.com (Kanban on nostr) and zapddit.com (a reddit-style nostr client)

Made garlic rasam and brinjal (eggplant) fry for lunch today

#foodstr #foodchain

nostr:npub1ltx67888tz7lqnxlrg06x234vjnq349tcfyp52r0lstclp548mcqnuz40t So I’ve been thinking about this.

To keep things simple, for Satellite, I’m going to go ahead and use kind 4549 as a direct clone of kind 1 as nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z suggested. So the content string of 4549 will be text just like kind 1.

My initial concern was that having a single kind defined as a “community post” would preclude the reuse of other event kinds, which is why I suggested “wrapping” the events.

I still intend to use kind 4549 as a wrapper to post non-kind-1 events into communities. When a non-kind-1 event is posted, the 4549 event will include a “k” tag indicating the kind of event that was wrapped.

But for 4549 events that do not have a “k” tag (or a “k” tag equal to 1), Satellite will assume that they should be treated like kind 1 and render the content directly.

I like this cause it’s just doing the simple “clone kind 1 thing” but adding the “k” tag allows me to do also do the wrapping thing so I can support other event types on Satellite. If other apps only care about kind 1 that’s fine.

I’m also implementing this weekend and writing up some documentation. Lmk if you wanna collab 🤙

Awesome :) thanks for the detailed response 🙏 I will try to do the same

I will get back to you with questions if I get any during implementation.

My weekend schedule is still adhoc and me being in India makes synchronous collab impossible.

Will keep a message channel open for async collab, if that's ok with you.

> After a person clicks the submit button after composing a community note, he will see two popups from the signer extension . Not sure if that would startle them as generally only one is expected

Good point. Although when posting an existing note into a community, the user will only be signing one event. (that's actually one additional benefit of this approach, it allows users to "pull" other notes into communities with kind 4549 events, just like how mods can pull events into communities with kind 4550 events)

> When someone zaps or reacts to a community post, we need to make sure to count it against the post request and not the approval event or the orginal kind 1 event if it exists. Is my understanding correct?

Correct, that's my understanding as well. Zaps/reactions would go to the post request, since that event will be present and indexed on relays.

> in case the user doesn't want the new note in their feed, there will be no "e" tag in their post request, right?

Actually I think it *would* make sense to include the 'e' tag so that clients can query to find all the post requests for an event (this would be relevant when an existing note was posted-requested into a community).

> I think it is a neat way to ask A client not to look for the actual event.

Well clients that don't support communities are not going to pull the kind 4549 post-requests in the first place, right? So they'll never have any reason to look for the actual events. And clients that *do* support communities won't need to look for the events since they already have the actual events (they can parse them from the content string)

Thanks for the in-depth response, and please let me know if I misunderstood any of your points!

Will the NIP be changed like nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj suggested?

Can I go ahead and make these changes this weekend?

Cc: nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn

Why are community subscriptions on zapddit different from subs on nostr.kiwi and satellite.earth? They are not sharing the same lists...

Hi.. this is fixed now.. 🙂

Spending this night at the movie theatre watching Indiana Jones

Not sure how it is...

#moviestr

nostr:npub1ltx67888tz7lqnxlrg06x234vjnq349tcfyp52r0lstclp548mcqnuz40t Was looking over your Expiration NIP this morning – nip-40.

Do you know of relays/clients that have implemented this? Is it widely supported?

My contribution in that nip was just some typo corrections and grammar changes.. 😁

nostr:npub13prsf02zzus79yhdhl6zadm4gllpzhr0lxp9kz8uxe47fntfa8mqyrh6a9 seems to be the author of that NIP

Why are community subscriptions on zapddit different from subs on nostr.kiwi and satellite.earth? They are not sharing the same lists...

Hi..I am a developer of zapddit. We are not using the same event to store the subscriptions today.

nostr:npub1cz2ve34nk0ukn0ph4yq2qx3ud8rfy5e0ak4epx42dn8gha0sdgpsgra9kv is working on this at the moment.

Positively sometime this week you can use all 3 softwares using the same subscriptions.

Though the non-BTC part of this news sounds correct, there is no mention of BTC anywhere in the article.

Most probably a clickbait

> After a person clicks the submit button after composing a community note, he will see two popups from the signer extension . Not sure if that would startle them as generally only one is expected

Good point. Although when posting an existing note into a community, the user will only be signing one event. (that's actually one additional benefit of this approach, it allows users to "pull" other notes into communities with kind 4549 events, just like how mods can pull events into communities with kind 4550 events)

> When someone zaps or reacts to a community post, we need to make sure to count it against the post request and not the approval event or the orginal kind 1 event if it exists. Is my understanding correct?

Correct, that's my understanding as well. Zaps/reactions would go to the post request, since that event will be present and indexed on relays.

> in case the user doesn't want the new note in their feed, there will be no "e" tag in their post request, right?

Actually I think it *would* make sense to include the 'e' tag so that clients can query to find all the post requests for an event (this would be relevant when an existing note was posted-requested into a community).

> I think it is a neat way to ask A client not to look for the actual event.

Well clients that don't support communities are not going to pull the kind 4549 post-requests in the first place, right? So they'll never have any reason to look for the actual events. And clients that *do* support communities won't need to look for the events since they already have the actual events (they can parse them from the content string)

Thanks for the in-depth response, and please let me know if I misunderstood any of your points!

This is great. Thanks for the responses. I am good with this proposal

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z So here's an idea:

Instead of tagging a post with an 'a' tag to request that it goes into a community, the user publishes a new event that contains (stringified in the content field) the event he wants to post into the community, like how reposts work. This community post event would contain 'a' tags of all the communities the user wants to post into, as well as the 'e' and 'k' tags for the stringified event (just like kind 4550). For the sake of discussion, we can call this a "kind 4549 post request"

When mods create a 4550 post approval event, they can just copy the content string of 4549 post request event. All the tags are the same, so the person who created the request can still get notified that the post was approved.

If a user only wants his post to show up in communities, he creates whatever kind of event but does not publish that event directly — rather it gets posted as the content of a new 4549 event

If the user wants the post to show up in the main feed as well, he can publish the original event as well.

I like this solution it means event existing event kind can be posted into a community, not just text notes. (like long form, media, ect.) Communities would just have a modqueue of 4549 events.

I like this proposal. This

- allows any event kind to play with communities

- allows unmoderated feed to be displayed

- allows notifications of approvals

- allows a mod queue display

I have a few questions though:

- After a person clicks the submit button after composing a community note, he will see two popups from the signer extension . Not sure if that would startle them as generally only one is expected

- When someone zaps or reacts to a community post, we need to make sure to count it against the post request and not the approval event or the orginal kind 1 event if it exists. Is my understanding correct?

- in case the user doesn't want the new note in their feed, there will be no "e" tag in their post request, right? I think it is a neat way to ask A client not to look for the actual event.

Today's updates from #zapddit

- Want more real-estate? Just collapse the sidebar and feel the breeze 🍃

https://void.cat/d/6qnVHFDHLcW1iRS2uf6Tuh.webp

- NIP-05 verified plebs will now get a purple icon instead of a blue one

https://void.cat/d/PSEzBuvGKLzGQqHivJDVcR.webp

- Bye bye ugly scroll bars! Welcome, thin and slim scroll bars :)

- I know the Green 'approve' button never looked good in the actions of a note. Moved it to a separate section to keep the actions bar clean.

https://void.cat/d/FLLs2UaVvnT3ufJGAwnP9Y.webp

- Fixed bug about community approvals not reflecting -> Reported by nostr:npub10awzknjg5r5lajnr53438ndcyjylgqsrnrtq5grs495v42qc6awsj45ys7

- Other minor UI tweaks and eye-candies

You can access #zapddit at https://zapddit.com

#clientlife #plebchain #puravida

Did some UI cleanup today ✨

nostr:nevent1qqsqshay0xvssatu3mduhajc229t55axnck7yyzepcvj4ehcwa0hu4cpp4mhxue69uhkummn9ekx7mqzyp6gh758csmm99qkf5tcfvey5rfwjj2usf5wqpzw83medga3tryasqcyqqqqqqgppes6u

Replying to சாரு-秋陽

More than zappdit? 😜

I use amethyst more than I use zapddit 🙂 so yes

Where can I see this picture in a zoomable format?

Amethyst is my favorite 👻

nostr:naddr1qqxnzd3c8y6rqv3kxgenvdp5qgsqf6jehatkh8zp4kxjzd798r20fxt30wea79845gxefzwuc3thwngrqsqqqa285lvz4m

Yes, please take you time, man. I’m just planning on updating my Reddit guide, so was checking out all the clients that support communities.

Some interest towards this feature is starting to spark

Hey Tony! Now it is reliably giving results. Tweaked the relay query a little bit.

Ctrl/Cmd + R on Desktop and Clear cache using site-settings on Android should give you the latest version now.

I did but found it to be quite boring quite quickly.

Agree. I have paused at least 5 times for many months now . Screenplay is not very captivating

How many of us in #nostr watches/watched the series Mr.Robot ?

I am finding it very relevant to us with lot of things we could learn

🫡

Forgot to tell you. Just do a ctrl/cmd+R on desktop or clear cache from site settings ->zapddit.com on Android to see the bug fix

🫡

I took a look. Found a bug and fixed it.

However, in some rare cases, I see that relays are not giving the approval events sometimes.

In fact, when we click on the note to see it alone, the approvals are fetched 100% of the time.

Is it ok if i investigate more on my morning tomorrow? Looking at it with fresh eyes may help perhaps.

Replying to சாரு-秋陽

Zappdit by nostr:npub1ltx67888tz7lqnxlrg06x234vjnq349tcfyp52r0lstclp548mcqnuz40t

Thanks a lot 🙏

Load More