• 0 Posts
  • 1.79K Comments
Joined 2 years ago
cake
Cake day: December 29th, 2023

help-circle

  • Pup Biru@aussie.zonetoAustralia@aussie.zone*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 days ago

    this law covers the fediverse. aussie.zone now has a verification process

    i agree with the above commenter: something should be done, but this is the wrong way to do it… it creates problems and effectively solves none

    real vibes of

    The laws of mathematics are very commendable, but the only law that applies in Australia is the law of Australia.

    - Malcom (cunt) Turnbull - a conservative ex-PM





  • i completely agree, i just don’t think that particular line of reasoning (not taking into account anonymous sites) proves that

    if they wanted to do it properly, they’d have a system that integrates with mygovid that sites can integrate with via some oauth-like flow (login with facebook, login with google, etc: but verify with mygov), and the only thing the site gets back is a “yes over 16”

    the government has this data; there’s no reason anyone else should see it

    of course that’s also assuming the whole concept is a good idea, which is absolutely not… it’s wallpapering over a massive problem whilst solving absolutely nothing and causing issues





  • the vuln afaik is for remote code execution via basically a mechanism that’s kinda like a transparent RPC to the server (think like you just write frontend code with like a “getUsers” and it just automatically retrieves and deserializes the results so you can render the UI without worrying about how that data exists in the browser)

    i’m not a front end engineer, and haven’t used react server components, but i am a principal software engineer, i do react for personal projects, and have written react professionally

    i can’t think of a way it’d be exploitable via purely client-side means

    i THINK what they mean is that you can use some of the RSC stuff without the RPC-style interfaces, and in that case they say the server component is still vulnerable, but you still need react things running on your server

    a huge majority of react code is client-side only, with server-side code written in other languages/frameworks and interfaces with something like REST or GraphQL (or even RPC of course)




  • in the same way that engineering disciplines often provide priority to women because it’s hard af for them in the discipline not for any good reason but just because the industry is misogynistic af

    being a women and a gamer is far more toxic than being a man and a gamer, and that drives away a lot of women who may have been the best, and men don’t have that same hindrance just by virtue of their gender

    id argue too that anyone claiming to be trans probably has similar levels of toxicity, and therefor it shouldn’t be an issue: if the division is about encouraging diversity to combat toxicity, who cares if that toxicity comes from transphobia or misogyny


  • most things scale if you throw enough resources at them. we generally say that things don’t scale if the majority case doesn’t scale… it costs far fewer resources to scale with multiple repos that it does to scale a monorepo, thus monorepo doesn’t scale: i’d argue even the google case proves that… they’ve already sunk so much into dev tooling to make it work… it might be beneficial to the culture (in that they like engineers to work across the entire google codebase), but it’s not a decision made because it scales: scale is an impediment





  • you can’t apply group behaviour to single events… it takes time to change human behaviour in a group - especially when it’s politicised behaviour … if every restaurant were serving raw patties and raw was incorrectly politicised as “healthier” and then 50% started being cooked you’d say that’s progress… it’d remain horrible, but it is indeed progress and clearly those doing better should be congratulated for somehow managing to get their shit together even a little bit