Sigmoid Social

Inautilo<a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> <a href="https://mastodon.social/tags/Approaches" class="mention hashtag" rel="nofollow noopener" target="_blank">#Approaches</a> How I use GitHub issues · The joy of community-engaged issue handling <a href="https://ilo.im/165w3e" rel="nofollow noopener" translate="no" target="_blank">https://ilo.im/165w3e</a>_____ Programming <a href="https://mastodon.social/tags/BugReports" class="mention hashtag" rel="nofollow noopener" target="_blank">#BugReports</a> <a href="https://mastodon.social/tags/Discussion" class="mention hashtag" rel="nofollow noopener" target="_blank">#Discussion</a> <a href="https://mastodon.social/tags/Community" class="mention hashtag" rel="nofollow noopener" target="_blank">#Community</a> <a href="https://mastodon.social/tags/Workflow" class="mention hashtag" rel="nofollow noopener" target="_blank">#Workflow</a> <a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a> <a href="https://mastodon.social/tags/Backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Backend</a>

ResearchBuzz: FirehoseDaniel Stenberg: Death by a thousand slops. “The general trend so far in 2025 has been way more AI slop than ever before (about 20% of all submissions) as we have averaged in about two security report submissions per week. In early July, about 5% of the submissions in 2025 had turned out to be genuine vulnerabilities. The valid-rate has decreased significantly compared to previous years.”<a href="https://rbfirehose.com/2025/07/19/daniel-stenberg-death-by-a-thousand-slops/" class="" rel="nofollow noopener" target="_blank">https://rbfirehose.com/2025/07/19/daniel-stenberg-death-by-a-thousand-slops/</a>

Karl Voit :emacs: :orgmode:(1/2) It's very good to report <a href="https://graz.social/tags/bugs" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugs</a> in <a href="https://graz.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> projects. Services like <a href="https://graz.social/tags/github" class="mention hashtag" rel="nofollow noopener" target="_blank">#github</a>, <a href="https://graz.social/tags/gitlab" class="mention hashtag" rel="nofollow noopener" target="_blank">#gitlab</a>, <a href="https://graz.social/tags/codeberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#codeberg</a> and so forth makes it easy to do so without creating a new account for each report.My recommendations:- be polite - people are spending their spare time to help you- explain it thorough: exact steps to reproduce, difference between actual result and expected result, mention exact version numbers, surrounding environments with their versions, background stories (maybe in an extra section at the end), ...Fun fact: many(!) of my <a href="https://graz.social/tags/bugreports" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugreports</a> get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards....

ResearchBuzz: FirehoseArs Technica: Open source project curl is sick of users submitting “AI slop” vulnerabilities. “‘A threshold has been reached. We are effectively being DDoSed. If we could, we would charge them for this waste of our time,’ wrote Daniel Stenberg, original author and lead of the curl project, on LinkedIn this week.”<a href="https://rbfirehose.com/2025/05/10/ars-technica-open-source-project-curl-is-sick-of-users-submitting-ai-slop-vulnerabilities/" class="" rel="nofollow noopener" target="_blank">https://rbfirehose.com/2025/05/10/ars-technica-open-source-project-curl-is-sick-of-users-submitting-ai-slop-vulnerabilities/</a>

Kevin Dominik KorteAI Slop is increasingly blocking open-source developers from doing critical work. If you hunt for bugs, please do so yourself and do not let AI hallucinate them into being for you. <a href="https://fosstodon.org/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <a href="https://fosstodon.org/tags/bugreports" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugreports</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://arstechnica.com/gadgets/2025/05/open-source-project-curl-is-sick-of-users-submitting-ai-slop-vulnerabilities/" rel="nofollow noopener" translate="no" target="_blank">https://arstechnica.com/gadgets/2025/05/open-source-project-curl-is-sick-of-users-submitting-ai-slop-vulnerabilities/</a>

Ars Technica NewsOpen source project curl is sick of users submitting “AI slop” vulnerabilities <a href="https://arstechni.ca/LAhpm" rel="nofollow noopener" translate="no" target="_blank">https://arstechni.ca/LAhpm</a> <a href="https://c.im/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerabilities</a> <a href="https://c.im/tags/bugreports" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugreports</a> <a href="https://c.im/tags/hackerone" class="mention hashtag" rel="nofollow noopener" target="_blank">#hackerone</a> <a href="https://c.im/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://c.im/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://c.im/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> <a href="https://c.im/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>

FinchHaven sfba<a href="https://indieweb.social/@clhenrick" class="u-url mention" rel="nofollow noopener" target="_blank">@clhenrick</a> "Anyone know where to submit a bug report for the official Mastodon iOS app?"That would be here:Github, Mastodon, mastodon-ios IssuesYou'll need your own login, I do believeHere: <a href="https://github.com/mastodon/mastodon-ios/issues" rel="nofollow noopener" translate="no" target="_blank">https://github.com/mastodon/mastodon-ios/issues</a><a href="https://sfba.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> <a href="https://sfba.social/tags/iOSapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOSapp</a> <a href="https://sfba.social/tags/BugReports" class="mention hashtag" rel="nofollow noopener" target="_blank">#BugReports</a>

