If you're missing the @CFMLNotifier feed: @CFNotifications has picked up the slack

G'day:
SSIA, really. Adam Tuttle just asked if I still did the @CFMLNotifier Twitter feed; I do not.

But there's the @CFNotifications feed which covers the same ground, and does a more polished job of it than I ever did. This new feed is managed by Stephen Walker, of @cfuser fame.

@cfmlNotifier now sending updates from the CFML Bloggers RSS feed

G'day:
Well the title pretty much sums this up: the @CfmlNotifier Twitter feed is now sending out status updates when coldfusionBloggers receives new articles:

(Adam Cameron's CFML Blog): @cfmlNotifier now sending updates from the CFML Bloggers RSS feed (http://t.co/RDkdWPsrIf)
— CfmlNotifier (@CfmlNotifier) March 6, 2014

It should be polling every hour, once I set it up to do so.

That's it.

--
Adam

ColdFusion 11: @cfmlnotifier feeds updated

G'day:
(yeah, you're going to get a battering from me today). I've updated the @cfmlnotifier feed to report the following on ColdFusion 11 bugs:

Gavin is a star!

G'day:
Within minutes of me reaching out for help regarding my wee icon for the @CfmlNotifier Twitter account, me mate Gavin Pickin had sent me a number of options, more than one of which was eminently fit for purpose.

So I've picked this one:

That's pretty cool, and is fairly simple. Which suits me :-)

Currently my Twitter page is broken (Twitter are claiming responsibility) so I can't update it just yet.

Gavin: next time we're in the same place at the same time: there will be beer.

Cheers mate!

--
Adam

@CfBugNotifier renamed to @CfmlNotifier

G'day:
This is just a heads-up that I have renamed the @CFBugNotifier Twitter account to @CfmlNotifier. It will continue, short-term, to provide exactly the same status updates that it does now, but I intend to diversify it slightly perhaps. Plus I want to decouple it from the notion of "ColdFusion", as it'll have some CFML-vendor-neutral content too.

Outage on CfmlNotifier

G'day:
I actually meant to post this when it actually happened: yesterday or the day before yesterday whenever it was. It's been a busy week. Anyway, there was an outage on the CfmlNotifier feed. It's now resolve.

@CfmlNotifier and untriaged bug count

G'day:
Just a quicky. Scott and Dave had a bit of a strop at me today on CFHour: the "annoying Twitter accounts" reference in the show precis is a reference to @CfmlNotifier Twitter account. Which they don't like.

(1/4): it's not all about ColdFusion 10 bugs. CF 9.x has outstanding bugs too...

G'day:
First the "1/4" thing. Matt Bourke has just challenged me to release another four blog articles today. Let's see if I can do it. I make no apologies for the quality (or length) of the writing today. I'm not in the pub for one thing ;-)

This one is really short, but was underway before Matt challenged me.

CFML: Quicky: another feed going to @CfmlNotifier

G'day:
If you follow @CfmlNotifier on Twitter (and if yer a CF developer, you should be!), you'll note I've started another feed to it, reporting along the lines of:

2014-04-05 14:36 Untriaged ColdFusion 10 bug count: 61. List: http://t.co/XGoReqPrfq
— CfmlNotifier (@CfmlNotifier) April 5, 2014

I'm doing a status update on that every six hours 24 hours. It'll be interesting to see how the count changes. Due to how Twitter works, if I duplicate a status message (eg: in six hours time there's still 87 untriaged ColdFusion 10 bugs), the latter update will possibly be marked as a duplicate and not sent. I think this is OK: "no news is... well, not good news, but at least the status quo".

Hopefully you find this at least mildly informative.

And don't forget to vote for bugs that affect you, or if you need to give Adobe further information (like "why did you close this ticket saying 'never fix'? It's a right sball-ache for me!"). They do listen.

FYI, the count was over 100 a coupla days ago, so they do seem to be doing some triage at the moment. So that's good news. And it's certainly an improvement from when I wrote this: "212 untriaged ColdFusion 10 bugs" (back in May). Good work Adobe, but... hey... there's still quite a way to go, eh? All this stuff should be triaged already. They don't need to be fixed, but they should be triaged as soon as they're raised. Not months / years later.

Oh, and I know I've been a bit quiet this week (on the blog, anyhow). Work's been busy, and I've been a bit crook with a cold, so just watching telly in the evenings. I've got a coupla articles on the go, I just need the code sorted out.

Righto.

--
Adam

Adobe possiblynot messing with ColdFusion community projects again

G'day:

Stop Press

(although, like, that can only be done before something gets published, I guess ;-)
There's a chance this is down to an IP address change on Adobe's end, and a DNS caching issue on my end. Stay tuned...

...Stop the press, take to it with a sledgehammer, throw press away

Well I owe Adobe an apology! It was indeed mostly an IP address chance at their end, and DNS caching on my end. Once I got the server restarted (with some config changes), the DNS issue is solved, and I can reach Adobe again. They have changed their bugbase JSON responses slightly so I need to rejig my end of things, but that's nae bother and I should have it sorted out tomorrow.

I really did leap to judge too soon here, and I feel a bit daft for having done so. I'm all for applying derision to a situation, but I do actually think it should have a foundation, and it doesn't in this case.

Apologies, Adobe.

I'm gonna leave the rest of the article here as a monument to my stupidity.

This time, let's nip something at the bud: I don't give a shit who interprets who is at fault for any of this, nor how people confuse the notions of fault and blame, and will contort analogies to convince themselves they're right (I am not blameless here). This isn't about that.

Adobe have messed with the viability of some community projects again. This time: my ones.

CfmlNotifier down and back up again

G'day:
I don't actually keep a close eye on the @CfmlNotifier Twitter feed, so sometimes don't notice when it goes down. This happens occasionally if the ColdFusion instance it runs on gets cycled, or [some other reason]. It's a hosted box to which I have no admin rights, so if it stops working, I just go [shrug] and reload its services: I don't attempt to get to the bottom of it. On the whole it just chugs along fine by itself.

Update to / reminder about @CfmlNotifier

G'day (again):
A very quick one. Brad Wood is a very helpful community bod, he's one of the main evangelists for Coldbox, and keeps an eye on my prattlings on this blog, keeping me on the straight and narrow.

@CfmlNotifier

G'day:
I've finally sussed out how the Twitter & Bitly APIs work, and found time to knock-together a Twitter-based ColdFusion / ColdFusion Builder bug notifier.  It polls the Adobe bugbase every coupla hours and see if there's been any new activity since its last poll, and updates its Twitter account's status with the bug headline and a link to it.  So if you want to keep track of new bugs in the bugbase, then "follow" CfmlNotifier.