4 ms·
Remove your tin foil hats, while MSNBC's search sucks they still have a mention of it that was linked from the front page. http://maddowblog.msnbc.msn.com/_new
by krschultz 17y ago
Remove your tin foil hats, while MSNBC's search sucks they still have a mention of it that was linked from the front page.
http://maddowblog.msnbc.msn.com/_news/2010/04/05/4117730-wikileaks-posts-combat-video-from-iraq-showing-civilian-casualties http://maddowblog.msnbc.msn.com/_news/2010/04/05/4117730-wik...
Also NYTimes has one:
http://www.nytimes.com/aponline/2010/04/05/us/politics/AP-US-Iraq-Shooting.html http://www.nytimes.com/aponline/2010/04/05/us/politics/AP-US...
- iamdave 17y agohttp://dl.dropbox.com/u/109063/screenshots/us_civil_forces_msnbc.PNG http://dl.dropbox.com/u/109063/screenshots/us_civil_forces_m... This is the front page of MSNBC. You can't possibly justify their search function not presenting results when the blurb provides marginal insight into how severe this video is.
- conflux0 17y agoRedditors/Wikileaks is making a big stink about it, but it really isn't about being righteous. Its about making a big stink. Every army fighting a war against an insurgency makes mistakes like this. If you are saying that the rules of engagement are flawed it might be eye-opening to realize the reduction of military casualties by having a more aggressive set of rules. The only solution in my mind is to not go to war from the beginning and to end it as soon as possible with the best means possible.
- aphyr 17y agoTin foil hats? /?q=wikileak works, /?q=wikileaks returns an error. It's a politically sensitive topic involving the death of two press employees, possibly unethical conduct by the military, and the government has attempted to suppress its release. What more do you want? It seems pretty obvious to me that their search dept is trying to stop people from finding the story. Either that or their search is broken in a truly bad way--given that those words should stem to the same query, it's suggestive to say the least. [edit] Looks like their article search is working again. [edit] You know what? I'm sorry, that was premature. It is suggestive, but there are other plausible (and, to my mind, preferable) explanations. "wikileak" returns web results, whereas "wikileaks" returns article results. MSNBC may have a local index for their stories and a fallback to Bing. Perhaps it's a failure for a newly-emerging search term that only applies to the local index, which does not stem queries. Or perhaps they're doing extra processing for stories which failed, for any number of reasons.
- deleted 17y ago[deleted]
- conflux0 17y agoJust think about it this way. How many people using msnbc will actually make the query that will match the regex "/^wikileaks$/i". If they were truly trying to prevent people from accessing information about it they would have done a better regex. "It seems pretty obvious to me that their search dept is trying to stop people from finding the story. Either that or their search is broken in a truly bad way--given that those words should stem to the same query, it's suggestive to say the least." It really doesn't. I'm going to take a big guess here and say that the good people over at MSNBC are not that inept.
- buster 17y agoMy guess is: There is a list of searchterms which now looks like that: 1. Wikileaks 2. Obama 3. Sex 4. Reef 5. Oil . . . 32. wikileak There is probably a simple "ban this word" textbutton and the person in charge will naturally just ban wikileaks.
- aphyr 17y agoMy guess is they're not doing regexes. Someone in charge probably said "Stop people from searching for wikileaks" and they added that term to a hacked-together blocklist ASAP. Either that or they added it to a special list of queries that get extra processing (topic summary for the top of results, perhaps) which was crashing, and deployed without checking the results. Either way, it looks like their search is working now although the error persists, which suggests things over at MSNBC are much in flux. :)