@fabio@manganiello.eu gaza-verified looks that is not updating anymore.
-
@fabio@manganiello.eu gaza-verified looks that is not updating anymore. Take the first family/campaign, for instance: "Eyad family From Gaza
's" It states 0$, but instead, it fortunately received 7 donations in the last week.
thank you for this project! i hope you can fix it easily
-
@fabio@manganiello.eu gaza-verified looks that is not updating anymore. Take the first family/campaign, for instance: "Eyad family From Gaza
's" It states 0$, but instead, it fortunately received 7 donations in the last week.
thank you for this project! i hope you can fix it easily@lan@meetiko.org the particlar case you highlighted happened because of connection issues with the instance that hosts that account (ieji.de) - most of the automated requests made by the archive to that account fail with a timeout, so without getting an up-to-date version of the campaign URL the campaign is still stuck.
That should be the only case I see consistently though. If you spot any other accounts with similar issues that have actually collected donations in the past week please let me know.
-
R relay@relay.an.exchange shared this topic
-
@lan@meetiko.org the particlar case you highlighted happened because of connection issues with the instance that hosts that account (ieji.de) - most of the automated requests made by the archive to that account fail with a timeout, so without getting an up-to-date version of the campaign URL the campaign is still stuck.
That should be the only case I see consistently though. If you spot any other accounts with similar issues that have actually collected donations in the past week please let me know.
@fabio@manganiello.eu I guess you are meaning social activity of their accounts in the fediverse. However, I meant the collected amount of money, that shouldn't depend on the mastodon instance. For instance (huh), check Anghamelkhalil.
It says that in last 7 days, no donation was done https://gaza.onl/campaigns/accounts/@anghamrlkhalil@mastodon.social?currency=USD&start_time=2026-02-25T00:00:00&sort=donation.created_at:desc&limit=50
However, if you look at their chuffed campaign page, it actually shows 4 donations in last 7 days https://www.chuffed.org/project/148450-urgent-help-for-anghams-displaced-family
Maybe I'm repeating myself and you already got this, sorry if this is the case! -
@fabio@manganiello.eu I guess you are meaning social activity of their accounts in the fediverse. However, I meant the collected amount of money, that shouldn't depend on the mastodon instance. For instance (huh), check Anghamelkhalil.
It says that in last 7 days, no donation was done https://gaza.onl/campaigns/accounts/@anghamrlkhalil@mastodon.social?currency=USD&start_time=2026-02-25T00:00:00&sort=donation.created_at:desc&limit=50
However, if you look at their chuffed campaign page, it actually shows 4 donations in last 7 days https://www.chuffed.org/project/148450-urgent-help-for-anghams-displaced-family
Maybe I'm repeating myself and you already got this, sorry if this is the case!I guess you are meaning social activity of their accounts in the fediverse. However, I meant the collected amount of money, that shouldn’t depend on the mastodon instance.
In the archive case it does.
I need to fetch the latest snapshot of their profile data in order to get their campaign URL (there are several cases of campaign URL changes). And if the archive can't do that then it won't proceed with processing that account, assuming that it's unreachable.
I have just changed this behaviour, so if it can't fetch an account's profile for any reason the archive falls back to the latest db snapshot (if available). This means however that we may end up with stale data in case they change their campaign URL and the profile still can't be fetched by my server.
For instance (huh), check Anghamelkhalil.
This is a different case.
This happened because the campaign URL was originally posted on the profile as
https://www.chuffed.org/project/148450and it's now been changed tohttps://chuffed.org/pay/campaign/148450(which directly points to the payments form).The archive wasn't designed to handle this type of URL too, so it skipped the processing of that campaign assuming that it didn't have a valid URL.
This has now been fixed too.
The archive has now just been restarted with both the fixes and it should probably catch up with those campaigns soon too.
Thanks for the reports!
-
I guess you are meaning social activity of their accounts in the fediverse. However, I meant the collected amount of money, that shouldn’t depend on the mastodon instance.
In the archive case it does.
I need to fetch the latest snapshot of their profile data in order to get their campaign URL (there are several cases of campaign URL changes). And if the archive can't do that then it won't proceed with processing that account, assuming that it's unreachable.
I have just changed this behaviour, so if it can't fetch an account's profile for any reason the archive falls back to the latest db snapshot (if available). This means however that we may end up with stale data in case they change their campaign URL and the profile still can't be fetched by my server.
For instance (huh), check Anghamelkhalil.
This is a different case.
This happened because the campaign URL was originally posted on the profile as
https://www.chuffed.org/project/148450and it's now been changed tohttps://chuffed.org/pay/campaign/148450(which directly points to the payments form).The archive wasn't designed to handle this type of URL too, so it skipped the processing of that campaign assuming that it didn't have a valid URL.
This has now been fixed too.
The archive has now just been restarted with both the fixes and it should probably catch up with those campaigns soon too.
Thanks for the reports!
@lan@meetiko.org btw @SolSoCoG@ieji.de I thought that the issue with parsing the two accounts on your instance was due to your server blocking requests from mine (I've been careful about generated traffic, you shouldn't see more than 5-6 requests to your API every couple of hours from the gaza-verified archive scrapers).
But now I see that the requests actually fail at DNS level (often because of timeouts), no matter which DNS I use:
❯ time nslookup ieji.de 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: ieji.de Address: 185.237.100.33 Name: ieji.de Address: 185.237.100.34 Name: ieji.de Address: 185.237.100.35 ;; communications error to 208.67.222.222#53: timed out ;; communications error to 208.67.222.222#53: timed out ;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached nslookup ieji.de 208.67.222.222 0.01s user 0.01s system 0% cpu 15.046 totalAre you aware DNS resolution issues for your instance?
