oddities with ballpark values

I think you're giving them way too much credit. They just don't seem all that computer savvy to me. How many of you play the windows version of the game?

All I know is, besides the boards which are full time non-secure http, I have noted sporadic dropouts from secure http (https) during the following actions:

- saving draft list
- saving lineups
- saving settings

Not all the time, not even a majority of the time. But sporadically and infrequently I have received browser notifications on it. Maybe it is just me. Who knows.

In the 21st century, there is no reason for this to ever be the case except on an internal-only facing network.

Combine all this up and I am doubly unhappy with the lack of transparency that Nev and others have requested for years. I was not around since ATG I, but my first game night played here was Oct 18, 2004, and my first ATG try was ATG III.
I have always been only an occasional player so did not get too involved.

For perspective, I can't say there was a good ol days either. Bernie Hou was accessible 24/7 and a good guy (didn't he even go on the B.o.b.b.y vegas trip?), but he occasionally ran out of bubble gum and sometimes TSN would have things mucked up for days with no results. So, they have come a long way for what this is, but transparency was needed then and the weekend of weather effects shows it is needed now.

I know they have a proprietary product that is an unequaled game engine, but at least put an asterisk and point to what rule that was invoked. Doesn't have to show the mechanics under the hood.

This is important, FrankieT explains it well. I'm not a techie, so correct me if I'm wrong -- but secure issues are inherent with our team settings, meaning someone who is especially ambitious and knows how to do this hacking, can scan team settings, lineups etc. That's not tolerable, unforgivable.

Cheers Hack. Yeah, I have to caveat it as I said because what happens at my client isn't necessarily an issue on the distant end.

But the possibility exists with a few "ifs"

If a stream is unsecure http,
and if the stream is being actively monitored,
and if the stream is captured,
and if the stream can be understood (this is not trivial and not something that you can do manually),
then yes the unsecure data stream with that particular site could be intercepted if someone had the desire to do so.

With the boards, as long as you aren't entering any login creds or anything, it really doesn't matter too much. Is just odd.

Thank you, Frankie. Sooo, not too concerned about our boards, for obvious reasons of diatribe amok, more concerned about teams in play and how their settings could get hacked. You've described it well. Holy cow!

Again though--it has only happened a few times and it might be my end, so I am not saying they have an issue. But in the context of some other stuff, it was odd to me.

I mean--the game site is secured. So you could enforce https-only through your browser and see if any hiccups.

Theoretically, I am not sure what would cause a hiccup on an https site though. Maybe a redirect to an insecure area and then back to the secure area? I don't know. Could very well be my own client.

The reality is that ALL of us were impacted. Every. single. game. At least on Saturday/Sunday (and I happen to think as far back as last Thursday, but can't prove it). They could probably comp EVERYONE a credit or two; but for as many wronged parties as there were, there were also accidental beneficiaries, which is my point.
...
The least that SOM could do is offer every active owner a free credit or two by way of apology; but I don't see any mechanism for them to discern which of us are deserving and which of us are not.

Well put. To me, the real issue is not the Ws/Ls. I realize it could be for some--understandably--because you can't unscramble the egg equitably.
The issue is the customer discovered the significant problem with the product.
Like if I have to run my tea through a lab analysis to ensure it doesn't have dandelions. That should be done before I get my tea. OR--put it on the label.

But I am at a loss for how the weather effects could randomly be switched on. I would just like a more honest and complete explanation. I value that more than a credit.

Well OF COURSE it was BB Daily, or NBJFB,as I've called it from the get-go (NOT Bill James Fantasy Baseball)

As far as the coding and "how does that happen" questions ... I can easily see how a feature that is normally set to "off" was turned "on" for the deployment of the 2022 Daily Card Set (as SOM has claimed). I think they reprogrammed the start-up code at the beginning of games that determined what the weather would be and forgot to filter it by player set; thus applying it to ALL SETS on accident.

It is plausible that this was built into the game engine as a launch sequence step, so it was not considered wrong when they tested it, because they only tested in on the Daily Game card set, but when they implemented it, they missed a filter/layer and incidentally impacted all of us.

Kind of seems like maybe don't release new game code on Friday and then leave for the weekend though.

Well OF COURSE it was BB Daily, or NBJFB,as I've called it from the get-go (NOT Bill James Fantasy Baseball)