AU9913's avatar
AU9913 auggie@nakaMOtown.com 2 weeks ago
Its not negative, it just doesn't make sense. Like you could also have global events shared to a gated community, goes both ways.
AU9913's avatar AU9913
Yeah, that was my initial reaction too when @hzrd149 was describing this too me. But inherently, the events "leak", which is not a problem, but you need to signal to the clients that "this doesn't make sense in global". Its like when replies to long form posts were just kind 1 and ended up showing up in feeds as orphaned notes making no sense. That way, they can choose to display them, bc it'd allow them to display them differently, for example the way meetstr does calendars is that events belong to a calendar, these community events could/should be displayed separately. Like John Doe putting out weekly coffee meetup with no description into public makes no sense, but in the context of it being on a community calendar it does
View quoted note →
↑ Parent

Replies (3)

Troy's avatar
Troy 2 weeks ago
A gated community isn't the same analogy as Telegram groups. People don't join a gated community to share information. They join it for being able to close the gate; for privacy, or to keep the public out. Compared to Telegram groups, where information is categorized, but also sharable with anyone that is outside the group. The equivalents in Nostr would be a hashtag, or "relay turned into a category/group". People that are members share info, yet anyone can share that info to people that aren't members. I still don't see what the issue is with this data being on global, aside from "it doesn't belong there". Based on what? It's not private information, and there's no negative aspect. What practical cause would necessitate non-private data being hidden from the "everything firehose"?
1 replies ↓
AU9913's avatar
AU9913 auggie@nakaMOtown.com 2 weeks ago
I don't see how telegram isn't a gated community. There are mods. Only specific topics can be discussed, even if most groups say talk about whatever, if it's too much off topic they will tell you to take it else where. "It doesn't belong there" is a ux problem. Let's say I am a member in 5 groups. I post 1 event per week per group. If I just show all of my events for a specific group that is basically spam to that group. Ok, you say the solution is tags, which I accept solves that single problem. However then the problem is events on global, that, while not private are not shown in their context. If I go to global, I want to see events in context. While grouping these by tags makes sense, I don't want these shared to global unless I explicitly share them as global. For example an event where I can only fit 10 people in the venue. If I use the same kind, the event gets too much attention and then my venue doesn't work. The context also is a bigger issue than you're making. Showing global where half of the events aren't intended for you to see them (but it's not a problem if you do) is a ux problem. Imagine you're at a conference. The location of each session is just room a, b, etc. That event only makes sense in context of "we are all in this building" so showing that on global is dumb.
1 replies ↓
↑