This link shortener service. It's nearly good enough for public testing.

Finding a good domain name, though.... 😅

Sometimes human stupidity still surprises me.

Today I was able to stop the release of a ticket at the last moment that intended to put urls WITH A SECURITY TOKEN TO ACCESS USER DATA through a link shortener.
Some PM assumed that it would be a reasonable course of action to map an url secured via jwt through to a 4 character, countable, base64 string so that we don't have to send multiple sms if they contain this url. I can accept that the implications might slip through one person but the fact that this was put into a ticket by a pm, prioritized by PO, estimated by an entire team, implemented by a professional developer, reviewed by a senior and then scheduled for release without anyone asking themselves if there might be a reason for a security token to be long, that one shocks me.

Google has a really strange idea of what a rate limit is.

I’m trying to feed a few hundred URLs into the link shortener service. Docs say “1m a day, 1 req per second per user.”

No problem. Put a 1.2s sleep between hits.

Almost to the end... 403 rate limit exceeded.

(╯°□°）╯︵ ┻━┻