𞋴𝛂𝛋𝛆

  • 40 Posts
  • 661 Comments
Joined 2 years ago
Cake day: June 9th, 2023
  • 𞋴𝛂𝛋𝛆@lemmy.worldtoTechnology@lemmy.world•Discord's face scanning age checks 'start of a bigger shift'English
    122·
    2 days ago

    Actually look at the way Discord works in your network, like all the raw IP addresses and and connections with no clear ownership or human readable name, with dozens of changing connections to get any of it to work. Then go try to ask questions about what is going on and who you’re connecting to. Discover that none of it is documented or described anywhere. Then realize that this means no one running Discord is doing so on a fully audited and logged host. You simply cannot be without a bunch of effort. I made it to the 6th layer of whitelisted raw IP addresses, and still nothing worked while trying to connect to Discord in a fully logged and documented network. I am simply unwilling to write a script to annotate that many connections so that all of my logs make sense. I seriously doubt anyone on Discord is doing so, and they certainly lack any understanding of what they are connecting to, why, or the protocols. So the Discord user is telling me “my opsec and privacy awareness is as nonexistent as a pig in a herd running off a cliff, and my system should be assumed compromised with no idea of what might be connected.” Everyone else doing it is a garbage excuse. That no one appears to have gotten hurt – has tissue thin merit, but also reveals that the user runs blind in herds while hoping for the best. Such information infers a lot about a person, their depth, accountability, and ethics – in certain scopes.

  • 𞋴𝛂𝛋𝛆@lemmy.worldtoAssholeDesign@lemmy.world•Open Teams in a mobile browser and Microsoft says your browser is unsupported and to download the app, but if you request the desktop site it worksEnglish
    11·
    4 days ago

    It is the CPU back end that is giving me trouble with build all. The free as in freedom aspect of open source is violated when any software promotes and primarily supports a proprietary tool chain. Things like how there are two checklist files, one in the primary and one in the build directory likely prevents many from succeeding. If the initial configuration was wrong or needs to be changed, the user will likely attempt to change the checklist in the main directory only to find that the changes do nothing. Several of the back ends also require manually tracking down their library paths and adding these to the source. Many of these, such as BLAS, CuBLAS, and Vulkan will fail until just the right version is included while the errors have no hinting. There are numerous other issues like ARM options not described as such, and ambiguous runtime options. Various edge case options generate a fatal warning error. Once any of these are set, the build fails without hinting about the cause, and the barely mentioned solution of manually editing the checklist yields no results.

    I’m sure this is trivial for the average dev, but dev I am not. I’m just some weird script kiddie that can also build an ALU with a NOR gate, or might talk about a 65C816 in a room of 6502 fans. But I have a large number of other interests in life.

    Be nicer to people. When some dumbass takes 8.5 of your 9 cat lives on the road one day, cordiality can have a large impact on your daily. I was much the same to others and regret it.

Moderates