presents
brain
presents | brain | |
---|---|---|
1 | 9 | |
7 | 1,530 | |
- | - | |
10.0 | 7.2 | |
over 5 years ago | 22 days ago | |
Go | 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.
presents
-
New UUID Formats from IETF
I’ve been working on a robust scheme for encrypted sequential IDs, which is done, including implementations in Rust, JavaScript and Python, pending just a smidgeon more writing about it and reviewing a decision on naming. You store an integer in the database, then encrypt it with a real block cipher, and stringify with Base58. I have three modes: one for 32-bit IDs, using Speck32/64 and producing 4–6 character IDs; one for 64-bit IDs, using Speck64/128 and producing 8–11 character IDs; and one hybrid, using the 32-bit mode for IDs below 2³² and the 64-bit mode above that, providing both a forwards-compatibility measure and a way of producing short IDs as long as possible. Contact me (see my profile) if you’re interested, or I’ll probably publish it in another day or two. Trouble is that I’ve been getting distracted with other related concepts, like optimally-short encoding by using encryption domains [0, 58¹), [58¹, 58²), …, [58¹⁰, 2⁶⁴) (this is format-preserving encryption; the main reputable and practical choices I’ve found are Hasty Pudding, which I’ve just about finished implementing but would like test vectors for but they’re on a dead FTP site, and NIST’s FF1 and FF3, which are patent-encumbered), and ways of avoiding undesirable patterns (curse words and such) by skipping integers from the database’s ID sequence if they encode to what you don’t want, and check characters with the Damm algorithm. If I didn’t keep getting distracted with these things, I’d have published a couple of weeks ago.
(I am not aware of any open-source library embodying a scheme like what I propose—all that I’ve found have either reduced scope or badly broken encryption; https://github.com/yi-jiayu/presents is sound, but doesn’t stringify; Hashids is broken almost beyond belief and should not be considered encryption; Optimus uses an extremely weak encryption.)
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?
uuid7 - UUID version 7, which are time-sortable (following the Peabody RFC4122 draft)
Synaptic.js - architecture-free neural network library for node.js and the browser
uuid6-python - New time-based UUID formats which are suited for use as a database key
natural - general natural language facilities for node
dart-uuid - Generate RFC4122(v1,v4,v5,v6,v7,v8) UUIDs
typeid - Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
vanity-uuid - Create "readable" UUIDs such as "5eedbed5-f05e-b055-ada0-d15ab11171e5" for all your UUID needs!
deeplearn.js
prototypes - Draft Prototypes and Tests for UUIDv6 and beyond
ConvNetJS - Deep Learning in Javascript. Train Convolutional Neural Networks (or ordinary ones) in your browser.
typeid-go - Go implementation of TypeIDs: type-safe, K-sortable, and globally unique identifiers inspired by Stripe IDs
Dannjs - Easy to use Deep Neural Network Library for JavaScript.