Ad blocking is under attack | Adguard

Andrey Meshkov (Adguard); Ad blocking is under attack; In Their Blog;

tl;dr → An ad Some server was delisted by an ad block list due to a DMCA order.

Mentions

  • Filter Lists, lists of filters
  • Admiral
  • functionalclam.com

Participants

Who

Referenced

Time Line

2017-08-11, 08:09 GMT
an EFF representative
offered their help to EasyList maintainers.
2017-08-11 11:34 GMT
Filters maintainers commented on the situation
2017-08-11 13:13 GMT
Comment from Admiral
2017-08-11 17:05 GMT
The original DMCA notice is now available
2017-08-11 21:13 GMT
Github representative commented on the situation
2017-08-10
commit in the repo of EasyList, 2017-08-10.
tl;dr → The “functionalclam.com” domain was removed with a comment “Removed due to DMCA takedown request”.
2017-07-19 (2017-08-11 – 23 days)
commit, 2017-08-11 minus 23 days
tl;dr → added “functionalclam.com” to EasyList.

  • @dmcahelper (an account at GitHub?) threatened <someone/> or <something/>.
  • A similarity is observed in
    Staff (Block Ad Block); Is Adblock Plus Violating The DMCA; In Their Blog; WHEN?

Actualities

Leading with commas — ugly or efficient? An investigation over 320 GB of SQL code | Hackernoon

Leading with commas — ugly or efficient? An investigation over 320 GB of SQL code;
Felipe Hoffa (staff?); In Hackernoon; 2017-07-26.
Teaser: Winning arguments with data: Let’s analyze 320 Gigabytes of open source SQL code to determine if we should use trailing or leading commas. Popularity is not enough — can we determine which style leads to success?
Felipe Hoffa, Developer Advocate @Google, San Francisco

Concept

# trailing commas
SELECT name,
  company,
  salary,
  state,
  city
FROM `employees`
WHERE state='CA'
# leading commas
SELECT name
  , company
  , salary
  , state
  , city
FROM `employees`
WHERE state='CA'

Summary

  • Categories
    • Leading Commas → fewest projects
    • Mixed Style → some more
    • Trailing Commas → the majority
  • Projects that allow a mix of styles show the most success.
  • Projects that enforce leading commas
    •  don’t show as much success as mixed
    • more successful than trailing
  • The trend is stable throughout the years  2016 & 2017.

Results

presented as an image, not as data:

Mentions

  • BigQuery
  • SQL is shown.

Actualities

#standardSQL
WITH comma_lines_per_files AS  (
    SELECT sample_repo_name, sample_stars_2016, sample_stars 
      , REGEXP_CONTAINS(line, r',\s*$') has_trailing 
      , REGEXP_CONTAINS(line, r'^\s*,') has_leading
      , line
    FROM `fh-bigquery.github_extracts.contents_sql`
      , UNNEST(SPLIT(content, '\n')) line
    WHERE line LIKE '%,%'
    AND LENGTH(line)>5
), stats_per_repo AS (
  SELECT sample_repo_name
    , MAX(has_leading) has_leading
    , MAX(has_trailing) has_trailing
    , ANY_VALUE(line) sample_line
    , ANY_VALUE(sample_stars) stars
    , ANY_VALUE(sample_stars_2016) stars_2016
    , (SELECT COUNT(DISTINCT actor.id) FROM `githubarchive.month.2017*` WHERE sample_repo_name = repo.name AND type='WatchEvent') stars_2017
    , (SELECT COUNT(DISTINCT actor.id) FROM `githubarchive.month.2017*` WHERE sample_repo_name = repo.name) actors_2017
    , (SELECT COUNT(*) FROM `githubarchive.month.2017*` WHERE sample_repo_name = repo.name) activity_2017
  FROM comma_lines_per_files
  GROUP BY sample_repo_name
)
SELECT COUNT(DISTINCT sample_repo_name) repos
  , IF(has_trailing, IF(has_leading, 'both', 'trailing'), IF(has_leading, 'leading', 'none')) commas 
  , ROUND(AVG(stars), 2) avg_stars
  , ROUND(AVG(stars_2016), 2) stars_2016
  , ROUND(AVG(stars_2017), 2) stars_2017
  , ROUND(AVG(actors_2017), 2) actors_2017
  , ROUND(AVG(activity_2017), 2) activity_2017
  , STRING_AGG(sample_repo_name ORDER BY stars DESC LIMIT 3) top_repos
FROM stats_per_repo
GROUP BY commas
ORDER BY repos
repos commas stars stars17 actors17 activity17 top_repos 571 leading 22.99 7.36 10.04 39.89 drone/drone,aspnetboilerplate/aspnetboilerplate,HazyResearch/deepdiv2847 both true 29.37 6.44 11.73 156.63 apache/spark,begriffs/postgrest,mybatis/mybatis-3  
5933 none false 20.05 4.8 7.57 54.43 ajaxorg/ace,zulip/zulip,fivethirtyeight/data  
69665 trailing false 13.06 3.22 5.49 43.68 Microsoft/vscode,rails/rails,kubernetes/kubernetes

Consensual Software: How to Prioritize User Safety Before It Becomes a PR Nightmare | InfoQ

Consensual Software: How to Prioritize User Safety Before It Becomes a PR Nightmare; Danielle Leong; In InfoQ; 2017-05-18.

tl;dr → GuitHub is on it. Ms. Leong’s team comprise the guardians.  Their rubric appears midway.

Rebuttal: Machines work for their owners. In SOA, that is not you, you are the product.

Danielle Leong
  • engineer, Community & Safety, GitHub
  • founder developer, Feerless
    <quote>an app that provides trigger warnings for Netflix users with PTSD</quote>
    One “develops” an app; one “founds” a religion, a country or a company.

Rubric

<quote>

  • Is every user explicitly consenting to use this feature, or are we assuming they want to participate?
  • Is it easy to opt-out of this feature?
  • Is it easy to block a person who is abusing the feature to spam, harass, or threaten others?
  • Are there audit logs to see how users are interacting with your feature? Metrics?
  • Is it easy for your support staff to untangle what happened if an incident occurs?
  • How much personally identifying information is public?
    • How easy is it to redact past or sensitive information? (i.e. a trans person’s deadname, a user’s physical address, private email addresses, AWS keys, etc)
    • Do we really need to store or expose personally identifying information?
  • Are you allowing users to upload images?
    • Are you filtering out porn?
    • Are all users explicitly consenting to receiving uploaded images?
    • Can you solve this problem by using a pre-vetted image integration like GIPHY?
  • Do you allow 0-day accounts the same privileges as a vetted user?
  • How could a stalker ex use this feature to hurt someone?
  • How are your support tickets handled for each new release?

</quote>

Collaboration on Social Media: Analyzing Successful Projects on Social Coding | Yoshikawa, Iwata, Sawada

Yuya Yoshikawa, Tomoharu Iwata, Hiroshi Sawada; Collaboration on Social Media: Analyzing Successful Projects on Social Coding; In Some Venue; 2014-08-25; 10 pages; landing.

Abstract

Social Coding Sites (SCSs) are social media services for sharing software development projects on the Web, and many open source projects are currently being developed on SCSs. One of the characteristics of SCSs is that they provide a platform on social networks that encourages collaboration between developers with the same interests and purpose. For example, external de velopers can easily report bugs and improvements to the project members.

In this paper, we investigate keys to the success of projects on SCSs based on large data consisting of more than three hundred thousand projects. We focus on the following three perspectives: 1) the team structure, 2) social activity with external developers, and 3) content developed by the project. To evaluate the success quantitatively, we define activity, popularity and sociality as success indexes. A summary of the findings we obtained by using the techniques of correlation analysis, social network analysis and topic extraction is as follows: the number of project members and the connectivity between the members are positively correlated with success indexes. Second, projects that faith- fully tackle change requests from external developers are more likely to be successful. Third, the success indexes differ between topics of softwares developed by projects. Our analysis suggests how to be successful in various projects, not limited to social coding.

How A Hacker Nabbed $600,000 In Two Months By Googling People’s Home Networks for Synology Home Cloud NAS Servers | Business Insider

How A Hacker Nabbed $600,000 In Two Months By Googling People’s Home Networks for Synology Home Cloud NAS Servers; ; In Business Insider; 2014-06-17.

Mentions

  • Dell
  • Synology
  • Pseudonym: Folio on GitHub.
  • <quote>The hacker’s exploits were documented by Dell’s security team</quote>
  • <quote>In 2013, a security researcher discovered a flaw with the Synology product that let a hacker find, and ultimately control, these computer storage devices by searching for them on Google. </quote>