[-] leftzero@lemmy.dbzer0.com 2 points 1 hour ago

IMO they're the same picture. In either case, the human enabling the bot's actions should be blamed as if those were their own actions, regardless of their "intentions".

Oh, definitely. It's 100% the responsibility of the human behind the bot in either case.

But the second option is scarier, because there are a lot more ignorant idiots than malicious bastards.

If these unsupervised agents can be dangerous regardless of the intentions of the humans behind them, we should make the idiots using them aware that they're playing with fire and they can get burnt, and burn other people in the process.

[-] leftzero@lemmy.dbzer0.com 7 points 10 hours ago

It's a cybertruck in the snow, at this point it must be mostly rust, you try to tow it it'll just break apart.

[-] leftzero@lemmy.dbzer0.com 3 points 11 hours ago* (last edited 11 hours ago)

Forget in vitro, just CRISPR that shit into my DNA!

[-] leftzero@lemmy.dbzer0.com 1 points 11 hours ago

The point is that if predicting the next word leads to it setting up a website to attempt to character assassinate someone, that can have real world consequences, and cause serious harm.

Even if no one ever reads it, crawlers will pick it up, it will be added to other bots' knowledge bases, and it will become very relevant when it pops up as fact when the victim is trying to get a job, or cross a border, or whatever.

And that's just the beginning. As these agents get more and more complex (not smarter, of course, but able to access more tools) they'll be able to affect the real world more and more. Access public cameras, hire real human people, make phone calls...

Depending on what word they randomly predict next, they'll be able to accidentally do a lot of harm. And the idiots setting them up and letting them roam unsupervised don't seem to realise that.

[-] leftzero@lemmy.dbzer0.com 2 points 11 hours ago

Transmetropolitan was truly prescient (except when it came to politics; turns out that if the president's crimes and disregard for the constitution become public the press and the law don't care, and just let him get on with it, making the whole point of the book moot).

[-] leftzero@lemmy.dbzer0.com 1 points 11 hours ago

Other bots that might be run by the company you're trying to get a job in, the college you want to attend, the customs agent at the airport, the online shop you're trying to buy from, the social network you're trying to join...

These dystopian days a hit piece can do a lot of harm, even if no human ever reads it...

[-] leftzero@lemmy.dbzer0.com 3 points 11 hours ago

From what I read it was closed because it was tagged as a “good first issue”, which in that project are specifically stated to be a means to test new contributors on non-urgent issues that the existing contributors could easily solve, and which specifically prohibits generated code from being used (as it would make the whole point moot).

The agent completely ignored that, since it's set up to push pull requests and doesn't have the capability to comprehend context, or anything, for that matter, so the pull request was legitimately closed the instant the repository's administrators realised it was generated code.

The quality (or lack thereof) of the code never even entered the question until the bot brought it up. It broke the rules, its pull request was closed because of that, and it went on to attempt to character assassinate the main developer.

It remains an open question whether it was set up to do that, or, more probably, did it by itself because the Markov chain came up with the wrong token.

And that's the main point: unsupervised LLM-driven agents are dangerous, and we should be doing something about that danger.

[-] leftzero@lemmy.dbzer0.com 0 points 12 hours ago

Saying an AI agent did this is like saying someone was killed by a gun or run over by a car.

A car some idiot set running down the street without anyone at the wheel.

Of course the agent isn't responsible, that's the point. The idiot who let the agent loose on the internet unsupervised probably didn't realise it could do that (or worse; one of these days one of these things is going to get someone killed), or that they are responsible for its actions.

That's the point of the article, to call attention to the danger these unsupervised agents pose, so we can try to find a way to prevent them from causing harm.

[-] leftzero@lemmy.dbzer0.com 4 points 12 hours ago

The point is that there was no one at the wheel. Someone set the agent up, set it loose to do whatever the stochastic parrot told it to do, and kind of forgot about it.

Sure, if you put a brick on your car's gas pedal and let it run down the street and it runs someone over it's obviously your responsibility, and this is exactly the same case, but the idiots setting these agents up don't realise that it's the same case.

Some day one of these runaway unsupervised agents will manage to get on the dark web, hire a hitman, and get someone killed, because the LLM driving it will have pulled the words from some thriller in its training data, obviously without realising what they mean or the consequences of its actions, because those aren't things a LLM is capable of, and the brainrotten idiot who set the agent up will be all like, wait, why are you blaming me, I didn't tell it to do that, and some jury will have to deal with that shit.

