I switched from Tiddlywiki to Logseq 3-4 months ago and LOVE Logseq.
Part of the reason I didn’t like Tiddlywiki was it kept everything in a single html file (including embedded images – eww) which made it annoying to move information around. (Note there is an option to run your own server which gives you extra flexibility, but I wasn’t interested in doing that.)
With Logseq, it’s separate markdown file per journal entry / wiki page. I like the addons that are available as well as the queries, e.g., {{query (todo doing)}} displays my do now tasks on my journal page.
Here’s a Beginner’s Guide on how to use LogSeq: YouTube video by Keep Productive
Better to create your own instance then.
It’s about reducing risk not eradicating it and there’s a huge difference in risk in being targeted for legal action due to hosting c/piracy (via caching/mirroring) than from a single piracy post in c/hellokitty.