gay blue dog

https://lucario.dev/

  • 0 Posts
  • 41 Comments
Joined 2 years ago
cake
Cake day: March 19th, 2024

help-circle
  • some parts intriguing, but mostly disappointing. several chunks of the text felt AI-generated. no fewer than 34 “it’s not X but Y”'s, by my count, and the out-of-nowhere typographies / tables definitely smell of slop. and obviously, the images definitely were. (can’t even be bothered to fix the typos in photoshop? why make a fake poster for The Stepford Wives??)

    some notes:

    • i’m not entirely convinced the revulsion response in women can be explained entirely as a reflective recognition of the subjected female self. maybe it’s also because AI art is entirely bland and/or fuck ugly

    • some reproductive labors, in the Marxist-feminist sense, are getting subsumed by AI, sure, but they’re largely the ones that already got subsumed by the computer. we had pagers with scheduling and appointment reminders in the 80’s. about the only thing an LLM can do that our previous tech couldn’t is the customer service / “emotional labor” part, albeit poorly. and the other labors are non-optional – my laundry actually does have to go in the dryer, and no matter how many plastic pictures of clean clothes i generate, they can’t actually go in my closet.

    • speaking of, the article appears to use a mangled paraphrase of that Joanna Maciejewska tweet (“I want AI to do my laundry and dishes so that I can do art and writing, not for AI to do my art and writing so that I can do my laundry and dishes”), and then attributes it to “AI enthusiasts” (ew).

    • the article notes that reproductive labor is coded feminine and that the assistants that (attempt to) do this labor are designed female, with feminine voices and affects, despite being, y’know, robots. and not women. the next step to me would be to note that this isn’t just reflecting the subjectification of the female and the designation of women to a particular labor class, but actually aiding to construct and reproduce the subject of “female” itself too. maybe throw some Butler in there. but we just breeze right past this. no third-wave? i don’t see any feminist arguments past the 80’s in here

    • the typography of wives is total bullshit. “The Open-Source Wife” fuuuuucccckk offfff. but. BUT. i do think there is something correct in there about xAI/Grok/Ani basically being the modern adaptation of Vivian James

    • there’s an argument that obviously used to be about AI art, and got transmogrified into a nonsense concept, bordering on colorless green ideas.

    Women’s labor is being extracted, automated, and sold back without credit.

    • the nonsense below it about “alignment” clearly intends to imply that the machines are only faking being our friends / submissive wives(!!1!).

    • but this is okay because women are uniquely suited to interface with AI! this is because (all) women (innately) communicate with the goal of building relationships (female) instead of the utilitarian (manly) execution of transactions (male). there’s an odd essentialist undercurrent that’s not really being challenged here, despite the fact that that would render “female robots” impossible

    • “outsource-maxxing” fuuuuuucuk youuuuuuu

    • the conclusion of the article is basically “women are uniquely capable of interacting with (female) AI because they’ve BEEN the female AI”, with a call-to-action for women to basically… well. resume that role, except now using the AI as your girlbestfriend.









  • i’ll go against the grain here: Librewolfs’s defaults are firmly “meh” for me. still an improvement over the “what the fuck” that’s happening in Firefox.

    pros: nixs the annoying Pocket / AI / “suggested” nonsense by default. no annoying extras.

    neutrals: Firefox Sync is off, but one click and a restart to turn back on. reasonable for a non-Mozilla project. no cookies saved by default might be annoying for some, but you can add exceptions right from the URL bar and i only have a dozen or so of those set for various sites. gods, cohost is still in that list…

    cons: ResistFingerprinting is IMHO way overkill and breaks nice things like automatic dark modes just for preserving privacy in the 0.001% of cases where browser fingerprinting matters. same as WebGL being off by default – i just don’t need that kind of protection

    i still recommend it. Disable ResistFingerprinting, enable WebGL, enable Firefox Sync, and decide for yourself if you want auto-clearing cookies or not. i also always enable vertical tabs because my horizontal space is a lot less constricted than my vertical. (it’s a FF feature!)



  • the obnoxious self-aggrandizement is dripping all over the text, not the least of which when he conceptualizes himself as a part of a “new and potentially valuable class of contributors”, as if the addition of a slop-generator can transform the layperson into someone capable of contributing to a complex software project. but that’s old news. here’s what’s getting me now:

    For a project like Mesa, which uses the permissive MIT license, accidentally incorporating a snippet of code that carries the “viral” obligations of the GPL could potentially trigger a legal catastrophe. Faith Ekstrand drove this point home with a chillingly practical example: “If we piss off Nvidia and they sue us, the project is over. It doesn’t matter whether or not we can theoretically win.”

    this is a legal issue – this should be Seyfarth’s home turf! obviously he can’t code and has a sneering contempt for anyone who learns to do so, but in this micro-instance, giving an informed legal opinion on how this issue could be handled would actually be in the Mesa project’s best interests! let’s see how he

    However this is a hypothetical scenario and there are several ways to mitigate such legal risks. Most projects already shift the legal burden to the contributor. The project still has to reject any code that openly violates the licensing terms, but if such violations are not obvious, there is little legal risk to the project itself.

    “it wouldn’t happen, and even if it did, you could just try to sacrifice your individual developers to NVIDIA one at a time and hope that makes them go away.” great cool thank you. this is the best you’ve got with your legal background. fantastic. what an utter tool



  • and people get very defensive about this one too. like i’m pretty confident that coolboy004 on reddit is not giving a nuanced delivery on the ethics of a company running an ai-powered call center when he types “screws will not replace us” in all caps on /r/fuckai, and yet

    i think it sucks that we’re stuck with, say, bluesky engineers genuinely trying to pull the most moronic variant of “but what if the stochastic text generator might have feelings in the future too”, but we still need to be able to talk about why people feel the need to make “clanka with the hard r” jokes (answer it’s racism)


  • from what i see, white people simply clamor for a context in which they’re “allowed” to finally call someone the n-word, and are willing to accept substitute targets for their racism

    add in a protective cloak of “it’s ironic and a joke and YOU’RE the real racist for pointing this out” and you get a whole lot of people who are extremely okay slinging around barely modified racial slurs