this post was submitted on 29 Apr 2026
695 points (98.9% liked)
Microblog Memes
11422 readers
3058 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Non-deterministic software is fine and we've been using it for ages. It's usable when:
That rules out several applications of current LLMs, but it rules in several others.
If I have to verify the output of an AI then unless I can do the verification in 30 seconds but work would somehow take me hours then it's not useful. I can't think of many scenarios in which verification is fast but the work itself is slow.
This can be the case for coding. A good example is when the change is simple but involves a library you're unfamiliar with. You can set it off and not have to read any docs, and it will be easy to check if it got the API right.
Elsewhere I gave the example of copyediting. It's a lot quicker to check the output than to refine it yourself.
Easy-to-verify tasks are everywhere I think. Not at the scale of seconds versus hours, but seconds versus minutes