Everyone's tired of the standard test values you make up by writing English words in hex, like 0xDEADBEEF, or 0xDEFACED, or 0xC0FFEE.
But if you're writing in C or C++, you can get a few slightly less familiar ones by making use of the U, L, UL, LL or ULL suffixes on integer literals. 0xBA5EBALL, 0xDAFF0D1L, 0xDECE17FUL.
Or maybe you think those are still boring? Then just stick with 0xDULL.
Unfortunately, we no longer care much about architectures that trap on unaligned reads, so one of the original criteria for generating such numbers (that it should be odd so that it will trap if dereferenced) no longer applies. I guess that still works if you treat it as a pointer to a floating-point vector, because many vector units don't support unaligned access.
I remember reading the list of criteria (I think there were five or six of them) but don't recall where.
If I remember the criteria went something like this:
* Large and negative when treated as an integer so it will get caught by bounds checks * Recognizable when dumped in hex * Trap when dereferenced * Trap representation when treated as floating-point (e.g., SNaN) * Trap when used as a jump/call target (e.g., by being in a non-executable memory range)
@wollman hmm, so what hex value _does_ meet all those constraints? If you want it to be a negative integer and an IEEE754 SNaN then it has to start with 'ff', so _none_ of the wordplay-based constants in this thread will do. 0xDEADBEEF, for example, is a perfectly sensible finite float value representing -6259853398707798016.
0xDECAF is another prime word made of nothing but letter-type hex digits. If you allow 01579 to stand for OISTG then there are longer ones: 0xBEA71F1ED, 0x5AB07A9E5, 0x50C1E71E5, 0x57EADFA57 are all prime.
Among the extra words you get from optional trailing U or L/LL, 0xDAFF0D1L is prime, and is the largest I found. Second largest is 0x7A57EFUL.
And 0xDULL isn't the smallest, because of course there's 0xBULL too! I didn't spot that one. Epic 0xFA1L.
No joke, I use 0xAA55AA55 since it also stands out in binary as well (alternating run of on/off bits) in the rare case I'm working at that low a level.
I also like to pretend that it would upset that one 10baseT hub still in service out there (CSMA/CD jam signal)
Stop using generative AI for fun - it wastes water. When there's no more drinking water in 15 years, you will regret all the weird time you spent with your AI bot buddy and wish that instead you spent that time protesting late stage capitalism, because you will be very thirsty.
they should let me set my timeline to forward chronological order, i want the first post on my home page to be some bullshit that gargron said in 2016 like it was always meant to be
Kid1 asked me where we go after we die, and I answered "where do knots go when they're untied? The string is still there". It seems to have stuck with him and I think the place where untied knots go is now part of our family mythology.
Furries need to spend less time going or trying to go or complaining about furry conventions they don’t like and more… just going out and meeting specific furries that they actually want to meet or hangout with (with the other’s approval obviously).
Been kinda pushing for this for a long while (2013-15-ish? The beginning of the end of furry cons.) but it’s like pulling teeth. Don’t want to impose or weird folks out.
Gaz, Emejn and I went and fursuited at Stonehenge for the summer solstice. Gaz unfortunately had to leave early, which is why there are no photos of him enfoxed, only Emejn (otter) and me (husky).
Hmm, oh well, no Rambly Raccoon for me. After an 8 GB download, Indigo Park (which I only heard about a few hours ago but is free and looks fun) won't do anything but show a loading screen with a sketched raccoon popping up and down in the bottom left corner. It uses a lot of CPU time and spools up the fans in my laptop, but I've had Steam verify (and fix) the files, and left it on the loading screen for nearly 15 minutes without anything else happening. The support site link in Steam doesn't work, can't find anything much else, so… oh well, it was worth a shot. Maybe I'll just find a let's play of it.
I think this *may* be enough info to get the point I was trying to make, though it unfortunately validated another point of concern I had with reachability I have with fedi. As cool as the platform(s) is, I just can't seem to get the reach on the things that actually matter, and I'd prefer to get the reach, instead it's always my shitposts that get the numbers. I don't really care much for numbers and interactions most of the time, but there are cases where I very much care about it, and getting data like this is very much one of them. I hope this changes, but unfortunately with the amount of people I see sticking with Shitter no matter how much Elon pile drives it into the ground, I honestly don't see that changing any time soon. Sorry for the mini rant, guess it just kinda stung a little.
PSA for artists still using X. Stop announcing shit exclusively on X.
And if you still announce things on x, always include the link in every post, because users without x accounts can't see any posts without direct links, or even browse your profile to find *litterally anything else about you*.
Nobody wants to use that platform anymore and the only thing keeping most people I know there are announcements from creators, that's it.
Visibility on the platform has gotten so garbage, whenever someone posts something from x that doesn't include a direct link to the thing its talking about; we have to send out search parties to dig up the links so the announcement is actually announcing something its possible to *find.*
The official video for “Never Gonna Give You Up” by Rick Astley. The new album 'Are We There Yet?' is out now: Download here: https://RickAstley.lnk.to/AreWe...
Since people seem to be pissed off at me today about private messages for some reason, now is as good a time as any to repost my blog on how to test Faraday containers, which also, inexplicably, seems to infuriate a small set of people.
And speaking of things I've done that infuriated people, nothing prepared me for the absolutely unhinged fury this paper, published in the IEEE Security and Privacy journal, unleashed in the US locksmithing community. They don't, it turns out, appreciate it when irresponsible outsiders like me infringe on their turf or reveal weaknesses in their products.
It was utterly wild. A coven (I assuime that's the collective noun) of angry locksmiths doxed me ("let's see what kind of lock he has on HIS house"), and a trade publication called The National Locksmith ran monthly guest editorials about what a rotten guy I must be.
When I moved to U. Penn the following year, the in-house locksmith wrote regular letters to the dean warning about my bad character to try to get me fired.
I didn't react to this the way they hoped. Every time the locksmith guy complained about me, I'd give a talk to the undergraduates on the relationship between cryptography and physical security, using my master key attack as an example.
Which would, of course, further infuriate the locksmith.
Eventually I figured it was time to move on, and wrote a paper about how safecracking works and its relationship to security metrics. The locksmiths appreciated it every bit as much as I had hoped.
Back and still alive after yesterday's #BFD. I enjoyed myself and got to "move to the music" with old and new friends. And yes, I'll keep the flower chain.
The upside is that the burial will be cheap, as you just need to hand out shovels and Ukrainians will dig a hole so deep that they can hand him over to Satan in person.
I wish people would read more about Long COVID. People think it's rare; it's not. Or they think the healthy and the young can't get it; they can.
"I want people to know that I'm not lying, [long COVID] is real and can happen to anyone. I want people to know I'm not just trying to get out of doing school or sport — I wish I could do sport … I wish they understood I am just trying to save myself from being stuck in bed in pain for days afterwards."
They're losing their formative years to this debilitating disease. But for too many children with long COVID, finding help is a frustrating and traumatic process that leaves them feeling isolated and invisible.
TIL: Scaleways’ instance metadata service requires your source port for the HTTP request be <1024 and
This is actually a big security improvement over everyone else’s because now your instance metadata (potentially containing secrets or credentials) is only accessible by root on the VM and not by any random process, and
This is just about the only valid use of the root port restriction I’ve seen since 1990
![Screenshot of the tumblr post at https://www.tumblr.com/sailorbryant/149429272264/a-fragile-sort-of-anarchy-bad-news-our-boss.
OP by a-fragile-sort-of-anarchy:
Bad News: Our boss locked the keys inside the building.
Good News: We didn't have to wait around for a locksmith.
Bad News: My boss finds it very concerning that I know how to pick locks, and tried to unlock my Tragic Backstory™. I was too embarrassed to admit that the reason I learned was because, at thirteen, I figured that was the kind of skill that would impress cute girls.
Good News: A cute girl saw me do it.
Bad News: It was Maggie, and since she's already seen me fall out of several trees, cry because I saw a fawn that was just too damn small, and knows I can ride a unicycle, she'll never think I'm cool no matter what I do. It's too late. She knows.
[End OP]
Reblog reply by sailorbryant:
There are million dollar blockbuster movies that were less entertaining than the rollercoaster this post just took me on.](https://floof.org/photo/preview/640/503535 "Screenshot of the tumblr post at https://www.tumblr.com/sailorbryant/149429272264/a-fragile-sort-of-anarchy-bad-news-our-boss.
OP by a-fragile-sort-of-anarchy:
Bad News: Our boss locked the keys inside the building.
Good News: We didn't have to wait around for a locksmith.
Bad News: My boss finds it very concerning that I know how to pick locks, and tried to unlock my Tragic Backstory™. I was too embarrassed to admit that the reason I learned was because, at thirteen, I figured that was the kind of skill that would impress cute girls.
Good News: A cute girl saw me do it.
Bad News: It was Maggie, and since she's already seen me fall out of several trees, cry because I saw a fawn that was just too damn small, and knows I can ride a unicycle, she'll never think I'm cool no matter what I do. It's too late. She knows.
[End OP]
Reblog reply by sailorbryant:
There are million dollar blockbuster movies that were less entertaining than the rollercoaster this post just took me on.")
Unfortunately, we no longer care much about architectures that trap on unaligned reads, so one of the original criteria for generating such numbers (that it should be odd so that it will trap if dereferenced) no longer applies. I guess that still works if you treat it as a pointer to a floating-point vector, because many vector units don't support unaligned access.
I remember reading the list of criteria (I think there were five or six of them) but don't recall where.
If I remember the criteria went something like this:
* Large and negative when treated as an integer so it will get caught by bounds checks
* Recognizable when dumped in hex
* Trap when dereferenced
* Trap representation when treated as floating-point (e.g., SNaN)
* Trap when used as a jump/call target (e.g., by being in a non-executable memory range)
@wollman hmm, so what hex value _does_ meet all those constraints? If you want it to be a negative integer and an IEEE754 SNaN then it has to start with 'ff', so _none_ of the wordplay-based constants in this thread will do. 0xDEADBEEF, for example, is a perfectly sensible finite float value representing -6259853398707798016.
Perhaps they looked in a Welsh word list!
@robinhouston checking a dictionary:
0xDECAF is another prime word made of nothing but letter-type hex digits. If you allow 01579 to stand for OISTG then there are longer ones: 0xBEA71F1ED, 0x5AB07A9E5, 0x50C1E71E5, 0x57EADFA57 are all prime.
Among the extra words you get from optional trailing U or L/LL, 0xDAFF0D1L is prime, and is the largest I found. Second largest is 0x7A57EFUL.
And 0xDULL isn't the smallest, because of course there's 0xBULL too! I didn't spot that one. Epic 0xFA1L.
Search for English words that have a hex representation as a prime number
GistNo joke, I use 0xAA55AA55 since it also stands out in binary as well (alternating run of on/off bits) in the rare case I'm working at that low a level.
I also like to pretend that it would upset that one 10baseT hub still in service out there (CSMA/CD jam signal)
Content warning: mild sexual humor