Difference between revisions of "Patch.com"

From Archiveteam
Jump to navigation Jump to search
(6 intermediate revisions by 4 users not shown)
Line 4: Line 4:
| description = Your neighborhood. Your news.
| description = Your neighborhood. Your news.
| URL = <nowiki>http://www.patch.com/</nowiki>
| URL = <nowiki>http://www.patch.com/</nowiki>
| project_status = {{closing}}
| project_status = {{specialcase}}
| source = https://github.com/ArchiveTeam/patch-grab
| source = https://github.com/ArchiveTeam/patch-grab
| archiving_status = {{inprogress}}
| archiving_status = {{saved}} - [https://archive.org/details/archiveteam_patch archives]
| irc = cabbagepatch
| irc = cabbagepatch
| tracker = [http://quilt.at.ninjawedding.org/patchy here]
| tracker = [http://quilt.at.ninjawedding.org/patchy here]
Line 13: Line 13:
'''Patch.com''' is a "hyperlocal" news community which is [http://www.webcitation.org/6IrUArBiV being downsized] from its current ~900 sites to ~500.
'''Patch.com''' is a "hyperlocal" news community which is [http://www.webcitation.org/6IrUArBiV being downsized] from its current ~900 sites to ~500.


=== Current status ===
== Current status ==


antomatic has prepared (what appears to be) a [[List_of_Patch.com_sites|complete list of sites]].  A prototype seesaw project (no Warrior integration yet) also exists.
In progress.  Warrior integration coming soon.


There's what looks like a master site map (with links to sub-sitemaps) at http://www.patch.com/sitemaps.xml also.
== Patch.com will rate-limit you across all sites ==


Most/all(?) Patches seem to share similar directories and content structures - e.g. /news, /blogs, /boards, /events, /directory, /jobs, etc.
Patch.com institutes a rate-limit (some unknown hundreds of requests/hour) across all sites. If you exceed this, all of your requests will be met with HTTP 420s.


=== Next steps ===
If the patch-grab script detects these, it hard-aborts.  A kinder solution would be to sleep for some period of time (an hour?) and try again; suggestions appreciated.


Patch subdomains are (1) big and (2) appear to implement some sort of request cap per IP per unit time.  (You'll start getting HTTP 420s after a while.)  We need to investigate whether we need to implement a complicated mechanism to split up individual sites and then megawarc them together, or just take each site slowly (e.g. n requests every hour).
{{Navigation box}}
 
Pop in the IRC channel if you want to help.

Revision as of 02:13, 30 December 2014

Patch.com
Your neighborhood. Your news.
Your neighborhood. Your news.
URL http://www.patch.com/
Status Special case
Archiving status Saved! - archives
Archiving type Unknown
Project source https://github.com/ArchiveTeam/patch-grab
Project tracker here
IRC channel #cabbagepatch (on hackint)

Patch.com is a "hyperlocal" news community which is being downsized from its current ~900 sites to ~500.

Current status

In progress. Warrior integration coming soon.

Patch.com will rate-limit you across all sites

Patch.com institutes a rate-limit (some unknown hundreds of requests/hour) across all sites. If you exceed this, all of your requests will be met with HTTP 420s.

If the patch-grab script detects these, it hard-aborts. A kinder solution would be to sleep for some period of time (an hour?) and try again; suggestions appreciated.


Retrieved from "https://wiki.archiveteam.org/index.php?title=Patch.com&oldid=21297"