[daniel31x13]

I maintain an open-source project called Linkwarden and this exact discussion is one of the reasons why it exists, teams needed a way to preserve referenced URLs reliably without having to depend on external services.

It stores webpages in multiple formats (HTML snapshot, screenshot, PDF snapshot, and a fully dedicated reader view) so you’re not relying on a single fragile archive method.

There’s both a hosted cloud plan [1] which directly supports the project, and a fully self-hosted option [2], depending on how much control you need over storage and retention.

[1]: https://linkwarden.app

[2]: https://github.com/linkwarden/linkwarden

[raybb]

Linkwarden is awesome and with the singlefile extension it's pretty easy to store things you can see but the scraper gets blocked on.

One question, what's your stance on adding a way to mark articles as read or "archive" them like other apps that are branded a bit more as storing things to read later. You can technically do something similar with tags but it's a bit clunky of a UX.

[daniel31x13]

Thanks! At the moment we’re focused on archiving rather than read-later workflows, but this is great feedback. I’ve already added it to the feature requests list.

[moontear]

Archival is one side of the coin, but consumption as-in read-later is very important as well.

I am currently evaluating Linkwarden, Wallabag, Hoarder, Linkding and each of the services has pro and cons making it hard for me to choose one. Linkwarden is AWESOME in its way to store content in multiple formats, but the read-later wfs could be improved.

Without checking again: does Linkwarden sync reading location across devices and automatically scrolls to that location on the next device? Does it tell me how „long“ an article takes to read (solely based on the length of it)? Does Linkding support marking up text and persist (mark some text yellow and see those marks somewhere or even add comments or favorite specific parts of texts).

No need to answer any of the questions, I can research myself, just putting these out there for a read-later solution I would like. Add a link on my mobile device, Linkwarden could do its magic in the backend, and I check out the content later on desktop or even on my mobile device.

[lxgr]

> with the singlefile extension it's pretty easy to store things you can see but the scraper gets blocked on

FWIW, at least on iOS, it's possible to inject Javascript into the web site being currently displayed by Safari as a side effect of sharing a web link to an app via the share sheet.

Several "read it later" style apps use this successfully to get around paywalls (assuming you've paid yourself) and other robot blockers. Any plans for Linkwarden to do this (or does it already)?

[ghxst]

Any docs on this? I didn't know this was a thing.

[lxgr]

I believe the key search term was NSExtensionJavaScriptPreprocessingFile, e.g. documented here: https://developer.apple.com/library/archive/documentation/Ge...

[daniel31x13]

https://docs.linkwarden.app/Usage/upload-from-singlefile

[lxgr]

That's cool, but also requires using the Singlefile extension (and granting it access), right?

What I like about the share sheet JS method is that it doesn't get access to most of my browsing sessions. (The shared-to app getting access to my browser session is somewhat unexpected, though.)

[iririririr]

Neat. How does the archive.org integration works?

Does it just POST the url to them for them to fetch? Or is there any integration/trust to store what you already fetched on the client directly on their archives?

[daniel31x13]

> Does it just POST the url to them for them to fetch?

Correct.

[TechPlasma]

I literally just came across and installed your project on my server today. It's fantastic and with it I was able to cancel my readwise subscription. Great work!