Gregory's ServerThe first rule of #Enshittification is that proper lock-in cannot occur if the product is thriving as Open Source, so once you've reached sufficiently high switching costs, pull out the rug.
|
9 posts total
Show previous comments
 Thinking of starting a new consulting business, called "That's Fucked Up As A Service". I sit there and you explain your legacy system to me, and all I do is say "That's fucked up." If you agree, you get a discount. If you try to justify the brokenness, you have to pay double.
Show previous comments
  "It looks like the reason you are paying so much tax, is that your profits are too high." " I can help you with that. " :D Well done, Rolling Stone. That's how you write a headline. (And the rest of the obit brings more 🔥.) https://www.rollingstone.com/politics/politics-news/henry-kissinger-war-criminal-dead-1234804748/ Ken Thompson's original Unix backdoor of "Reflections on Trusting Trust" fame was apparently never published. 40 years (!) later, here it is: 99 lines of code plus a 20-line shell script. That's it. Nicely annotated and explained by Russ Cox:  @jschauma oh SWEET apparently he was just waiting to be asked for the code! now we feel silly   Remember the X.509 PKI? You know, the one that gave us - "Oh wait, certificate revocation is basically all broken" and my all-time favorite: - Honest Ahmed's Used Cars and Certificates It's great, because it secures virtually all web traffic, and all you have to do is get a certificate from a certificate authority -- any one at all! Don't be picky: there are literally hundreds in your trust bundle: You guys! It's here! It's finally here! Party like it's Y2K38! 🎉 https://www.calendar-australia.com/holiday/easter-sunday/4-20-2025/
Show previous comments
@jschauma Interesting. It just reset to 0 epoch time rather than roll over to 1901. @jschauma Meanwhile, NTFS users are safe until sometime on May 28, 60056. XD  w00t! i spent new years eve of 1999 like most of my friends. online, waiting to see what we'd miss in the way of y2k fixes. for 2038, i'm just going to be sitting there, with my gas powered generator to keep my freezer making ice, sipping cocktails, and chuckling quietly to myself. occasionally muttering "told em so" or "you'd think they'd have learned by now" under my breath as i smile. Who reads your email? Ok, ok, nobody does. Even you don't want to, I know. But... who _could_? A 🧵 about centralization of MX records across gTLDs: SMTP relies on MX records in the DNS to identify which server(s) it should hand the mail off to, and over 40 years after RFC722 was published, email is still cleartext. Together, this means that any receiving mail server can trivially read any message passing through. |
@jschauma I thought I was into a good one there.
*Sigh* Time to look into paying those switching costs
@jschauma According to this statement from Bitwarden on Twitter, it wasn’t intentional: https://xcancel.com/bitwarden/status/1848135725663076446
@jschauma@mstdn.social
@bitwarden@fosstodon.org what is this supposed to mean? Do you plan to make all your clients depends on a proprietary SDK while still calling your software FOSS? That's not persuasive enough. 😡
#Bitwarden