FAWD v1.0--Update Note: Dec 22/17 - Maaaybe outta the woods?
8 years ago
General
●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●
●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●
●●●●
●●●●
●●●● FA Writers Directory v 1.0
●●●●
●●●●
●●●● Update Note: Dec 22/17 (Copied from main page)
●●●●
●●●●
●●●●
●●●● The thrill of being shot at and missed: Mmmm, vastly overrated,
●●●● IMHO. On Friday, a CGI script called chk_jschl went operational by way of
●●●● redirect, and blocked the FAWD software from talking to FA. Google
●●●● revealed that chk_jschl is a Cloudflare defensive measure, intended to
●●●● stop anybody from connecting if they're not using a Javascript-enabled
●●●● browser. Ie., furs can get on, but trolls or attackers using software or
●●●● servers or what-not, can't.
●●●●
●●●● Arguably not that bad an idea. Except that chk_jschl caught the
●●●● FAWD too. Erk. Does this mean the FAWD just died screaming and on fire?
●●●● (Well, 's what I thought).
●●●●
●●●● Answer: Maybe not. Chk_jschl has been turned off--for unknown
●●●● reasons--so a very nervous and rattled knife-wielding kitten could do an
●●●● update run while waiting for his computer to explode (What do I know
●●●● about what Cloudflare can do?).
●●●●
●●●● Now: When or if will chk_jschl get turned back *on*? And just wut th'
●●●● fug is happening here? And is this project doomed after all? Doooomed.
●●●● And will FA's tech people get back to me before the heat death of the
●●●● Universe arrives, pleeease? (Insert plaintive kitten mew here. :- ) )
●●●●
●●●● More furious/frantic Google work revealed enlightenment, in the form
●●●● of a few possible fix ideas, although gonna have to do gobs of research to
●●●● figure out what the *hell* all those geeks are talking about. One
●●●● [comprehensible] idea involves using Internet Explorer, controlled by code
●●●● through Window's COM framework, so chk_jschl will see a JS-enabled
●●●● browser after all. Hmmm. I'm sounding pretty geeky myself there.
●●●●
●●●● Anyway. I *think* the FAWD's gonna be here next week, but I will
●●●● confess to some uncertainty. Foreclaws crossed that someone from Admin
●●●● notices this issue; TT is in. If that fails, the flaming blimps carrying
●●●● banners are next, followed by the squadron of sexy female kangaroos in
●●●● G-strings hopping through windows holding signs. This is FA. Whatever
●●●● works.
●●●●
●●●● Let it not be said that I've lost my sense of humour.
●●●●
●●●● <Mew?> :- )
●●●●
●●●●
●●●●
●●●●●●●●●●
New Work This Week -- Dec15/17 - Dec 22/17
NEW POETRY...
(3 poems from 3 new poets, 12 from 11 existing poets)
NEW WRITING...
(139 stories from 78 new writers, 491 from 326 existing writers)
●●●●●●●●●●
The FA Writers Directory v 1.0
●●●●●●●●●●
●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●
●●●●
●●●●
●●●● FA Writers Directory v 1.0
●●●●
●●●●
●●●● Update Note: Dec 22/17 (Copied from main page)
●●●●
●●●●
●●●●
●●●● The thrill of being shot at and missed: Mmmm, vastly overrated,
●●●● IMHO. On Friday, a CGI script called chk_jschl went operational by way of
●●●● redirect, and blocked the FAWD software from talking to FA. Google
●●●● revealed that chk_jschl is a Cloudflare defensive measure, intended to
●●●● stop anybody from connecting if they're not using a Javascript-enabled
●●●● browser. Ie., furs can get on, but trolls or attackers using software or
●●●● servers or what-not, can't.
●●●●
●●●● Arguably not that bad an idea. Except that chk_jschl caught the
●●●● FAWD too. Erk. Does this mean the FAWD just died screaming and on fire?
●●●● (Well, 's what I thought).
●●●●
●●●● Answer: Maybe not. Chk_jschl has been turned off--for unknown
●●●● reasons--so a very nervous and rattled knife-wielding kitten could do an
●●●● update run while waiting for his computer to explode (What do I know
●●●● about what Cloudflare can do?).
●●●●
●●●● Now: When or if will chk_jschl get turned back *on*? And just wut th'
●●●● fug is happening here? And is this project doomed after all? Doooomed.
●●●● And will FA's tech people get back to me before the heat death of the
●●●● Universe arrives, pleeease? (Insert plaintive kitten mew here. :- ) )
●●●●
●●●● More furious/frantic Google work revealed enlightenment, in the form
●●●● of a few possible fix ideas, although gonna have to do gobs of research to
●●●● figure out what the *hell* all those geeks are talking about. One
●●●● [comprehensible] idea involves using Internet Explorer, controlled by code
●●●● through Window's COM framework, so chk_jschl will see a JS-enabled
●●●● browser after all. Hmmm. I'm sounding pretty geeky myself there.
●●●●
●●●● Anyway. I *think* the FAWD's gonna be here next week, but I will
●●●● confess to some uncertainty. Foreclaws crossed that someone from Admin
●●●● notices this issue; TT is in. If that fails, the flaming blimps carrying
●●●● banners are next, followed by the squadron of sexy female kangaroos in
●●●● G-strings hopping through windows holding signs. This is FA. Whatever
●●●● works.
●●●●
●●●● Let it not be said that I've lost my sense of humour.
●●●●
●●●● <Mew?> :- )
●●●●
●●●●
●●●●
●●●●●●●●●●
New Work This Week -- Dec15/17 - Dec 22/17
NEW POETRY...
(3 poems from 3 new poets, 12 from 11 existing poets)
NEW WRITING...
(139 stories from 78 new writers, 491 from 326 existing writers)
●●●●●●●●●●
The FA Writers Directory v 1.0
●●●●●●●●●●
FA+

outta me; way unexpected. TYs to Google for instantly burping up info. Suggests that
chk_jschl *isn't* a permanently-on thing, but will be unpredictable and random.
Will say, that beats lethal as all bat-shit--to the FAWD anyway--but think some hacking
time on a fix will still be well-spent.
More strokes like the one I had, I'm not even gonna be able to spell the word <Mew!> :- )