Contact GritsConference

A note before you write. GritsConference is a one-person project, so I can help with things directly related to the site: a broken download link, a question about an install note I wrote, trouble with your favourites list, or a comment that still hasn’t appeared after a couple of days. I can’t help with licences, serial numbers, lost accounts for third‑party apps, or anything that needs a fix inside the software itself. For those, please reach out to the developer who makes it.

What to put in your message

The more context you give me, the sooner I can give you a useful answer. A good email mentions three things: the program name exactly as it appears on its GritsConference page, the version number listed on that page, and the details of the Mac you’re running it on. For the Mac, I need the macOS version and whether the machine uses Apple silicon (M1, M2, M3, or their Pro and Max siblings) or an Intel processor. You can find that under About This Mac from the Apple menu; the chip line will just say “Chip” on an Apple‑silicon Mac, or list a processor name that mentions Intel. If the question is about an older build I still list, tell me which build you downloaded. An example of the sort of note that saves a round of back‑and‑forth:

“I’m looking at SoundSaga (v3.1.2 on your page) on a MacBook Air with macOS 14.2 and an M2 chip. After I follow your install note about right‑clicking the installer, it quits silently. Is there a workaround?”

That gives me a clear starting point. You don’t need to write a formal letter—just a short, specific note works.

When to expect an answer

I read everything that comes to [email protected], but I answer messages in batches around my day job and family. Most people get a reply within a couple of days. If a weekend or a holiday falls in the middle, it might stretch a little longer. I don’t promise a set turnaround, because I’d rather answer slowly and well than dash off something vague. If you’ve waited a week and haven’t seen a reply, check your spam folder first—sometimes straightforward, link‑free messages land there mysteriously—and then send a polite nudge. The nudge itself helps, because it tells me the first one got buried.

The same inbox handles everything else, too: reader corrections, tips about a version bump I haven’t caught yet, and suggestions for software to add. I’m most likely to add a program if it clearly fits the weekend‑creator angle and runs on a Mac that’s still in active use around my part of Atlanta. There’s no editorial board behind the scenes, just me trying to keep the catalogue useful for people who make things on Saturday mornings and Sunday afternoons. If you’re one of them, I’m glad you’re here.