Skip to content

discussion on my prev pr #67 (emergency coordination design) #69

Description

@gauravk16in

Problem

Hi everyone, especially @ni5arga 👋

Following the review on my previous PR, I'd like to discuss a few protocol decisions before working on a new implementation.

I think it's better to agree on the design first rather than keep changing the code later as @ni5arga's bot suggested

  1. Identity

Should emergency alerts carry the sender's long-term identity, or should they use an ephemeral/anonymous identity to better protect user privacy?

  1. UI

My previous implementation showed the number of nearby reports (e.g. "7 people nearby"), but since this can't currently be authenticated, would it be better to not show a count at all in V1?

  1. TTL

The review also pointed out that emergency messages currently use the default mesh TTL (6 hours), while the docs mention 15 minutes.

Should emergency messages have their own TTL (e.g. 15 minutes), or is there a better approach?

I'd love to hear your thoughts before I start working on the next PR. Once we agree on the design, I'll implement it in smaller, focused PRs.

Proposal

let us settle three things first and I like to hear @ni5arga approach first

Safety notes

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions