@renchap@silverpill still brainstorming: Perhaps as part of a future FEP or just best practice is purge all such remote followers data from your db unless you follow those accounts - and only refresh remote use data when one manually goes back and looks at their profiles again?
@renchap@silverpill Still thinking: then perhaps limiting it only to the remote followers you have loaded into your view (if they have 3,000 but you have only browsed the first 50 shown to you — and if it only gets those - and NOT recursively their followers followers — would that be possible or tendable from a resource issue under AP and/Or Mastodon?
@renchap The main problem I was trying to solve for was accurate visible and being able to browse and manually pick and choose one at a time those one would wish to follow. In that use case if this FEP implemented does the same resource hogging dynamic you describe still have to occur under the hood so to speak?
As always thank you for this discussion! cc: @silverpill
The ability to think or mull over things deeply on vacation is a luxury akin to cooking rich meals while on break - something my work week rarely gives time for.
So instead of: • You → requesting all 600 followers • Server → refusing or returning just an empty collection
It would work like: 1. When you follow someone, your server sends an Add activity to add you to their followers collection. 2. Their server replies (or updates) the original activity with a proof: “Yes, this person was added to my followers.” 3. Anyone (including remote servers) can then verify that proof without needing the full follower list.
@silverpill > The measure of success for a FEP is not the FINAL status, but the number of implementations
Maybe there needs to be an IMPLEMENTED status, that comes after FINAL? Perhaps when at least 3 (unrelated) implementions are tested as compliant with that FEP spec?
@tchambers@renewedresistance@newsmast@surf@rimu@evan My concern would be how it performs with large numbers of actors in a collection. You’d have to have pagination configured for sure. It might end up overwhelming your regular timeline. Better to treat is somewhat like a list?
"And even our terms 'Server' Or 'Instance' make sense in an engineering flowchart but why in all that is holy would we foist those onto users to pretend to understand? At the very least we should talk about new folks joining a 'server community' of fellow users."
So much for "server" making more sense to newbies than "instance". I followed the herd on this usage, even though I questioned the wisdom, given how overloaded the term "server" is.
@box464@renewedresistance Ok one area on this I’d like your opinion on Jeff: do you think this technique might hold promise for more complex ActivityPub based feeds in general beyond just #piefed and upvoting services? For things like @newsmast or @surf feeds one day?
@box464@renewedresistance Thanks, and to be sure I read you correctly: so PieFed feeds DO federate now, but for time being, only to other PieFed servers? In future will they federate out to all ActivityPub?
When we read headlines like "The James Webb Space Telescope has discovered its 1st exoplanet and snapped its picture," we expect images like the ones shown below 😀
Alas, they look more like the image above, a few pixels wide. Images like the ones below would require a much more powerful telescope, such as one located > 550 AU away and which uses the Sun as a gravitational lens 😎.