Agreed, though i do think it’s a privacy thing. Many people use privacy and anonymity interchangeably but they are different things.

The options are:

• use a single email. If it is leaked you need to update hundreds of accounts or risk falling for a malicious email
• use a catch-all email and each service gets a separate email, but you can’t turn off receiving mail at a specific address unless you use a sieve filter. This doesn’t stop people from just guessing random addresses.
• use specific aliases for each service. Idk about this specific project but usually you can turn off receiving mail at an alias. So if a company gets a data breach i just change my email (or close the acct), then i turn off the old alias.

I did the catchall for a few years but have been doing aliases for 5+ now. In the end, the only people/ companies who have my email are the ones I want.

Even has kitty timestamps further down 😻

Just some general advice:

• get regular users. Contributors are going to be a subset of users as another commentor mentioned.
• make sure to have a CONTRIBUTING.md and that it is clear/ easy to follow. Some projects will link to a separate wiki from the .md which is fine. But make sure your “first time contributor” instructions are easy to follow to set up whatever dev environment needed. The less clear the documentation then the more motivated the contributors will need to be.
• if you haven’t already, make issues with feature requests that you are wanting to add. Include enough details that someone other than you will understand your requirements.
• consider a label you use to signify “great issue for a first time contribution”. These should be relatively simple fixes or simple features but give time for someone else to try them instead of completing it right away. Make sure to reference this label in your contribution documentation as a great starting point. If you’re able to get someone to do a simple fix then they will have set up the dev environment and may do other future issues.
• advertise that you’re looking for contributors. Point out your docs, first time contributor label, and any specific features you want/need help with.

So you dislike external sync options but also don’t want to pay for internal sync options? Additionally you are in a self hosted community so you’re looking for a presumably open source project (some you listed are not), and given internally supported sync services would be one way fund development i think this narrows what your are looking for by quite a bit. You basically would be looking for an open source project that meets all your other criteria and happens to let you sync the files to your own server for free. Why would such a project not just let you take things into your own hands with whatever flavor of sync/backup you prefer? Otherwise if they’re building a sync system it would probably be a monetized cloud service which brings us back to the beginning.

Maybe such a thing exists, but I haven’t seen such a thing since that is extra development for little to no gain. Most people are happy to either pay for the cloud service to fund development or sync on their own.

Logseq: Same issues as with obsidian: Paid sync. Didnt look much beyond

Logseq is open source. Obsidian is not. So yes, both have paid sync but you can also just sync or backup the files on your own. Just be careful of sync services that sync while files/db are in use to avoid conflicts.