Post #4223022

📢 #GazaVerified archive updates I’ve dedicated a bit of time to fix a couple of issues on the gaza-verified archive as well as implement some long-standing feature requests. Filter out inactive accounts. As the initiative progressed, some accounts were suspended, deleted, moved or their instances were gone, but the list was never cleaned up. The archive API and the UI now expose a Hide Inactive filter that allows to easily filter out accounts that are permanently inactive. Note that inactive accounts are not deleted from the archive - they can just be filtered out. An account is marked as inactive when:It’s suspendedIt’s no longer available (deleted or moved)Its instance has not been reachable for at least 3 daysFilter out inactive campaigns. Fundraisers expire, or are deleted either by the campaign managers or the platforms. When it happens, it’s important to skip inactive campaigns from the list so donors won’t be overwhelmed by a long list of accounts on $0. Note: ?hide_inactive=true is now the new default for the archive API, which means that also the gaza-verified campaigns page will now hide inactive campaigns. @gaza_verified_campaigns@mastodon.social will also no longer report inactive campaigns, which should make the list clearer.Support for whydonate campaigns - thanks @raphaellakay@mastodon.world for pointing this out and thanks @davidculley@hachyderm.io for calling out some volunteers to help on this. The campaign of @sharifgaza@mastodon.social is now indexed on the archive. The only caveat is that the whydonate API doesn’t expose donation dates. The “scraping timestamp” is a good approximation, but this means that for the first scraping the amount collected this week will surely be higher than it actually is - basically all the donations made so far have been accounted as made today. This will be fixed when the counters reset next week.**Fixed “stuck” Chuffed campaigns - thanks again @raphaellakay@mastodon.world for pointing this out. Only one campaign was affected AFAIK (@naeemafamily@mastodon.social), and that should now be fixed. The issue was tricky to find and fix - it basically boils down to a corner case where the last saved page cursor points to a donation ID that has been removed in the meantime (Chuffed has a few of these glitches), corrupting the current state of that campaign on the archive. When it happens, now the whole campaign is simply re-synchronizing again from the first donation. As usual, the code for the gaza-verified archive is open, so feel free to contribute. @aral@mastodon.ar.al @gazaverified@mastodon.ar.al