Category: Web/Tech

I have begun using PhilPapers.  "PhilPapers is a comprehensive directory of online philosophy articles and books by academic philosophers."  It is proving to be quite useful.  I see that they have scrounged up a few of my papers all the way back to 1976.  Ah, the wonders of the Web!

If only the proliferation of research tools, the multiplication of lines of inquiry, the ever-increasing specialization and technicality were sufficient to put philosophy on what Kant called den sicheren Gang einer Wissenschaft, "the secure path of science."

 

I sometimes have trouble getting the TypePad ComBox to accept my comments.  Others have had this problem.  I get the error message: "Sorry, this data cannot be accepted.'  By fiddling around, I have discovered that doing one or more of the following will trigger the system to accept data. (1) Make a minor alteration in the text. (2) Resubmit your name and e-mail address. (3) Copy your comment, open the blog in a new window and input the data via the new window.  It seems that problems arise if you leave the ComBox open too long in a given window or take too long composing your comment.

What I have yet to figure out is how to make full HTML functionality available in the ComBox.

Using the Google search engine this morning, I noticed that every search I did brought up sites flagged with the 'This site may harm your computer' warning.  I even Googled 'Google' and got the same result!  Could Google be flagging every site brought up by its engine?  That would be such an obvious piece of fear-mongering and traffic-reducing stupidity that I hesitate to impute it to them.  Any thoughts from the computer cognoscenti?

Despite my catchy title, it is your responsibility take precautions whenever you connect with anything in any way.  I am responsible for the content of this site, including in some measure the content of the comments, which is why I delete stupid and otherwise offensive comments and block those who send them.  But I take no responsibility for what goes on at the server end.

UPDATE: 9:30 AM.  Alexander Pruss informs me that the problem has been fixed.

UPDATE: 1:30 PM. Google explains the origin of the error.