Hi guys! I think I’m over Joplin. Don’t get me wrong, it’s simple, it works, but… why is it Postgres db…. I have the server on a small box with like 250 GB of space and backing it up with kopia to Backblaze with free 10 GB, so I’m a bit storage cautious.

With each snapshot, it seems like a good chunk of the database changes, even when I don’t use Joplin that day. That results in kopia backing up those changed files, and backups keep growing. Right now the Joplin database is like 200Mb, BUT when I export the notes from the app… all of them weigh 2Mb… including images. Yes there is versioning of notes, but they shouldn’t be that big after one-two months lol.

I know I know, I’m being a bit weird about it, but I’m getting daily notifications about backups and I see how they grow each day.

Anyway, do you have any alternatives that have an app on iOS and on Linux? Or should I just use Apple Notes in the browser? Thanks

EDIT: The answer was easier than I thought. Just don’t back it up, it’s synced which means each device has a copy of it anyway so there is not really need for it, thanks @[email protected] !

    • Footnote2669@lemmy.zipOPEnglish
      2·
      11 months ago

      I find their paradigm… different and not entirely sure if I like it yet, need to look into it more :)

      • fossphi@lemm.ee
        English
        1·
        11 months ago

        Do you mind expanding a bit on how you use joplin? I’m curious about the difference you found compared to logseq

        • Footnote2669@lemmy.zipOPEnglish
          2·
          11 months ago

          I use it just as a simple as possible, instructions on how I setup backups, important thing about container’s config, etc etc. I find it easier to just have a folder “Server” and put each container in a separate note or folder. It’s too much thinking about tags, links, pages and all in logseq, notes seem all over the place.

          • SayCyberOnceMore@feddit.ukEnglish
            2·
            11 months ago

            Yep, now, I initially found the daily journal approach a bit strange, but I use this for work as much as personal stuff, so it actually helps…

            My suggestion to your usecase would be to keep a page per “thing” ie server / container / etc and then when you make a change you can just say (on that day’s journal page):

            ‘’ Setup a backup for [[Server X]] and it’s going to [[NAS2]] (for example) ‘’

            Then, on either of those 2 pages you’ll automatically see the link back to the journal page, so you’ll know when you did it…

            I think you can disable the journal approach if it’s not useful…

            But, the important part is, the files underlying the notes you’re making are in plain text with the page name as the filename, whereas with Joplin you could never find the file…

            Also, if you modify the file (live) outside of Logseq, it copes with that and refreshes the content onscreen.

            And the links are all dynamic… renamed the NAS? Fine, Logseq will reindex all the pages for you…

            • Footnote2669@lemmy.zipOPEnglish
              2·
              11 months ago

              I would be willing to try it, but the workarounds to get sync on iOS are what makes me not do it