You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know there exists a "reuse" option right now, but from what I understand it's not what I'm looking for.
My desire is to shorten links sent inside of Discord Embeds to save on character limits in the request body.
I personally don't care about statistics or anything like that - I only care about keeping my total character count to a minimum.
Often times, the same links will be sent in my Discord messages (i.e. a link to a homepage, or a link to a specific user's profile) - and in those cases, I would rather it return the shortlink that already exists for those links instead of creating a new one.
My preference is to:
Never expire these links (for historical reference)
Create as few shortlinks as possible so I can use the shortest slug I can
Does this already exist and I've just missed it? Is this something the project would be open to supporting?
The text was updated successfully, but these errors were encountered:
This is what "reuse" does for you though, unless I misunderstood something you said. Let's say you have shortened https://example.com/hi and Kutt returned kutt.it/f8Sq1G, if you again send https://example.com/hi while reuse is set to true, you'd get back kutt.it/f8Sq1G.
I know there exists a "reuse" option right now, but from what I understand it's not what I'm looking for.
My desire is to shorten links sent inside of Discord Embeds to save on character limits in the request body.
I personally don't care about statistics or anything like that - I only care about keeping my total character count to a minimum.
Often times, the same links will be sent in my Discord messages (i.e. a link to a homepage, or a link to a specific user's profile) - and in those cases, I would rather it return the shortlink that already exists for those links instead of creating a new one.
My preference is to:
Does this already exist and I've just missed it? Is this something the project would be open to supporting?
The text was updated successfully, but these errors were encountered: