Gated is like an event that can be shared publicly but isn't necessarily. For example, a gated community can open their gate and let people on their road for a garage sale, but the rest of the time they keep it closed. For example, imagine I share my location as kind 1 in my gaged community, it makes sense in some context of a discussion that's happening in that group, but is out of place in my global feed. Another example, marketplace items I only want picked up at my meetup. Another example could be a long form article explaining something niche about the meetup, its not private information, but it doesn't make sense to display it alongside global context.

Replies (3)

Ah, interesting. I still wonder if relays are not the answer. The primary distribution scope of Nostr was really intended to be relays (I think, still a bit new to the protocol). But there does seem to be some use for ad hoc grouping. If we all ran personal relays and someone could host, that would work. "Have a few people over" vs "let's go to the tavern" sort of. I'm curious about this now. Thanks.
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