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
From my current understanding, events (log entries) have to be fetched on a board basis. This is potentially problematic since the bot would have to fetch the logs from all boards that have been the source of, at least, one status.
Furthermore, the log related endpoints (1 and 2) bring additional challenges. The first only provides the number of entries per day and the second, which returns a somewhat detailed list of events, does it by date (e.g. GET https://ptchan.org/i/logs/09-27-2022.json returns a list of /i/ events that happened yesterday).
TLDR: To know what has to be propagated, one must fetch logs from the current day in every board that has been the source of a status* and this has to be performed at least once per day (which is not ideal for obvious reasons, we should try to propagate changes every 30 minutes or so) in order safely ignore previous days changes.
*Threads are ephemeral in imageboards and it’s probably okay to assume that if a thread has not been deleted after t time, there’s nothing wrong with it. Maybe we can watch only “fresh” status.
... I don’t see how one could implement a such solution without persistent memory of threads (their id, board, and probably more) that have been posted.
Lacerkage
changed the title
Propagate deletion and edition of threads
Propagate moderation actions
Sep 29, 2022
If a thread gets deleted or edited on the imageboard, the respective status published by the bot should reflect those changes.
The text was updated successfully, but these errors were encountered: