Comments on: Missing videos and photos: A minor mystery

By: walt

walt — Thu, 08 Nov 2007 00:09:09 +0000

Well, as of 10/1 there’s no distinction between home and work. I suspect it’s some bizarre Firefox issue that’s not worth pursuing…

By: Jackie

Jackie — Thu, 08 Nov 2007 00:04:44 +0000

Is this happening at home or work? Or both? Here at my place of business we have those symptoms. We are running web filtering software which doesn’t block videos but instead puts up a warning screen first (to ask do you really want to be using the bandwidth for this). If the video is embedded in something else the warning screen can’t show so you just get a big blank box.

By: Dave Pattern

Dave Pattern — Mon, 05 Nov 2007 09:45:56 +0000

Not sure if it’s still the case, but Bloglines used to refuse to show images if they didn’t have a full URL as their HTML “src”. In other words, if the blog poster had used a relative link (e.g. src=”images/pic.jpg”) then the image wouldn’t appear.

By: walt

walt — Mon, 05 Nov 2007 01:00:34 +0000

1. Generally, yes–but in most cases, if it doesn’t show up in the Bloglines preview, it also doesn’t show up if I click through.

2. I don’t even know what GreaseMonkey is, so I’m probably not running it.

3. The only add-on I’m running is Google Toolbar. Otherwise, I have fairly vanilla settings.

This isn’t really a big problem. There’s very little “necessary” video/image content…and most of what is necessary, I see. This is mostly in the minor-nuisance category. Thanks for the tips, though.

By: jessamyn

jessamyn — Sun, 04 Nov 2007 22:41:42 +0000

A few troubleshooting steps

1. can you see the videos/photos elsewhere in Firefox but just not through bloglines?
2. are you running greasemonkey? have you tried this with GM off?
3. Are you running Ad-Block? have you tried this wth AB off?

I find that for me this often happens when I inadvertently block a server that is giving me lousy ads on one [age but might be serving video/image content that is more necessary on another site. You can also try starting FF in “safe mode” and see if that helps.