this post was submitted on 15 May 2026
64 points (100.0% liked)
Slop.
597 readers
317 users here now
For posting all the anonymous reactionary bullshit that you can't post anywhere else.
Rule 1: All posts must include links to the subject matter, and no identifying information should be redacted.
Rule 2: If your source is a reactionary website, please use archive.is instead of linking directly.
Rule 3: No sectarianism.
Rule 4: TERF/SWERFs Not Welcome
Rule 5: No bigotry of any kind, including ironic bigotry.
Rule 6: Do not post fellow hexbears.
Rule 7: Do not individually target federated instances' admins or moderators.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"security tweaks"
Yeah I'm no expert but [the bug they fixed could theoretically get cloud hosting private keys for the hosted service]
Complete hallucination, this is improper validation of requests, nothing about fetching something or leaking credentials.
Also, 169.254.0.0/16 is the link-local IPv4 network so it doesn't even make sense outside of the fact that aws servers may get metadata on such networks (which again is absolutely unrelated to this diff). Is this a 3b model? Seems like it ran out of context, maybe it loaded the entire html page.
I'll bold it next time. However, thank you for your analysis!
is this live? If it is please remove the comment and tell the devs. This could put people who already are being harassed on the regular by trolls at risk. I don't know if IP addresses are logged, not everyone uses burner email addresses etc.
I can't even mod the comment bc then it just shows up on the modlog, i'd have to remove the entire post.
They patched it. This is what the threat was.
It was not, that's only what deepseek said it was. I don't know why you edited the comment to hide the details of the hallucination instead of accepting that it fluked.
I changed it before I read your comment because a mod asked me to. Relax.
Ah good