home.social

#bugreports — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bugreports, aggregated by home.social.

fetched live
  1. 📰 Look out, world! #NetBSD 11.0 has arrived with all the fanfare of a wet noodle, charming us with its legendary "ISO images" and making sure to remind us how exciting mailing lists can be. 😂 But fear not, dear reader, for your bug reports shall have a loving home on the never-ending CVS repository! 🐌💾
    blog.netbsd.org/tnf/entry/netb #NetBSD11 #ISOImages #BugReports #CVSRepository #MailingLists #HackerNews #ngated

  2. 📰 Look out, world! #NetBSD 11.0 has arrived with all the fanfare of a wet noodle, charming us with its legendary "ISO images" and making sure to remind us how exciting mailing lists can be. 😂 But fear not, dear reader, for your bug reports shall have a loving home on the never-ending CVS repository! 🐌💾
    blog.netbsd.org/tnf/entry/netb #NetBSD11 #ISOImages #BugReports #CVSRepository #MailingLists #HackerNews #ngated

  3. 📰 Look out, world! #NetBSD 11.0 has arrived with all the fanfare of a wet noodle, charming us with its legendary "ISO images" and making sure to remind us how exciting mailing lists can be. 😂 But fear not, dear reader, for your bug reports shall have a loving home on the never-ending CVS repository! 🐌💾
    blog.netbsd.org/tnf/entry/netb #NetBSD11 #ISOImages #BugReports #CVSRepository #MailingLists #HackerNews #ngated

  4. 📰 Look out, world! #NetBSD 11.0 has arrived with all the fanfare of a wet noodle, charming us with its legendary "ISO images" and making sure to remind us how exciting mailing lists can be. 😂 But fear not, dear reader, for your bug reports shall have a loving home on the never-ending CVS repository! 🐌💾
    blog.netbsd.org/tnf/entry/netb #NetBSD11 #ISOImages #BugReports #CVSRepository #MailingLists #HackerNews #ngated

  5. 📰 Look out, world! #NetBSD 11.0 has arrived with all the fanfare of a wet noodle, charming us with its legendary "ISO images" and making sure to remind us how exciting mailing lists can be. 😂 But fear not, dear reader, for your bug reports shall have a loving home on the never-ending CVS repository! 🐌💾
    blog.netbsd.org/tnf/entry/netb #NetBSD11 #ISOImages #BugReports #CVSRepository #MailingLists #HackerNews #ngated

  6. We’ve been doing broad strokes on ForkMesh: getting the core pieces working, moving fast, and shaping the foundation.

    Now we’re ready for fine tuning — and we need feedback from real users.

    Test it, break it, tell us what feels confusing, missing, or exciting.

    forkmesh.com

    #ForkMesh #BuildInPublic #OpenSource #FOSS #Git #GitHosting #DistributedGit #LocalFirst #DevTools #IndieDev #Testing #BugReports #UIUX #UX #Feedback #Fediverse

  7. We’ve been doing broad strokes on ForkMesh: getting the core pieces working, moving fast, and shaping the foundation.

    Now we’re ready for fine tuning — and we need feedback from real users.

    Test it, break it, tell us what feels confusing, missing, or exciting.

    forkmesh.com

    #ForkMesh #BuildInPublic #OpenSource #FOSS #Git #GitHosting #DistributedGit #LocalFirst #DevTools #IndieDev #Testing #BugReports #UIUX #UX #Feedback #Fediverse

  8. We’ve been doing broad strokes on ForkMesh: getting the core pieces working, moving fast, and shaping the foundation.

    Now we’re ready for fine tuning — and we need feedback from real users.

    Test it, break it, tell us what feels confusing, missing, or exciting.

    forkmesh.com

    #ForkMesh #BuildInPublic #OpenSource #FOSS #Git #GitHosting #DistributedGit #LocalFirst #DevTools #IndieDev #Testing #BugReports #UIUX #UX #Feedback #Fediverse

  9. We’ve been doing broad strokes on ForkMesh: getting the core pieces working, moving fast, and shaping the foundation.

    Now we’re ready for fine tuning — and we need feedback from real users.

    Test it, break it, tell us what feels confusing, missing, or exciting.

    forkmesh.com

    #ForkMesh #BuildInPublic #OpenSource #FOSS #Git #GitHosting #DistributedGit #LocalFirst #DevTools #IndieDev #Testing #BugReports #UIUX #UX #Feedback #Fediverse

  10. Small but meaningful update: our main repo has moved from `newnewnode/forkmesh` to `forkmesh/forkmesh`, and we reinstalled our mirrors. It feels cleaner, more official, and more like home.

    ForkMesh is moving fast, and we’d love more people involved. We need testers, bug reporters, and UI/UX feedback.

    Join the mesh: forkmesh.com

    #ForkMesh #BuildInPublic #OpenSource #FOSS #Git #GitHosting #DistributedGit #LocalFirst #DevTools #IndieDev #SelfHosting #UX #UIUX #Testing #BugReports #Fediverse

  11. A: Našel jsem jehlu v kupce sena!
    B: Aha a kde ji máš?
    A: No hodil jsem jí zpátky, ale je tam, oprav to.

    #bugreports

  12. A: Našel jsem jehlu v kupce sena!
    B: Aha a kde ji máš?
    A: No hodil jsem jí zpátky, ale je tam, oprav to.

    #bugreports

  13. A: Našel jsem jehlu v kupce sena!
    B: Aha a kde ji máš?
    A: No hodil jsem jí zpátky, ale je tam, oprav to.

    #bugreports

  14. A: Našel jsem jehlu v kupce sena!
    B: Aha a kde ji máš?
    A: No hodil jsem jí zpátky, ale je tam, oprav to.

    #bugreports

  15. A: Našel jsem jehlu v kupce sena!
    B: Aha a kde ji máš?
    A: No hodil jsem jí zpátky, ale je tam, oprav to.

    #bugreports

  16. OBS Studio is finally catching up to 2015 technology by adopting Apple's Metal, because who needs backward compatibility or stable performance? 😂 Meanwhile, users can enjoy the thrill of "experimental" features—cue the endless forum threads of bug reports and existential crises. 🚀🔧 #InnovationOrRegression?
    obsproject.com/blog/obs-studio #OBSStudio #MetalCompatibility #ExperimentalFeatures #TechHumor #BugReports #HackerNews #ngated

  17. OBS Studio is finally catching up to 2015 technology by adopting Apple's Metal, because who needs backward compatibility or stable performance? 😂 Meanwhile, users can enjoy the thrill of "experimental" features—cue the endless forum threads of bug reports and existential crises. 🚀🔧 #InnovationOrRegression?
    obsproject.com/blog/obs-studio #OBSStudio #MetalCompatibility #ExperimentalFeatures #TechHumor #BugReports #HackerNews #ngated

  18. OBS Studio is finally catching up to 2015 technology by adopting Apple's Metal, because who needs backward compatibility or stable performance? 😂 Meanwhile, users can enjoy the thrill of "experimental" features—cue the endless forum threads of bug reports and existential crises. 🚀🔧 #InnovationOrRegression?
    obsproject.com/blog/obs-studio #OBSStudio #MetalCompatibility #ExperimentalFeatures #TechHumor #BugReports #HackerNews #ngated

  19. OBS Studio is finally catching up to 2015 technology by adopting Apple's Metal, because who needs backward compatibility or stable performance? 😂 Meanwhile, users can enjoy the thrill of "experimental" features—cue the endless forum threads of bug reports and existential crises. 🚀🔧 #InnovationOrRegression?
    obsproject.com/blog/obs-studio #OBSStudio #MetalCompatibility #ExperimentalFeatures #TechHumor #BugReports #HackerNews #ngated

  20. Daniel 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.”

    https://rbfirehose.com/2025/07/19/daniel-stenberg-death-by-a-thousand-slops/

  21. Daniel 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.”

    https://rbfirehose.com/2025/07/19/daniel-stenberg-death-by-a-thousand-slops/

  22. (1/2) It's very good to report #bugs in #FOSS projects. Services like #github, #gitlab, #codeberg 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 #bugreports get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards.

    ...

  23. (1/2) It's very good to report #bugs in #FOSS projects. Services like #github, #gitlab, #codeberg 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 #bugreports get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards.

    ...

  24. (1/2) It's very good to report #bugs in #FOSS projects. Services like #github, #gitlab, #codeberg 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 #bugreports get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards.

    ...

  25. (1/2) It's very good to report #bugs in #FOSS projects. Services like #github, #gitlab, #codeberg 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 #bugreports get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards.

    ...

  26. (1/2) It's very good to report #bugs in #FOSS projects. Services like #github, #gitlab, #codeberg 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 #bugreports get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards.

    ...

  27. Ah, the eternal struggle of transforming core dumps into a never-ending flow of #CVEs 😱. LWN.net bravely tackles this "urgent" issue with their subscriber-only content because nothing screams #exclusivity like bug reports 🤦‍♂️. Remember, dear reader, subscribing might just be the key to unlocking the secrets of dump management! 💼✨
    lwn.net/SubscriberLink/1024160 #coreDumps #LWNnet #bugReports #subscriberContent #HackerNews #ngated

  28. Ah, the eternal struggle of transforming core dumps into a never-ending flow of #CVEs 😱. LWN.net bravely tackles this "urgent" issue with their subscriber-only content because nothing screams #exclusivity like bug reports 🤦‍♂️. Remember, dear reader, subscribing might just be the key to unlocking the secrets of dump management! 💼✨
    lwn.net/SubscriberLink/1024160 #coreDumps #LWNnet #bugReports #subscriberContent #HackerNews #ngated

  29. Ah, the eternal struggle of transforming core dumps into a never-ending flow of #CVEs 😱. LWN.net bravely tackles this "urgent" issue with their subscriber-only content because nothing screams #exclusivity like bug reports 🤦‍♂️. Remember, dear reader, subscribing might just be the key to unlocking the secrets of dump management! 💼✨
    lwn.net/SubscriberLink/1024160 #coreDumps #LWNnet #bugReports #subscriberContent #HackerNews #ngated

  30. Ah, the eternal struggle of transforming core dumps into a never-ending flow of #CVEs 😱. LWN.net bravely tackles this "urgent" issue with their subscriber-only content because nothing screams #exclusivity like bug reports 🤦‍♂️. Remember, dear reader, subscribing might just be the key to unlocking the secrets of dump management! 💼✨
    lwn.net/SubscriberLink/1024160 #coreDumps #LWNnet #bugReports #subscriberContent #HackerNews #ngated

  31. Ars 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.”

    https://rbfirehose.com/2025/05/10/ars-technica-open-source-project-curl-is-sick-of-users-submitting-ai-slop-vulnerabilities/

  32. Ars 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.”

    https://rbfirehose.com/2025/05/10/ars-technica-open-source-project-curl-is-sick-of-users-submitting-ai-slop-vulnerabilities/

  33. AI 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.
    #AI #bugreports #opensource
    arstechnica.com/gadgets/2025/0

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

    arstechnica.com/gadgets/2025/0

  35. AI 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.
    #AI #bugreports #opensource
    arstechnica.com/gadgets/2025/0

  36. AI 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.
    #AI #bugreports #opensource
    arstechnica.com/gadgets/2025/0

  37. AI 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.
    #AI #bugreports #opensource
    arstechnica.com/gadgets/2025/0

  38. "It doesn't work for me." 😤

    That's the report I get 90% of the time. No steps, no context, just frustration. After years of pulling my hair out trying to debug from breadcrumbs, I've documented & packaged my solution for you.

    Learn how to actually KNOW what went wrong: 👇
    fline.dev/better-error-reporti

    #iOSDev #BugReports #SwiftUI #Feedback

  39. "It doesn't work for me." 😤

    That's the report I get 90% of the time. No steps, no context, just frustration. After years of pulling my hair out trying to debug from breadcrumbs, I've documented & packaged my solution for you.

    Learn how to actually KNOW what went wrong: 👇
    fline.dev/better-error-reporti

    #iOSDev #BugReports #SwiftUI #Feedback

  40. "It doesn't work for me." 😤

    That's the report I get 90% of the time. No steps, no context, just frustration. After years of pulling my hair out trying to debug from breadcrumbs, I've documented & packaged my solution for you.

    Learn how to actually KNOW what went wrong: 👇
    fline.dev/better-error-reporti

    #iOSDev #BugReports #SwiftUI #Feedback

  41. "It doesn't work for me." 😤

    That's the report I get 90% of the time. No steps, no context, just frustration. After years of pulling my hair out trying to debug from breadcrumbs, I've documented & packaged my solution for you.

    Learn how to actually KNOW what went wrong: 👇
    fline.dev/better-error-reporti

    #iOSDev #BugReports #SwiftUI #Feedback

  42. "It doesn't work for me." 😤

    That's the report I get 90% of the time. No steps, no context, just frustration. After years of pulling my hair out trying to debug from breadcrumbs, I've documented & packaged my solution for you.

    Learn how to actually KNOW what went wrong: 👇
    fline.dev/better-error-reporti

    #iOSDev #BugReports #SwiftUI #Feedback