Today, we’re excited to announce the release of Linkwarden 2.12! 🥳 This update brings significant improvements and new features to enhance your experience.
For those who are new to Linkwarden, it’s basically a tool for saving and organizing webpages, articles, and documents all in one place. It’s great for bookmarking stuff to read later, and you can also share your resources, create public collections, and collaborate with your team. Linkwarden is available as a Cloud subscription or you can self-host it on your own server.
This release brings a range of updates to make your bookmarking and archiving experience even smoother. Let’s take a look:
What’s new:
🫧 Drag and Drop Support
One of our most requested features is finally here! You can now drag and drop Links onto Collections and Tags. This makes it much easier to organize your bookmarks and keep everything tidy.
📤 Upload from SingleFile
SingleFile is an awesome browser extension that allows you to save complete webpages as a single HTML file on your device. As of Linkwarden 2.12, you can upload your saved links directly from the SingleFile browser extension into Linkwarden. This allows you to easily save articles which are behind paywalls or require authentication directly from your browser.
To use this feature, simply install the SingleFile extension, and then follow the documentation.
🌐 Progressed Translations
We’ve made significant progress in our translations, with many languages now fully supported. If you’re interested in helping out with translations, check out our Crowdin page.
✅ And more…
There are also a bunch of smaller improvements and fixes in this release to keep everything running smoothly.
Full Changelog: https://github.com/linkwarden/linkwarden/compare/v2.11.8...v2.12.0
Want to skip the technical setup?
If you’d rather skip server setup and maintenance, our Cloud Plan takes care of everything for you. It’s a great way to access all of Linkwarden’s features—plus future updates—without the technical overhead.
We hope you enjoy these new enhancements, and as always, we’d like to express our sincere thanks to all of our supporters and contributors. Your feedback and contributions have been invaluable in shaping Linkwarden into what it is today. 🚀
Love it 😊
Nice. Started using it just a couple weeks ago. I tested a big chunk of them and while Linkwarden isn’t perfect, it does everything better than everything else I tried.
Do we self-hosters need to do anything special? I remember looking at some docs about upgrading versions, but I don’t know how to tell which version I have.
I remember looking at some docs about upgrading versions, but I don’t know how to tell which version I have.
- User icon (top right) > ≡ menu (top left) to open side bar. Current version is displayed at the bottom of the side bar
As a general rule when installing anything with Docker Compose, rather than using “latest” I prefer to specify a version as it makes it easier to roll back should i find issues with an update.
Freaking quality post, OP! Lots of information about what’s new, barely even have to visit the link to know what’s going on here. Love to see it.
👍👍
Thanks! :)
I do host an instance of it but rarely use it. I’d love to see more in depth archival features like deep link archiving and archiving resources behind authorization. My use case is more archiving than bookmarking.
Then, I think you should be using Archive Box. Maybe you already do.
I actually don’t! I’ll check it out if it fits my needs. Thanks!
I’d love to move to it, but I cannot find any easy way to export from Readeck and import to Linkwarden. At least a list of pages.
I was using it, switched to hoarder, then readeck. Now I’m thinking about moving back to linkwarden, so this is bad news for me.
Sweet! Single-file looks like a decent workaround for those links that get locked behind captcha when they’re being saved. Always frustrates me when I go to review a link and it turns out it only saved a cloudflare redirect lol
Glad you like it!
Linkwarden kicks butt! I use it all the time now.
Linkwarden user here. Can confirm - it’s a great tool to dump links for later. I’ve setup an iOS shortcut that lets me share links directly to linkwarden. Super handy
Great to hear! Just wait till you hear about the upcoming official mobile app!
This is a fantastic tool, but I’d love to confidently expose the API to the internet for the shortcut. To do that you need read-only and running as a user; I saw that that’s not a thing that works from the issues.
Any thoughts on getting those security features working? Cause the app itself is so smooth I’d let my parents use it and be confident they wouldn’t need to be herded constantly.
So you want to disable registration? It’s possible.
No what I said isn’t about user registration; it’s about adding these to the
docker-compose.yml:read_only: true user: 6969:6969to prevent running as root and making the file system read-only. The API needs to be exposed without a VPN or other proxy login since my parents’ can’t handle that, so if I was able to implement these recommended security steps I’d feel like I could open up the container to the internet at large without too much risk.
Per this issue https://github.com/linkwarden/linkwarden/issues/799 it seems like there’s a lot of steps to take to get these settings to work.
It would be also ideal if I didn’t have to give the container (but not a deal-breaker):
cap_add: - CAP_SYS_ADMIN - CAP_SYS_CHROOTas the issue also states is required for the headless chrome scraper browser.
I am using it internally now and it’s really good, but to open it up for my parents (which I think they’d dig) I’d definitely want these security settings on without major issues. Linkwarden is an internet-facing application so these recommended security practicies are in its wheel-house, feature-wise, as well.
Hope that helps clear up my comment!
How would you add new links if its read only?
As always you store data you want to keep in the volumes section.
With read-only you prevent new binaries from being added in the image space. You can add ‘noexec’ to your volumes/tmpfs preventing binaries to the areas that are writable. Then ideally you are using an image with minimal surface area (e.g., only sh and the exact binaries needed to make it go) and it’s very secure! It’s still plenty secure without a minimal image.
Couldn’t the attacker just drop a dangerous binary into the data volume then?
Not if you annotate your data volume with said ‘noexec’ which prevents execution from anything in the data volume. It looks like this, you can slam it on any volume you like - no volumes should have executables in them anyways.
Also I’m pretty sure ‘noexec’ is the default, so that’s by default protected. But I can’t confirm that from a quick search so not 100% on that.
‘/mnt/data:/container/place/it/wants:rw,noexec,nosuid,nodev,Z’
‘rw’ means read/write. You can change it to ‘ro’ for read-only if the volume shouldn’t write to it (maybe a config file).
Z is for selinux that means “only one program can read/write tho this”. You can change it to ‘z’ lowercase in case more than one needs to read/write. Only case I’ve found for little z is crowdsec needing to watch Caddy’s log for blocking.
So overall, the idea is that your volume mounts can’t be used to execute arbitrary binaries AND the image file system is frozen so that arbitrary binaries cannot be loaded into the image (which is by default all executable, a requirement to run anything in it). So if someone was able to hack into an internet-facing container, they won’t be able to load up whatever they want. They’ll be limited to what’s built into the image (which ideally are secure and limited in scope).
This is great. Thanks!
