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

help-circle

  • It’s my perpetual gripe with many of those open tools that I love ideologically, but practically find lacking in some respects, typically UI/UX (including the pre-experience of the decision whether to use them). I don’t have all the skills or knowledge to fix the issues that bother me, as it’s often far eaiser to know what’s wrong than how to fix it.

    I understand and endorse the philosophy that it’s unfair to demand things of volunteers already donating their time and skills to the public, but it creates some interdisciplinary problems. Even if capable UX designers were to tackle the issue and propose solutions or improvements, they might not all have the skills to actually implement them, so they’d have to rely on developers to indulge their requests.
    And from my own experience, devs tend to prioritise function over form, because techy people are often adept enough at navigating less-polished interfaces. Creating a pretty frontend takes away time from creating stuff I’d find useful.

    I don’t know if there’s an easy solution. The intersection between “People that can approach software from the perspective of a non-tech user”, “People that are willing to approach techy Software” and “People that are tech-savy enough to be able to fix the usability issues” is probably very small.





  • I appreciate that you took the time to supply the nuances I omitted. While there is value in a positive framing, it’s important to acknowledge potential struggles as well. We can’t effectively tackle issues if we’re not aware of them.

    In any case, while I’m not qualified to help you with your difficulties, I hope you find - or have found - a way to work on overcoming them. Dealing with insecurities, from my own experience, can be a tough process, further amplified by setbacks and a lack of perceived progress. But if you persevere, even if you might not feel that you have improved much, you may find yourself looking back at a time when it was worse and, by contrast, see the progress you’ve made. May that hope, that your future self will look back and be proud of your hard work, give you the strength to keep going.



  • Well, you sound like a team player. You place the common good (fun together) higher than individual ambitions (or maybe place your own worth very low, I can’t tell from one sentence, but the outcome is the same).

    Saying deliberately sounds like it’s not just a thing that you find yourself doing again and again, but a conscious choice. That suggests there was a choice to make; that the option of playing a self-centered character was something you were actively aware of, but were sufficiently repulsed by it to make a point of being better than those people.

    I think you’re a nice person, empathetic, while not so entirely innocent as to not even consider the possibility, still principled and caring enough to actively defy it.

    I think you’re a net good for this world.




  • 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.