Deflate this!

Leave a comment

Got to see Bill DeCoste this week at DevNation and we relived some of our Superbowl memories. Here’s some pix

Ring ceremony was awhile ago, but I just love this picture.  The guy has 6 bleeping rings!

Deflategate is less probable and more like a maybe

1 Comment

Yeah, go read “About Me”…I’m a pats season ticket holder for 21 years.  I’m biased Honestly when I first got the report I was devastated.  I had been defending the patriots on message boards for 3+ months and felt duped.  Ready to hang up my gear and sell my tickets.  But, a funny thing happened.  I am constantly driving my kids somewhere nowadays and have huge downtime with nothing to do but read or listen to the radio.  This week, with this downtime I decided to read the report in detail.

Actual data more interesting than assumptions

  • The referee was unsure of what gauge he used to test the balls prior to the game.  He is pretty sure he used the Logo Gauge (gives higher reading, good for Pats), but Wells asked him if it was possible that he used the NoLogo Gauge (lower readings, bad for Pats), he said it was.  This can be read on top of page 52.  The Wells report often does this when recollections (or even written measurements) don’t line up with their predetermined conclusions.
  • If No Logo Gauge was used pregame, 3 Patriots Balls were LEGAL and in expected PSI range as explained by Ideal Gas Law.  page 113 of the report actually states this.
  • If the Logo Gauge was used pregame, the number of legal balls increases to 7.
  • Exponent Appendix states that wetness also effects PSI of balls, but it does not state by how much.  By reading their graphs, I’m guessing the effect is around 0.2-0.3 PSI.  More balls will pass if you take this into account
  • When the Patriots balls were tested also effects the measurements as the longer the balls are in the room, their PSI rises.
  • One ball was left out of the executive summary.  The intercepted ball.  Ironically the intercepted ball was legal and within the expected PSI.  See page 70 of the main report.  So, we know for certain that one legal ball was used during the game!
  • So, anywhere from 4-8 balls were legal.  Why would McNally only deflate some of the balls?  This was the biggest red flag to me.
  • The 2nd thing to look at is how much were the balls deflated from their expected value?  There were two balls way off, almost 1 PSI, but most of the others were within 0.15-0.5 (again depending on the gauge you use).  Does Brady really care about such a miniscule amount of PSI (0.15-0.5)?
  • Only 4 Colts balls were tested because the refs ran out of time.  This leads me to believe that the refs tested the Pats balls, then pumped up them up before testing the colts balls and the colts balls were in the locker room a whole 10 minutes before they were tested.
  • One of the colts measurements was swapped because Exponent assumed it was written down wrong.  This swapping helped with their conclusion.  Only 1 Pats ball was a full 1 PSI below its expected PSI.  Why wasn’t this ball thrown out?  Why is it assumed that every Pats ball was recorded and measured correctly?  Why did Wells override Walt Andersen’s recollection of which gauge he used?

Texts are damning, but are they?

I honestly believe the balls during the AFC Championship game were not deflated. However, the text where McNally calls himself the deflator in May 2014 before the season and how he isn’t going to ESPN yet is quite disturbing and leads anybody who admits it to themselves that there has been something  fishy been going on for years.  Still, the other texts shed some doubt on this assumption.

  • Page 77 talks about texts flying around during and after the Jets game.  Its clear that Brady was really pissed about the footballs.  Its also clear that NO DEFLATION OCCURRED during this game.  Jastremski talks how he tested some of the balls after the game and that they were at 16 psi.  Why didn’t McNally deflate in Jets game?
  • Wells report continually states in footnotes that many of the texts messages were recovered and that there are possibly missing texts in the flow of these conversations.  Can’t the Pats get the actual full text exchanges from phone company?  Rich Levine of CSNSE writes an article about thisDo full texts provide additional context we don’t know about?
  • McNally’s explanation of texts is that he was talking about getting tickets sold “done”.  Wells doesn’t buy it because you can easily sell them on the exchange.  Why not Wells?  Did you know that the Pats ticket exchange requires you to sell them at face value!!?  You can risk selling them for a lot more money on Stub Hub, but if the Pats find out, they can revoke your tickets.  If you are selling them like this, it would be stressful because losing your season tix would SUCK!
  • If Brady was ordering, hinting, or suggesting that McNally and JJ deflate the balls, why did he text JJ “You did nothing wrong.”

Not Cooperating? Or just avoiding harassment?

  • Wells complains that the Pats wouldn’t let him have a follow up interview with McNally to discuss the damning texts.  What he neglects to tell you is that he did not tell the Patriots’ counsel why he wanted to talk to McNally.  Since McNally already had been interviewed 4 times, and Wells wouldn’t say why interviewing him would be so important, Pats refused.
  • There was a report that McNally offered to speak with Wells again over the phone and Wells refused
  • Brady spoke to wells for 5 hours.
  • There were mulitple reports that the NFLPA advised Brady not to turn over his phone as it would set precedence.
  • Wells already had texts from Brady to JJ and Bird.

Obvious most of media didn’t read the report

