Nostr events are called nostr events but so are nostr events. So which KIND of nostr event are you referring to when you say nostr event?
Discussion
BOOST ALL THE EVENTS!
Sounds like we need a dedicated nevent type for IRL meat-space nostr events.
NIP
Title: Dedicated Event Kind for Meat-Space Nostr Events
Abstract:
This NIP proposes the creation of a dedicated event kind for in-person (meat-space) Nostr events to resolve the ambiguity and confusion that arises when such events are shared using existing event kinds. The new kind will help categorize these events distinctly and provide clearer context for users and clients.
Motivation:
Nostr events are categorized by specific "kinds," each assigned a unique number. While digital events, messages, and metadata are clearly assigned to event kinds, there is currently no dedicated kind for organizing, sharing, or discussing in-person (IRL) Nostr meetups or events. This lack of clarity leads to confusion among users and developers about where to place or find such events, as they do not neatly fit into existing categories. This proposal seeks to establish a distinct kind for meat-space Nostr events, enabling better organization and discovery of in-person events in the Nostr ecosystem.
Specification:
We propose adding a new event kind, for example:
kind 1392: Dedicated to meat-space Nostr events.
The event structure will follow the typical Nostr event format, with the following keys in the content field:
name: The name of the event.
location: The physical location of the event (address, venue, city, etc.).
date: The date and time of the event.
description: Additional details or agenda for the event.
organizer: Pubkey or NIP-05 of the event organizer.
Optionally, additional fields such as a URL for registration, a max number of attendees, or a link to the event’s group chat could be included as needed by the organizer.
Rationale:
The current absence of a dedicated event kind for IRL Nostr events results in misclassification or misuse of other kinds (such as generic note events) to share details about meetups. This proposal eliminates this issue by providing a clear and consistent kind specifically for these in-person events. It will allow clients to filter, organize, and display these events in a way that improves discoverability and user experience.
Backwards Compatibility:
This proposal does not interfere with existing kinds or break backward compatibility. Clients not supporting the new event kind will simply ignore it, while those that do can start implementing support to handle these event types appropriately.
Reference Implementation:
A simple implementation in a Nostr client could involve creating a new event type that populates the fields mentioned in the specification, allowing users to search for or post IRL event information easily. This implementation would involve minimal changes to the client’s user interface, focusing on rendering event details in a user-friendly manner.
Security Considerations:
There are some inherent privacy concerns with sharing real-world event locations and details. Users and clients should be aware of this, and implementers might want to consider warning users before publishing or engaging with this event kind, ensuring they understand the potential exposure of their real-world location and plans.