Adjust cache times based on various factors
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating XRay's cache policy and URL-fetch entry point, then read the related tests. Compare how the issue expects cache duration to vary for tweets, Instagram posts, and other URLs, and consider how clients could request a fresh fetch. Done means the caching behavior and any refresh option have clear, testable semantics for these cases.
Written by the indexing model from the issue text.
Description
- Tweets can't be edited, so they can be cached for a long time. (It's possible that Twitter may change their image CDN URLs so can't be infinite)
- Instagram posts can be edited, but most of the time the older a photo is the less likely it is to be edited
- Other URLs should be more conservative about being cached, since people sometimes use this for testing whether their markup changes are working, or it's used when verifying webmentions for updates. Could probably use similar logic to cache older posts longer.
Possibly give clients a way to force XRay to fetch the post if the client knows it may have been updated such as from a webmention update.
- Dominant language
- PHP
- Stars
- 96
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aaronpk/XRay
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 54/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
bug-report bug-report-triage customer report
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Codeinwp/tweet-old-post#1177 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
sonata-project/dev-kit#3119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
🧠 Admin
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day