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!”

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.

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.

Yeah, I think that’s probably more accurate than what I was thinking, and that leaving belongs to acceptance rather than depression.

I was actually aware of that, which is why I wrote depression/acceptance, meaning they probably moved from bargaining to either one of those, thinking either of those 2 stages could prompt people to leave. By fast-tracking, I meant that moved happened faster than they would have if the rebranding hadn’t happened. It’s still a fascinating bit, I have known about the stages of grief for a while, but only learned recently (like, this year) that they didn’t have to happen in order.

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.

Yeah, to be clear, what the friend was saying that day is that they don’t even have access to file names. For them it’s 100% mangled data.

I would definitely consider file names to be personal information, that I would expect to be encrypted. If I store a file named “Letter to IRS for 2020 violation.doc”, then suddenly you know something about me that I probably don’t want you to know.

Oh that’s interesting!

Yeah, that conversation is much, much older, pretty close to the very start of iCloud file storage. I’m guessing either things changed since and they used to be end-to-end encrypted, or more likely, what the friend was complaining about is his iCloud infrastructure team didn’t have access to the keys stored by another team, and reverse. So basically, Apple could technically decrypt those files, but they don’t by policy, enforced by org-chart-driven security.

Now excuse me while I go change a setting in my iCloud account… 😳

I once had a conversation under NDA (which has expired since) with an engineer at Apple who was working on iCloud infrastructure, and he was telling me that his team was a bit shocked to read that Dropbox was releasing apps for photos at the time “because they’ve noticed that most of the files users are uploading to Dropbox are photos”. He was like: how do they know that exactly? His team had no idea and couldn’t possibly find out if the encrypted files they were storing were photos, sounds, videos, texts, whatever. That’s what encryption is for, only the client side (the devices) is supposed to know what’s up.

Not having that information meant a direct loss of business insights and value for Apple, since Dropbox had it and leveraged it. But it turns out Apple doesn’t joke around about security/privacy.

Summary: “oh no, startups are risky”.

I don’t hate it, but every time now that I get linked to a Reddit post, I look at the comments, and every time I get a little more shocked at the amount of low-value, hateful comments over there compared to here.

In other words, I don’t hate it, but I feel like it hates me.

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.

HackerNews being a bit of a time-suck, I’m subscribed to HN Digest, the daily newsletter of only the top links of Hacker News.

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!

My best answer is: if they get to sufficient scale, both Lemmy and Kbin will face scaling issues to get through, but Lemmy is based on something that will make it much easier for humans to get through a lot of those bottlenecks.

I hope what this answer conveys is that the technology choice is a major factor, but not the only factor. If the Lemmy dev team doesn’t know how to scale a service, and don’t enlist the help of people who do, the underlying technology won’t make much of a difference. But it does give them a very strong upside.

Another Lemmy user was saying that the Kbin move to use PHP was like someone saying: “oh, I like the airplane you just built by yourself with the intention to fly above the clouds, I’m going to do the same thing, let me prepare my cardboard”, and there’s a lot of truth to it. 😉

The Kbin creator had initially joined to help Lemmy, but decided to create his own thing when he couldn’t take their political alignments anymore. The Lemmy devs used to be vocal Uyghur genocide deniers and pro-North-Korea, and would answer questions on Reddit’s r/AskATankie (a tankie is someone who supports communist dictatorships), but now that Lemmy is successful, they’ve kind of grown hush-hush on it, without really addressing it.

So, he went to create Kbin, but since he’s not a software engineer, he chose foundations that won’t really scale too well. Kbin is written in PHP, which is an interpreted and mono-threaded technology, it’s great at some stuff, but not high-scale services (source: that’s what I do for a living). Lemmy was written in Rust, which is compiled and multi-threaded. It doesn’t mean Lemmy won’t meet tricky scale bottlenecks, but it will give it a much larger toolset to get through whole classes of them.

And of course, Kbin being much younger, it doesn’t currently have a bunch of critical stuff that Lemmy already has. For instance: an API, which has been allowing other people to build great native clients for it.

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.