this post was submitted on 10 Jan 2026
428 points (99.3% liked)
Microblog Memes
11052 readers
1477 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
I forget the details because it's been a long time now, but I once was pressured into fixing my dad's Windows computer. Note that, while it was long enough ago that I was still using Windows for gaming, at the time I used Linux for everything else both professional and personal.
Anyway, it took me a while, but eventually I discovered the issue was a little known conflict between Hyper-V and some driver that Windows update had applied. IIRC the solution was to revert the update and wait for the next one. Figuring this out involved borrowing his computer for a few days, which was awkward because though it was his personal computer he primarily used it for work. Fortunately his company and customers really liked him and gave him a lot of leeway.
To my dad's credit, he didn't blame me for subsequent issues ... But it seemed like any time after that when he complained about his computer to someone who knew both of us, they would suggest that it was probably my fault for fixing it that one time.