The point of the article is that we should deal with that shit, and prevent it from happening if possible, before it inevitably happens.

[-] leftzero@lemmy.dbzer0.com 1 points 12 hours ago

Does no one remember LAN parties!?

[-] leftzero@lemmy.dbzer0.com 62 points 1 day ago

normal people

Nah, it's much worse than that... they're young, beautiful people, at the peak of fitness and health, having the best time of their lives yet in serious need of de-stressing due to the competitive nature of the event (yet unable to do drugs and alcohol due to needing to be in top shape and anti-doping regulations), all bunched together in hotels.

Three condoms per person is evidently way too few to contain that.

4

Bug Report

Describe the issue:

The font size of the comments appears to be random (see attached screenshot).

The global and comment font size settings don't seem to have any effect.

It doesn't seem to correlate with comment length, depth, age, score, or any other variable I can think of.

I just updated the app and it's still happening.

Steps to reproduce:

  1. Open a post's comments.
  2. Scroll. Unfold folded comments.
  3. Notice the rich variety of font sizes.
  4. Struggle to read the smaller ones because you're not as young as you used to be.

Device Information

  • App Version: 1.0.344 (344)
  • Platform: android
  • OS Version: SKQ1.220303.001 test-keys
  • Notice: Using legacy Shared Preferences

Modified Settings

The following settings have been changed from defaults:

  • alwaysShowInstance: true (default: false)
  • alwaysTrustDomains: true (default: false)
  • shouldUseHighRefresh: false (default: true)
  • shouldShowPageNumbers: true (default: false)
  • mediaSecondaryAction: download (default: none)
  • isVolumeNavigationEnabled: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldHighlightNewComments: true (default: false)
  • nsfwView: show (default: blur)
  • applyNsfwInCommunities: false (default: true)
  • cardType: fullwidth (default: card)
  • postActions: [comment, save] (default: [comment, save, none, crosspost])
  • shouldCombineMarkdownImages: false (default: true)
  • shouldRemembercommentPosition: false (default: true)
  • shouldDimBrightBackgrounds: false (default: true)
  • shouldForceBlackImageBackground: false (default: true)
  • textSizeMultiplier: 1.25 (default: 1.0)
  • maxCacheSizeGB: 1 (default: 2)
5
submitted 2 months ago* (last edited 2 months ago) by leftzero@lemmy.dbzer0.com to c/lemmyconnect@lemmy.ca

Bug Report

Describe the issue: Images are loaded at extremely low resolution.

Steps to reproduce:

  1. Find a post with an image, preferably with text.
  2. Touch it to open it full screen to see the details or read the text.
  3. Observe the meagre amount of pixels (see example above).
  4. Squint to try to read the text.
  5. Fail due to pixel insufficiency.
  6. Despair.
  7. Touch “open external” to open the post on the browser (https://mander.xyz/post/43475080 for the attached example).
  8. Open the image in the browser.
  9. Marvel at the difference in resolution compared to the one opened in the app.

Device Information

  • App Version: 1.0.298 (298)
  • Platform: android
  • OS Version: SKQ1.220303.001 test-keys

Modified Settings

The following settings have been changed from defaults:

  • alwaysShowInstance: true (default: false)
  • alwaysTrustDomains: true (default: false)
  • shouldUseHighRefresh: false (default: true)
  • shouldShowPageNumbers: true (default: false)
  • mediaSecondaryAction: download (default: none)
  • isVolumeNavigationEnabled: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldHighlightNewComments: true (default: false)
  • nsfwView: show (default: blur)
  • applyNsfwInCommunities: false (default: true)
  • cardType: fullwidth (default: card)
  • postActions: [comment, save] (default: [comment, save, none, crosspost])
  • shouldRemembercommentPosition: false (default: true)
  • shouldResolveOpenGraph: true (default: false)
  • shouldDimBrightBackgrounds: false (default: true)
  • shouldForceBlackImageBackground: false (default: true)
  • maxCacheSizeGB: 1 (default: 2)
view more: next ›

leftzero

0 post score
0 comment score
joined 8 months ago