“Won” my first “case” today

I have to apologize for my liberal use of quote marks—but I felt they were necessary to qualify those terms. First, by winning I mean that I received a settlement check in response to a demand letter I sent on behalf of a client, so there was no neutral arbitrator to declare me a winner. Second, the issue never got to litigation, so there wasn’t really a case.

But it sure does feel good. Plus, I was pretty proud of how that demand letter came out. The only difficult part of the whole thing was making sure that the settlement check got to my client within a reasonable amount of time.

Protect against tkdot[dot]com!?

Like many new website owners, I took a look at my website analytics to find that tkdot[dot]com (I am replacing the “.” with “[dot]” to avoid accidentally sending them traffic) was linking to my site with various sex-related keywords. I don’t know why, but this is evidently a fairly common problem.

Like the example above, many of the website owners are wondering if anything can be done. I think the answer is yes, at least with my hosting service, GreenGeeks. GreenGeeks gives me a function called “IP Deny Manager” in my “cPanel”. Certainly, other hosting services have similar functions in their user interface. Anyway, mine looks like this:
Set up to (hopefully) block tkdot[dot]com
To get to the point illustrated above, I just entered the URL of the offending website, and the Ip Deny Manager spit back out the IP address.
Hopefully this will work. If it doesn’t, I’ll let you know. If anyone sees anything wrong with this approach, or knows something I don’t, please let me know in the comments!

EDIT: After some consideration, I don’t think this will do what I want it to do. I think the IP Deny Manager will simply keep anyone from that IP, in this case, from being able to access my website. So, if the guy at the server farm where tkdot[dot]com is located hops on and tires to direct his browser to my website, he’ll get an error message. Consequently, I don’t think it will keep anyone from seeing a link to my site at tkdot[dot]com and following it to my website, which is what I want. It may, however, keep the tkdot[dot]com spiders from cataloging my website, which may keep it from popping up in searches. As of today, May 1, I have not seen any traffic from tkdot[dot]com. This may simply be a coincidence or may be attributable to the fact that May is only thirteen hours old at this point. I’ll keep you posted.

Enforcement, Privacy, and Constitutional Problems with Virginia’s New Texting-While-Driving Law

Virginia’s new texting-while-driving law is not only unenforceable, as a recent article in the Washington Post notes, but raises privacy and constitutional concerns as well. The new law retains the existing language in Va. Code Ann § 46.2-1078.1, which prohibits entering multiple letters or text into a cellphone “as a means of communicating with another person” and readings texts or emails transmitted to or stored on your cellphone. This language leaves police officers, while traveling at 65 mph, to determine whether a driver is using his cellphone to send a text or call his wife.

Enforcement problems. As the traffic division commander for the Fairfax police said in the WaPo article, police officers would have a very difficult time determining whether a person was texting or typing the name of a restaurant into Google Maps. Also, drivers could just lie about what they were doing on their phone if they are pulled over, as suggested by a recent blog postNews reports, however, report that police officers will give people the option to present their cellphone to prove that they have not been texting or emailing or to fight the ticket in court. But someone could easily write an app that displays fake text messages with fake timestamps. Ideally, such an app would look just like the native text message/email app and contain copies of the actual texts and email on the phone, but have timestamps that subtracted an hour from the real timestamps.

