[GH-ISSUE #28] Potential scenarios where you could unintentionally share your location to rtirl #15

Closed
opened 2026-03-02 03:59:31 +03:00 by kerem · 3 comments
Owner

Originally created by @juaoose on GitHub (May 17, 2024).
Original GitHub issue: https://github.com/eerimoq/moblin/issues/28

Hello! I believe there are some potential scenarios where a user could leak their location on rtirl by mistake:

When one starts a stream with rtirl and location enabled and then perform one or many of the actions listed below, the /stop endpoint of rtirl is not called, and as such you potentially still appear in the public map.

  • Disable location.
  • Disable rtirl.
  • Add a privacy zone that overlaps with the current location?

Calling stop in these scenarios would help the streamer not have to stop streaming and be able to not show in rtirl map. (Maybe for the privazy zone case there could be other alternatives...)
Thanks!

Originally created by @juaoose on GitHub (May 17, 2024). Original GitHub issue: https://github.com/eerimoq/moblin/issues/28 Hello! I believe there are some potential scenarios where a user could leak their location on rtirl by mistake: When one starts a stream with rtirl and location enabled and then perform one or many of the actions listed below, the `/stop` endpoint of rtirl is not called, and as such you potentially still appear in the public map. - Disable location. - Disable rtirl. - Add a privacy zone that overlaps with the current location? Calling stop in these scenarios would help the streamer not have to stop streaming and be able to not show in rtirl map. (Maybe for the privazy zone case there could be other alternatives...) Thanks!
kerem closed this issue 2026-03-02 03:59:31 +03:00
Author
Owner

@eerimoq commented on GitHub (May 17, 2024):

Will have a look at it.

<!-- gh-comment-id:2116586430 --> @eerimoq commented on GitHub (May 17, 2024): Will have a look at it.
Author
Owner

@eerimoq commented on GitHub (May 17, 2024):

Should be fixed in 0.273.0. Thanks for reporting.

Let me know if it works as expected once the fix is available in TestFlight.

<!-- gh-comment-id:2116591738 --> @eerimoq commented on GitHub (May 17, 2024): Should be fixed in 0.273.0. Thanks for reporting. Let me know if it works as expected once the fix is available in TestFlight.
Author
Owner

@juaoose commented on GitHub (May 17, 2024):

Should be fixed in 0.273.0. Thanks for reporting.

Let me know if it works as expected once the fix is available in TestFlight.

Yeah, that seems to work! Thanks for the help!

<!-- gh-comment-id:2118038339 --> @juaoose commented on GitHub (May 17, 2024): > Should be fixed in 0.273.0. Thanks for reporting. > > Let me know if it works as expected once the fix is available in TestFlight. Yeah, that seems to work! Thanks for the help!
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/moblin#15
No description provided.