Selfhosted

43945 readers

338 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

If I self host mastodon and matrix, and shutdown the device, when I turn it on again, will it receive all the activity that happened in the meantime? (programming.dev)

submitted 1 week ago by ICastFist@programming.dev to c/selfhosted@lemmy.world

3 comments fedilink hide all child comments

I've been thinking of self hosting a mastodon (gotosocial, more specifically) + a matrix server on an old computer I have, but sometimes I might need to turn it off for 2 days or more (not to mention some energy or internet outages that might happen here)

I suppose with the mastodon part the server will properly sync and download whatever's been missing, but I'm not entirely sure that'll be the case with matrix. If anyone sent me a DM on there while my server was down, would it get through after it was back up?

you are viewing a single comment's thread
view the rest of the comments

[–] F04118F@feddit.nl 2 points 1 week ago* (last edited 1 week ago)

Took a look at the specification, this is what I found:

For federated servers performing delivery to a third party server, delivery SHOULD be performed asynchronously, and SHOULD additionally retry delivery to recipients if it fails due to network error.

So they should retry. Note that should is not the same as must. So there is no obligation. There is no timeline in the spec about for how long or how often retries should be done. The wording says network error.

My interpretation: the spec leaves a lot of room for implementations to differ. Network problems don't normally last for days though. I'd guess that if your server is down for 5 minutes, you'll still receive most or everything you'd normally receive. I wouldn't trust on that if your server is offline for more than a day.