fracture [he/him]

  • 0 Posts
  • 12 Comments
Joined 1 year ago
Cake day: June 21st, 2023
  • fracture [he/him] @beehaw.orgtoTechnology@beehaw.org•AI-Powered Social Media Manipulation App Promises to 'Shape Reality'
    1·
    15 days ago

    beyond the obvious ways this is fucked up, imagining this happening with AI gen text is insane. trying to craft a post to both empathize with another poster, kindly demonstrate flaws in thinking or logic about a point they usually care a lot about, and trying to explain how the different point of view better supports the things they care about it such a monumental effort already that AI just cannot do. no actual persuasion will come out of this (not that a ton happens on the internet to begin with, but even less than that)

    and honestly if you’re firehosing people like that, AI is just going to absolutely drown out any actual communication from happening. at some point, we’ll just have bots going to war for us about our points, and no one will be reading it

  • fracture [he/him] @beehaw.orgtoTechnology@beehaw.org•Low Tech Magazine: Communal Luxury: The Public Bathhouse
    6·
    1 month ago

    i would have liked it if this had offered a COVID perspective on communal baths. i’m inclined to think that a hot moist environment is a likely place for it to flourish, and it seems odd to neglect to mention that three years of a pandemic probably had an outsize impact on the number of bathhouses still open in 2022

    obviously we probably don’t have a ton of data on how to circulate air and filter COVID out of bathhouses, but i also bet there’s a way to do it in a relatively energy efficient way

    anyways, it feels like a major spot that’s lacking in an otherwise informative and well thought out read

  • fracture [he/him] @beehaw.orgtoTechnology@beehaw.org•Designing Friction (philosophical essay about technology)
    2·
    3 months ago

    it’s an interesting article, but i think the authors are conflating friction for wanting genuine human interaction; its easier than ever for me to make friends because i can instantly connect with and message back and forth, quickly and in real time, over various platforms e.g. discord, the depth of which is only limited by our interactions and how we treat them. forcing us back to sms/email/paper mail doesn’t make our interactions deeper, even though it adds friction. it means we can easily choose what the depth of connection we want is

    that isn’t to say that there aren’t examples where less friction leads to less interaction. dating apps are a great example. but i think the authors are conflating the friction for the interaction. yes, you could add friction that would encourage interaction, but you could also add friction that doesn’t. i think the more salient point would be, encouraging interaction often includes friction, but one shouldn’t shy away from that, as a UI/UX developer

    which, granted, isn’t as catchy of a title. but they could have gone into greater detail for that in the article, too

    regardless of this critique, i enjoyed reading it and the perspective it offered, even if i don’t strictly agree

  • fracture [he/him] @beehaw.orgtoTechnology@beehaw.org•Tumblr and Wordpress to Sell Users’ Data to Train AI Tools
    1·
    8 months ago

    thanks for sharing this information with us, i think it’s important to discuss this stuff on the fediverse

    i notice that beehaw doesn’t have a similar clause in its TOS, as far as i can tell. without the expectation of you answering this question, i’m wondering what the difference is between the two such that cohost has such a clause and beehaw doesn’t. maybe it’s because one is run by an individual and one is run by a small company?

    i did a search on cohost itself to see if anyone else talked about this and found this quite extensive thread: https://twitter.com/rahaeli/status/1588769277053739010

    so based on what you’ve said and what’s in that thread, i’m gonna update my post with some qualifications about cohost. thanks for piqing my interest in the TOS