imho with unusually sensitive things like precise location data it could just not let you opt-in to making it all public, and make it much easier to share with a specific named friends than to share on a public directory
I really don't understand these criticisms of Strava, it has excellent privacy controls so you can share as little or as much as you want. You can already choose to share your activities with only your friends (followers). Or keep your activities private or hide the location data.
It does but my point is that your settings are applied to all activities.
Here's a few examples that might help demonstrate my point:
I used to do parkrun regularly. I had no problem sharing my Strava activities for parkrun because me doing it wasn't a secret, nor was the location secret, nor was my time secret. All of these things could be found from the parkrun website once the results had come up. John Doe was at this location at 9am and ran this route with 400 others in a time of 26 minutes or whatever.
I was also part of a cycling club that did a regular "club run" on a Sunday. 5-15 of us all doing the same route. It was good for club morale for us all to upload our rides to help show how popular it was and encourage other club members to come along. They could see that we weren't going at a silly pace and that we stopped regularly to regroup as we had riders of all abilities and speeds riding with us.
But then I also helped out with my kids running club at school, taking a bunch of 7-11 year old's on a 20 minute jog/run (depending on how quick they were) around the local area. This absolutely should not appear on Strava (public or not). The running club wasn't a secret (everyone at the school knew since they had the option of letting their kid do it) but that's a whole world of difference from having it public on Strava showing the usual start time, the various routes we used to take, where we stopped, etc. Privacy zones can help hide the start/end but that wouldn't help hide everything.
We just made sure that all of the parents who helped out knew that we shouldn't even record it with their smartwatch. I just used to create a manual entry of "Morning run" with approximate distance and time. That was good enough for my training stats.
There's no one privacy setting that handles all of this. Whatever setting you use relies on me to manually adjust the activities that don't fit that setting. The problem is that humans are fallible, so remembering to make it private or hide the location data isn't entirely reliable. You're also at the mercy of Strava (or whatever) not doing something stupid and accidentally making private data visible due to some bug, glitch or leak.
And then ask another question, and the LLM changes its mind again ("are you sure?").
It's not actually realizing anything so much as it's following your lead. Yes, followup questions can help dislodge more information, but fundamentally you can accidentally or on purpose bully an LLM to contradict itself quite easily, and it is only incidentally about correctness.
I used to be able to reliably BSOD a work computer by doing a largish git pull inside WSL2, with the culprit seemingly being the McAfee realtime scanner. VirtualBox VMs were fine though. Not confidence-inspiring!
> That number isn't a projection. It isn't an estimate. It's the sum total of confirmed individuals affected across 735 breach reports filed with the HHS Office for Civil Rights - and it's growing every week.
Even easier is just using an X server, if you have it set up properly you just need to run the remote app and the window pops up on your machine.
(I think terminal-based GUIs are neat just for fluidity of use- you can pop one open during a terminal session and close it without switching to mouse or shifting your attention away from the terminal. They can also be a nice addon to a primarily CLI utility without introducing big dependencies)
Yeah I love that about X. I remember in the 90s when I first figured that out. I was logged in from a university workstation into my home computer with SSH and I launched my mail client or something and I thought doh, stupid that will only popup locally.
Then colour my suprise when it popped up on my screen right there. Slow as molasses but still. Wow. Magic.
It's a shame Wayland dropped this. Yes I know there's waypipe but it's not the same.
It... really isn't. Like you said, remote X was barely usable even over an entirely local network. Most applications these days are also not designed for it, using loads of bitmap graphics instead of efficient, low-level primitives. So you end up being just one tiny step away from simply streaming a video of your windows. We have better tools for doing things remotely these days, there's a reason approximately no one has used remote X after the mid-90s. It's a neat party trick, but I don't blame the Wayland authors for not wanting to support it.
> one tiny step away from simply streaming a video of your windows
In the 80s/90s this wasn't feasible due to network latency and bandwidth, but it's pretty common now to do exactly this, with VNC and other remote desktop protocols.
The big obvious one is web-based tooling. Your information & settings are stored on a server and you use a web browser to view it via whatever device you're on. For more locally based workflows, we have networked filesystem protocols, automatic syncing between systems, that kind of thing. It's not a 1-1 equivalent of running a remote program and viewing it locally obviously, but it gets the same job done, in a much more useful & flexible manner than X forwarding did.
For example, the remote mail client usecase I was replying to is simply done with a webmail client today.
I don't really feel like web interfaces or syncing are really a substitute tbh, and I'm not sure how they're more flexible. ssh -> run -> gui opens, and the program itself doesn't need to be designed differently to work
> and I'm not sure how they're more flexible. ssh -> run -> gui opens
But this doesn't work on your phone, or on a Windows or macOS device, right? That's what I meant by flexible, X forwarding fits a pretty narrow set of usecases, while on the other hand keeping programs on the clients and data centrally located on a server allows for a whole lot more options for how to interface with that data.
(To be clear, nothing wrong with X forwarding! It's a cool tech and I'm glad you have a use for it! I'm just arguing that it's fine for Wayland to not try to support that kind of thing, because we've got other ways of working remotely now.)
Phone I didn't know, but the sibling comment interests me. Windows, it works fine on local WSL but for remote yes you do have to have something like mobaxterm running. Not a big deal to me. Mac, I thought it just worked? It used to at least for me, but the last mac I owned was on snow leopard, so I wouldn't be surprised if they decided it wasn't the Mac Way to do things.
Most recently I used X forwarding to manage some LVM disks. I usually like using cli, but for me it's just easier to deal with disks with a GUI. Shy of setting up a full remote desktop, which I've had a lot of trouble with getting to work reliably, what's a better option here for an arbitrary disk program?
X servers are available for phones, Windows, and macOS. X interfaces not designed for phones can be difficult to use on phones. But web interfaces not designed for phones can be difficult to use on phones.
There is not a web tool for every use. And web tools are not better for every use.
The main advantage of x forwarding for me was when I'd randomly need it and had nothing set up ahead of time. Hopefully it starts getting installed in distros by default eventually.
suspect this problem is essentially unsolvable. what possible method wouldn't be vulnerable to this? it's fine if it's just a sort of larp but if people think this could actually work... man
Your CED or laserdisc player needs to be smart enough to be able to decode whatever you put on it, which- in the era that they were relevant- pretty severely limited what you could do.
Yah that was never on their front pages or on their apps, probably hidden on an archival web page. I looked everywhere. Only found the story in a few places on Feb 28, the day it happened.
reply