• 0 Posts
  • 28 Comments
Joined 4 months ago
cake
Cake day: May 7th, 2024

help-circle



  • The latter has been taken over by ElMu and his shenanigans, the former was originally a Twitter-internal project for a decentralised social media interfacing protocol, got forked out from Twitter in 2021 (the year before Musk took over Twitter), has a lot of Ex-Twitter people on it and promises to do a lot of things a lot better than either Twitter (now X) and offer a little more resilience against things like moderator abuse.

    Curiously, that last bit is the first time I’ve seen a reasonable use case for Blockchain: Your content can be stored on arbitrary servers and migrated to others. Your identity is tied to keys that can be used to verify your content is actually yours. The info where the public half of the key and all your content are stored is recorded in a public, distributed, append-only ledger, where each entry verifies the integrity of the previous one. Thus, once you’re registered on that, no single moderator can arbitrarily ban you anymore. (Pretty sure there’s a hole in that logic, but I’m not versed enough to confidently assert as much.)

    Of course, there’s a caveat: To discover content, you need an index (“relay”) of all the content feeds. That takes some of the content aggregation load off your individual content servers and makes hosting them easier. However, it shifts the content moderation / federation power from the individual instances to the shared index: If a given index blocks your content, people using it won’t see your content.

    In theory anyone can host their own relay and everyone can choose which relay they want their content feed to use. In practice, hosting a relay is resource-intensive, bsky have a solid headstart and probably more resources, and their app also obviously uses their own index by default, so if you do want to create a “competitor”/alternative index, you’ll have a lot of catching up to do. They even state that expectation: “In all likelihood, there may be a few large full-network providers” src

    Which is basically a small-scale version of Google and Bing (and the AT Protocol Overview explicitly uses that comparison): Sure, you can make your own search engine, but if Google is the default everywhere, has a lot of storage and computing power to serve more requests and has way more indexed content, why would people use yours instead? Thus, if you want your content to be seen by many people, you have to play by the big relays’ rules.

    Much decentral. Very open.


    (I’m being snarky here, but I will give them the benefit of the doubt: They probably do mean to make self-hosting your personal data and content easier, and it’s easier for custom feeds to use single, big relays to draw from rather than doing the indexing and collation themselves. However, it provides them with a lot of leverage and just because they call themselves a “public benefit corporation” doesn’t mean I trust them not to start enshittifying for profit at some point.)




  • If you have no idea how long it may take and if the issue will return - and particularly if upper management has no idea - swapping to alternate solutions may seem like a safer bet. Non-Tech people tend to treat computers with superstition, so “this software has produced an issue once” can quickly become “I don’t trust anything using this - what if it happens again? We can’t risk another outage!”

    The tech fix may be easy, but the manglement issue can be harder. I probably don’t need to tell you about the type of obstinate manager that’s scared of things they don’t understand and need a nice slideshow with simple words and pretty pictures to explain why this one-off issue is fixed now and probably won’t happen again.

    As for the question of scale: From a quick glance we currently have something on the order of 40k “active” Office installations, which mostly map to active devices. Our client management semi-recently finished rolling out a new, uniform client configuration standard across the organisation (“special” cases aside). If we’d had CrowdStrike, I’d conservatively estimate that to be at least 30k affected devices.

    Thankfully, we don’t, but I know some amounts of bullets were being sweated until it was confirmed to only be CrowdStrike. We’re in Central Europe, so the window between the first issues and the confirmation was the prime “people starting work” time.









  • Why would you want backwards compatibility? To play games you already own and like instead of buying new ones? Now now, don’t be ridiculous.

    Sarcasm aside, I do wonder how technically challenging it is to keep your system backwards-compatible. I understand console games are written for specific hardware specs, but I’d assume newer hardware still understands the old instructions. It could be an OS question, but again, I’d assume they would develop the newer version on top of their old, so I don’t know why it wouldn’t support the old features anymore.

    I don’t want to cynically claim that it’s only done for profit reasons, and I’m certainly out of my depth on the topic of developing an entire console system, so I want to assume there’s something I just don’t know about, but I’m curious what that might be.




  • I used to sneer at the kids in my class that used it. Must have been fairly shortly after it launched, something like fourteen to fifteen years ago. I’m still grappling with a certain inertia when it comes to switching away from something I have relied on for so long, but I’m coming around to the idea of giving DDG a try at least (irrational as it is, I’ve been reluctant to even try - I suspect out of fear of liking it and having to change).

    Past Me would be exasperated that Present Me is even toying with the idea. But then, Past Me had a lot of stupid takes anyway.