90 karma · joined December 4, 2020
Overall the degree to which information is being controlled right now is pretty alarming.
And as a general principle I don't like having all of my transactions logged and tracked. That's the same fallacy of "if you have nothing to hide, then submit yourself to complete tracking"
I honestly don't know, but I personally assumed the death threats came from people who simply didn't like that Parler existed in the first place.
ULID is 128 bits vs 64 bits for instagram id, so ULID is stored in a uuidfield but instagram id can be stored in bigint field.
There is some advantages of using the application code to generate the ID though (avoiding roundtrip to DB if need to use the ID afterwards), but I'm seduced by just offloading this work to the DB and being able to use bigint field to store the id.
As someone who is just about to commit to using ULID or an instagram-like bigint id generator, would you have any thoughts you could share on which may be better?
[0] https://instagram-engineering.com/sharding-ids-at-instagram-...
I've found ULID to be great for my purposes. Wonder if anyone else has tried using them too?