mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #28] Link Parsing: Add support for OneTab bookmark exports #20
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#20
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 @compliment on GitHub (Jun 30, 2017).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/28
https://www.one-tab.com/
@pirate commented on GitHub (Jun 30, 2017):
Onetab exports are super simple, just a list of URLS and titles. Unfortunately they don't have timestamps, so we'll have to make some up or come up with a different uuid for each archive (hash of the url maybe?).
Sample:
@compliment commented on GitHub (Jul 4, 2017):
Yeah, and one-tab shared urls like this one
It's like a webpage though.
wget stucks at one-tab.com domain resolution for some reason.
@pirate commented on GitHub (Jul 4, 2017):
wget had a bug in a recent version that stopped it from resolving a ton of totally valid urls, upgrading it to 1.9.1_1 fixed it for me instantly.
@pirate commented on GitHub (Jan 30, 2019):
This should be working now with the new full-text link parser. If you try it, let me know if it doesn't work and I'll reopen this ticket.