Self-hosting email is not at all easy, and I’d recommend paying for hosted email from a service that lets you use a custom domain. Most will let you have multiple inboxes, although this may cost extra.
Then, just buy a domain (NameCheap is fine) and point your MX records at the email provider.
Fair enough; I didn’t consider artifacts like logs and traces. I suppose a stale marker might prompt the original reporter to retest and supply fresh ones (or confirm it’s fixed in the dependency case).
In an ideal world I suppose we’d have automated tests for all bug reports but that’s obviously never going to happen!
It’s a very different kind of beast, but I’m very much enjoying it so far. Linking things is definitely Joplin’s weak point whereas this is a core strength for logseq.
I often used bullet points in my Joplin notes, so having that as the default works for me too. However, since Op has said they want plain text notes Obsidian seems like a better fit (although logseq does save pages as text it’s not what it feels like in use).
Huh, that’s weird: when I posted, I saw your your comment as a top-level comment but I now I see it as a reply. Maybe it’s a Lemmy bug; I’ll keep an eye out in future.
It is far too confusing what to use - even as someone who uses Linux on various servers, a media centre, WSL and used to run a Gentoo laptop I still don’t know which distro to use, let alone which of KDE/Gnome, X11/Wayland, init/systemd etc.