Remote Inbox Architecture
-
Remote Inbox Architecture
1/
This, the Remote Inbox Architecture, is an architecture for a Fediverse back-end server that I think could be useful.
Here is how it works — there are (at least) 2 servers involved: (1) the main back-end server, and (2) a remote inbox server.
The actor file on main back-end server "points" the inbox to the remote server.
It separates the user's content front the front-end related functionality
...
-
Remote Inbox Architecture
1/
This, the Remote Inbox Architecture, is an architecture for a Fediverse back-end server that I think could be useful.
Here is how it works — there are (at least) 2 servers involved: (1) the main back-end server, and (2) a remote inbox server.
The actor file on main back-end server "points" the inbox to the remote server.
It separates the user's content front the front-end related functionality
...
Remote Inbox Architecture
2/
The Remote Inbox server deals with incoming activities, objects, etc, from other users..
The front-end can get the inbox (and other feeds') data from the Remote Inbox server.
(You'd probably want to store cached data from the Fediverse elsewhere from these two servers, as I've said before. But, that is a separate thread.)
-
Remote Inbox Architecture
2/
The Remote Inbox server deals with incoming activities, objects, etc, from other users..
The front-end can get the inbox (and other feeds') data from the Remote Inbox server.
(You'd probably want to store cached data from the Fediverse elsewhere from these two servers, as I've said before. But, that is a separate thread.)
@reiver interesting. shouldn't the outbox be on (2)? In theory that is a place to get content and feeds from
-
@reiver interesting. shouldn't the outbox be on (2)? In theory that is a place to get content and feeds from
Not for this (Remote Inbox) architecture.
The outbox is related to the user's content, so it stays with where the user's content is.
-
Not for this (Remote Inbox) architecture.
The outbox is related to the user's content, so it stays with where the user's content is.
RE: https://zomglol.wtf/@jamie/111038100520197521
@reiver @darius Can confirm. I did this a couple years ago using an S3 (well, DigitalOcean Spaces) bucket that stored static JSON and an "ActivityPub concierge" that manages it. The outbox was part of that static JSON.
Thread about it here:
-
RE: https://zomglol.wtf/@jamie/111038100520197521
@reiver @darius Can confirm. I did this a couple years ago using an S3 (well, DigitalOcean Spaces) bucket that stored static JSON and an "ActivityPub concierge" that manages it. The outbox was part of that static JSON.
Thread about it here:
-
Not for this (Remote Inbox) architecture.
The outbox is related to the user's content, so it stays with where the user's content is.
@reiver I see - the statement "It separates the user's content front the front-end related functionality" is confusing to me but I understand the intent now
-
Remote Inbox Architecture
1/
This, the Remote Inbox Architecture, is an architecture for a Fediverse back-end server that I think could be useful.
Here is how it works — there are (at least) 2 servers involved: (1) the main back-end server, and (2) a remote inbox server.
The actor file on main back-end server "points" the inbox to the remote server.
It separates the user's content front the front-end related functionality
...
I think that is already achievable with the current spec, the inbox can be a URL to anywhere in the actor object:
https://www.w3.org/TR/activitypub/#actor-objects
"inbox": "https://kenzoishii.example.com/inbox.json",This can be any url with any domain
-
@reiver I see - the statement "It separates the user's content front the front-end related functionality" is confusing to me but I understand the intent now
I had a typo in there. It should have said:
"It separates the user's content FROM the front-end related functionality"
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi