Krafting@lemmy.world to Microblog Memes@lemmy.worldEnglish · edit-23 months agoThese kinds of pictures...lemmy.worldexternal-linkmessage-square49fedilinkarrow-up11.16Karrow-down116file-text
arrow-up11.14Karrow-down1external-linkThese kinds of pictures...lemmy.worldKrafting@lemmy.world to Microblog Memes@lemmy.worldEnglish · edit-23 months agomessage-square49fedilinkfile-text
minus-squareZiglin@lemmy.worldlinkfedilinkEnglisharrow-up1·3 months agoProof of authenticity? I have gimp. Also why does your auto correct edit things you paste? If the important feedback from the terminal is out of view a screenshot still doesn’t help. The entire output piped into the clipboard is far more useful.
minus-squareCouldbealeotard@lemmy.worldlinkfedilinkEnglisharrow-up1·3 months agoAre 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.
minus-squareZiglin@lemmy.worldlinkfedilinkEnglisharrow-up1·3 months agoI 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…
Proof of authenticity? I have gimp.
Also why does your auto correct edit things you paste?
If the important feedback from the terminal is out of view a screenshot still doesn’t help. The entire output piped into the clipboard is far more useful.
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.
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…