When Wells decided to do a conference call with the media, any number of these people could have dived into any number of the holes I found in 1 day reading the full report.  They all asked superficial questions with no detail which proved to me none of them read the report beyond the executive summary.  Only Mike Florio of Profootbal Talk seems to have done his homework.  This is funny because he was one of the biggest Patriots detractors in the beginning.  What pissed me off the most is that not one Boston Globe report, Boston Herald reporter, nobody on WEEI, nobody ESPN, nobody on 98.5 Sportshub ever mentions the most glaring red flag and ironic part of the report: THE INTERCEPTED BALL WAS LEGAL!

Deflategate has soured me on football

Finally, this whole mess has really soured me on football.  For those of you who don’t know, I actually went to Superbowl 49.  My first (and last) Superbowl.  It was almost ruined by Deflategate, but Bill Belichicks Mona-Lisa-Vito press conference got me pumped up again and roaring and ready to fly to Phoenix.  Now my memories are soured and tainted because I know that I cannot share the Bucket-list experience with anybody outside of New England without being called cheater.  Irregardless of whether anybody actually cheated or not.  I’m seriously considering giving up my tickets after 21 years.  This week I’ve been a miserable bastard and I need to do some serious soul searching of why this whole thing bothers me so much and why I’m so vested in it.  Its just a game afterall…

HTTP Quote of the day

Leave a comment

“T]hose who do not understand HTTP are doomed to re-implement it on top of itself

I wonder how many of us have done this?  I know I did a few times when I first started writing REST-based services.

Keycloak 1.1.0.Beta2 Released: Adapters, Proxy, Wildfly Subsystem

Leave a comment

A lot of new features this release.

  • Tomcat 6, 7, and 8 adapters
  • Jetty 8.1, 9.1, and 9.2 adapters
  • HTTP Security Proxy for platforms that don’t have an adapter based on Undertow.
  • Wildfly subsystem for auth server.  Allows you to run keycloak in domain mode to make it easier to run in a cluster.

Hope to do 1.1.0.Final sometime end of January.  See for more details.

Keycloak 1.1.Beta 1 Released: SAML, Clustering, Tomcat 7

Leave a comment

(Copied from Stian’s announcement) Pretty big feature release:
  • SAML 2.0 support.  Keycloak already supports OpenID Connect, but with this release we’re also introducing support for SAML 2.0.  We did this by pulling in and building on top of Picketlink’s SAML libraries.
  • Vastly improved clustering support.  We’ve also significantly improved our clustering support, for the server and application adapters. The server can now be configured to use an invalidation cache for realm meta-data and user profiles, while user-sessions can be stored in a distributed cache allowing for both increased scalability and availability. Application adapters can be configured for either sticky-session or stateless if sticky-sessions are not available. We’ve also added support for nodes to dynamically register with Keycloak to receive for example logout notifications.
  • Adapter multi-tenancy support.  Thanks to Juraci Paixão Kröhling we now have multi-tenancy support in application adapters. His contribution makes it easy to use more than one realm for a single application. It’s up to you to decide which realm is used for a request, but this could for example be depending on domain name or context-path. For anyone interested in this feature there’s a simple example that shows how to get started.
  • Tomcat 7 Adapter.  A while back Davide Ungari contributed a Tomcat 7 application adapter for Keycloak, but we haven’t had time to document, test and make it a supported adapter until now.
What’s next?
The next release of Keycloak should see the introduction of more application adapters, with support for JBoss BRMS, JBoss Fuse, UberFire, and Jetty.
For a complete list of all features and fixes for this release check out JIRA.
I’d like to especially thank all external contributors, please keep contributing! For everyone wanting to contribute Keycloak don’t hesitate, it’s easy to get started and we’re here to help if you need any pointers.

Resteasy 3.0.9 Released

Leave a comment

I really want to thank Ron Sigal, Weinan Li, and the rest of the Resteasy community for having my back the last 5 months while I was focused on other things.  Thanks for your hard work and patience.  3.0.9.Final is a maintenance release.  There are a few minor migration notes you should read before you upgrade, but most applications shouldn’t be affected.  We’ll try and do another maintenance release in like 6-8 weeks.  Check out for download links, jira release notes, and documentation.

Keycloak 1.0 Final Released

1 Comment

After 1 year of hard work, the team is proud to release our first final 1.0 release of Keycloak.  We’ve stabilized our database schemas, improved performance, and refactored our SPIs and you should be good to go!  I don’t want to list all the features, but check out our project website at for more information.  You can find our download links there as well as screen cast tutorials on our documentation page.

What’s Next?

Keycloak 1.1 will be our integration release where we start bringing Keycloak to different protocols, projects, and environments.  Here’s a priority list of what we’re tackling

  • SAML 2.0 – by merging with Picketlink IDP
  • Uberfire/BRMS adapter
  • Fuse FSW adapter
  • EAP 6.x and Wildfly console integration
  • Tomcat 7 adapter
  • …More planned, but we’ll see how fast we can move before we announce anymore

In parallel, we hope to look into a few new features:

  • Internationalization
  • TOTP Improvements like allowing multiple token generators
  • IP Filtering

Older Entries


Get every new post delivered to your Inbox.

Join 742 other followers

%d bloggers like this: