Updated about 20 minutes after original post -- detail added to the "So why I did not find. . ." paragraph.
The only detail so far unexplained in the deactivation of the Vridar.wordpress blog is why I apparently did not receive a warning notice from WordPress itself.
The times below are in Australian Central Standard Time, my local time. (Some images may be over-size for iPad viewing but to reduce them further would make them difficult to read.)
2:26 AM, Tuesday June 28th, WordPress/Automattic email me notice of their takedown of my post about Joel’s nonsense.
But being 2:26 AM I am, as usual for that time, asleep.
Around 3 AM I wake up (as I do from time to time) and check my iphone for current news and recent blog activity.
If I looked at my Gmail at that time (I don’t recall if I did, but if I did then I would have ignored anything that did not look interesting — I would have ignored anything from “WordPress” since it’s usually some notice of a new product, new theme, — I’m not interested) the subject header would have meant nothing to me (what’s “DMCA”?, looks technical, some outage time?) and I would have ignored it.
The only thing I know for certain is that I did not take any notice of my email at that hour.
But I did see something odd: my post on Joel’s history/science nonsense is in ‘private’ status. Maybe Tim is doing something with it. I decide to check with him later and go back to sleep.
Once awake I check the post in “private” status, see nothing wrong with it, so restore it to “public” status.
About 6 AM I see Tim is online and ask him about the private status of that post. I wonder if there had been a WordPress glitch. I conclude that Tim had accidentally put it in “private” status. Continue reading “Last Piece of the Vridar Takedown Puzzle”
There is no doubt that Joel Watts attached a CC (Creative Commons) Licence notice to the blog post of his that I copied and reused.
So what IS a CC licence?
The whole idea behind a CC licence (we might even call it the CC philosophy) is to foster a win-win situation in the world of ideas. That is, the person who creates the new work will not lose anything if someone else, who likes that work enough to want to re-use it, picks it up and does re-use it to create something new.
So, for example, if I post a new literary work, all sweated from my own furrowed imagination, like,
I feel so egg-ceptionally, god-blessed smart today that I think you have egg all over your godless dumb face
and you think, Wow!, I like that! — then the CC licence is just for you! But it’s also for me who was inspired to write the original!
It’s for me, since I only need check of the tick-boxes in the CC form to tell the world what I want and don’t want others doing with my inspired words — e.g. do I allow you to make $$$$ from my words? do I allow you to re-use without telling the world I was the original creator of those words?
And it’s for you — you can re-use my words any way you would like within the constraints of the check-boxes I ticked.
So if you take my words and create something that argues against their original intent, and even proves they are shite, no worries! If you have also created your post under a CC then I can take that, re-use it, and argue the exact opposite!
Greg Jenks — a Jesus Seminar Fellow who brought John Shelby Spong to the little city of Toowoomba where I once lived and worked (and met Spong) — has posted the following on Facebook: (I think it’s a form notice, but no matter. . . .)
Burma may turn into the next Rwanda unless we raise our voices and stop the racist attacks right now — will you join me?
To blame the killing on “religion” is simplistic and hides a far deeper and more complex problem. There are ethnic differences; local jobs are thought to be at stake; cultural differences are sharp and offensive to some; there is a new nationalist sentiment beginning to blossom in Burma; religious difference is easily identified for hostile targeting and becomes the scapegoat. Continue reading “Can we help Burma? Another Rwanda Looming?”
[I edited this post on Friday, July 5. See the Addendum at the bottom of the page. –taw]
Well, it was fun while it lasted. I was really rooting for the Time-Lord option for Joel, but Samphire has proved, to my satisfaction at least, that Joel did not jump into his TARDIS and return to Wednesday, June 26.
It’s about time
First, let me explain to the Windows users out there how the Macintosh Menu Bar and Dock behave. In Microsoft Windows, each application has its own menu bar. That is, each window usually has its own bar that contains the standard menu items: File, Edit, View . . . Help. Nonstandard apps like Chrome may break that convention. Each software vendor has the ability to change these user interface characteristics. It’s a free-for-all. Or perhaps a “mess” is a better description.
It isn’t like that on the Mac. The menu bar “belongs” to the operating system. So when each application (e.g., Firefox, Finder, Microsoft Word, etc.) comes to the foreground, its “File-Edit-etc.” menu is anchored to the same place. Apple touts this behavior as a convention that enhances ease of use.
The Dock on the Macintosh is similar to the Windows Taskbar, but with key differences — one of which is the way minimized windows zoom down to the Dock. They remain in a minimized state, visible as a small icon. As with the Windows Taskbar, you can move the Dock to either the side of the desktop, but I think most users keep it on the bottom of the screen.
Screenshot 1: Date & Time Preference Panel on My MacBook
One feature the latest versions of Windows and OS X have in common is the ability to synchronize time with a trusted network host. In the old days, we used to synchronize our servers with “tick” and “tock”: two Network Time Protocol (NTP) servers run by the U.S. Navy. But nowadays, most people in America either use the NTP servers run by NIST or the vendor-operated NTP servers like time.windows.com or time.apple.com.
And that brings us back to the question of time. As you can see from the screenshot of my Macintosh (see Screenshot 1), which shows the Date & Time Preference Panel, I’m letting Apple’s time server act as the trusted date and time reference for my system. You can see that the main application running in the foreground is System Preferences. If I minimize the Date & Time window, it’ll get sucked down into the Dock.
Screenshot 2: Minimized Date & Time Preference Panel
The System Preferences application is still considered to be “in the foreground.” (Incidentally, that’s why we still see the words “System Preferences” next to the Apple icon in Joel’s desktop screen capture.) However, the Date & Time panel is tucked away until I need it again.
In Screenshot 2, you can see that the minimized icon for the Date & Time Preference Panel is actually a snapshot of exactly what it looked like before I minimized it. And you can tell that it belongs to the System Preferences application, because of the tiny “gears” image pasted in the icon’s lower right-hand corner.
So now that we have all that background knowledge out of the way, let’s take a look at the new evidence that Samphire has just now brought to light.
Watts up, Dock?
Samphire wrote:
I went to Watt’s own full screenshot displayed on his webpage and found that down at the bottom right of his screenshot the minimised icon of the Date & Time icon could be seen (it’s pretty distinctive even when minimised) sitting on the Dock.
Let’s take a closer look for ourselves. Here’s Joel’s desktop image again — cropped and enlarged:
This is my response to James McGrath’s post, Mythicist Language is Designed to Make Lies Sound Truthful. Is McGrath really saying that a mythicist argument by Brodie is actually a set of “lies”? If so, that underscores the very point I have been making about how censorship works in academia — and McGrath is himself one of the most stalwart of guardians of “correct thoughts” in the arena of New Testament studies.
James McGrath continues to refer to even the most dry, factual posts and writings that lean towards favoring the Christ myth thesis as “rants” and “lies” — presumably solely on the grounds that any writing that leans to such a conclusion must by definition be a “rant” or a “lie”.
And THAT is exactly why it is an Orwellian joke that such a person should be considered as qualified to speak about censorship and academic freedom in the context of the Christ myth. THAT is how censorship in academia works. It is through this sort of institutional intellectual bullying — denigrating anyone who advances certain types of alternative views as peddlers of “rants” or “lies” — that we see censorship working in all sorts of areas. There is no need for a “conspiracy” — and of course McGrath likes to intimate in his same post that mythicists are “conspiracy peddlers”, too — which is a real rant and lie. Academia is not immune from this sort of subtle systemic censorship, and never has been, as Julien Benda pointed out so dramatically in another context with “The Treason of the Intellectuals”. What was true of France in his day has been just as true of the English speaking intelligentsia up to our own day. And if it is so blatant in the political arena, we should not be surprised if it is alive in the world of public religious convictions, too. Politics and religion, the most ideological of our academic “disciplines”.
The same old
Of course McGrath will protest that he has engaged with and rebutted mythicist arguments many, many times. He will wave his hand and invite readers to look at all those posts and comments he has made in the past.
I have to thank Manoj Joseph for pointing out some date/time oddities in Joel’s testimony concerning exactly when he emailed Neil about the DMCA takedown. With all the work I had to do to bring Vridar back to life, I barely had time to skim a handful of the relevant posts around the web.
But now with the passage of couple of relatively peaceful days, I think it’s time to reflect on what happened. In particular, we should look more carefully at those screenshots that Joel so graciously provided. I just checked his site, and they’re still there, but just in case he catches on to his mistake, you will still be able to find them in various web caches.
Watts the story?
Joel says he warned Neil on the 26th. Explaining his actions, he begins by showing a screen capture of a comment by Neil. He writes: “I then sent an email to him, shortly there after [sic] . . . Note the time difference. I know he’s in Australia.”
Comment posted at 12:43 AM local to Joel’s blog.
That’s a curious little side note from Mr. Watts. The WordPress administrator tool in the screen capture shows a local time (EDT) of 12:43 AM. WordPress doesn’t show you the local time of the sender; that would be insane. No, this is Joel’s local time: Eastern Daylight Saving Time.
Comparing the system time to the sent time
So what’s this business about a “time difference“? Joel wants to prepare us for a little con job that he’s about to foist on us. It reminds me of short-change artists who confuse you with their nonsensical patter just before they coax you to give them an extra 20-dollar bill.
Nothin’ up my sleeve
Next, Joel kindly shows us an image capture of his desktop. Looking at his Sent Items folder, we’re led to believe that he sent an email to Neil at 12:56 PM on the 26th. So, Neil posted shortly after midnight (EDT) on the 26th. Joel allegedly sent his mail “shortly there after [sic]” — I guess 12 hours is a “short time” in Joel’s mind. No matter. It is, after all, the same calendar day.
But hang on. Compare the wall clock time on Joel’s Macintosh to the time on the email. Remember: These are all local times of the sender. Outlook doesn’t show the local time of the recipient; that would be crazy.
On a related matter: Joel Watts has been writing quite a lot to portray WordPress.com through Automattic as diligently investigating the merit of his claim before posting a DMCA takedown notice. See Ugh – Once Again the DMCA and his various comments on James McGrath’s post, Vridar No Longer Available.
Well, if one reads the statement by Automattic that Joel has kindly posted for our benefit one can see that Automattic explained to Joel exactly what they checked. Read that second last one-sentence paragraph:
That’s it. They explained to Joel that they had received his DMCA takedown notice and reviewed it for completeness.
It was the same when I submitted my counterclaim. I had to check off a whole lot of boxes confirming I had included everything in my statement that they required. They did not check my or Joel’s blog sites to see if my statement was true.
That is, Automattic at this stage does not investigate and confirm the validity of the claims. That is a later process and the responsibility of a court. Automattic’s job is to be sure that each party submits its sworn statements according to due process.
One reader has posted a classic cartoon of the recent events as explained by a certain M. Joel Watts, MA. . . . For full details of the particular post by M. Watts that this cartoon depicts, as well as the original source photographs on which it is based (they are also classics!) you must visit the original post by pithom on his blog. It includes a little webliography of recent related posts, too.
The original Vridar site has now been restored by WordPress.com minus one controversial post. I have disabled comments on that legacy site, though, since Vridar.org (the site y0u are reading now) will be the active one from now on.
The Vridar blog was deactivated by its hosting company, WordPress.com, in response to my reactivation of a post that I did not realize had been taken down as a result of a reader’s complaint.
I have since issued a counter-claim and WordPress.com has responded by contacting me to say they have reinstated the original blog minus the post in dispute. That post will remain inactive pending a further response from the claimant within 14 days.
We have Tim to thank for getting up this new site for Vridar so quickly.
I would like anyone who has produced a blogpost or knows of a blogpost discussing what has happened to the Vridar blog to drop a comment and link, here, please. Also — any online discussions maybe.
I have left comments on a couple I chanced upon and would like to reestablish contact with those (and I do apologize — last few days have been a bit chaotic and I haven’t kept records to recall who I have visited recently). We’ve lost all our old blog links and subscriber lists as far as I can tell and need to reestablish these from scratch. I’d also like to offer personal thanks to any blogger who has commented on this fiasco and perhaps give an explanation on any blog that has been misinformed about the facts.
Cheers and many thanks,
Neil
Here’s one I came upon a few moments ago. I’m sure there are a couple more somewhere (including another I commented on recently) . . .
James McGrath has posted a revealing reply to my critique of a single point in his review of Thomas Brodie’s Beyond the Quest for the Historical Jesus: Memoir of a Discovery. Ironically he appears to be unaware that his every point is illustrating the very problem I was trying to address and that is close to the core of the historical Jesus vs Christ myth controversy. (One can hardly call it a two-sided intellectual debate or exchange at this stage.)
I concluded with the message that McGrath “brings a hostile intent to every page” he reads by a mythicist.
In my critique of a single point in McGrath’s review of Brodie’s memoir I pointed out that McGrath unfortunately failed to establish his claim with any factual reference to what Brodie had written. Indeed, when one reads the pages that McGrath cited as support for his view, one finds that Brodie’s words belie McGrath’s claims. How is this possible?
McGrath explains
McGrath explains. He draws on his own personal experience and personal weaknesses and reasons that these should guide his and our reading of Brodie’s book. It’s called projection.
McGrath’s explicit reliance upon his own experience while at the same time dismissing and/or ignoring anything Brodie says to the contrary is a classic case of this all too common bit of the human condition. McGrath fails to see that his own experience is irrelevant unless he can directly relate it to the evidence Brodie states — not to “impressions” McGrath gets from putting unspecified inferences he brings together from various pages.
The point I was making in that section of my review was about the fact that Brodie drew a conclusion about whether Jesus was a historical figure even before learning how to do scholarship in the appropriate manner. I can tell you that I myself had all sorts of ideas that I thought were brilliant, publication-worthy insights as an undergraduate. Few withstood the testing to which I subjected them in my ongoing studies.
No, Brodie did not come to the conclusion that Jesus was not historical before “learning how to do scholarship”. McGrath originally said that that was his impression and now he is saying that this was “a fact” he was trying to point out. I have been discussing Brodie’s book in detail and it is clear that McGrath has nothing but his own “impression” — no data — to support what he now says is a “fact” about Brodie.
But it does not stop there. In his original review McGrath invites his readers to share in this projection. He does this by pointing to general motherhood statements that most others can relate to from their student days and invites readers to think of Brodie’s argument through this perspective. Continue reading “How Did McGrath Get Himself Inside Thomas Brodie?”
On 26th June I wrote a post exposing the incompetence and culpable ignorance of Joel Watts with respect to a particular point he was using in an attempt to lampoon mythicism.
That blog post contained a detailed, point by point criticism of Joel’s post. Whenever criticizing the works of others I habitually bend over backwards to be sure I am fair to the other side and let their own views be understood. And since Joel Watts had always had a Creative Commons license condition attached to all of his blog posts (I also have a Creative Commons license) I saw nothing amiss in quoting his blogpost in full — especially seeing it consisted of nothing but a list of 25 web links, a tweet from someone else, and no more than about half a dozen lines of typical Watts-like puerile insult. I made sure I linked to the original site, and that I identified the author, and that the views of the post did not reflect mine. After all, all of those conditions were in large measure the whole reason for my post.
This CC notice was removed from Joel’s blog only on the morning of 29th June 2013 Australian Central Time. It appears as if this was removed soon after this CC notice on Joel’s blog was publicly advertised: http://www.freeratio.org/showthread.php?p=7493335#post7493335
At no time before my blog was deactivated did I receive any notice from Joel Watts, the owner of the blog post I copied for critical discussion, or from WordPress warning me or asking me to remove or modify the post. My email account is Gmail and files can be verified and in the event of legal proceedings I would welcome such a check.
If Joel really did send me a warning letter then one must wonder why he only confessed to his own involvement after I posted the evidence — did he not expect me to be able to that from the beginning?
Joel Watts did not follow the specified steps to contact me directly with a complaint about my blogpost. This was in contradiction to Automattic’s direction to complainants according to their directions at http://automattic.com/dmca/ :
2. Contact the blogger directly. Go to the blog post in question and leave a comment with your complaint to see if the matter can be resolved directly between you and the blogger.
Well, we’re alive again. Did I miss anything while we were dead?
Folio 55 verso : Phoenix (Fenix) rising from its ashes. (Photo credit: Wikipedia)
“Waaaah! They stole my content!”
Here’s the short version of what happened. In one of Neil’s blog posts, he copied the content from one of Joel “Takedown” Watts’ posts, not to steal content (heaven forbid), but to prove that Joel had merely scraped Google for links related to “the science of history.”
Joel took issue with it and claims he sent Neil an email. Perhaps he did. Neil still can’t find any evidence of it, not even in his spam pile. Joel then complained to WordPress.com, and demanded that the post containing his stolen property be taken down.
As far as we can tell, what happened next is that the WordPress guys put that post on private, but neglected to tell us why. Yesterday, Neil asked if I’d changed a post’s status to “Private,” or if we were experiencing another WordPress glitch. I said I might have fat-fingered something. I had been setting some posts I was working on from Draft to Private, because I was worried I might accidentally publish them.
“Nice blog ya got here. It’d be a shame if sumpin’ was tuh happen to it.”
So Neil, unaware of the storm brewing on the horizon, set the post back to Public. At that point, it appears WordPress interpreted our behavior as evidence that we were flouting the rules and ignoring the DMCA takedown order. Please note that neither Neil nor I received any warnings from WordPress about the Sword of Damocles hanging over our heads.
Two new books arrived in my mail this morning. One I had purchased, the other was a gift.
Having skimmed a few pages of each I am already well pleased with my new acquisitions. Stephanie Fisher once commented on one of these, Muslim Secular Democracy, edited by Lily Zubaidah Rahim, and that has only just been released:
It seems to me, from the interview, your summary and the blurb on Amazon, that what she claims is beyond refute. It’s historically demonstratable and what I once thought was commonly understood. I do wish those who dismiss Islam with assumptions about a ‘heart’ etc, would honestly read a bit of history. The more I dwell on it the more convinced I am that this book, combined with Espositos must be read for the sake of a future – for god’s sake world, read them and understand….:
Stephanie’s remarks about reading and knowing a little history turn out to be a most pertinent message of both my new books.
Another commenter recently asserted, in effect, that the failure of Muslim populations of the Middle East to change their governments demonstrated that they loved oppressive and dark religious authoritarian rule more than freedom and an open society. I wish such readers could have a look over my shoulder as I read the first page of the introduction to Muslim Secular Societies:
In the wake of the political sandstorms unleashed by the “Arab Uprisings,” almost every Arab state faces serious political challenges and pressures to reform. Authoritarian governance, both Islamic and secular, has been resoundingly rejected by the Muslim masses. Also resoundingly rejected by the Muslim masses are the violent methods of militant Islamists. (p. 1)