Thursday, July 17. 2008

Going hyperlocal

I've watched the hyperlocal news discussions with interest, but rarely do I feel the need for local news beyond a subscription to the local paper and signs and banners in the square (Davis Square). Today however, I needed, ok wanted, the hyperlocal news. The small restaurant across the street, Supreme Kitchen, had crime tape on it and a broken window when I left to have dinner with my Dad at about 5:30 pm. This is not the sort of place that would be robbed or where there'd be a fight. It's across the street from the hospital and just a few blocks from the fire station.

When I got home I planned to find out what happened. Before I could I listened to the message on the answering machine. It was from the police. Apparently on Saturday there was a hit and run two blocks from me. (The nine year old who was stuck will fully recover, thankfully.) The police, using our reverse call out tool no doubt, were asking neighbors for any information to help track down the perpetrator.

So, how did I find out what happened at Supreme Kitchen? I thought about the hyperlocal sites I'd heard of (Boston and surrounding are not a prime candidate yet) and immediately went to Google News. No luck. Then I went to Google's blogsearch. Bingo. The "other" local paper's blog had the story with cheeky headline ("Do you want eggs with your reckless driving?") and photographs.

Posted by Adena Schutzberg at 06:00 | Comment (1) | Trackbacks (0) |

Comments

Display comments as (Linear | Threaded)

Are you familiar with Davis Square LiveJournal? We didn't have the Supreme Kitchen story, but we're superhyeperlocal.

#1 Ron Newman on 2008-07-24 09:04 (Reply)

Add Comment

Name
Email
Homepage
In reply to	[ Top level ]#1: Ron Newman on 2008-07-24 09:04
Comment	Enclosing asterisks marks text as bold (*word*), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. E-Mail addresses will not be displayed and will only be used for E-Mail notifications To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information?   Subscribe to this entry