I have similar, albeit probably more radical, views.
All dragnet surveillance done by law enforcement or given to law enforcement by private entities should be public. (Targeted surveillance by law enforcement is a different thing.)
We should all be able to "profit" from this data collected about us. There are likely a ton of interesting applications that could come from this data.
I would much rather independently run a "track my stalker" application myself versus relying on law enforcement (who have no duty to protect the public in the US, per SCOTUS) to "protect" me, for example.
It might be that such a panopticon would be unpalatable to political leaders and, ideally, we'd see some action to tamp down the use of dragnet surveillance (and maybe even make it illegal).
It's doesn't seem like much of a grey area to me. Presumably Flock serves the useful function of satisfying the third-party doctrine, making the surveillance they gather immune from 4th amendment protection (since I "willingly shared" my location with them by passing one of their cameras). If law enforcement has access to that data without a warrant it's de facto public to me.
FOIA isn't the same thing as having the data at my fingertips like LE does. I think the public deserves the same access LE has. If they can run ad hoc searches so should the public.
Personally I'd rather see all dragnet surveillance just go away.
> law enforcement has access to it without a warrant it's de facto public
I think the public would be entitled to the specific data that was purchased or accessed by the government, but absolutely not the entire corpus of broadly available data. What if law enforcement were required to "pay per search" a la PACER or journal subscriptions?
> What if law enforcement were required to "pay per search" a la PACER or journal subscriptions?
My immediate reaction is that it changes the nature of the surveillance enough to require further reflection. It would put a time-bounded window on the ability of law enforcement to abuse the data (albeit assuming the ALPR companies actually removing data per their stated policies).
I appreciate your comment, for sure. I'll have to ruminate on it and see how it meshes with my more-strongly-held-than-I'd-like reactionary (and probably not well thought out) beliefs. >smile<
Almost no new technology is respectful enough to its users for me to consider making accomodations for it in my life.
It's not just that it's not fun. Any fun I derive is canceled-out by the inevitable loss.
I've felt white-hot blazing anger so many times when a feature is taken away by an "update" that I am not permitted to revert. I don't want to feel that feeling anymore.
"Eventually they realized that this was something they were going to have to sort out, and they passed a law decreeing that anyone who had to carry a weapon as part of his normal Silastic work (policemen, security guards, primary school teachers, etc.) had to spend at least forty five minutes every day punching a sack of potatoes in order to work off his or her surplus aggressions. For a while this worked well, until someone thought that it would be much more efficient and less time-consuming if they just shot the potatoes instead. This led to a renewed enthusiasm for shooting all sorts of things..."
- Douglas Adams, "Life, the Universe, and Everything"
(It took an unreasonably long time to find this quote!)
Commenting to provide a confirming data point. I bought a Kobo Libra H2O a few years ago. Unboxed it, modified the config, and immediately started using it with Calibre. It has never participated in any manufacturer's "ecosystem" and has functioned well in a totally "offline" capacity.
I was sad to hear newer Kobo devices are shipping with Secure Boot. I've never reflashed my Libra H2O (it's my daughter's and I'd never be able to get it away from her long enough to replace it) but I liked knowing that I owned the device. I'm sad to hear the new ones are owner-hostile.
I used the Kobo with its ecosystem, even bought a few books with the store. Also disappointed to hear that they seemingly don't allow unlocking the bootloader on their newer devices... If that's true.
I don't care about secure boot / a locked bootloader so much as the ability to unlock it.
I'm not sure about that. The relevant discussion here is at https://news.ycombinator.com/item?id=46194337 but from the linked Github issue it's not at all clear that a true bootloader lock is involved. It should still be possible to boot something else on device, it's just likely to require a lot of work.
> If you were an investor or trader, managing millions of dollars, would you keep the only copy of critical information in a cloud?
I don't think the idea that they could lose access to their accounts occurs to most people. I've done enough business continuity and disaster recovery work with small business to be confident in saying it doesn't occur to small business owners. I'm not sure why individuals would be any different.
It's very hard to put yourself in the mindset of a non-technical person.
> I don't think the idea that they could lose access to their accounts occurs to most people
Most people do not store anything valuable in the cloud anyway. The only problem is that they won't be able to login into Windows if MS bans the account, and they won't be able to install apps if Google bans their account along with phone serial number.
Presumably, as the GP said, you're not a normal person and you live in a basement. >sigh< (I'm with a lot of what the GP said but they didn't need to be insulting.)
The solutions self-hosting storage for non-technical people are terrible. Presumably there's no market for selling a solution that gives individuals data sovereignty. I would guess the margin isn't there and a recurring subscription for something you own is probably unpalatable to a lot of consumers. So this is what we get.
The main side-effect is the lack of trust and integration. For example, if you self-host your email (or more realistically push it on a VPS), then the moment you want to send an e-mail you are going to be marked as spam.
To register on some websites you may sometimes receive: “please use real email from gmail/outlook/etc”.
When you have a business meeting with a customer: “oh just install Jitsi on your mobile phone” is the best way to lose a sale.
Or no way to pay train tickets because you cannot install the app because your Apple / Play Store account is locked.
I get what you are saying, but the examples are not great:
I've rarely seen (if ever?) a website so stupid and user hostile, to claim that there are no other "real" e-mail service providers out there, other than gmail, outlook, or a maybe a few others. There are services, which reject things like tempmail, that much I have seen, definitely.
Jitsi Meet runs in the browser. Does it not on a mobile phone? Perhaps there is something to this one, if it is the case, that customers in some areas don't even own any working machines any longer and only have phones.
Train tickets, at least where I am from and living, one can always buy, by going to a service center, or online via browser. I never had to use an app to buy train tickets. Even when traveling in China, which is arguably much further in terms of digitization than Germany, I was able to buy train tickets via a website comfortably, upon which the ticket was registered to my passport.
But I get it, there can be such examples.
Though I don't think this really matches the "depend on the cloud" thing. It's more like depending on services, that make use of "the cloud", and not directly using cloud services oneself.
I agree with you, and I think your reasoning is totally understandable. Just that I see additional friction, and friction in a business world is risk :/
(side-note, with Jitsi, it feels like I have a fireplace log in the hands when I use it)
I think Samsung rejected non-"Big Emails", but pretty sure we can find exceptions both ways.
Fun stuff I found while searching:
> https://transportation.ucsc.edu/buses-shuttles/dvs/
>
> The Disability Van Service (DVS) is a shared-ride service that provides on-campus wheelchair ramp–equipped transportation for those unable to use the regular Campus Transit system due to disability
>
> If you are a visitor, please use a Gmail address to complete the form or email dvs@ucsc.edu if that is not possible
and then, the form is behind... a Google login wall
> and then, the form is behind... a Google login wall
Ugh. The people making that should really be informed about the issues they are causing with this. They probably are just uninformed and want to offer a good service, but actually are forcing people to give up personal data to Google, which is a big no-go. This is what happens when digital rights and privacy unaware people are in charge of something like this.
Concert and theatre venues in the US, mostly locked into exclusive agreements with Ticketmaster, practically require a smartphone running the Ticketmaster app. You can load the tickets into the Apple and Google "wallet" apps but you have to have the Ticketmaster app to do that. In the past year I've had to pretend to be a confused elderly person and beg box offices to get me printed tickets because I don't want to load the Ticketmaster app. Eventually I'll have to buy a burner device, assuming I still want to attend live events.
Ah, perfect! One question: is Ticketmaster rejecting non-"Big email providers" ? I suspect they do, due to bots (wouldn't it be the same with Tinder, etc ?)
I don't know. My Ticketmaster account was created in August, 2005, and is a one-off email address at my personal domain. I have no idea if I could create an account like that today (and I'd be afraid to try).
> there's no market for selling a solution that gives individuals data sovereignty
Theres no turnkey solution (of course not, it is prohibitively complex to architect one), but the bits and pieces are there, built on tried and tested software. For example, SMB and rsync and their clients, are practically enough to do backups.
Sovereignty also means responsibility. Either you have to keep your network secure, or you pay someone else do it (not always very well), otherwise you get security problems. Same goes for redundants backups, hardware maintenance, etc.
I have an RTL-SDR rig with the stock tiny omni antenna in a second story of a building adjacent a public parking lot. I'm using rtl433 and I am able to reliably pick up TPMS from the lot. I've never done any testing to see what the metes and bounds of my reception are, but it's definitely not touching the tire. My rig is at least 30 feet away from the closest parking spot.
reply