Login
You're viewing the adforward.org public feed.
  • Nov 8, 2026, 2:39 PM

    The ability to report a Paperback issue to me directly from within the app, no GitHub account required, is coming to Paperback 1.2, and is already in dev builds! Just go to the help menu, hit report a problem, type what happened, optionally give your email, decide whether you want logs included or not, hit send, and it shows up in my inbox. It also automagically asks you if you want to send logs when a crash happens, with the ability to turn that off, of course.

    Also, because I'm me, the tools Claude and I wrote for this are open source. There are three crates: one to handle the mail format and sending, one that's the little server that handles the POST requests, and one that's the wxDragon-based problem report dialog. MIT licensed, and on crates.io already. The server can be grabbed with a simple cargo install, or ran like I'm doing it, with podman. github.com/accessware/mailbag #rust #rustlang #wxdragon

    💬 7🔄 9⭐ 5

Replies

  • 💬 1🔄 0⭐ 0
  • Nov 8, 2026, 3:53 PM

    @FreakyFwoof @TheQuinbox I asked claude about setting up something like that, and it didn't offer anything like this I need to eventually figure out how to do this. I know the tool is here, but I wouldn't know the first thing about putting that in my app, but I could attempt to maybe figure it out.

    💬 0🔄 0⭐ 0
  • Nov 8, 2026, 4:11 PM

    @JamminJerry It's not horribly complex. If your app uses wxDragon, start with the "Adding the dialog to a wxDragon app" section of the README. There's a copy-paste example for wiring up Help -> Report a Problem. All you really need for that part is your app name, version, and the URL to send reports to. The other half is mailbag-server. It can be ran as a standard binary or put in podman. You run it somewhere with an SMTP account and tell it which address to deliver reports to. That's where the mail password lives, in my case a gmail app password. Your app just POSTs the report to the URL you gave it. If you're using a different GUI toolkit, you can still use the same server. You'd make your own dialog and use the mailbag crate to build and send the report. Outside of Rust is a bit trickier, but I'm sure the server is reusable and the rest can be adapted. @FreakyFwoof

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 8, 2026, 4:31 PM

    @ysotomayor Honestly, given how many issues get opened against that repo every day, I wheep for whoever's inbox they choose for that.

    💬 2🔄 0⭐ 0
  • Nov 8, 2026, 4:40 PM

    @TheQuinbox I was mostly kidding. But they do need to find a way to make submitting issues much easier for none technical consumers. Not an easy problem to solve I'm sure.

    💬 0🔄 0⭐ 0
  • Nov 8, 2026, 5:01 PM

    @TheQuinbox @ysotomayor I am really sorry I have to say this, but they have been extremely unserious about internationalization for many, many years. As hard as that would be to implement, it would be a much better eror-reporting flow for the non-English-speaking non-Github folk.

    💬 0🔄 0⭐ 0
  • Nov 8, 2026, 6:28 PM

    @TheQuinbox Thank you for this. This is one of my biggest gripes about people who do open source applications: filing a bug is an always the most convenient for people or the most easy for people who are less tech savvy. Believe me, as a IT professional, I work with many, many blind and visually impaired people with all sorts of skill sets, sometimes people just really need something simple that they can fill out and send to you, so this is going to help a lot of people

    💬 0🔄 1⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 8, 2026, 11:17 PM

    @jscholes By strictly enforcing sending from the app, and also rate limits. Not flawless, but haven't gotten spam yet.

    💬 0🔄 0⭐ 0