Eval: kage for archiving auction listings post-bid #60

New issue

Open

opened 2026-07-05 11:22:50 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-07-05 11:22:50 -07:00

Owner

Source

https://github.com/tamnd/kage — MIT license

What it is

Go-based web archiver. Headless Chrome renders the final DOM, JavaScript stripped.
Folder mirrors, ZIM archives, or desktop apps as output. MIT license.

Snipe use case: listing preservation

Auction listings (eBay, CT Bids, estate sales) are often removed or substantially
modified after a sale closes. A winning bidder has no record of:

The exact item description and condition stated
All photos at time of listing
Seller's stated policies and guarantees
Original price and bidding history

These matter for:

Dispute resolution: "The listing said X but I received Y"
Insurance claims: Documented value and condition at purchase
Resale: Provenance documentation for antiques/collectibles
Record-keeping: Tax documentation for significant purchases

Proposed flow:

User places a bid / Snipe schedules a snipe
kage archives the listing at bid time (full rendered DOM, all photos)
If user wins, archive is attached to the purchase record
Archive accessible from "My Purchases" view

Implementation

kage Go binary as subprocess or sidecar. Archive stored in
~/.snipe/archives/<listing-id>/. Photo-heavy listings may be large — add
configurable max-size limit.

License

MIT — clean for all CF tiers.

## Source https://github.com/tamnd/kage — MIT license ## What it is Go-based web archiver. Headless Chrome renders the final DOM, JavaScript stripped. Folder mirrors, ZIM archives, or desktop apps as output. MIT license. ## Snipe use case: listing preservation Auction listings (eBay, CT Bids, estate sales) are often removed or substantially modified after a sale closes. A winning bidder has no record of: - The exact item description and condition stated - All photos at time of listing - Seller's stated policies and guarantees - Original price and bidding history These matter for: - **Dispute resolution:** "The listing said X but I received Y" - **Insurance claims:** Documented value and condition at purchase - **Resale:** Provenance documentation for antiques/collectibles - **Record-keeping:** Tax documentation for significant purchases Proposed flow: 1. User places a bid / Snipe schedules a snipe 2. kage archives the listing at bid time (full rendered DOM, all photos) 3. If user wins, archive is attached to the purchase record 4. Archive accessible from "My Purchases" view ## Implementation kage Go binary as subprocess or sidecar. Archive stored in `~/.snipe/archives/<listing-id>/`. Photo-heavy listings may be large — add configurable max-size limit. ## License MIT — clean for all CF tiers.