Nip-29 is on the horizon, promising to reduce our reliance on group communication tools like Slack and Telegram.

I envision it as a straightforward and user-friendly solution, including the deployment of a Nip-29 relay. With Nip-29, you’ll be able to join relays to discuss topics that interest you. Moderation features will be available, allowing for the possibility of being banned. However, this isn’t a significant issue—if your voice isn’t welcomed somewhere, you can easily set up your own relay with your preferred groups. This process will be accessible to users of all experience levels.

This is the driving force behind Seer. I’m starting with native apps for Apple platforms because I believe that using platform-specific tools and frameworks yields the best results. My goal is to create applications that seamlessly integrate with the platform they run on.

Stay tuned for updates—Seer development is progressing well.

Reply to this note

Please Login to reply.

Discussion

Really looking forward to this!

Look forward to it

🤙🏻 yes!

Slack is a "Good Mood" destroyer and Telegram has been a dumpster fire for a decade. Miserable interface.

#GoodRiddance

nostr:note1rz4t0fzd6wc8ruxc45yjqpr7867cw64wwvn695lk874c5dx35djs2nyp7z

Greeeeaaat to hear!

Curious for the design angle on this 👀.

More to come on this, but my philosophy in terms of design is to stick as close to the native platform look as possible. One thing this enables is easier maintenance of code and also it just feels at home on the platform. In my opinion an app should look and feel as if it was made for the platform.

Can't clients enforce the moderation rules? For public groups, where everyone can see the posts, you don't actually need relay cooperation do you?

A NIP-29 aware relay could restrict event delivery to group members, and provide some privacy, as a value add, though. I'm not sure how inclined I am to trust such a relay to never leak, and since nostr events are non-repudiable, all it takes is one mole to ruin privacy.

Initially the focus is on public groups, but I understand your concern in terms of private groups. We will tackle that after getting a good public experience.

I'm actually more interested in public groups too.

My question is just: Do you really need a NIP-29-aware relay at all, for public groups?

Yes I believe so because if you look at nip29 you can see it adds some of the basic building blocks like groups, group members, moderation kinds, etc. Seer aims to simply do group communication, so it’s much easier to just subscribe to these specific kinds without having sift through all the other stuff.

100% this BUT I think differentiation at the relay level is the wrong approach, it would be better if it's in the protocol

Not sure I understand what you mean?