C
clintonG
I am really tired of subversive page title spamming morons from sites like
ASPAlliance.com whose page titles are either not present or are stuffed with
spam preventing or hindereing the page from being saved as a Favorite when
using IE or other browsers.
Selecting Favorites from the IE toolbar to open the Favorites Explorer Bar
(renamed yet once again as a 'task pane') will not allow Favorites to be
saved when the page title is stuffed with spam making the length of the page
title too long to be saved from the toolbar. Editing out all of the spam and
reformatting the page title is a serious waste of time. Spamming page titles
results in Favorites that can not be read when wanting to recall a Favorite
because the Windows user interface does not support resizable dialogs. This
seems to be true when using other browsers as well.
Subversive Page Title Spamming:
ASPAlliance.com The #1 ASP.NET Community CodeSnip Refreshing a Parent Page
from a Popup Page in VB.NET
Professional and Considerate Implementation:
Refreshing a Parent Page from a Popup Page in VB.NET - ASPAlliance.com
NOTE:
** There is no reason to spam page titles with crap such as 'The #1 ASP.NET
Community' or 'CodeSnip' or anything else that is not specific to the page
itself and does nothing with regard to SEO..
** The identity of the hosting site should 'follow' the page title, not
'preceed' it to enable the Favorite to be read when wanting to recall.
Because IE and other browsers restrict the width of their 'task panes' and
dialogs which often can not be resized all we can read when recalling a
Favorite is the page title spam. I contend it is more important to make the
actual page title available than the name of the website and useless spam
where the article resides. Hello you selfish moronic spamming pigs?
** I'd even like to propose for discussion a standardized 'well-formed' page
title schema for software development articles:
[language] page title (resource)
[VB] Refreshing a Parent Page from a Popup Page (ASPAlliance.com)
Noting that such a proposed page title schema is a compromise that still
impacts the use of restrictive task panes and dialogs by requireing a prefix
of four or five characters that take up space but at least provides valuable
meaning rather than page title spam.
I mean this really gets to me and I know my own implementations have not
been as ideal as I am now striving to achieve. We live and learn do we not?
Most of us work really hard to learn to be as good as we can and care about
those using what we produce but others are simply greedy moronic spamming
pigs that will do anything to break and hinder usage to make sure they stick
their name in your face and will not change or even respond to e-mail asking
for such change. There is no need for this as it only breeds discontent.
I have been sending a 'nice' message to several sites including
ASPAlliance.com and have been ignored. Now I am of the mind to simply say
f*ck them as they are no different than any other spammers.
What do you say?
ASPAlliance.com whose page titles are either not present or are stuffed with
spam preventing or hindereing the page from being saved as a Favorite when
using IE or other browsers.
Selecting Favorites from the IE toolbar to open the Favorites Explorer Bar
(renamed yet once again as a 'task pane') will not allow Favorites to be
saved when the page title is stuffed with spam making the length of the page
title too long to be saved from the toolbar. Editing out all of the spam and
reformatting the page title is a serious waste of time. Spamming page titles
results in Favorites that can not be read when wanting to recall a Favorite
because the Windows user interface does not support resizable dialogs. This
seems to be true when using other browsers as well.
Subversive Page Title Spamming:
ASPAlliance.com The #1 ASP.NET Community CodeSnip Refreshing a Parent Page
from a Popup Page in VB.NET
Professional and Considerate Implementation:
Refreshing a Parent Page from a Popup Page in VB.NET - ASPAlliance.com
NOTE:
** There is no reason to spam page titles with crap such as 'The #1 ASP.NET
Community' or 'CodeSnip' or anything else that is not specific to the page
itself and does nothing with regard to SEO..
** The identity of the hosting site should 'follow' the page title, not
'preceed' it to enable the Favorite to be read when wanting to recall.
Because IE and other browsers restrict the width of their 'task panes' and
dialogs which often can not be resized all we can read when recalling a
Favorite is the page title spam. I contend it is more important to make the
actual page title available than the name of the website and useless spam
where the article resides. Hello you selfish moronic spamming pigs?
** I'd even like to propose for discussion a standardized 'well-formed' page
title schema for software development articles:
[language] page title (resource)
[VB] Refreshing a Parent Page from a Popup Page (ASPAlliance.com)
Noting that such a proposed page title schema is a compromise that still
impacts the use of restrictive task panes and dialogs by requireing a prefix
of four or five characters that take up space but at least provides valuable
meaning rather than page title spam.
I mean this really gets to me and I know my own implementations have not
been as ideal as I am now striving to achieve. We live and learn do we not?
Most of us work really hard to learn to be as good as we can and care about
those using what we produce but others are simply greedy moronic spamming
pigs that will do anything to break and hinder usage to make sure they stick
their name in your face and will not change or even respond to e-mail asking
for such change. There is no need for this as it only breeds discontent.
I have been sending a 'nice' message to several sites including
ASPAlliance.com and have been ignored. Now I am of the mind to simply say
f*ck them as they are no different than any other spammers.
What do you say?