Shakedown Social

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....

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>

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>?

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>

Jon Collins 👨🏻‍💻Heads up devs. Got alerted to a nasty little issue on iOS where a firebase auth of signInWithRedirect is no longer returning a user object. It's broken several of my apps - was able to fix with a signInWithPopup instead but this is FAR from ideal. Might want to go through and check any Firebase SSO apps you might have for user issues and friction. Here's the github thread: <a href="https://github.com/firebase/firebase-js-sdk/issues/6716" rel="nofollow noopener" target="_blank">https://github.com/firebase/firebase-js-sdk/issues/6716</a><a href="https://hachyderm.io/tags/Firebase" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firebase</a> <a href="https://hachyderm.io/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a> <a href="https://hachyderm.io/tags/BugReports" class="mention hashtag" rel="nofollow noopener" target="_blank">#BugReports</a> <a href="https://hachyderm.io/tags/SSO" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSO</a>

Recent searches

Search options

Administered by:

Server stats:

#bugreports