56
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Feb 2025
56 points (100.0% liked)
Selfhosted
61877 readers
422 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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 3 years ago
MODERATORS
You're talking about syncing and downloading content from external services, which makes me think you're just imagining these as being a client versus an "instance". In that case, just use a client because neither of these services inherently do what you're asking, that's what a client of these services does.
My dummy understanding is that each instance could be considered a "client", in the sense that they're always on the lookout for data from other instances whenever the latter generates new content. Either that or, when one connected user checks what's on a different instance, it downloads to the local cache, ie: if I, from programming.dev, am the first to check this thread, a copy gets saved locally (cache) in the programming.dev server, which might check back on the original source in the case of any edits.
Sort of, but not really. It's a pub/sub ecosystem, so if your services are offline, they aren't going to be pulling the delta of missed data beyond a threshold. That's why clients are clients, because they are built to do this for this purpose.
It wouldn't make sense for a deployment acting as an active instance to act like a client in the way you're describing, because the services are configured and tuned to NOT act that way, but ingest data available at time of publish to the endpoints they are subscribed to.
Matrix works like email. It used a push model where a server pushes a message to another server that stores it. The message might be stored on the server of origin or it may not.