Hashids.java
brain
Hashids.java | brain | |
---|---|---|
31 | 9 | |
1,012 | 1,530 | |
0.3% | - | |
0.0 | 7.2 | |
6 months ago | 18 days ago | |
Java | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Hashids.java
- Hashids: Generate short unique ids from integers
-
Auto Generate Sequential UIID
You basically want Hashids but sequential? Why not simple convert a base 10 (0-9) number to hex? (0-F)
-
Features I'd Like in PostgreSQL
I found hashids [1] to be a great compromise between integer ids in the database and copyable non-enumerable strings on the client.
[1] https://hashids.org/
- Short, friendly base32 slugs from timestamps
-
We Chose NanoIDs for PlanetScale’s API
I wonder how this might compare to just storing regular autoincrementing ints in the database, and converting to/from hashids (https://hashids.org/) at the edge. It eliminates the collision concern and stores more compactly at the cost of a tiny amount of encode/decode when processing requests. You’d want to push it down as close to the database layer as possible to avoid inadvertent int ID leaks; I added native hashids support to clickhouse but I’m not sure what other database support might entail.
-
How can I generate truly unique slugs?
Since hashids are not really hashes and are not secure at all this is not even achieved. Hashids can be easily decoded without the salt by a simple brute-force attack described by the authors of hashid themselves right on their website: https://hashids.org/
-
How to handle id-based routes with UUID
You don't necessarily need to use UUIDs. You could use something like Hashids to generate random strings from your sequential IDs in a reversible way, so that users can't predict what their values will be, but you can decode them as needed.
-
All of my database models have id replaced with UUID4s. Is there any risk to using these in URLs?
You should not use UUIDv4 as a primary key. You can use normal int values and then use hashids to make them safe for URL. UUIDv7 might be good to use as well once they are more widely supported as well.
- What’s Django’s argument for using 64-bit int as default pk over uuid. Can anyone point me to something I can read?
- Library for generating string IDs from number IDs
brain
- The UX of UUIDs
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
for those researching this topic, I keep a list of these UUID/GUID implementations!
https://github.com/swyxio/brain/blob/master/R%20-%20Dev%20No...
-
Things I did before app launch and what I wish I have done
here are my notes as someone who studied this stuff extensively for my book launch (just crossed $200k revenue) https://github.com/sw-yx/brain/blob/906dbc6fd6d22fa69968ebc6...
in generally for OP's stuff i would disagree on launching on product hunt first. PH is a giant pyramid scheme where people just compete for the #1 badge each day. what the most successful products do is launch everywhere else first, and then after a few months email their happy customers to support them on PH. this is why you are #20 because you didnt study the game
- Digital Gardening
- UUID list: list of unique id implementations, concepts, and resources
-
Plan B for UUIDs: double AES-128
I've been collecting all my notes on UUIDs here https://github.com/sw-yx/brain/blob/master/R%20-%20Dev%20Not... in case it is helpful to anyone
-
New UUID Formats from IETF
(poster here)
these formats are not new new, but are still pretty new.
the context is i keep a list of uuid impls and knowledge for my own reference. posted this up today simply because I got a PR from some subscribers https://github.com/sw-yx/brain/pull/36
- A second brain in the wild
-
Bottom-Up Idea Exploration
Putting together this massive effort involved pulling in notes from 18 months of covering Concurrent React by myself, in particular studying prior art from Rodrigo Pombo in cloning the API from scratch. You can check out his talk here to contrast what he did vs me.
What are some alternatives?
BLAKE3 - the official Rust and C implementations of the BLAKE3 cryptographic hash function
Synaptic.js - architecture-free neural network library for node.js and the browser
uuid7 - UUID version 7, which are time-sortable (following the Peabody RFC4122 draft)
natural - general natural language facilities for node
Guava - Google core libraries for Java
typeid - Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
JGit - JGit project repository (jgit)
deeplearn.js
Embulk - Embulk: Pluggable Bulk Data Loader.
ConvNetJS - Deep Learning in Javascript. Train Convolutional Neural Networks (or ordinary ones) in your browser.
JADE - a pug implementation written in Java (formerly known as jade)
typeid-go - Go implementation of TypeIDs: type-safe, K-sortable, and globally unique identifiers inspired by Stripe IDs