Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Corel

Journal BlackBolt's Journal: I Was Always Paranoid, But This Is Paranoid Pro 6

Posting an inane and mindless poll comment a moment ago, (oh wait, 2 moments ago, bloody Slashdot lameness filters!), and going through my new posting ritual of hitting Preview, then back, then Preview again, etc. until I finally get to see a human-readable preview, a very paranoid thought hit me. Every one of those previews gave me a new ad banner.

Now that Slashdot is part of the "beleaguered" (TM of Apple Computers, Inc, since 1980; used without permission) VA Linux/Software/Anime-lovers Keiretsu, page hits and ad revenue is more important than ever. A few "bugs" here and there may more than triple ad revenue, as I've seen more individual ads in the last month than ever before due to the repetitive clicking I do in order to do a simple post.

Just a thought. Intentional or not, Slashdot is benefitting financially from these coding SNAFUs. What do you think? Since XFiles is over, and they killed the Lone Gunmen, I need to get my conspiracy fix somewhere, and here's as good a place as any.

This discussion has been archived. No new comments can be posted.

I Was Always Paranoid, But This Is Paranoid Pro

Comments Filter:
  • Comment removed based on user account deletion
  • Why are you hitting the back button? If you want to preview and change, doesn't it make more sense to hit the preview button on each page without going back?
    • Hey Turg!

      When I hit the 'Preview', I often get this blank screen except for the headers and sidebar with the sections stuff and whatnot. I can't actually see what I typed because it's not there! So I have to hit 'Back' to try to 'Preview' it again. It's very weird. Maybe the other guys are right, maybe it's Mozilla... I hope not, I dig Moz. But I've noticed it's definitely worse during Slashdot's heavy load hours of the day, when we're all supposed to be working and are surfing Slashdot instead....

  • One of the things that has annoyed me in the year-and-a-half since I switched from AWeb to Mozilla, is the behavior of the back arrow. IMHO (probably because I got used to this behavior over many years), back arrow should never under any circumstances, load a page. It should always come from local cache. Regardless of headers.

So... did you ever wonder, do garbagemen take showers before they go to work?

Working...