Implement the new simplified/improved algorithm

[aradalvand]

sqids/sqids-spec#11

[LeaFrock]

I see the changes in unit tests. I wonder whether v3 will output a different id for a pointed int number with v2, even though the alphabet and other configs are all the same?

[aradalvand]

Hi @LeaFrock, actually yes, v3 outputs different IDs than v2 even with the same configurations, because as you can see in this PR, the algorithm has been modified, which brings about a number of major improvements — you can learn more about those in sqids/sqids-spec#11 — but it does result in a breaking change.

Most Sqids ports (this one being an exception) were on pre-release versions, so it made sense to do this now. Though we don't plan to introduce any more breaking changes in the algorithm; this one, however, was very much justified because it fixed a few important issues the previous version of the algorithm had.

[LeaFrock]

Well, it sounds reasonable, though it indeed makes some troubles to me. We've already been using this library in our production.

we don't plan to introduce any more breaking changes in the algorithm

Hope so. And I also hope Sqids releases a stable(rather than pre-release) version for production soon. Thanks for your reply!

[aradalvand]

Well, it sounds reasonable, though it indeed makes some troubles to me. We've already been using this library in our production.

Understandable. Sorry for the inconvenience. I didn't actually know whether anyone was already using the library in production but I assumed it's probably not that many people, since it has been only a few weeks since the library was published; hopefully the transition goes smoothly for you.

[LeaFrock]

I imported HashIds in the last project, and it has been running well since 2021. Recently we create a new project and at the very first time I want to choose HashIds again.

When I'm going to check if there's a new release on the website, I'm surprised that HashIds rebrands to Sqids. Therefore ... you know the rest of the story 🤣 .