Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 680
    • Issues 680
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 12
    • Merge Requests 12
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #1683

Closed
Open
Opened Dec 23, 2019 by cano wig@canowig379
  • Report abuse
  • New issue
Report abuse New issue

Add a 'safe' status in case of disaster?

I read in japan several apps have the ability to make others know you are safe, like facebook has a 'safe' mark during natural disaster.

Given the nature of briar I think it would be a great addition to have. However I am not sure what would be the best way to implement it.

I thought about 3 possibilities:

1 User can decide themselves whenever to check the 'safe' check (but then it would be too abused I suppose?And might worry people if you don't have 'safe' checked).

2 depending on the location briar could issue an alarm message about a disaster and give the option to check 'safe' (but then briar would have to scan third-party portals and the burden would be on briar not on the user).

3 let the user in private groups the option to create a warning: e.g. 'flood happened in city X please all check safe if you are good' and then users can individually check their status (I think this sounds the best option, although like all other 2 could be abused so maybe give such option only to the creator of the group?.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#1683