[App Request] - a link shortener app

[nullcount]

One of the biggest downfalls of URL shorteners is they can be used to track you and log your IP and I think that is why a lot of people stay away from them. They can be useful for tracking clicks and of course, making it easier to share/remember URLs.

In a private, locally hosted environment, one might use this to help them remember where things are hosted putting a use to the "custom address" advanced option. For example, they could create http://umbrel.local:9999/jellyfin to redirect to the port used for the Jellyfin web UI, etc. That way they only have to remember the port of the URL shortener service.

If the user is comfortable exposing their link shortener publicly with one or more of their own domains, it could be useful for sharing links IRL and analyzing who visits your links. The ability to self-host a link shortener ensures that the data about who is clicking your links stays with you and isn't used against you or sold by third parties.

Some likely candidates:

Kutt Shlink Dub

[IMPranshu]

In a private, locally hosted environment, one might use this to help them remember where things are hosted putting a use to the "custom address" advanced option. For example, they could create http://umbrel.local/jellyfin to redirect to the port used for the Jellyfin web UI, etc.

I believe we can't just use a custom address just to bypass ports locally. Like If you are trying to use a URL shorter for umbrel.local:8909 which is the jellyfin app to umbrel.local/jellyfin that can't be done.

Also for URL shortener to work on Umbrel Reverse Proxy has to be set up but currently, that is not the case.

[nullcount]

@IMPranshu

I suppose the URL shortener service couldn't listen on umbrel.local. So a "private" short url would look something like this: umbrel.local:9999/jellyfin where 9999 is the port number of the shortener app. I edited the OP to reflect this. I still think its a valuable feature.

Many umbrel users already have their own reverse-proxy to expose umbrel services publicly. I imagine they could do the same with a link shortener service.

[IMPranshu]

So a "private" short url would look something like this: umbrel.local:9999/jellyfin where 9999 is the port number of the shortener app.

Let's say umbrel.local:8899 is the address of the jellyfin app and likewise other apps might have some other port number. So you are shortening the URL of jellyfin i.e. umbrel.local:8899 to umbre.local:9999/jellyfin which I don't think is really shortening it in anyway. Am I missing something here?

Many umbrel users already have their own reverse-proxy to expose umbrel services publicly. I imagine they could do the same with a link shortener service.

Yup it's true.

[nullcount]

Let's say umbrel.local:8899 is the address of the jellyfin app and likewise other apps might have some other port number. So you are shortening the URL of jellyfin i.e. umbrel.local:8899 to umbre.local:9999/jellyfin which I don't think is really shortening it in anyway. Am I missing something here?

True, it's not shorter, but may be easier to remember.

A user just has to remember the app name ("jellyfin" or whatever they want to call it) and the port of the shortener service (9999 for example). Without a shortener, they would need to remember the port for each service.

Maybe it doesn't make sense to use the shortener on LAN only. But it can be done which is worth mentioning. The main value comes from exposing the service publicly and configuring with a domain.