The Legislature Raids

Apparently I still haven't managed to properly reset the notification process for comments. Mary had things set up so that all comments, except those which google determined to be spam - generally pretty accurately - generated an email notification to her, which she could then decide to publish or not. In the past when she was away, or unable to manage the Ledge Raids due to treatment, I would switch, or add, notification so that I too would be notified and able to release/publish appropriate comments promptly. It used to work just fine, but Google, like most IT outfits, has a habit of changing stuff, often for no discernible reason and definitely not an improvement. I'm more old school, if it ain't broke, don't fix it (or move the Start Button or put Word Wrap on a different menu)!

When I first realized I wasn't being notified (Mea Culpa previous) I checked out the comments folder, and spam folder and wound up releasing about 30-40 comments. Then after resetting the comments notification I started getting at least two notifications for each comment. Then I re-adjusted the settings and now again I've been getting no notifications. I checked the folder today and have just released almost twenty recent comments, so if you commented in the last week or two and wondered why it wasn't published, check now and it will likely be there. If you need to contact the blog e-mail me at:
kootcoot@hotmail.com
To the commenter who was asking about the future of this site, to wit:

Is this now a dormant site? If not, perhaps someone should make a statement about its status.

If there aren't regular BC Rail updates here you'll lose your the audience, and the valuable archive that Mary left us will be relegated to the dusty shelves.

The postings don't all have to be lengthy tomes, in fact, better that most of them aren't. Is anyone able to carry on the research that Mary used to do on this subject? i.e. not turn it into a general blog on any subject

Hoping the site will carry on, through whomever, if possible. Even if nothing more than a permanently available archive blog. She brought the best investigative stuff to the surface, way more than Alex Tsakumis (she just didn't have the insider's contacts that he does).

2 April, 2012 1:29 PM

The site will carry on, however there is no one on the horizon to carry on the level of constant research that Mary was so good at doing. I don't have the time to carry on my own stuff and replace Mary. However, I did always provide a certain degree of tech support for her and was involved with TLR and will continue to keep it running. Recently I have published three appropriate pieces by Robin Mathews and I am willing to publish anything submitted by anyone that is appropriate, in other words has bearing on BC Rail and the crooks that stole it. Also it will remain available as an archive, and anyone with access to the visitor logs would be amazed at the volume of traffic that TLR still attracts. Much of the traffic is the result of search engine referrals when web surfers use key words that relate to the subject matter of the more than 2000 posts that Mary published since 2006.

I am also in the process of backing up the entire blog onto other media, so that even if the internet ceased to exist, the work that Mary did on behalf of everyone that cares about British Columbia will live on, even if it has to be chiseled in stone or applied to papyrus scrolls.

Also, RossK of the Pacific Gazette, will likely, if he chooses, be back as a contributor. We've been having a problem with his posts to his own site somehow overwriting the entries on third party blogrolls and then that would create a link that led to an error page if someone tried to link to The Legislature Raids. Under the circumstances, I was afraid that might cause some folks to think the blog had been cancelled/deleted. That issue and the inconsequential Map_key issue both have yet to be resolved. The key issue though is easy for now, just click on Okay, on the pop-up error message and carry on, everything works on the front end and the back end (excepting the comment notification, which is most likely my bad). I may just eliminate the comment approval prior to publication, at least as a trial. Google Blogger does a good job sorting out the genuine spam and in general if it is the matter of a comment in poor taste, I've always felt that reflected entirely on the commenter, rather than the host. Either way, I will get into the habit of checking the comment folder more often, at least until I either free the process up, or straighten out the notification process.