How is location expensive to encrypt? I share my location all the time but to do that I have to write an entire sentence to other people where I am. Just introduce a new message type (like with edits) frontend to enable location sharing. Location is sent every 5min or if the other person requests an update, than location is updated again (send location update request message to trigger response on the other side). Same encryption as everything else and easy to implement. Of course the devil is in the detail but the basis are trivial.
The “hardest” part would be to show the location on a map without leaking data but just add a warning dialog and open externally. Every link in Signal you press has the same privacy issues.
The amount of data is a joke for location “streaming”. There is no need to update the location every second, most people on earth don’t travel with rockets. Updating the location at most every 30 seconds is probably more than enough for most usecases. Let’s make it 15s. Let’s be generous and just use two 32bit floats (could probably get away with 16bit half precision or fixed point). The size of the entire message (without meta data and encryption) is just 8 bytes. There are emojis that need more than that. And in practice people that can’t share their location often just end up sending images, so the amount of data is definitely not the issue with location sharing. A single image you send on Signal uses more data than streaming the location ever 15s for a few days.
Location showing only goes against privacy If it’s not done right.
It’s expensive to encrypt it and forward it through the servers or proxies, but revealing if done peer to peer. (And less reliable)
But by the time I’m giving “live location” I don’t think my ip address is THAT private 😝
How is location expensive to encrypt? I share my location all the time but to do that I have to write an entire sentence to other people where I am. Just introduce a new message type (like with edits) frontend to enable location sharing. Location is sent every 5min or if the other person requests an update, than location is updated again (send location update request message to trigger response on the other side). Same encryption as everything else and easy to implement. Of course the devil is in the detail but the basis are trivial.
The “hardest” part would be to show the location on a map without leaking data but just add a warning dialog and open externally. Every link in Signal you press has the same privacy issues.
Encryption isn’t hard, the service to stream live data over an hour is what costs money.
Continuous data
It’s peanuts compared to video calls, which signal already supports.
Fair enough
See my comment here for the amount of data it would take to share updates for 24 hours, it’s almost nothing:
https://lemmy.ml/comment/8085552
It’s not continuous, and it’s not much data. It’s GPS coordinates once every five minutes and when it’s requested.
When you’re looking at the map, it’s continuous.
And it doesn’t sound like a lot of data until you compare it to text messages that are 2kb a couple times per day
The amount of data is a joke for location “streaming”. There is no need to update the location every second, most people on earth don’t travel with rockets. Updating the location at most every 30 seconds is probably more than enough for most usecases. Let’s make it 15s. Let’s be generous and just use two 32bit floats (could probably get away with 16bit half precision or fixed point). The size of the entire message (without meta data and encryption) is just 8 bytes. There are emojis that need more than that. And in practice people that can’t share their location often just end up sending images, so the amount of data is definitely not the issue with location sharing. A single image you send on Signal uses more data than streaming the location ever 15s for a few days.
Fair enough