Feature Requests

Hi There, At Vbet we are using Short io for different teams, we have 54 users. We have a case when a newcomer must gain permission to a group of links(500 links) but can't see the rest. We can do it only manually, which is almost impossible. If we have a feature to grant permission to a Folder of links, it will solve the issue.

It would be nice if the devs could make a blog post of this potential workaround for users of bit.ly free plans. You can simply log into your free bit.ly account, go to the links page, scroll down until all your links load, scroll back to the top, drag to copy paste over all the links. Paste everything into Excel. Use the find and replace feature to select everything beginning with "http" or " bit.ly " and replace it with "http" or " bit.ly " formatted in a different text color so you can see it easily. Then use Excel's sort function to sort by the text color you selected. And there you go, all your original http or bit.ly links at the top. Copy paste them into a separate Excel file, save as a .CSV and upload it to short.io

Can u add stuff like this https://www.link11.com/en/solutions/web-protection/bot-management/ ? Thanks. or a own solution with the detailed infos and function.

its very very risky currently for organizations and anyone can use the key it should only be hitted from backend server IP and rest all restriction

The new Link Router ( https://shortcm.canny.io/changelog/link-router ) allows variable, passthrough slugs, but I don't think there are any stats that tell you what it was that was passed through. This would be useful in replacing uniquely generated "personal URLs" by allowing a single link to handle them all, while still having visibility into the stats for each one. At a base level, this might just be click count, but could be the ability to segment the link to break out all the variable paths passing through it.

We occassional need to go back to responsible parties, so being able to export a report of who created is essential. I also so if a user leaves they revert to unknown, which is not helpful, we should be able to see who was originator, as well as who last edited, regardless if they are active in the account.

Currently short.io seems to always generate the trailing slash / (when using $1/ in the Original URL) or always remove the trailing slash / (when using $1 in the original URL) even if there had been a trailing slash in the request path. Simply preserving the request path and appending it exactly as it is (either with or without a trailing slash) does not seem possible with short.io . This feature request should allow preserving the * part for a 404 or wildcard slug (including the optional trailing slash) We would like use the slug (404 catch-all link) to redirect any path from https://source.org/ to original URL https://target.org/path/$1 while preserving the trailing slash (only if it exists). So for example https://source.org/foo should redirect to https://target.org/path/foo and https://source.org/foo/ should redirect to https://target.org/path/foo/ The original request path component should be preserved in $1 (including an optional trailing slash) and placed where $1 is located in the original URL.

extend geotargeting functionality also according to the language of the user's browser