How to Report Bugs
-
Bug Report Tips:
- Start off by swearing at the idiots who wrote this bug fest
- Never post a link to the site where the crash occurred. At most, give a cryptic clue — its more fun for the developers.
- Everyone uses Windows 10, so there is no need to tell anyone what OS you're using. If it is a bug that doesn't occur on Windows 10 then its not worth fixing.
- Don't bother to check your hard drive for malware or viruses. Only paranoid wimps use diagnostic system tools.
- Be brief. Don't tell anyone what you were doing at the time.
- When filing bugs, always send a crash report, but make sure its the wrong one. Don't give too much away at first.
- File at least two or three more bug reports with different details, just in case the first got lost in cyber-space
- Demand that it be fixed yesterday, and if it is not that you're going back to your previous program and won't ever use this one again
- Every time a new version comes out, download it just to see if your pet bug was fixed
-
Yes, it's easy to get frustrated by the seemingly endless stream of mo****** seemingly incapable of even basic troubleshooting on their own machine.
Looking at the amount of reports after a major release, you'd think Vivaldi was a bug-ridden mess. But for comparison, take a look at the Chrome support forum on any given day, it will put things into perspective. People just get into all kinds of trouble because they do... all kinds of "weird stuff" I guess.
Sometimes I wish there was an exam before people were let onto the internet, proving a basic knowledge of internet protocols and troubleshooting. But that's just me
* See, I'm not too polite to say it
modedit language!
-
-
Fair enough. But now it looks even ruder
-