-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live position sharing #113
Comments
maybe a "start geo share" + "end geo share" messages that append the info into |
Yes, regularly sending eg |
I barely even have words to describe this idea, and regardless of the general perception of acidvegas, I have to agree with him on this.... This has got to be the most obnoxious (not to mention, privacy-violating) extension IRCv3 has come up with so far. |
You open your IRC app and open a private message tab with your friend. You press "share my location", select a duration, like "15 minutes". Then for 15 minutes your app sends its location to your friend by message over IRC. Just like WhatsApp. |
I do not share my location on any applications, though even then it sounds a bit risky, as it can always happen that a friend is not a genuine friend, or being impersonated etc. The implementation would ideally only allow this in queries then, to not accidentally leak one's location to an entire channel. |
Depends on #112 |
yall need to really take a step back and breathe. none of this is privacy violating if a user voluntarily decides to share their location with a trusted recipient(s). not only would this be an optional extension/capability if it ever actualized for both servers and clients but even if you're client/server of choice implemented this, you would be under no obligation to use it. this org is about the protocol, not necessarily just the use cases we use irc for today. |
You know that nothing stops you already from saying in IRC (channel or query) a message like "hey mate, I am at 0°1' lat, 2°3' lon", right? This proposal just allows clients to show nicer GUI for this, nothing more. |
It is true that nothing stops the user from sharing their location by typing it out, but accidentally pressing a button of sharing location, and then quickly just pressing "accept" to make it go away again are very likely to happen, as people accidentally press the wrong buttons often. the idea also mentioned nowhere that it is for trusted recipient(s) only, if it had mentioned that this is for queries only, that would be acceptable. there is indeed no obligation to use it, though for that case "humans press the wrong button by accident more often than they should" sadly still stands, and sometimes users do need to be protected from themselves. |
had to look this up myself, but the geo url is https://en.wikipedia.org/wiki/Geo_URI_scheme for anyone uninitiated |
IMO, since this can be implemented as a client-to-client extension that doesn't require server cooperation, it also doesn't require the normal consensus-seeking process. I think the best path forward would be to spec and build this as a vendor extension, before (or instead of?) advancing it as an IRCv3 extension. |
Also in spec should be an option for location disabled by settings, to refuse an answer. but I think this should be added to the ctcp spec as in ctcp geo |
my use-case for this is letting people share any location they want, so if I want to show someone where I went on holiday, I can share the location which can defer to some map app or something deals with the |
Sharing the current fixed location without live updates can be done with a PRIVMSG with a
geo://
URI. However, sharing live position updates will require a more sophisticated solution.The simplest solution would probably be something like a TAGMSG with a client tag (akin to the existing typing indicator spec).
The text was updated successfully, but these errors were encountered: