1263020 - Additiional edits to whitelist and Remove additional adult sites from domain whitelist

Status: RESOLVED INCOMPLETE

(Hello (Loop) :: Client, defect)

Description

[Ian Bicking (:ianbicking)]

In https://bugzilla.mozilla.org/show_bug.cgi?id=1261467#c5 it was noted that at least these adult domains are in the whitelist:

  gotporn.com, upornia.com, mundosexanuncio.com

We might want to add an additional blacklist?

Comment 1

[chris hofmann]

also remove txxx.com

Comment 2

[chris hofmann]

here is another potencial problem with the list.

alexa usually summarizes the domain (calls a site "alfredangelo.com" where the real content lives at "www.alfredangelo.com" ) and doesn't seem to follow redirects very well where the site content is moved to another domain entirely.  So the result is if we don't do wild carding of first elements of the domain name or if we don't spider to understand where the current redirects live then the whitelist will miss matches and not report hello users share sites where they might be.

I'll attach output where I found moved content when trying to visit the alexa link that's in our whitelist.

Comment 3

[chris hofmann]

Attachment: moved.txt

sites where alexa doesn't understand where the real content lives that users might be visiting and sharing via hello.

Comment 4

[chris hofmann]

ignore the "meta site 'name of other site info...'" at the end of each line.  curl didn't want to seem to do newlines very well when visiting some sites and spitting out content so that's usually the name of the next site that I tried to visit in my spider.

Comment 5

[chris hofmann]

http://jav68.me/ is another international porn site that should be removed from the current list.  

It was found with a simple spider that visited all sites in the list then looked for advertisements of porn and sex in the meta keyword and description tags of the content.

In this case I was looking for english terms that turned up in the meta tags of all the sites.  More work would be needed to turn up meta tags that contained porn and sex expressed in international languages.

If we want this list to really work as intended I think more spidering and visual reviewing and testing of content is needed.

Comment 6

[chris hofmann]

only mozilla.org is on the list.  Ian mentioned one of the objectives of the study was to learn about employee/mozillian use of hello.  If that's to be accomplished we ought to add mozilla.com and any domain where work gets done to discuss projects (groups.google.com...  github, hg, ), communicate ( https://v.mozilla.com ) check for benefit and employee info  http://elance.com/ , workday etc..., schedule meetings and arrange calendars  ( http://tribe2016may.eventzilla.net/web/event?eventid=2138836900 ), arrange travel ( https://www.egencia.com/ ) and other things that might pop up in a common work day and would be interesting to share or discuss on a private side channel.

Comment 7

[chris hofmann]

yammer would be another good addition if you are looking to see if Mozillians are sharing confidential and internal posts specifically you would be looking for  https://www.yammer.com/mozilla.com/#/threads/company?type=general  but generally the white list entry would be https://www.yammer.com/

Comment 8

[Mark Banner (:standard8)]

Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.