Of course there was a breach of some kind.  Sudden password reset requirements along with disabling the ability to promote user to admin status in Blox.  There's not much else it could be.  

The question of course is what exactly happened.  It feels like an insult that TN hasn't felt an obligation to share some details with us.  Our entire operation relies on Blox and TNCMS -- a commitment that requires an enormous amount of trust in a partner company.  Not hearing anything from TN is likely as bad or worse than the initial incident.

Or put a link in the breaker with a line like "updated story here" and go ahead and use the second URL because it gives you the ability to push a second Facebook promotion without getting dinged for double posting one URL. 

Because of course we should let our workflow be governed by Zuckerberg's *&%$! algorithm.

This is critical.  I can't get by without the traffic I get from FB instant articles, but I can't actual execute my digital strategy with a gaping hole in my paywall. 

There are a ton of different improvements, refinements and modifications I'd like to see in Blox, but none of them are as important as this.

FYI, you can also insert an html <style> block into the subhead of the form field, something like

<style>

.container .jumbotron h1 {text-shadow: none;}

</style>

would work.  It's also a totally ugly hacky excuse for a fix, against every version of web dev best practices, and something I would never, ever do when I was in a hurry.  Nope, never...

It'd be great to see something like this, but I'd prefer seeing it as source agnostic.   We pull in election results programatically and by hand depending on jurisdiction and don't use AP results at all...but I'd love to see a flexible front end we could just plug json, xml or csv into.

Added to template

function getUserDetails(){

                var userData = {'loggedIn': false, 'screenName': 'none'};

                    if (TNCMS.User.isLoggedIn() == true){

                             userData.loggedIn = true;

                              userData.screenName = TNCMS.User.getScreenName();

                       };

               return userData

};

OMG, this!  The notifier  app is overall a big improvement, but this drives me nuts.  Our standard workflow was to have stories written, tagged, and socializ-ed before editing, with the do not publish flag checked.  Way more efficient than what we have to do now because the notifier defaults to draft.

I'll second what Kevin said about the existing look and content of our emails.  Not necessarily because it's the best option, but it's what my boss wants :) 

In our case the email scrapes a template on our site that includes an image and a headline along with some branding.  All of it is a link to the asset we've flagged as breaking.  It would be great to replicate this functionality in the notifier -- would result in fewer after hours calls of "I can't remember how to send a breaking news email" at least :) 

I think you may want to run through it at least once more to see if it's not just some edge case that's affecting Robert and I (which would be the worst of all possible worlds, but totally could happen, especially with google's frequently undocumented breaking changes...)

And it'd be good to let readers sign up for notifications when they register for an account -- while we've got 'em in the box clicking mood :)  

I've got a way to do this if you've got Google Analytics and are willing to play with a bit of code.  Email me at aholder AT SIGN yakimaherald DOT com and I'll hook you up.