ResearchBuzz: FirehoseTom’s Hardware: Alleged 7-Zip arbitrary code execution exploit leaked to Twitter — the 7-Zip author claims this exploit not only isn’t real but was generated by AI . “Yesterday, user @NSA_Employee39 allegedly posted a zero-day exploit for the popular open-source file decompression utility 7-Zip on Twitter, only to have 7-Zip author Igor Pavlov swiftly dismiss it as a fake report. Other […]<a href="https://rbfirehose.com/2025/01/02/toms-hardware-alleged-7-zip-arbitrary-code-execution-exploit-leaked-to-twitter-the-7-zip-author-claims-this-exploit-not-only-isnt-real-but-was-generated-by-ai/" class="" rel="nofollow noopener" target="_blank">https://rbfirehose.com/2025/01/02/toms-hardware-alleged-7-zip-arbitrary-code-execution-exploit-leaked-to-twitter-the-7-zip-author-claims-this-exploit-not-only-isnt-real-but-was-generated-by-ai/</a>

Benjamin Carr, Ph.D. 👨🏻‍💻🧬<a href="https://hachyderm.io/tags/Opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#Opensource</a> <a href="https://hachyderm.io/tags/maintainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#maintainers</a> are drowning in junk <a href="https://hachyderm.io/tags/bugreports" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugreports</a> written by <a href="https://hachyderm.io/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <a href="https://hachyderm.io/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://hachyderm.io/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://hachyderm.io/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer</a>-in-residence decries use of bots that 'cannot understand code' <a href="https://www.theregister.com/2024/12/10/ai_slop_bug_reports/" rel="nofollow noopener" translate="no" target="_blank">https://www.theregister.com/2024/12/10/ai_slop_bug_reports/</a> <a href="https://hachyderm.io/tags/slop" class="mention hashtag" rel="nofollow noopener" target="_blank">#slop</a> <a href="https://hachyderm.io/tags/AISlop" class="mention hashtag" rel="nofollow noopener" target="_blank">#AISlop</a>

Werner KeilBis zum <a href="https://mastodon.social/tags/Burnout" class="mention hashtag" rel="nofollow noopener" target="_blank">#Burnout</a>: <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>-Entwickler von <a href="https://mastodon.social/tags/KI" class="mention hashtag" rel="nofollow noopener" target="_blank">#KI</a>-<a href="https://mastodon.social/tags/BugReports" class="mention hashtag" rel="nofollow noopener" target="_blank">#BugReports</a> genervt | heise online <a href="https://www.heise.de/news/Bis-zum-Burn-out-Open-Source-Entwickler-von-KI-Bug-Reports-genervt-10195951.html" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/news/Bis-zum-Burn-out-Open-Source-Entwickler-von-KI-Bug-Reports-genervt-10195951.html</a>

VitexSupport <a href="https://f.cz/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> by filling <a href="https://f.cz/tags/bugreports" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugreports</a>!

Kevin Karhan :verified:<a href="https://awscommunity.social/@Quinnypig" class="u-url mention" rel="nofollow noopener" target="_blank">@Quinnypig</a> you quote a reply to <a href="https://infosec.space/tags/Canonical" class="mention hashtag" rel="nofollow noopener" target="_blank">#Canonical</a> <a href="https://infosec.space/tags/BugReports" class="mention hashtag" rel="nofollow noopener" target="_blank">#BugReports</a>?

Henryk PlötzMany, many years ago, this was with Bugzilla in the early 2000s, I got my first automated lecture on what constitutes a good bug report. I probably didn’t pay attention. Since then, I’ve seen this list countless times, in various levels of detail, across a broad array of systems:<ul><li>What did you do?</li><li>What happened?</li><li>What did you expect to happen?</li></ul>Over the last few years I’ve come to realize that this list is irreducible, if you’re losing one item you lose important context, and represents a kind of deep wisdom:<ol><li>What Did You Do? — If we cannot see the steps that brought you into the situation, it’ll be hard to find the place in the program where it happens. It’ll also set up our mental model of the program in question to see what we think should happen. Preferably this should be detailed and reliable enough to reproduce the problem on our side. Things that cannot be reliably reproduced are very hard to fix, because you’ll never truly know if they’re gone.</li><li>What happened? — This gives context on what happened for you, which might be different for us, indicating some other issue. In some cases this is what we thought should happen, so this also gives a clear statement to set up the next point.</li><li>What did you expect to happen? — Stating how your expectation differs from reality is what makes this a bug. You’re not reporting issues where the system does what you expected it should do. But this expectation might differ from what we were expecting. The issue need not be in the code or the implementation, but might be somewhere else. Maybe the documentation gave you a wrong idea on what should happen?</li></ol>Sometimes a bug report can be succinct but still contain all three items: “I clicked on save. It did not save. I expected it to save.” Though in this case the first part really should be longer, because this is probably something that only happens under certain circumstances. And even if part 3 is only “I expected it to work”, that’s good to write out.Bug reports consisting of a single screenshot, for example of an error message, are often not helpful. They, more or less, cover part 2, but leave out important context. It may not be obvious from the screenshot on how to get there. And it’s as likely as not that we think that this is the expected behavior. You should state why you think this error message is, as it were, in error.The three parts of a good bug report are interlocking. Like describing the way to the train station to a stranger. You’re not going to describe it as “Turn left second street, go right first street, go right third street.” You’re giving context: “Go down this street and turn left at the second intersection, right behind the flower shop. You should see the church in front of you, turn immediately right and go into the small alley. If you then turn right at the third street you should see the train station in the distance.”This is redundant. But redundancy is good. It allows for error checking and correction. It allows for there to be errors in both the environment and in its mental model or description thereof.So, repeat after me: What did you do? What happened? What did you expect to happen?<a href="https://blog.ploetzli.ch/2024/making-good-bug-reports/" class="" rel="nofollow noopener" target="_blank">https://blog.ploetzli.ch/2024/making-good-bug-reports/</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.ploetzli.ch/tag/bug-reports/" target="_blank">#bugReports</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://blog.ploetzli.ch/tag/bugs/" target="_blank">#bugs</a>

