You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see from my pixelfed.social account that the network timeline is flowing nicely but on my instance, on the latest commit, and with a postgresql backend, it is entirely immobile only updating when my home timeline also updates.
I have PF_NETWORK_TIMELINE=true in my .env file and ran php artisan config:cache as per the norm but after 12 hours, I'm yet to see any unique activity on my network timeline that isn't on my home timeline.
I also note that the remote account layout on posts is different on pixelfed.social than it is on my instance.
on pixelfed.social the format is <accountname> from <domain>
on my up-to-date instance the format is just the webfinger norm of <accountname>@<domain>
Is this likely a postgresql oversight, or something else? How is the timeline populated?
The text was updated successfully, but these errors were encountered:
I can see from my pixelfed.social account that the network timeline is flowing nicely but on my instance, on the latest commit, and with a postgresql backend, it is entirely immobile only updating when my home timeline also updates.
I have PF_NETWORK_TIMELINE=true in my .env file and ran php artisan config:cache as per the norm but after 12 hours, I'm yet to see any unique activity on my network timeline that isn't on my home timeline.
I also note that the remote account layout on posts is different on pixelfed.social than it is on my instance.
on pixelfed.social the format is
<accountname> from <domain>
on my up-to-date instance the format is just the webfinger norm of
<accountname>@<domain>
Is this likely a postgresql oversight, or something else? How is the timeline populated?
The text was updated successfully, but these errors were encountered: