Thu Nov 21 23:22:45 2024
EVENTS
 FREE
SOFTWARE
INSTITUTE

POLITICS
JOBS
MEMBERS'
CORNER

MAILING
LIST

NYLXS Mailing Lists and Archives
NYLXS Members have a lot to say and share but we don't keep many secrets. Join the Hangout Mailing List and say your peice.

DATE 2014-12-01

HANGOUT

2024-11-21 | 2024-10-21 | 2024-09-21 | 2024-08-21 | 2024-07-21 | 2024-06-21 | 2024-05-21 | 2024-04-21 | 2024-03-21 | 2024-02-21 | 2024-01-21 | 2023-12-21 | 2023-11-21 | 2023-10-21 | 2023-09-21 | 2023-08-21 | 2023-07-21 | 2023-06-21 | 2023-05-21 | 2023-04-21 | 2023-03-21 | 2023-02-21 | 2023-01-21 | 2022-12-21 | 2022-11-21 | 2022-10-21 | 2022-09-21 | 2022-08-21 | 2022-07-21 | 2022-06-21 | 2022-05-21 | 2022-04-21 | 2022-03-21 | 2022-02-21 | 2022-01-21 | 2021-12-21 | 2021-11-21 | 2021-10-21 | 2021-09-21 | 2021-08-21 | 2021-07-21 | 2021-06-21 | 2021-05-21 | 2021-04-21 | 2021-03-21 | 2021-02-21 | 2021-01-21 | 2020-12-21 | 2020-11-21 | 2020-10-21 | 2020-09-21 | 2020-08-21 | 2020-07-21 | 2020-06-21 | 2020-05-21 | 2020-04-21 | 2020-03-21 | 2020-02-21 | 2020-01-21 | 2019-12-21 | 2019-11-21 | 2019-10-21 | 2019-09-21 | 2019-08-21 | 2019-07-21 | 2019-06-21 | 2019-05-21 | 2019-04-21 | 2019-03-21 | 2019-02-21 | 2019-01-21 | 2018-12-21 | 2018-11-21 | 2018-10-21 | 2018-09-21 | 2018-08-21 | 2018-07-21 | 2018-06-21 | 2018-05-21 | 2018-04-21 | 2018-03-21 | 2018-02-21 | 2018-01-21 | 2017-12-21 | 2017-11-21 | 2017-10-21 | 2017-09-21 | 2017-08-21 | 2017-07-21 | 2017-06-21 | 2017-05-21 | 2017-04-21 | 2017-03-21 | 2017-02-21 | 2017-01-21 | 2016-12-21 | 2016-11-21 | 2016-10-21 | 2016-09-21 | 2016-08-21 | 2016-07-21 | 2016-06-21 | 2016-05-21 | 2016-04-21 | 2016-03-21 | 2016-02-21 | 2016-01-21 | 2015-12-21 | 2015-11-21 | 2015-10-21 | 2015-09-21 | 2015-08-21 | 2015-07-21 | 2015-06-21 | 2015-05-21 | 2015-04-21 | 2015-03-21 | 2015-02-21 | 2015-01-21 | 2014-12-21 | 2014-11-21 | 2014-10-21 | 2014-09-21 | 2014-08-21 | 2014-07-21 | 2014-06-21 | 2014-05-21 | 2014-04-21 | 2014-03-21 | 2014-02-21 | 2014-01-21 | 2013-12-21 | 2013-11-21 | 2013-10-21 | 2013-09-21 | 2013-08-21 | 2013-07-21 | 2013-06-21 | 2013-05-21 | 2013-04-21 | 2013-03-21 | 2013-02-21 | 2013-01-21 | 2012-12-21 | 2012-11-21 | 2012-10-21 | 2012-09-21 | 2012-08-21 | 2012-07-21 | 2012-06-21 | 2012-05-21 | 2012-04-21 | 2012-03-21 | 2012-02-21 | 2012-01-21 | 2011-12-21 | 2011-11-21 | 2011-10-21 | 2011-09-21 | 2011-08-21 | 2011-07-21 | 2011-06-21 | 2011-05-21 | 2011-04-21 | 2011-03-21 | 2011-02-21 | 2011-01-21 | 2010-12-21 | 2010-11-21 | 2010-10-21 | 2010-09-21 | 2010-08-21 | 2010-07-21 | 2010-06-21 | 2010-05-21 | 2010-04-21 | 2010-03-21 | 2010-02-21 | 2010-01-21 | 2009-12-21 | 2009-11-21 | 2009-10-21 | 2009-09-21 | 2009-08-21 | 2009-07-21 | 2009-06-21 | 2009-05-21 | 2009-04-21 | 2009-03-21 | 2009-02-21 | 2009-01-21 | 2008-12-21 | 2008-11-21 | 2008-10-21 | 2008-09-21 | 2008-08-21 | 2008-07-21 | 2008-06-21 | 2008-05-21 | 2008-04-21 | 2008-03-21 | 2008-02-21 | 2008-01-21 | 2007-12-21 | 2007-11-21 | 2007-10-21 | 2007-09-21 | 2007-08-21 | 2007-07-21 | 2007-06-21 | 2007-05-21 | 2007-04-21 | 2007-03-21 | 2007-02-21 | 2007-01-21 | 2006-12-21 | 2006-11-21 | 2006-10-21 | 2006-09-21 | 2006-08-21 | 2006-07-21 | 2006-06-21 | 2006-05-21 | 2006-04-21 | 2006-03-21 | 2006-02-21 | 2006-01-21 | 2005-12-21 | 2005-11-21 | 2005-10-21 | 2005-09-21 | 2005-08-21 | 2005-07-21 | 2005-06-21 | 2005-05-21 | 2005-04-21 | 2005-03-21 | 2005-02-21 | 2005-01-21 | 2004-12-21 | 2004-11-21 | 2004-10-21 | 2004-09-21 | 2004-08-21 | 2004-07-21 | 2004-06-21 | 2004-05-21 | 2004-04-21 | 2004-03-21 | 2004-02-21 | 2004-01-21 | 2003-12-21 | 2003-11-21 | 2003-10-21 | 2003-09-21 | 2003-08-21 | 2003-07-21 | 2003-06-21 | 2003-05-21 | 2003-04-21 | 2003-03-21 | 2003-02-21 | 2003-01-21 | 2002-12-21 | 2002-11-21 | 2002-10-21 | 2002-09-21 | 2002-08-21 | 2002-07-21 | 2002-06-21 | 2002-05-21 | 2002-04-21 | 2002-03-21 | 2002-02-21 | 2002-01-21 | 2001-12-21 | 2001-11-21 | 2001-10-21 | 2001-09-21 | 2001-08-21 | 2001-07-21 | 2001-06-21 | 2001-05-21 | 2001-04-21 | 2001-03-21 | 2001-02-21 | 2001-01-21 | 2000-12-21 | 2000-11-21 | 2000-10-21 | 2000-09-21 | 2000-08-21 | 2000-07-21 | 2000-06-21 | 2000-05-21 | 2000-04-21 | 2000-03-21 | 2000-02-21 | 2000-01-21 | 1999-12-21

Key: Value:

Key: Value:

MESSAGE
DATE 2014-12-20
FROM Ruben Safir
SUBJECT Re: [NYLXS - HANGOUT] DRM SOPA MPAA continuing advancement



This is the January 25th email from MPAA Global General Counsel Steven
Fabrizio, laying out the group's Goliath strategy:

Site Blocking/ISP Measures - INPUT REQUESTED - PRIVILEGED

We did not get to have a full discussion of site blocking during our
January meeting. However, I believe I have spoken with enough of you
individually to have a good read of the room as to our authority to
proceed with the necessary analysis. In this email, I outline the
planned scope of analysis. Because the analysis will involve some
expense for technical experts, consultants and lawyers (likely totalling
in the $200-300k range), I want to make sure we are on the same page. If
anyone disagrees with the plan, as described below, please let me know.
Otherwise, we will proceed, with the goal of having something to present
to you at our March meeting. (My goal is to use our February meeting to
present and discuss a detailed US Goliath strategy.)

SCOPE We have traditionally thought of site blocking in the US as a DMCA
512(j) issue. In some ways, that is too narrow and we plan to expand our
scope of inquiry on two levels. First, DMCA 512(j), by its terms,
necessarily creates an adversarial relationship with the target ISP (and
more generally with the ISP community). We have been exploring theories
under the All Writs Acts, which, unlike DMCA 512(j), would allow us to
obtain court orders requiring site blocking without first having to sue
and prove the target ISPs are liable for copyright infringement. This
may open up avenues for cooperative arrangements with ISPs. Second, we
start from the premise that site blocking is a means to an end (the end
being effective measures by ISPs to prevent infringement through
notorious pirate sites). There may be other equally effective measures
ISPs can take, and that they might be more willing to take voluntarily.
Our intention is to work with our own retained experts and Comcast (and
MPAA’s Technology group) to identify and study these other
possibilities, as well as US site blocking technical issues.

ANALYSIS The analyses that remain to be done fall into three general
categories:

Legal Analyses. The legal analyses that remain to be completed are the
smallest part of the project. We need to finalize the All Writs Act
research and confirm that developments in the law since the time of
previous 512(j) analyses do not materially affect the existing analyses.
In the event we recommend or present litigation options, we will also
consider tactical issues, including issues related to venue and the
interplay of the All Writs Act and 512(j).

Technical Analyses. Very little systematic work has been completed to
understand the technical issues related to site blocking in the US
and/or alternative measures IPSs might adopt. We will identify and
retain a consulting technical expert to work with us to study these
issues. In this context, we will explore which options might lead ISPs
to cooperate with us.

Political Analyses. Here, we mean political in the broadest sense. There
are important Hill issues to consider (e.g., how a strategy might impact
the copyright review process). We also need to consider ISP relations
issues (e.g., whether a strategy might impact the Copyright Alert
program, or any progress we have been making to secure voluntary ISP
assistance). Finally, in the post-SOPA world, we need to consider the
extent to which a strategy presents a risk of a public relations
backlash (e.g., whether a strategy might invigorate and galvanize the
anti-copyright forces we saw in the SOPA debates, and what ultimate
impact that might have). Each of these issues are like to have
considerations that cut in many directions. To get a comprehensive
assessment and weigh them in context, we will work closely with the MPAA
Policy and Communications teams (and, with them, will solicit input from
the appropriate studio policy and communications people).

Hopefully, at the conclusion of this set of analyses, we will be in a
position to make a decision that is informed by all considerations of
consequence.

If you have any questions, or want to talk through any of this,
don’t hesitate to call. Best,
SBF


On Sat, Dec 20, 2014 at 06:11:05PM -0500, Ruben Safir wrote:
>
> http://www.theverge.com/2014/12/12/7382287/project-goliath
>
> Project Goliath: Inside Hollywood's secret war against Google
>
> SOPA was just the beginning
>
> By Russell Brandom
> on December 12, 2014 12:59 pm
> Email
> -at-russellbrandom
>
> 214
> (Spencer Platt/Getty Images)
> Share on Facebook (5,026) Tweet (2,669)
> Share Share (468) Pin (1)
>
> What is "Goliath" and why are Hollywood’s most powerful lawyers
> working to kill it?
>
> In dozens of recently leaked emails from the Sony hack, lawyers from the
> MPAA and six major studios talk about "Goliath" as their most powerful
> and politically relevant adversary in the fight against online piracy.
> They speak of "the problems created by Goliath," and worry "what Goliath
> could do if it went on the attack." Together they mount a multi-year
> effort to "respond to / rebut Goliath’s public advocacy" and
> "amplify negative Goliath news." And while it’s hard to say for
> sure, significant evidence suggests that the studio efforts may be
> directed against Google.
>
> At the beginning of this year, the MPAA and six studios — Universal,
> Sony, Fox, Paramount, Warner Bros., and Disney — joined together to
> begin a new campaign against piracy on the web. A January 25th email
> lays out a series of legally and technically ambitious new tools,
> including new measures that would block infringing sites from reaching
> customers of many major ISPs. Documents reviewed by The Verge detail the
> beginning of a new plan to attack piracy after the federal SOPA efforts
> failed by working with state attorneys general and major ISPs like
> Comcast to expand court power over the way data is served. If
> successful, the result would fundamentally alter the open nature of the
> internet.
>
> mpaa goliath
>
> "We start from the premise that site blocking is a means to an end,"
> says MPAA general counsel Steven Fabrizio. "There may be other equally
> effective measures ISPs can take, and that they might be more willing to
> take voluntarily." According to the email, the group has retained its
> own technical experts and is working with Comcast (which owns Universal)
> to develop techniques for blocking or identifying illegally shared files
> in transit.
>
> That strategy also involves significant political risks. "In the
> post-SOPA world, we need to consider the extent to which a strategy
> presents a risk of a public relations backlash," Fabrizio continues,
> "whether a strategy might invigorate and galvanize the anti-copyright
> forces we saw in the SOPA debates." SOPA, also known as the Stop Online
> Piracy Act, proposed ambitious new site-blocking measures in 2011, but
> was ultimately defeated by coordinated outcry from web companies and
> their users. The new emails suggest Hollywood hasn’t given up on the
> idea. "We have been exploring theories under the All Writs Acts, which,
> unlike DMCA 512(j), would allow us to obtain court orders requiring site
> blocking without first having to sue and prove the target ISPs are
> liable for copyright infringement," one email reads.
>
> The only thing standing in their way? Goliath.
>
> The MPAA’s venture is referred to over and over as "Project
> Goliath," an effort to take Goliath down, with each studio contributing
> funds towards a project that will benefit them all. One telling email
> — titled "Goliath data summary" — comes with an attachment
> titled "Search Engine Piracy Discussion (MPAA Discussion)," seeming to
> suggest the codename is a stand-in for Google. A number of
> Goliath-related emails also point to examples of copyright-infringing
> search results found on Google; the persistence of file-sharing links in
> Google search rankings has been a sore point in Hollywood for years.
> ""We start from the premise that site blocking is a means to an end.""
>
> The emails reveal a multi-pronged approach to defeating Goliath. One
> tactic is legal, convincing state prosecutors to take up the fight
> against Goliath. After a series of meetings at the National Association
> of Attorneys General in February, MPAA counsel Fabrizio writes, "Goliath
> has told the AGs to pound sand…they pretty clearly told the AGs that
> they aren’t going to do anything and essentially threatened the AGs
> with the possibility of attacking them as they attacked folks in DC
> during SOPA. The AGs did not like that." As a result, the counsels
> report a growing coalition of attorneys general willing to take action
> against Goliath, and the group budgeted $500,000 a year towards
> providing legal support. Much of that budget went towards retaining the
> prestigious law firm Jenner & Block, specifically Jenner partner and
> former US Associate Attorney General Thomas J. Perrelli, who has billed
> the group for as much as $40,000 a month.
>
> In other emails, Google comes up as a specific target. After a dispute
> over Google’s most recent anti-piracy measures in October, Fabrizio
> suggested further action may be yet to come. "We believe Google is
> overreacting — and dramatically so. Their reaction seems tactical
> (or childish)," the email reads. "Following the issuance of the CID
> [civil investigative demand] by [Mississippi attorney general Jim] Hood
> (which may create yet another uproar by Google), we may be in a position
> for more serious discussions with Google." A report from the previous
> February suggests that the Goliath group drafted civil investigative
> demands (similar to a subpoena) to be issued by the attorneys general.
> "Some subset of AGs (3-5, but Hood alone if necessary) should move
> toward issuing CIDs before mid-May," the email says. (Hood issued a CID
> against Google in July concerning pharmaceutical counterfeiting, but he
> does not appear to have issued any actions against the company since
> Fabrizio’s letter in October.)
> ""We believe Google is overreacting — and dramatically so.""
>
> The fight against Goliath also has an investigative side. Other emails
> describe a proposed project called Keystone — budgeted at $70,000
> — devoted to gathering enough evidence against Goliath to provoke
> further action by the state attorneys general. "There is only so far we
> can get with the AG’s unless we develop better evidence and
> intelligence against Goliath," an email reads, "and that is the budget
> for Keystone." The planning for the Goliath Project is laid out in
> dozens of emails after the initial January meeting, although the emails
> peter out after May for reasons that are still unclear. Still, budget
> projections suggest that the group was prepared for a long battle. "To
> take this through and have a reasonable chance of success, we probably
> would need to continue through year two," one email reads.
>
> In another instance, the group seemed to look to articles on political
> corruption not as a cautionary tale but as an instruction manual. In one
> email, the MPAA's Senior VP of State Government Affairs circulated an
> investigative New York Times series on lobbyists wielding increasing
> influence over state attorneys general. The series details many tactics
> involved in Project Goliath, including hiring former attorneys general
> as counsel and targeting officials at the state level where lobbying
> dollars may stretch farther. The MPAA official offered only the caption
> "FYI, first in a series of articles." The email was sent to 62 people,
> including executives at Paramount, Warner Bros., Fox, Comcast, and the
> RIAA.
> ""There is only so far we can get with the AG’s unless we develop
> better evidence and intelligence against Goliath.""
>
> Still, the emails reveal a remarkable hostility towards Goliath, and a
> persistent desire to stop copyright infringing traffic as it moves
> across the web, a position that puts it in stark conflict with many of
> the guiding principles of the web. That, in turn, has created a serious
> conflict with many of the companies that have grown powerful on the web,
> a fight that, without an ambitious action like Project Goliath, the
> industry seems primed to lose. As one counsel noted in March, "There is
> much to commend an expanded Goliath strategy — the status quo has
> not exactly been favorable for us and, absent our doing something, it
> doesn’t promise to get better anytime soon."
>
> As of press time, neither the MPAA nor Sony has responded to a request
> for comment. Google declined to comment.
>
> Additional reporting from Ross Miller and Bryan Bishop. Illustration by
> Dylan Lathrop.
>

  1. 2014-12-01 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: fraud warning]
  2. 2014-12-01 mrbrklyn-at-panix.com Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  3. 2014-12-01 mrbrklyn-at-panix.com Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  4. 2014-12-01 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: [Dng] fraud warning]
  5. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  6. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  7. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  8. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  9. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  10. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  11. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  12. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  13. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  14. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  15. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  16. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  17. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [Dng] fraud warning
  18. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [jaromil-at-dyne.org: Re: [Dng] fraud warning]
  19. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [martin-at-waschbuesch.de: Re: [Dng] fraud warning]
  20. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [jaromil-at-dyne.org: Re: [Dng] fraud warning]
  21. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [martin-at-waschbuesch.de: Re: [Dng] fraud warning]
  22. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  23. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [my-debian-mails-at-gmx.de: Re: [Dng] fraud warning]
  24. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [eagle1-at-maledet.to: Re: [Dng] fraud warning]
  25. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  26. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [mutek-at-riseup.net: Re: [Dng] fraud warning]
  27. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  28. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  29. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [eagle1-at-maledet.to: Re: [Dng] fraud warning]
  30. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [mutek-at-riseup.net: Re: [Dng] fraud warning]
  31. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  32. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  33. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [eagle1-at-maledet.to: Re: [Dng] fraud warning]
  34. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [dr.klepp-at-gmx.at: Re: [Dng] fraud warning]
  35. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  36. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [devuan-list1-at-dekkers.org.uk: Re: [Dng] fraud warning]
  37. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [stefan-at-ott.net: Re: [Dng] fraud warning]
  38. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [rueday37-at-gmail.com: Re: [Dng] fraud warning]
  39. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [m.panella-at-level28.org: Re: [Dng] fraud warning]
  40. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  41. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [my-debian-mails-at-gmx.de: Re: [Dng] fraud warning]
  42. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [devuan-list1-at-dekkers.org.uk: Re: [Dng] fraud warning]
  43. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  44. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [jaromil-at-dyne.org: Re: [Dng] fraud warning]
  45. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [xiep-at-openmailbox.org: Re: [Dng] fraud warning]
  46. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [mfidelman-at-meetinghouse.net: Re: [Dng] fraud warning]
  47. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  48. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  49. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: [Dng] fraud warning]
  50. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [martin-at-waschbuesch.de: Re: [Dng] fraud warning]
  51. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [my-debian-mails-at-gmx.de: Re: [Dng] fraud warning]
  52. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [jaromil-at-dyne.org: Re: [Dng] fraud warning]
  53. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [mfidelman-at-meetinghouse.net: Re: [Dng] fraud warning]
  54. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [hellekin-at-dyne.org: Re: [Dng] fraud warning]
  55. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  56. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [hellekin-at-dyne.org: Re: [Dng] fraud warning]
  57. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [devuan-list1-at-dekkers.org.uk: Re: [Dng] fraud warning]
  58. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] [mfidelman-at-meetinghouse.net: Re: [Dng] fraud warning]
  59. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  60. 2014-12-01 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  61. 2014-12-02 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Notes on Memory Cache and Internal Memory
  62. 2014-12-02 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] Re: [Dng] fraud warning
  63. 2014-12-05 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] NYLXS Linux Distribution
  64. 2014-12-07 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Computer Available
  65. 2014-12-07 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Fwd: Reminder: webOS Cloud Services to end January 15, 2015
  66. 2014-12-08 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Notes Done on In and Out, Operating Systemsm Modules and Memoery
  67. 2014-12-08 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Foundation for OPTCODE and Machine Instruction
  68. 2014-12-09 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] [LIU Comp Sci] Machine Instructions notes
  69. 2014-12-09 Ruben Safir <mrbrklyn-at-panix.com> Fwd: Re: [NYLXS - HANGOUT] [ruben-at-mrbrklyn.com: Re: Architecture
  70. 2014-12-09 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] CPU Instructions - Notes for Chapter 14
  71. 2014-12-10 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Assembler Class online and free
  72. 2014-12-10 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] laptop madness
  73. 2014-12-11 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Fwd: turning attibute values into relations?
  74. 2014-12-11 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Fwd: Invitation: Flatiron Alumni Present!
  75. 2014-12-12 mrbrklyn-at-panix.com Subject: [NYLXS - HANGOUT] [csconnection-at-computer.org: Is 3D Printing for You?]
  76. 2014-12-14 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] [mrbrklyn-at-panix.com: Re: [LIU Comp Sci] Answers to the final review
  77. 2014-12-15 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] sky fy
  78. 2014-12-17 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Fwd: Re: [opensuse] Firefox 34?
  79. 2014-12-18 Ruben <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] cowards
  80. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] linksys smart routes external connections
  81. 2014-12-20 eminker-at-gmail.com Re: [NYLXS - HANGOUT] linksys smart routes external connections
  82. 2014-12-20 eminker-at-gmail.com Re: [NYLXS - HANGOUT] linksys smart routes external connections
  83. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] DRM SOPA MPAA continuing advancement
  84. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] DRM SOPA MPAA continuing advancement
  85. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] DRM SOPA MPAA continuing advancement
  86. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] DRM SOPA MPAA continuing advancement
  87. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] DRM SOPA MPAA continuing advancement
  88. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] fighting back against the MPAA
  89. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] fighting back against the MPAA
  90. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] linksys smart routes external connections
  91. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] linksys smart routes external connections
  92. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Fraud Alerts
  93. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Fraud Alerts
  94. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Devuan Fork and Fraud
  95. 2014-12-20 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] DNS assualt by MPAA
  96. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] [jaromil-at-dyne.org: Re: [Dng] Devuan Fork and Fraud]
  97. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] [jonathan-at-plews.org.uk: Re: [Dng] Devuan Fork and Fraud]
  98. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Re: [Dng] Devuan Fork and Fraud
  99. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] [jaromil-at-dyne.org: Re: [Dng] Devuan Fork and Fraud]
  100. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] Re: [Dng] Devuan Fork and Fraud
  101. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  102. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  103. 2014-12-21 Ruben <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Fwd: Re: [Dng] Devuan Fork and Fraud
  104. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Re: [Dng] Devuan Fork and Fraud
  105. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Re: [NYLXS - HANGOUT] Re: [Dng] Devuan Fork and Fraud
  106. 2014-12-21 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Nice Paleontology Class
  107. 2014-12-22 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  108. 2014-12-22 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  109. 2014-12-22 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  110. 2014-12-22 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  111. 2014-12-22 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  112. 2014-12-22 Ruben Safir <mrbrklyn-at-panix.com> Re: [mrbrklyn-at-panix.com: [NYLXS - HANGOUT] Devuan Fork and Fraud]
  113. 2014-12-23 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Signal to Noise ration
  114. 2014-12-30 Ruben Safir <mrbrklyn-at-panix.com> Subject: [NYLXS - HANGOUT] Creating a New OS: Final Projects for MS degree

NYLXS are Do'ers and the first step of Doing is Joining! Join NYLXS and make a difference in your community today!