Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JO
Posts
6
Comments
279
Joined
2 yr. ago

  • Keep in mind that even if some are scams, they might appear to work at first. The problem is that the key you get may be marked as stolen or purchased with a stolen credit card/etc, and then your key becomes invalid even if you've already redeemed it.

  • How would you verify that an instance actually verified its users? Someone could spin up their own malicious instance, create 1000s of users, and just mark them as verified in the database, and then I don't think instances receiving updates from it would have any way to know? One instance basically has to trust another instance that it's telling the truth.

    I do still think some sort of circle-of-trust type of thing could help, but I'd be worried about that getting abused too.

  • For things to work properly, yeah. Other instances need to be able to connect to your instance to send updates/etc. You could use cloudflare tunnels or something like that instead of port forwarding though

  • I remember using tiddly wiki a long time ago. Do you still prefer it over other solutions? I feel like my tiddly wiki would be too large of a file by now to be manageable, but I'm not really sure.

  • Thanks so much for the detailed response! I didn't realize livesync handled conflicts better, that's almost enough by itself to make the switch.

    I think originally I was mostly hesitant to try it because I didn't want to expose a public couchdb, but it's actually not that big of a deal now that I think about it, especially if it's using end to end encryption.

    I have a few vaults that I share with others and multiple people can work on the same file simultaneously with no issues at all.

    Do you just share the entire vault? I'm assuming each person you share with would just end up using the same credentials? I tried sharing a vault with my partner before using remotely-save+nextcloud and it was kind of clunky, we ended up just using a shared folder and let nextcloud desktop app sync it instead. It doesn't help for mobile though.

    Thanks for sharing your config too, I'll probably try setting it up with a test vault this week and see if I run into any issues with it

  • Thanks! I'm assuming you meant tasks.org? It looks interesting, I'll give it a try. I knew etesync could be used to sync calendar/contacts, but didn't really think about tasks and notes too.

    Etenotes looks like it might be too simple for me, but I have been looking for a new task/todo list.

    I also saw etebase is its own thing, but it looks pretty interesting too and I'll keep it in mind for future projects.

  • Have you had any issues with the self-hosted livesync plugin? I currently use the "remotely save" plugin and sync to a nextcloud instance, but I thought about trying the livesync plugin instead. I just wasn't sure if it was worth spinning up a couchdb instance just for that.

  • If you're already using Nextcloud, it has a chat w/ video chat as well.

    Matrix / Synapse / Element.io is also pretty cool. The UX might not be on par with what some family expects though. I don't know if voice/video chat is built-in yet or not, but it was at least an option before.

  • Bookstack is a really nice wiki/documentation tool.

    You may also like wiki.js or even just storing markdown files in a git repo. Lately I've been using Obsidian to manage some notes about servers, but am thinking of going back to bookstack to "publish" docs for others.