en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Server stats:

252
active users

#uuid

0 posts0 participants0 posts today

My favorite hobby: reading EDN spec and finding examples where practice diverges from theory.

E.g. did you know that

.1

parses as a symbol?

Or that

:/

and

:///

are both valid keywords but

://

isn’t?

Also this:

#uuid "f-7-1-a-8"

is a perfectly fine UUID.

Anyway, have a good weekend!

there seems to be a lot of excitement for #uuidV7 these days (timestamp-based). it's very cool, and a good choice if you're using the #uuid or #guid as a database key (to avoid fragmentation)

https://ntietz.com/blog/til-uses-for-the-different-uuid-versions/

i also really like
#ulid for this, and they can be converted to uuids/guids easily and quickly.

one thing i don't see many people talk about when they move to monotonically incrementing ids (like v7/ulid) is this: if you have a distributed database you will end up with poor balancing with these ids. not what
most people do, i guess, but it's something to think about.

ntietz.comTIL: 8 versions of UUID and when to use them | nicole@web

What would be your advice?

Am I ready to go live with a full-on production company, or what?

#Traversy style n all! Look at that!
:D

youtu.be/aHnDl0Mt36Y?si=yX_-WD

In all seriousness.

Maybe anyone struggling with understanding file and folder #permissions and the corresponding #CHMOD numbers to set your desired ---rwx--- options...

#UID #UUID
#ACP

Replied in thread

@timbray
“UUID should be represented by the "hex-and-dash" string format consisting of multiple groups of uppercase or lowercase alphanumeric hexadecimal characters “

Every time I’m handling uuids in code I need to remember to think about case. I have seen resource IDs in azure recently consisting of multiple uuids in the one resource ID string. where some UUIDs are in caps and others are lower case. *In the same ID string*. But if you were building that resource ID string to use in an azure SDK you would have to respect which UUIDs are in caps and which are lc otherwise it will not be useable. It’s an absolute nightmare.
because the standard allows both and some library code has not implemented the standard correctly, we get issues with case. #Azure #UUID