If you find yourself at risk of mistakenly following a goatse.cx link at work, you're already debatably off task.
I can also see this creating a snowball effect of content rating. Sure; we'd start with NSFW and SFW, but like a previous post mentioned, what is safe for work in some instances is not safe in others. This could rapidly become a gangly beast of keywords assigning metadata to content, which would not be fun for web developers.
Like any good web technology, the only way it will work is large-scale adoption. IMHO, if this WAS standardized and 25% of websites with NSFW content adopted it, that would be pretty damn impressive. It doesn't help you, the off-task employee, with the other 75% though.
In terms of ad revenue, sites that depend on impressions or ad clicks would never mark content as NSFW; their ads would never be viewed.
That would be quite nice. My first decree as Interstellar Czar of Music Appreciation would be to go to your local music store purchase John Coltrane's "A Love Supreme" and listen to what real expression of rhythm and soul is. Nerdcore is funny and entertaining, but it's sure as hell not a musical movement.
As the sysadmin of an outfit who provides email news letters for sports teams and leagues, the blockheaded nature of "spam control" major ISPs implement these days is quite frustrating. On a daily basis, we deal with Subscriber Subset A who decide they no longer like their hometown's minor league baseball team and click the "This is Spam" button in their pretty little ISP-GUI inboxes (AOL, *cough*). This, in turn, causes ISPs to freak and rate limit us until the cows come home. Meanwhile, Subscriber Subset B missed last nights game and is irate that they did not receive the Game Notes and Box Score. While we are dealing with our clients complaints, the ISP has already contacted our upstream provider who is now threatening to unplug not only our SMTP box, but our entire WWW pool.
And, hell if I'm going to pay GoodMail for beans. Sigh...
Slashdot Mirror
If you find yourself at risk of mistakenly following a goatse.cx link at work, you're already debatably off task.
I can also see this creating a snowball effect of content rating. Sure; we'd start with NSFW and SFW, but like a previous post mentioned, what is safe for work in some instances is not safe in others. This could rapidly become a gangly beast of keywords assigning metadata to content, which would not be fun for web developers.
Like any good web technology, the only way it will work is large-scale adoption. IMHO, if this WAS standardized and 25% of websites with NSFW content adopted it, that would be pretty damn impressive. It doesn't help you, the off-task employee, with the other 75% though.
In terms of ad revenue, sites that depend on impressions or ad clicks would never mark content as NSFW; their ads would never be viewed.
Good idea though.
Under an umbrella on a beach in the cayman islands.
That would be quite nice. My first decree as Interstellar Czar of Music Appreciation would be to go to your local music store purchase John Coltrane's "A Love Supreme" and listen to what real expression of rhythm and soul is. Nerdcore is funny and entertaining, but it's sure as hell not a musical movement.
I've never witnessed such a display of an utter lack of creative musical prowess! Does anybody else feel embarrassed to be white?
As the sysadmin of an outfit who provides email news letters for sports teams and leagues, the blockheaded nature of "spam control" major ISPs implement these days is quite frustrating. On a daily basis, we deal with Subscriber Subset A who decide they no longer like their hometown's minor league baseball team and click the "This is Spam" button in their pretty little ISP-GUI inboxes (AOL, *cough*). This, in turn, causes ISPs to freak and rate limit us until the cows come home. Meanwhile, Subscriber Subset B missed last nights game and is irate that they did not receive the Game Notes and Box Score. While we are dealing with our clients complaints, the ISP has already contacted our upstream provider who is now threatening to unplug not only our SMTP box, but our entire WWW pool.
And, hell if I'm going to pay GoodMail for beans. Sigh...