mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1639] Feature Request: Archive.org Excluded Domains #3997
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#3997
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JeckDev on GitHub (Jan 21, 2025).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1639
Originally assigned to: @pirate on GitHub.
What type of suggestion are you making?
Modification of existing behavior
What is the problem that your feature request solves?
Sometimes I want to archive stuff on my personal intranet, which means not sending the link to archive.org; however I also like having the archive.org save feature turned on.
What is your proposed solution?
A config setting with a list of domains that are excluded from being sent to archive.org
What hacks or alternative solutions have you tried to solve the problem?
The workaround is to manually disable archive.org indexing before archiving a page, then turning it back on again.
Share the entire output of the
archivebox versioncommand for the current verison you are using.How badly do you want this new feature?
Mini Survey
@pirate commented on GitHub (Jan 21, 2025):
It's a good idea, and I've been thinking about ways to allow arbitrary config overrides on a per-URL/per-domain basis for a while, but it's not implemented yet.
I would welcome a PR to add your specific request earlier if it's very simple, otherwise I'd probably want to wait until I push the full feature that allows arbitrary config overrides.