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
Three possible ways to do this: 1) storing and comparing responses to GET req's at onboarding.solid.com/public/Links--this would require figuring out how to store a response in Github actions (the pipeline tool we're currently using); 2) if we start adding datetimes by default to every new resource, we could maybe also just check for any datetime that is less than one hour old (if the cron job runs every hour, for example); 3) is there a last-modified header in the response?
The text was updated successfully, but these errors were encountered:
Three possible ways to do this: 1) storing and comparing responses to GET req's at onboarding.solid.com/public/Links--this would require figuring out how to store a response in Github actions (the pipeline tool we're currently using); 2) if we start adding datetimes by default to every new resource, we could maybe also just check for any datetime that is less than one hour old (if the cron job runs every hour, for example); 3) is there a last-modified header in the response?
The text was updated successfully, but these errors were encountered: