W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2010

[Bug 11505] New: the problem i try to solve is spam pop ups and aggressive spam page authoring (which ban you from going backward and is obviously made up for banks and exploited by spammers). my idea is to depreciate (not allow) pop ups and also the annoying backward bro

From: <bugzilla@jessica.w3.org>
Date: Thu, 09 Dec 2010 01:19:39 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-11505-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11505

           Summary: the problem i try to solve is spam pop ups and
                    aggressive spam page authoring (which ban you from
                    going backward and is obviously made up for banks and
                    exploited by spammers). my idea is to depreciate (not
                    allow) pop ups and also the annoying backward bro
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML Canvas 2D Context (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: http://dev.w3.org/html5/spec/Overview.html
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top

Comment:
the problem i try to solve is spam pop ups and aggressive spam page authoring
(which ban you from going backward and is obviously made up for banks and
exploited by spammers).
my idea is to depreciate (not allow) pop ups and also the annoying backward
browsing lock (we had more of those in the past) in any regular http and allow
it only on https. I thought a lot before posting it here. i think it can work
although I am really not sure if it is technically possible to separate code
of https and http but maybe it is and maybe it can make the web act better.  
as for video I am trying to develop a content that it might be need video full
screen. it'd suppose to be GOOD and Valuable content so i think it's a pity to
throw it to garbage. the visual is also very important side of the browsing
experience. So there is a new  idea i have which is to make httpv for video or
m - media streaming which will make video streaming online and prevent
spamming. maybe a library of approved sites  can work but it's too
monarchistic and against the web open spirit so  it is probably not such a
good idea. 

If you think these ideas are good or crappy. i like to know. Sorry if i am
confusing and got you confused too. it's a pretty vogue view from here. 

Sivan langer

donotonly@gmail.com


Posted from: 109.186.27.215

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 9 December 2010 01:19:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 December 2010 01:19:48 GMT