Privacy concerns. Despite the reassurance that police officers would give a driver the option to submit to a search of the cellphone for evidence of a recent text or refuse the search and fight the ticket in court, Professor Gershowitz of William & Mary explains in a recent article that police officers have constitutional grounds to search cellphones for evidence of texting under all of the different state texting-while-driving laws. Specifically, Professor Gershowitz posits that such searches are permissible under two different exceptions to the Fourth Amendment’s protection against unreasonable search and seizure, the search-incident-to-seizure exception and the automobile exception. The search-incident-to-seizure exception would not apply to the revised Virginia law because the statute does not give a police officer the authority to arrest a suspect. Under the automobile exception, however, Professor Gershowitz says that police officers would have authority to search cellphones in a traffic stop for texting-while-driving even without the authority to arrest. Specifically, the professor reasons that police officers would have authority to search cellphone “containers” in such a traffic stop because the officer personally observed the driver texting. This personal observation give the officer sufficient probable cause for both the traffic stop and the search of the cellphone “container” under existing Fourth Amendment jurisprudence, even if the officer mistook the use of Google Maps for texting or emailing. Therefore, under the automobile exception to the Fourth Amendment, a police officer may legally decide to search a driver’s cellphone even if the driver refuses to consent to the search when the driver is pulled over for allegedly texting-while-driving—even if the driver was just searching for an address on Google Maps.

Constitutional problems. In this article, however, Professor Gershowitz says that, while the automobile exception clearly allows cellphone searches during stops for texting-while-driving, it is not clear where in the cellphone, or what apps on the phone, the police officer may search. That is to say, it is not clear whether the police officer’s authority to search is limited to only an app used primarily for texting or email, or if the officer has the authority to search any app that could possibly be used for communication such as a Facebook app or a web browser. This would be a concern as well for those that submit to the officer’s request to search the cellphone, assuming the officer will only check for texts and emails, and finding out that the officer searched through their web browsing history.

Professor Gershowitz explains that the where authority is likely controlled by the language of the statute. The language of Va. Code Ann § 46.2-1078.1, recall, prohibits in part entering text into a cellphone to communicate with another. Therefore, police officers would certainly be able to review texting and email apps, as those are primarily direct communication apps, but what about your Facebook app? Is a Facebook post a “means of communicating with another person” under the meaning of the statute? Most people do not expect direct replies from their Facebook updates, like you would a direct text, but people certainly intend to communicate to others through a Facebook post. If officers have authority to search beyond email and texting apps, could they have the authority to search your cellphone’s web browser as well? Many people choose to use a web browser over a specialized app for accessing Facebook because of privacy concerns. Additionally, if the police officer has the authority to search for Facebook posts, certainly they have the authority to search for postings to message boards or blogs that were posted through the web browser. What about a Reddit app?

The legislature should revise the texting-while-driving law sooner than later to avoid the cost of enforcement, privacy violations, and constitutional problems of the pending version of Va. Code Ann § 46.2-1078.1. I would support a blanket ban on the use of hand-held cellphones, which was Maryland’s recent solution to the problems discussed above. However, criminalizing the use of hand-held devices likely disproportionately affects those who cannot afford a car with an integrated hands-free device. But I believe that a blanket ban on the use of cellphones in the car would be an overreaction to the problem as well.


Adding WordPress Content to an HTML Page

I know there are a lot of posts out there about this, and at least one from wordpress.org, but I thought I’d share what I learned from reviewing all these posts and, ultimately, my friend John Branigan. Also, I may be able to write this in a less technical way than the other posts, because I have no idea how to use the necessary lingo.

  1. Install WordPress with your Internet host.
  2. Save your HTML index page with a .php extension. It seemed counterintuitive to me, but that is what finally got my WordPress posts to populate on my website.
  3. Add the following header, provided by wordpress.org, between <head> and </head> tags:
    /* Short and sweet */
    define('WP_USE_THEMES', false);
  4. Then John gave me the following script to place in the body of the page, where you want the blog post to populate on the page:
    <?php query_posts('showposts=-1');
    if (have_posts()) :
    while (have_posts()) :
    <h2><?php the_title(); ?></h2>
    <?php the_content(); ?>
    <small><?php the_time('F jS, Y') ?> <!-- by <?php the_author() ?> --></small><br><br><br>

With those three steps, I was able to make it happen. I am going to, or already have, added some more php code to display other parts of the WordPress blog such as the publication time and date. My goal is to display the comment section, but some of the reading I’ve done makes it look like that will be difficult. Good luck to us both!