Your JoeDog has been following the President-elect on Twitter for quite some time. He’s a Howard Stern fan and Trump was part of the Howard Stern universe. Then something unexpected happened to this frequent Stern Show guest. He won the presidency. Yep, saw that coming….
So while it’s now possible that a tweet from atop a gilded toilet could touch off a nuclear holocaust and get us all killed, there another more awesome possibility. See, Your JoeDog’s greatest disappointment was his exclusion from Richard Nixon’s Enemies List. He was very young when Nixon left office but that guy was assholish enough to put a child on his Enemies List. It could have happened! Sadly, it never happened. Now according to news reports, Trump blocks people from his Twitter feed. That’s the contemporary equivalent to an Enemies List. Could Your JoeDog get himself blocked???
Now anyone can get on the Presidential Twitter feed and throw some F-bombs and get himself blocked. I was determined to play it clean. Full-frontal snark! I wanted blocked for getting under his skin, like Nixon’s enemies got under his. So how’s that effort going? Sadly, not so good….
It probably wasn’t an intern who liked that tweet. This appeared in my notifications while Trump was in the midst of a Tweet storm. He was probably scrolling replies and read the first part of a compound thought. “You won the Electoral College by a landslide…” LIKE “… if by ‘landslide’ you mean ‘one of the all time slimmest margins’.” Attention to detail isn’t a trait Americans look for in a President.
You can follow Your JoeDog’s attempts to get blocked by the 45th President @jeffyguy
Well at least it wasn’t Runner1234, amirite?
I do. Sorry been moving. Just in case Milia hasn't gotten it to you let:
I don’t think 2017 is going to be much better….
Remember when Jeb Bush was giving a sad and lonely speech on the campaign trail? He made some stupid point and the audience sat stone-faced as he stood there awkwardly. After what seemed like an eternity, the young Bush hopeful implored his audience to “Please clap.” That’s Your JoeDog right now. But instead of applause, we need you to test the latest siege release candidate. Siege-4.0.3-rc2
We know what you’re thinking: What’s in it for me? Exciting new features, that’s what! Really? Like what?
Continue reading Please Test
Well Your Linux distributors should be happy now. For years they’ve been bugging Your JoeDog to eliminate his convenience library. Linux distributors don’t like convenience libraries which is odd because they’re very convenient. With this release, we move that code from lib/joedog into src.
Valery Levental fixed and improved issues involving the data URI scheme, chunked transfers and zero-length content.
Danylo Hlynskyi improved the man page documentation.
Somebody sent Your JoeDog a patch that he promptly lost. If that person could resend it, he’d very much appreciate it…..
UPDATE: Your JoeDog found the patch. It’s a fine piece of work by Valery Levental. The patch tested out and was submitted to version control. In all likelihood, we won’t release a beta distribution. You can grab the code off github.com.
- Fixes our improper handling of the Data URI scheme
- Fixes our improper handling of HTTP 1/1 responses containing Content-Length: 0
- Improves our handling of chunked transfers
- Further optimizes the http header parser.
Some siege users have reported hangs with version 4.x.x This update may fix those conditions (although in some cases, the problem was tied to a specific version of glibc.)
Your JoeDog is pleased to announce the release of siege-4.0.1.
This release contains no recognizable goodies for you to play with but it will probably reduce the number of times you curse at us. It is primarily a bug fix.
You knew that was coming, right? Some of you may have put off the move to 4.x in anticipation of the blessed 0.0.1 bug fix release. Well, here it is!
This release includes a patch by Niklas Hambüchen which improves the efficiency of chunked encoding reads. It also includes a patch by Warren Young which improves / fixes issues with cookie handling and expiration. Trent Oswald included additional default MIME types and V. Filanovsky added support for URLs longer than 4096 characters.
The release also includes several other minor bug fixes and documentation errors.
If you’re running version 4.0.0, then you should probably upgrade.
[SIEGE RELEASE: 4.0.0]
Good news, JoeDoggers. Siege 4.0.0 is finally out of beta.
While this release contains exciting new features, it’s built upon a major architectural overhaul. For most of you, these changes will go unnoticed but they will certainly make things better for Your JoeDog.
Did you ever look at code you wrote fifteen years ago and wretch? Large portions of this program invoked that reaction. Siege was originally written in 1999 and as such it contained large portions of code that were styled like we coded back in 1999, i.e., suckishly.
Your JoeDog still prefers C to C++ but that doesn’t mean he’s averse to object oriented design. In fact, he loves himself some objects. Just because you code in C doesn’t mean you can’t enjoy the benefits of OO design. Afterall, what is an object other than a thing that references itself? With Siege-4.0.0 nearly all code modules were reworked as objects. This makes debugging so much simpler which gives Your JoeDog a happy.
Who cares? What about the features?
- Cookie Persistence — It persists cookies according to directives set by the server. They are stored in $HOME/.siege/cookies.txt on a thread by thread basis.
- Color Output — Or more importantly, non-color output. Siege 4.0.0 allows you to turn off color output using ‘color = off’ in your siege.conf file.
- Cache Support — Siege has always had some cache support, but this version is more compliant with RFC 2616. See the documentation for more information.
[SIEGE: Release 4.0.0]
Your JoeDog is pleased to announce a new utility for your fun and games. This is a full-featured version of a perl script we wrote and which is now implemented in C. Introducing AJPing.
This program began life as a snippet which should pave the way for Apache JServ Protocol (AJP) support for siege. Since it’s very useful for checking connectivity and/or measuring the health of a servlet engine, we decided to release it as a fully functional utility.
AJPing supports both IPv4 (default) and IPv6. You can invoke the latter with a command line switch. Let’s take a look at this puppy in action, mmmkay?
Bully $ ajping -i6 -r5 ajp://ip6-localhost:8009/
--- ajping v1.0.1 to ip6-localhost:8009 ---
5 bytes from ip6-localhost (::1): seq=1 time=979 ms
5 bytes from ip6-localhost (::1): seq=2 time=257 ms
5 bytes from ip6-localhost (::1): seq=3 time=199 ms
5 bytes from ip6-localhost (::1): seq=4 time=235 ms
5 bytes from ip6-localhost (::1): seq=5 time=239 ms
--- ip6-localhost:8009 ajping statistics ---
5 packets sent, 5 received, 0% packet loss, time: 1909 ms
rtt min/avg/max = 199/381/979 ms
The first thing you’ll notice is the output looks a lot like ping. That was by design. AJPing sends and receives 5 byte packets and measures the round trip time in milliseconds. When the run is complete, it summarizes the transaction stats in the statistics section of the output.
[AJPing: Initial Public Release]