Standard for how to track hitchhiking rides

Applications which help hitchikers track their trips should rely one a common data format such that records of rides can be shared easily and be used for the benefit of all.

This standard should reflect the diversity of hitchhikers such that it allows shallow records from the average or beginner hitchhiker as well as very in-depth and almost customized records from super-hitchhikers.

This data format should reflect a single ride via hitchhiking. Building up on this it will be possible to connect rides to trips, judge the "hichhikability" of certain frequently used spots as well as to gain deeper insights into state of hitchhiking.

This standard should also provide the single source of truth about how a hitchhiking ride NOSTR event should be tagged.

To describe the tags of this standard we took inspiration from OSM tagging and NOSTR Standardized Tags.

To establish this standard and to propose new features of hitchhiking rides that could be recorded the proposal process from OSM is adapted.

• create a new issue called "Proposal: xxx", stating which new dimenion of hitchhiking you want to add to the already existing standard or how you would extend or change it to better capture the reality of hitchhiking in more detail.
• find a consensus about how to make the proposal happen - the discussion should be about the how rather than the if as applications will decide independently whether they and their user base will be able to record this new feature
• if a consensus is reached document it in STANDARD.md, another file named object_name.md might be used to define more complex objects.
• inform applications like hitchmap.com about the extension/ change of the standard to make it come alife.

The corresponding Nostr event

{
  "kind": ...,
  "created_at": 1715000000, // Timestamp of THIS event object
  "content": "...",
  "tags": [
    ["d", "..."], // Unique ID
    ["title", "..."],
    ["published_at", "..."], // Timestamp of first publication
  ],
  "pubkey": "...",
  "id": "...", // ID of this specific event
  "sig": "..."
}