ALT GitHub comment thread: Hey guys, this issue is a critical one!😥 Facing it right now in the pytest-bdd==7.0.1 version as well! Wondering why it is not being tracked actively right now! 🤔 Tagging folks for reach: @youtux , @bubenkoff , @olegpidsadnyi @The-Compiler @amak @lrowe @Himawari995 @drothlis @hvdklauw @pelme @saxix --- [@lrowe] it would be helpful for me (and maybe others) if you could be specific about why you are mentioning us all here. Personally, I've not done much Python for a while. If there is some specific code or a bug report I've written or commented on that is relevant I can try and understand what this is about but otherwise I'm just confused why I'm included here. --- [@the-compiler] Please don't ping random people in open source projects. Maintainers usually do a lot of work in their free time, and what you're doing is a great way to either confuse people (see above); or annoy them and slowly burn people out. If someone wants to be notified about comments

ALT qutebrowser crash report email, empty other than the following text in the "contact" field: CANNOT VERIFY INTEGRITY OF RELEASED CODE = SECURITY ISSUE GPG ISSUE where your damn keys can't verify releases solution: stop masturbating to PGP and include sha256 keys with the releases if addicted to PGP at least make it so you don't have to go on a jungle expedition to attempt to somehow retrieve some key which is stored somewhere somewhere who knows where fuck pgp

ALT Screenshot of text: ========== Report ========== delete the crash reporting functionality from the software it's useless to begin with ========== Contact ========== delete the crash reporting functionality from the software it's useless to begin with

ALT screenshot of 6 qutebrowser crash report mails, sent by the same reporter in a timespan of 14 minutes

ALT screenshot of a crash report text: "opening a fucking website", with no contact information

ALT Github monologue: <reporter> commented 10 minutes ago Well, seeing as its quite a problem that even when you disable something, its left enabled (and can be accessed by some sites) that it should be fixed, no? <reporter> commented 4 minutes ago Alright well it seems like you're not willing to fix this issue. I'll be uninstalling QuteBrowser then, as I don't even want to imagine what other options which I set to False are still working, and accessible to sites. Have a good day. (me: thumbs-up reaction)

ALT GitHub conversation: The-Compiler closed this as not planned 5 hours ago <reporter> commented 5 hours ago Then how is CreepJS accessing that information? <reporter> commented 5 hours ago Adding disable-webgl to the c.qt.args in the config.py file doesn't work either <reporter> commented 8 minutes ago So that's it? No response? The-Compiler commented 4 minutes ago With that attitude, definitely not. Go take that somewhere else, or ideally, nowhere.

ALT screenshot of the two final comments here: https://github.com/The-Compiler/pytest-xvfb/issues/31