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
Right now, atproto-hub keeps the DIDs of all accounts bridged into and out of Bluesky in memory, and updates them every 10s. It only adds to them, though; it doesn't remove them when they're disabled. We handle disabled accounts fine later on, in receive tasks, but this means that when we disable acounts due to volume/overuse, eg #1669, it doesn't take effect in atproto-hub until we restart it.
We should drop the status/enabled_protocols filters from these queries, check those in memory, and remove DIDs that got disabled. (Or do two queries.)
Right now, atproto-hub keeps the DIDs of all accounts bridged into and out of Bluesky in memory, and updates them every 10s. It only adds to them, though; it doesn't remove them when they're disabled. We handle disabled accounts fine later on, in receive tasks, but this means that when we disable acounts due to volume/overuse, eg #1669, it doesn't take effect in atproto-hub until we restart it.
We should drop the status/enabled_protocols filters from these queries, check those in memory, and remove DIDs that got disabled. (Or do two queries.)
bridgy-fed/atproto_firehose.py
Lines 87 to 97 in 9e2479e
The text was updated successfully, but these errors were encountered: