projectwallace / projectwallace/projectwallace.com
Test run with another UA string for CSS scraper
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
See if there's fewer websites blocking the scraper if it looks more like a conventional browser.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:146.0) Gecko/20100101 Firefox/146.0 (compatible; Project Wallace CSS Scraper/1.2; +https://www.projectwallace.com/docs/css-scraper)
If moving on with this then also update the docs (version number + changelog).
TODO: come up with a list of domains that are blocked now and may start working after this change.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files or tests are named. Start by locating the CSS scraper's user-agent configuration and identify domains currently blocking it; compare a run with the proposed UA. If the change proceeds, update the documentation's version and changelog, and record which previously blocked domains work afterward.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100