The argument for using a code auto formatter:
All code looks the same, updates to the formatter are applied universally.
The argument against using a code auto formatter:
No! NO! NOOOOOO. I am special. I’m different. I am very smart. MY CODE HAS TO LOOK DIFFERENT THAN THAT.
While reading some postfix documentation I came across this passage:
New queue files are created with names such as 3Pt2mN2VXxznjll.
These are encoded in a 52-character alphabet that contains digits
(0-9), upper-case letters (B-Z) and lower-case letters (b-z).
For safety reasons the vowels (AEIOUaeiou) are excluded from
the alphabet. The name format is: 6 or more characters for
the time in seconds, 4 characters for the time in microseconds,
the 'z'; the remainder is the file inode number encoded in the
first 51 characters of the 52-character alphabet.
First off, thank you to whoever took the time to write this down.
Let’s step through this:
We know what the queue IDs will look like:
New queue files are created with names such as 3Pt2mN2VXxznjll so far so good.
We know their encoding
These are encoded in a 52-character alphabet. Hm, a 52 character alphabet is a bit weird is it just upper and lowercase letters? As we see next, it’s
digits (0-9), upper-case letters (B-Z) and lower-case letters (b-z). Starting from B is slightly weird too. And now we see why
For safety reasons the vowels (AEIOUaeiou) are excluded from the alphabet.
For safety reasons the vowels AEIOUaeiou are excluded from the alphabet.
Aside from being the same alphabet as an early 2000s startup name generator why are these vowels unsafe? Why can we can keep Y and y? Is it the part time vowel status?
Moving on to the rules for encoding a message:
- 6 or more characters for the time in seconds
- 4 characters for the time in microseconds
- the remainder is the file inode number encoded in the first 51 characters of the 52-character alphabet
What time? Unix time? System time? Just calling gettimeofday()? It’s gettimeofday. A quick aside: Postfix doesn’t maintain any sort of source control repository and just distributes code via tarball o_O.
On to the best part
the remainder is the file inode number encoded in the first 51 characters of the 52-character alphabet.
And now we throw out another one of the characters from our 52 character alphabet and only use the first 51 for whatever is left after getting the time. The reason for this is that the time/inode separator is ‘z’.
After digging through all of the configuration references and source code I’m left wondering, wait…but why?
If you’ve ever thought about trying out Rocket.chat, don’t bother. I’ve done it for you. Here’s the UI: https://i.heliost.at/Opalstack_2019-03-16_18-08-23.png
“What’s your official GDPR policy?”
My official policy is: https://www.youtube.com/watch?v=VYOjWnS4cMY
Portland: We need to make residential streets safer for pedestrians and cyclists. What can we do?
Me: Widen the roads and add a shoulder so street parking isn’t so dangerous?
Me: Widen the roads and add sidewalks on all streets?
Portland: We’ll decrease the speed limit by 5 mph.
I really hate the school district’s policy of “we’ll announce school closures, 1 hour late starts, and 2 hour late starts by 6 a.m. on the day”.
Since the sun doesn’t come up until 7:30 a.m. I’m pretty sure the road conditions aren’t going to change between 22:00 and 06:00.
It’s been a really interesting day.
Mobile phone insurance is such a scam: $15/month for a $700 phone. I pay $17/month for full coverage insurance on $10,000 worth of Apple hardware that includes ‘accidents’.
CenturyLink is just wrapping up a 40+ hour nationwide outage/degraded service event that took down some 911 services. That’s a post mortem I sure as hell want to read.