I’ve been telling people that the notion that the ER lets poor people die in the US is false; instead, they make you wish you did.
Mint uses an OAuth token (I think through Plaid). This is not the same thing as sharing a username/password, and is authorized by your bank, since they provide the OAuth flow; otherwise OAuth wouldn’t work in the first place.
Oh, that was me, sorry guys.
Right, and in my case to be clear, it was all businesses headquartered in the US, doing business in Europe, and getting compliant with Europe’s GDPR. I have no idea if it was any different if the businesses were headquartered in Europe (guessing no), but I thought I’d confirm that was the situation.
Yeah, there were different interpretations there from different counsels. It went from “well, they put it there and we don’t store it anywhere else, so nobody is preventing them from removing it, we don’t need to do anything”, with some “oh this field is actually durably stored somewhere else (such as an olap db or something), so either we need to scrub it there too when someone changes a value, or we can just add a ‘don’t share personal information in this field’ little label on the form”; to doing that kind of stuff on all fields.
Overall, the feeling was that we needed to do best effort depending on how likely it would be for a field to durably contain personal info, for it to smell a judge’s smell test that it was done in good faith, as is often the case in legal matters.
Reposting what I posted here a while ago.
Companies abiding by the GDPR are not required to delete your account or content at all, only Personally Identifiable Information (PII). Lemmy instances are unlikely to ask for info such as real name, phone number, postal address, etc; the only PII I can think of is the email that some (not all) instances request. Since it’s not a required field on all instances, I’m going to guess that the value of this field does not travel to other instances.
Therefore, if you invoked the GDPR to request your PII to be deleted, all that would need to happen is for the admin of your instance to overwrite the email field of your account with something random, and it would all be in compliance. Or they could also choose the delete your account, if they prefer.
Source: I’m a software engineer who was tasked at some point with aligning multi-billion-dollar businesses to the GDPR, who had hundreds of millions of dollars in liability if they did it wrong and therefore took it very seriously. I am not a lawyer or a compliance officer, but we took our directions from them directly and across several companies, that’s what they all told us.
I think it’s spot on. It’s people who were already going through the stages of grief, were kinda stuck in “bargaining” (like: “nah, Twitter is not really dead, it’ll come back”), and the symbolism there about Twitter really being gone-gone fast-tracked them to depression/acceptance.
Even if it’s the wrong decision in your case to trust your gut, I worry that if you don’t, you’ll spend the rest of your life wondering what it would be like if you did.
Yup it’s been real. https://www.piquenewsmagazine.com/must-reads/bc-government-hit-tweet-limit-amid-wildfire-evacuations-7268169
The rate limits are because serving such a service at scale without the user noticing requires continuous innovation to get through scale bottlenecks; but with the engineering team greatly reduced, a lot of that work isn’t happening anymore. Typically, you’d get through those bottlenecks by coming up with some heuristics that make it seem like the service is doing a ton, when really it only needs to do little (like by sharding data, or by pre-caching a bunch of stuff). Without anybody to work on those heuristics to fake things, you gotta restrict with real restrictions.
Source: that’s what I do for a living. I’ve been working on some of the highest-scale services out there for over a decade.
Custom-made ear plugs. Even if you only wear ear plugs occasionally (I do when in a noisy hotel, or when a neighbor goes a bit too crazy), they are so worth having.
Basically you go to an audiologist and they put something kinda liquid in each of your ears to take a mold of your ear canals. A couple of weeks later, you have plastic earplugs that have the exact shape of your inner ears.
Upsides: • They work, always. I would typically use wax or silicon disposable ear plugs before that, and sometimes in the middle of the night they might move and let the sound in; those don’t. Also, foam disposable ear plugs don’t stay in my ear, don’t ask me why. • They never hurt. Since disposable ear plugs get shoved into your inner ear until they take the shape, they continuously push against the walls of your ear canals. I would often feel kinda bruised after using them for a long time. • They are crazy comfortable. Put your ear on a pillow, and you barely feel them at all. • But do they block too much sound? That’s up to you. Basically, you choose the level of noise you want to keep out, which I believe is achieved by using different kinds of plastic.
They’re not a trivial purchase (I think mine cost $150), but then you use them for decades, so it’s definitely worth it. It was a stupid purchase in my case, because I bought them on a whim out of anger against my neighbor’s party one night; but they’ve followed me everywhere since!
I’m thinking because it’s as nice as it’s pointless, thereby showing that the devs were detail-oriented in how to delight players.
No, it wasn’t like that. Remember that while computer technology was fairly mainstream, it wasn’t nearly as engrained into our lives as today. So people were talking about a worst-case scenario that involved technological things: potential power outages, administrations maybe shutting down, some public transportation maybe shutting down, … To me, it felt like people were getting ready for being potentially majorly inconvenienced, but that they weren’t at all freaking out.
I do remember the first few days of January 2000 felt like a good fun joke. “All that for this!”