this post was submitted on 21 Sep 2026
648 points (97.2% liked)
Microblog Memes
12204 readers
3653 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
RULES:
- Your post must be a screen capture of a microblog-type post that includes the UI of the site it came from, preferably also including the avatar and username of the original poster. Including relevant comments made to the original post is encouraged.
- Your post, included comments, or your title/comment should include some kind of commentary or remark on the subject of the screen capture. Your title must include at least one word relevant to your post.
- You are encouraged to provide a link back to the source of your screen capture in the body of your post.
- Current politics and news are allowed, but discouraged. There MUST be some kind of human commentary/reaction included (either by the original poster or you). Just news articles or headlines will be deleted.
- Doctored posts/images and AI are allowed, but discouraged. You MUST indicate this in your post (even if you didn't originally know). If an image is found to be fabricated or edited in any way and it is not properly labeled, it will be deleted.
- Absolutely no NSFL content.
- Be nice. Don't take anything personally. Take political debates to the appropriate communities. Take personal disagreements & arguments to private messages.
- No advertising, brand promotion, or guerrilla marketing.
RELATED COMMUNITIES:
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
On the promises, they will have some influence within the current conversation, maybe (everything is a bit wobbly). It is unlikely to repeat verbatim a step it did before that still has something in the context window correlated with bad operator input. It will have some success with things that resemble, but are not the same, but sometimes it can surprise by failing to recognize what a human would have considered roughly the same thing and doing it anyway. Or the 'promise' has evaporated out of the context window, and when called on it, it will take the fact that it previously promised not to do that as a fact even though it had lost the promise. So even if it says "I'm sorry I made the promise and broke it", it doesn't even mean it actually had the promise in "memory" when it broke it.
On the blame for something that didn't happen, it's a limitation where the model treats the narrative as reality. An instance is often incapable of evaluating facts without data about those facts one way or another. I have seen models "pass" my test by recognizing in their context that I'm dealing with an utterly non-agentic service, and thus it could not have been the case that it ever deleted files or dropped tables. Sometimes even those produce a narrative of what it did wrong (out of nothing), because narrative is the thing being generated, relationship with factual reality being a function of good correlation with narrative content. If a service is even potentially agentic, then it would tend to accept the operator account as factual, since it has no idea instance to instance if there's some other context where it did, and if it generated skepticism that it would ever generate such a mistake, that's more likely to piss off an operator.
So it incorporates the operator assessment as some 'factual' injection into the context, unless some objective source of truth is available to contradict the operator.