cross-posted from: https://programming.dev/post/58898830
There has been some QoL improvements added recently. Notable ones are:
- Support for OIDC login
- Batched inserts
- Temporary link disabling
- Faster reply and redirection due to async handling of some less-important tasks
There have also been small changes to the backend and UI that improve the user experience overall.
If you’re looking for a selfhosted URL shortener, please check it out.
Extra links: Codeberg, Official website
Please refer to rules 7&8. The tag must be included in the title, with a disclosure if applicable.Thanks!
URL shortering is a security risk imo. I want to see where I’m going before I click.
It’s about trusting the source/sharer.
My friends and family trust me, so trust links I send.
And people currently use public link shortened, this is at least an order of magnitude (or more) better than sharing our data with those people.
While I agree on principle, we’re not always using big-name websites. The argument falls short for some-local-blog.com, there’s no security improvement on clicking that link as opposed to shortener.tld/blog-link. I’d say we should trust the source of the link instead of the link itself. Link shortening can be useful if you want long links to look nice when sharing, or simply for personal use so that you don’t need to remember long links to access an internal resource. Or just for personal websites. I can link my CV at
https://domain.tld/cvinstead of the full PDF file path, for example.I mean, you could always create a server-side symlink?
Yeah, but I could also use a shortener. It’s more ergonomic, easier to use, edit etc. Different tools exist for a reason.



