Another year, another blog post. I'm closing out 2022 by channeling my inner
@fasterthanlime with a deep dive into the basic TFTP protocol and my approach
to parsing packets in Rust. Please enjoy!
https://tuckersiemens.com/posts/parsing-tftp-in-rust/
#rust #rustlang #rustdev #tftp #networking #parsing #nom #blogging
A sad story about User Agent strings.
https://miketaylr.com/posts/2022/12/how-the-IE-11-ua-string-broke-sites-in-firefox.html
Just had a fantastic virtual #LANParty with some high school buddies. #JustinCON 2022 baby, one for the books.
Whoa, I didn't know rustdoc had an (unstable) "scraped examples" feature. #rust
See it in action on the aws-sdk-s3 docs: https://docs.rs/aws-sdk-s3/latest/aws_sdk_s3/error/struct.HeadObjectError.html#method.unhandled
Docs: https://doc.rust-lang.org/nightly/rustdoc/scraped-examples.html
I'm not sure why a container-based build isn't the default recommendation on the dd-wrt or OpenWrt forums. But here's mine:
It's my first container-based build environ. I'm not sure what other folks do, but I'm mounting the source dir in the container (with -v), changing to that dir (with -w), and running the compiler. When that's all automatic via make, it's seamless and easy. So I think I like it.
Cross-compile build environs usually screw up my normal host environ more than I like, and compete with each other, so I'm putting it in a container.
Never heard of anybody using that before. Fortunately, the algorithm for generating balanced ternary basically worked.
Nice ending to #AdventOfCode - I'd seen balanced ternary before, but never had to figure out an algorithm to generate it. Then the complexity got bumped just a little for #BalancedQuinary.
In the cold light of morning, I was able to improve that visualization for #AdventOfCode Day 24 a lot. Different shades for storms makes it a lot less "flashy"
#AdventOfCode Day 24 - very pleasant. Especially after breaking the brain on cubes and such. Feels like the end of a long run where you are just cooling down and finishing.
Maybe I'll go for a run now!
And todays #AdventOfCode was fun but (part 2) extremely painful.
That's a pretty great little poem I think, and the prompt I used was exactly as stated above starting with "please". Then after the first two stanzas I asked, "Please continue it further.", and it wrote the rest.
#ChatGPT seems to know about recent world events here - but I did tell it to consider Twitter "out of control". I did not explain what a social network was, and I did not capitalize Mastodon in my prompt, but it seems to know both.
There once was a social network grand
Called Mastodon, run by a man
#JohnMastodon was his name
And he ran things with great fame
On his platform, all were welcomed, not banned
Twitter, on the other hand
Was run by a man named Elmo
And on his platform, chaos would flow
The tweets flew fast and wild
As the rules and order were reviled
On Twitter, all were free to go.
But Mastodon was a different kind
Where users could speak their mind
#JohnMastodon led with care
Creating a platform that was fair
For all who wished to share and find
Twitter, on the other hand
Was a platform out of control
Elmo just let it unfold
As chaos and drama were the norm
On Twitter, it was a storm
But Mastodon remained calm
So if you want a place to connect
Where you can share without regret
Where the rules are fair and just
Mastodon is a must
But if you want to watch the world combust
Twitter's the one, without a doubt
But just be prepared to be left in doubt
As to what's real and what's not, no doubt.
Never got a response to this one, perhaps that's not how the bot @multiset works. I did go to chatgpt and got a response...
Computer science guy, electrical engineer, US Air Force officer, jogger, likes teaching programming, aka KC0BFV.
Likes programming in: Rust, Python, JavaScript, C
Reluctantly uses: Roku's BrightScript, C++, anything