Little bit of everything!

Avid Swiftie (come join us at [email protected] )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 0 Posts
  • 102 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle




  • all good points, and I’ll for sure say that I’m not qualified enough to be able to answer that. I also don’t think politicians or moms groups or anyone are.

    All I’ll do is muddy the waters more. We as the vast majority of humanity think CSAM is sick, and those who consume it are not healthy. I’ve read that psychologists are split. Some think AI generated CSAM is bad, illegal, and only makes those who consume it worse. Others, however, suggest that it may actually curb urges, and ask why not let them generate it, it might actually reduce real children from being actually harmed.

    I personally have no idea, and again am not qualified to answer those questions, but goddamn did AI really just barge in without us being ready for it. Fucking big tech again. “I’m sure society will figure it out”



  • People who don’t like paying for labor declares new technology will finally let them automate people away. More at 11.

    I remember decades ago when I was working at mcds as a greasy teenager when they told me that I only had a couple years left there, that our jobs would probably be automated soon. That stores without humans at all were just around the corner.

    Any engineer who has worked with AI directly knows what it’s great at (a slim number of finite tasks), what it appears to be great at (many many tasks), and what it is not good at (everything else). Corporate America sees no distinction.







  • Ohhkay I finally get what you’re suggesting now. From something like Mastodon there’s no clear way to specify.

    Ehh, something to be solved but not a huge deal IMO. I think it’d have to be something custom, as there’s no concept on Mastodon like Lemmy’s communities, but I still stand by DNS isn’t the way to solve it. Mixing it in with a hashtag might be a good way, where if you could “subscribe” to a hashtag over there, like #community@instance.tld, but then we’re just talking about syntax. I actually do think there needs to be a standardization on “groups” then across the fediverse, and since Lemmy is the only one I’ve seen with a group syntax, I’d just suggest we standardize !


  • And that’s why users get @user and communities are !community. I’m not sure what you’re asking for tbh, I think the current system works fine, searching could be easier, but I haven’t seen anyone confused by the difference there.

    Nested DNS is a pain, and not really what it’s meant to do, that’s why we don’t use nested DNS. If you take DNS away as a solution (because it’s not really one), then what is currently happening makes a lot of sense.



  • As an instance owner, the amount of overhead to support that would be nuts for me. Each subdomain would have to have DNS routed to it, or a wildcard which isn’t the best supported. On top of that I’d need to somehow manage certs in a way where when the software detects a new community it’d have to ask for a new cert and broadcast the new domain to everyone. Then what do you do about communities from other instances on your instance?

    What is being done is the right way. We use DNS to tell us different services/hosts. We use the path to tell us a subsection of the same service