Objectionable Flag
If you are a keen observer of the blogspot.com environment you may have noticed the recent addtion to the strip across the top of this blog (and others). It now shows the word "Flag?" and a little picture of a flag. This new feature allows readers (or passersby) to mark a particular blog (or post) as "objectionable" to them.
Google reassures us that there is nothing to worry about:
Our main beef with this new "feature" though is that it has introduced invalid html code that is beyond the control of the user into every page of every blog on the system. We have gone to quite a bit of trouble to validate DLMSY to the "XHTML 1.0 Transitional" standard and to keep it validated. Admittedly, the actual impact on the viewing experience of readers is probably nil.
We reported the bug to Customer Service, but since it is "minor" there is no guarantee they will fix it anytime soon. The problem (which you can see by clicking on the W3C icon at the bottom of this page) is an improper "br" tag. All that is necessary to fix the error is to add a space and "/" between the "br" and the ">" of the tag.
Technically, the W3C icon is only supposed to be displayed on validated pages, but we're leaving it for now, hoping Google will fix this.
Google reassures us that there is nothing to worry about:
Blogger Help : What is the "Flag" button?: "What is the 'Flag' button?However, in the same article they also say:
The Flag button is not censorship and it cannot be manipulated by angry mobs. Political dissent? Incendiary opinions? Just plain crazy? Bring it on."
"Special Case for Hate SpeechWe'd be interested in seeing a clear, objective definition of "hate speech," if one exists. Absent that, it seems there is some potential for manipulation by "angry mobs." Mainly, this just seems unnecessary, a waste of bandwidth, and something to make the pages load a little slower.
When the community has voted and hate speech is identified on Blog*Spot, Google may exercise its right to place a Content Warning page in front of the blog and set it to 'unlisted.'"
Our main beef with this new "feature" though is that it has introduced invalid html code that is beyond the control of the user into every page of every blog on the system. We have gone to quite a bit of trouble to validate DLMSY to the "XHTML 1.0 Transitional" standard and to keep it validated. Admittedly, the actual impact on the viewing experience of readers is probably nil.
We reported the bug to Customer Service, but since it is "minor" there is no guarantee they will fix it anytime soon. The problem (which you can see by clicking on the W3C icon at the bottom of this page) is an improper "br" tag. All that is necessary to fix the error is to add a space and "/" between the "br" and the ">" of the tag.
Technically, the W3C icon is only supposed to be displayed on validated pages, but we're leaving it for now, hoping Google will fix this.
<< Home