I will. I was asking from CPU power and price perspective though.

I’m using Headscale for work and Tailscale for personal use. I tried to use Nebula but it’s not easy as Tailscale.

You’re right, I was just giving an example though.

I’ve mistyped, I meant message in JSON body :)

This one looks nice. Very detailed.

Looks like they’re recommending object of error code (number) and message.

These docs are for latest Lemmy version so you may experience some mismatches with a legacy instance but I didn’t see something like that so far.

TBH I find the docs very easy. It’s about JS documentation familiarity I guess.

You can see the URL and request body from LemmyHttp class method docs: https://join-lemmy.org/api/classes/LemmyHttp.html#getPosts

Why should I use JuiceFS instead of rclone though?

Unfortunately, I feel the same. As I observed from the commenters here, self-hosting that won’t break seems very expensive and laborious.

Yeah I really like the “parent backup” strategy from @hperrin@lemmy.world :) This way it costs much less.

Pretty solid backup strategy :) I like it.

It’s quite robust, but it looks like everything will be destroyed when your server room burns down :)

Can we use group meeting in self hosted version?

Yes, you can shoot me from there and you’re right but I don’t see much difference between Matrix clients. The experience is pretty common between them. Synapse is de facto standard.

I don’t think XMPP is simpler than Matrix. With my insufficient knowledge; XMPP servers and clients have different standards. Some supports audio/video calls, some requires encryption while other maybe not etc.

Matrix has a standard set of features and all software around it built for those features. TBH I find Matrix pretty instable lately tho.

“Ubuntu added on top” you mean Snap? No thanks :)

You need to pass host header. But if you really want to hide your IP, you need to proxy your outgoing activities too.

Did you just used an AI with sudo? lol 😄

I think you can migrate files while pict-rs running in read-only mode, without downtime. Then changing the S3 url should be enough, I guess? :)

Read-only mode is a v0.5 feature tho.