Axel RafnI can't believe it took me this long, but apparently, I'm just lucky in regards to bugs in software. I just reported my first ever bug to the <a href="https://hachyderm.io/tags/KDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDE</a> team. Woke up to about 15-20 Dr Konqi windows after Plasma Shell crashed repeatedly during the night. Most of the windows were non-responsive but the last one was usable, even though it soft-froze a few times while I was entering the data.<a href="https://hachyderm.io/tags/BugReports" class="mention hashtag" rel="nofollow noopener" target="_blank">#BugReports</a> <a href="https://hachyderm.io/tags/DoYourPart" class="mention hashtag" rel="nofollow noopener" target="_blank">#DoYourPart</a>

KDEHappy Holidays everyone! And thanks for all the bugs🪲🪲🎄!Seriously: Hurrah for team bug testers! The bug <a href="https://floss.social/tags/reports" class="mention hashtag" rel="nofollow noopener" target="_blank">#reports</a> you are sending in are great! <a href="https://floss.social/tags/Tests" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tests</a> are thorough and insightful, and your contributions will help make <a href="https://floss.social/tags/Plasma6" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plasma6</a>, when it arrives in February, so much better.Thank you for your time, have a great holiday, and keep the <a href="https://floss.social/tags/bugreports" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugreports</a> coming!<a href="https://bugs.kde.org" rel="nofollow noopener" translate="no" target="_blank">https://bugs.kde.org</a><a href="https://lemmy.kde.social/c/kde" class="u-url mention" rel="nofollow noopener" target="_blank">@kde@lemmy.kde.social</a>

DisTo clarify a bit, the reason I don't argue with <a href="https://techhub.social/tags/stalebot" class="mention hashtag" rel="nofollow noopener" target="_blank">#stalebot</a> more than once is simple: Filing a good bug report is hard work. (I'm not referring to feature requests, although those can be hard work too.)A project that uses <a href="https://techhub.social/tags/stalebot" class="mention hashtag" rel="nofollow noopener" target="_blank">#stalebot</a> invariably accumulates tons of valid but closed bugs. A few of them will get accidentally fixed, but most remain real and get lost. (A closed bug looks fixed, so users tend to open a new one.) This feeds the "need" for stalebot because "omg too many bugs!" even though they are just noise generated by stalebot to begin with.Back to <a href="https://techhub.social/tags/esphome" class="mention hashtag" rel="nofollow noopener" target="_blank">#esphome</a>: Why should I spend at least 30 mins searching their junk pile, plus at least an hour of gathering logs, experimenting, etc?The humans involved will never look at it, and eventually their robotic receptionist will tell me to go away. I refuse to put more effort into this than they do.<a href="https://techhub.social/tags/esphome" class="mention hashtag" rel="nofollow noopener" target="_blank">#esphome</a> <a href="https://techhub.social/tags/github" class="mention hashtag" rel="nofollow noopener" target="_blank">#github</a> <a href="https://techhub.social/tags/stalebot" class="mention hashtag" rel="nofollow noopener" target="_blank">#stalebot</a> <a href="https://techhub.social/tags/homeassistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#homeassistant</a> <a href="https://techhub.social/tags/bugs" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugs</a> <a href="https://techhub.social/tags/bugreports" class="mention hashtag" rel="nofollow noopener" target="_blank">#bugreports</a> <a href="https://techhub.social/tags/snr" class="mention hashtag" rel="nofollow noopener" target="_blank">#snr</a> <a href="https://techhub.social/tags/qa" class="mention hashtag" rel="nofollow noopener" target="_blank">#qa</a>

Recent searches

Search options

Administered by:

Server stats:

#bugreports