(later) Offsite Post Discover & Mirroring #249
freakoverse
commented
Owner
- degmods has relay.degmods.com (and/or other hardcoded relays) always connected to the degmods site/client
- The aggregation server also is always connected to those hardcoded relays
- if a goes to a different client, not connected with the hardcoded relays that degmods has, and publishes a post (mod or blog) there, it won't appear on degmods.com if the server is active (it would appear if the server is inactive, as the relay the mod is published at would be, most likely, within the user's metadata relay list).
- the user comes to degmods.com and manually adds that post address in the url (degmods.com/mod/address), and it loads normally as the user has the relays in his metadata.
- so that's the issue: the mod can be see by that user, but potentially not users, as it's only on the relays he published at, but not on the hard-coded relays degmods has, nor potentially on relays other users have in their meta-data
- Solution: The moment the post loads, it gets mirrored (republished) to all hardcoded relays (if it's not there: so it attempts to fetch them, it doesn't find it, but the user loads the event, so then it mirrors them). This results in having the mod both on degmods relays/hard-coded-relays and the aggregate server (since it reads and stores from those relays).
- So, to have a function that does that solution (function to mirror/republish)
- degmods has relay.degmods.com (and/or other hardcoded relays) always connected to the degmods site/client
- The aggregation server also is always connected to those hardcoded relays
- if a goes to a different client, not connected with the hardcoded relays that degmods has, and publishes a post (mod or blog) there, it won't appear on degmods.com if the server is active (it would appear if the server is inactive, as the relay the mod is published at would be, most likely, within the user's metadata relay list).
- the user comes to degmods.com and manually adds that post address in the url (degmods.com/mod/address), and it loads normally as the user has the relays in his metadata.
- so that's the issue: the mod can be see by that user, but potentially not users, as it's only on the relays he published at, but not on the hard-coded relays degmods has, nor potentially on relays other users have in their meta-data
- **Solution**: The moment the post loads, it gets mirrored (republished) to all hardcoded relays (if it's not there: so it attempts to fetch them, it doesn't find it, but the user loads the event, so then it mirrors them). This results in having the mod both on degmods relays/hard-coded-relays and the aggregate server (since it reads and stores from those relays).
- So, to have a function that does that solution (function to mirror/republish)
freakoverse
added the Kind/Enhancement
Priority
Low
labels
freakoverse
added this to the Issues project 
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?