Microblog Memes

5708 readers

3792 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:

Please put at least one word relevant to the post in the post title.
Be nice.
No advertising, brand promotion or guerilla marketing.
Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 1 year ago

MODERATORS

1142

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

51 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 months ago (1 children)

Are you seriously suggesting photo manipulation is a risk factor for sending and receiving software crash reports?

Manually typing or copy/pasting is vulnerable to typos, auto correct, formatting issues

If the important information is out of view of the screenshot, that's a skill issue that exists above the method of communication.

[–] [email protected] 1 points 2 months ago

I don't think there's a reason for anyone to fake crash reports. But an image still doesn't prove anything.

How is ctrl+shift+c, ctrl+shift+v vulnerable to those? (Or do you mean typing it by hand? That sounds really inefficient).

Almost all crash reports are multiple pages long, I wouldn't call missing relevant information a skill issue.

I'm starting to wonder if we use vastly different setups…