<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/">
  <channel>
    <title>Facebook</title>
    <link>https://www.linuxjournal.com/</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Facebook, Not Microsoft, Is the Main Threat to Open Source</title>
  <link>https://www.linuxjournal.com/content/facebook-not-microsoft-main-threat-open-source</link>
  <description>  &lt;div data-history-node-id="1340607" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/glyn-moody" lang="" about="https://www.linuxjournal.com/users/glyn-moody" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Glyn Moody&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;In the future, Facebook won't be a social-media site.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Facebook is under a lot of scrutiny and pressure at
the moment. It's accused of helping foreign actors to
subvert elections by using ads and fake accounts to spread lies—&lt;a href="https://www.newyorker.com/magazine/2018/10/01/how-russia-helped-to-swing-the-election-for-trump"&gt;in
the US&lt;/a&gt;, for example—and of acting as a conduit for terrorism in &lt;a href="https://www.nbcnews.com/tech/tech-news/streamed-facebook-spread-youtube-new-zealand-shooting-video-circulates-online-n983726"&gt;New
Zealand&lt;/a&gt; and elsewhere. &lt;a href="https://www.theverge.com/2018/9/4/17816572/tim-wu-facebook-regulation-interview-curse-of-bigness-antitrust"&gt;There
are calls&lt;/a&gt; to &lt;a href="https://www.nbcnews.com/tech/tech-news/elizabeth-warren-calls-break-facebook-google-amazon-n980911"&gt;break
up the company&lt;/a&gt; or at least to rein it in.
&lt;/p&gt;

&lt;p&gt;
In an evident attempt to head off those moves, and to limit the
damage that recent events have caused to Facebook's reputation, Mark
Zuckerberg has been publishing some long, philosophical posts that
attempt to address some of the main criticisms. In his most recent
one, he calls for new regulation of the online world in four areas: &lt;a href="https://www.facebook.com/4/posts/10107013839885441?sfns=mo"&gt;harmful
content, election integrity, privacy and data portability&lt;/a&gt;.
The call for data portability mentions Facebook's support for the &lt;a href="https://datatransferproject.dev/"&gt;Data Transfer Project&lt;/a&gt;.
That's clearly an attempt to counter accusations that Facebook
is monopolistic and closed, and to burnish Facebook's reputation
for supporting openness. Facebook does indeed use and support &lt;a href="https://opensource.facebook.com/"&gt;a large number of open-source
programs&lt;/a&gt;, so to that extent, it's a fair claim.
&lt;/p&gt;

&lt;p&gt;
Zuckerberg' previous post, from the beginning
of March 2019, is much longer, and it outlines an
important shift in how Facebook will work to what he calls &lt;a href="https://www.facebook.com/notes/mark-zuckerberg/a-privacy-focused-vision-for-social-networking/10156700570096634/"&gt;"A
Privacy-Focused Vision for Social Networking"&lt;/a&gt;. Greater protection
for privacy is certainly welcome. But, it would be naïve to think that
Zuckerberg's post is simply about that. Once more, it is an attempt to
head off a growing chorus of criticism—in this case, that Facebook
undermines data protection. This is the key idea:
&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;
I believe the future of communication will increasingly shift
to private, encrypted services where people can be confident what they
say to each other stays secure and their messages and content won't
stick around forever.
&lt;/p&gt;&lt;/blockquote&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/facebook-not-microsoft-main-threat-open-source" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 04 Jun 2019 13:24:19 +0000</pubDate>
    <dc:creator>Glyn Moody</dc:creator>
    <guid isPermaLink="false">1340607 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Time for Net Giants to Pay Fairly for the Open Source on Which They Depend</title>
  <link>https://www.linuxjournal.com/content/time-net-giants-pay-fairly-open-source-which-they-depend</link>
  <description>  &lt;div data-history-node-id="1340213" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/glyn-moody" lang="" about="https://www.linuxjournal.com/users/glyn-moody" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Glyn Moody&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;Net giants depend on open source: so where's the gratitude?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Licensing lies at the heart of open source.
Arguably, free software began
with &lt;a href="https://www.gnu.org/licenses/old-licenses/gpl-1.0.html"&gt;the
publication of the GNU GPL in 1989&lt;/a&gt;. And since then, open-source projects
are defined as such by virtue of &lt;a href="https://opensource.org/licenses"&gt;the licenses they adopt&lt;/a&gt; and
whether the latter meet the &lt;a href="https://opensource.org/osd"&gt;Open Source
Definition&lt;/a&gt;. The continuing importance of licensing is shown by the
periodic flame wars that erupt in this area. Recently, there have been two
such flarings of strong feelings, both of which raise important issues.
&lt;/p&gt;

&lt;p&gt;
First, we had the incident with &lt;a href="https://lernajs.io"&gt;Lerna&lt;/a&gt;, "a
tool for managing JavaScript projects with multiple packages". It came about
as a result of the way the US Immigration and Customs Enforcement (ICE) has
been &lt;a href="https://twitter.com/ACLU/status/1033084026893070338"&gt;separating
families&lt;/a&gt; and &lt;a href="https://www.bbc.com/news/world-us-canada-44518942"&gt;holding children in
cage-like cells&lt;/a&gt;. The Lerna core team was appalled by this behavior and
wished to do something concrete in response. As a result, it &lt;a href="https://github.com/lerna/lerna/pull/1616"&gt;added an extra clause to the
MIT license&lt;/a&gt;, which forbade a list of companies, including Microsoft,
Palantir, Amazon, Motorola and Dell, from being permitted to use the code:
&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;
For the companies that are known supporters of ICE: Lerna will no
longer be licensed as MIT for you. You will receive no licensing rights and
any use of Lerna will be considered theft. You will not be able to pay for a
license, the only way that it is going to change is by you publicly tearing
up your contracts with ICE.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;
Many sympathized with the feelings about the actions of the ICE and the
intent of the license change. However, many also pointed out that such a
move went against the core principles of both free software and open source.
&lt;a href="https://www.gnu.org/philosophy/free-sw.en.html"&gt;Freedom 0 of the
Free Software Definition&lt;/a&gt; is "The freedom to run the program as you wish,
for any purpose." Similarly, the Open Source Definition requires "No
Discrimination Against Persons or Groups" and "No Discrimination Against
Fields of Endeavor". The situation is clear cut, and it didn't take long for
the Lerna team to realize their error, and &lt;a href="https://github.com/lerna/lerna/pull/1633"&gt;they soon reverted the
change&lt;/a&gt;:

&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/time-net-giants-pay-fairly-open-source-which-they-depend" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Mon, 05 Nov 2018 13:00:00 +0000</pubDate>
    <dc:creator>Glyn Moody</dc:creator>
    <guid isPermaLink="false">1340213 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Weekend Reading: Privacy</title>
  <link>https://www.linuxjournal.com/content/weekend-reading-privacy</link>
  <description>  &lt;div data-history-node-id="1339865" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/carlie-fairchild" lang="" about="https://www.linuxjournal.com/users/carlie-fairchild" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Carlie Fairchild&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;
Most people simply are unaware of how much personal data they leak on a
daily basis as they use their computers. Enter this weekend's reading topic:
Privacy.
&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;
&lt;a href="https://www.linuxjournal.com/content/foss-project-spotlight-tutanota-first-encrypted-email-service-app-f-droid"&gt;FOSS Project Spotlight: Tutanota, the First Encrypted Email Service with an App on F-Droid&lt;/a&gt;
by Matthias Pfau
&lt;/p&gt;&lt;p&gt;

&lt;/p&gt;&lt;p&gt;
Seven years ago Tutanota was built, an encrypted email service with a strong focus on security, privacy and open source. Long before the Snowden revelations, Tutanota's team felt there was a need for easy-to-use encryption that would allow everyone to communicate online without being snooped upon.
&lt;/p&gt;

&lt;p&gt;
&lt;a href="https://www.linuxjournal.com/content/wire"&gt;The Wire&lt;/a&gt;
by Shawn Powers
&lt;/p&gt;

&lt;p&gt;
In the US, there has been recent concern over ISPs turning over logs to the
government. During the past few years, the idea of people snooping on our
private data (by governments and others) really has made encryption more
popular than ever before. One of the problems with encryption, however, is
that it's generally not user-friendly to add its protection to your
conversations. Thankfully, messaging services are starting to take notice of
the demand. For me, I need a messaging service that works across multiple
platforms, encrypts automatically, supports group messaging and ideally can
handle audio/video as well. Thankfully, I found an incredible open-source
package that ticks all my boxes: Wire.
&lt;/p&gt;

&lt;p&gt;
&lt;a href="https://www.linuxjournal.com/content/facebook-compartmentalization"&gt;Facebook
Compartmentalization&lt;/a&gt;
by Kyle Rankin
&lt;/p&gt;

&lt;p&gt;
Whenever people talk about protecting privacy on the internet, social-media
sites like Facebook inevitably come up—especially right now. It makes
sense—social networks (like Facebook) provide a platform where you can
share your personal data with your friends, and it doesn't come as much of a
surprise to people to find out they also share that data with advertisers
(it's how they pay the bills after all). It makes sense that Facebook uses
data you provide when you visit that site. What some people might be
surprised to know, however, is just how much. Facebook tracks them when they
aren't using Facebook itself but just browsing around the web.
&lt;/p&gt;

&lt;p&gt;
Some readers may solve the problem of Facebook tracking by saying "just
don't use Facebook"; however, for many people, that site may be the only way
they can keep in touch with some of their friends and family members.
Although I don't post on Facebook much myself, I do have an account and use
it to keep in touch with certain friends. So in this article, I explain how
I employ compartmentalization principles to use Facebook without leaking too
much other information about myself.
&lt;/p&gt;

&lt;p&gt;
&lt;a href="https://www.linuxjournal.com/content/protection-privacy-and-playoffs"&gt;Protection,
Privacy and Playoffs&lt;/a&gt;
by Shawn Powers
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/weekend-reading-privacy" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Sat, 27 Oct 2018 12:59:01 +0000</pubDate>
    <dc:creator>Carlie Fairchild</dc:creator>
    <guid isPermaLink="false">1339865 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Let's Solve the Deeper Problem That Makes Facebook's Bad Acting Possible</title>
  <link>https://www.linuxjournal.com/content/lets-solve-deeper-problem-makes-facebooks-bad-acting-possible</link>
  <description>  &lt;div data-history-node-id="1339946" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;a href="https://www.nytimes.com/interactive/2018/06/03/technology/facebook-device-partners-users-friends-data.html"&gt;Finding&lt;/a&gt; that Facebook has "data sharing partnerships" with "at least sixty device makers" is as unsurprising as finding that there are a zillion ways to use wheat or corn. Facebook is in the data farming business.&lt;/p&gt;

&lt;p&gt;Remember that the GDPR didn't happen in a vacuum. Bad acting with personal data in the adtech business (the one that aims advertising with personal data) is the norm, not the exception.&lt;/p&gt;

&lt;p&gt;This is why &lt;strong&gt;the real fight here is not just for privacy. It's for human agency&lt;/strong&gt;: the power to act with full effect in the world. The only way we get &lt;a href="https://www.linuxjournal.com/content/every-user-neo"&gt;full agency&lt;/a&gt; is by operating as &lt;a href="http://customercommons.org/2017/04/26/customer-comes-first/"&gt;first parties&lt;/a&gt; &lt;a href="https://medium.com/@dsearls/giving-customers-scale-a5f8a29efcdd"&gt;at scale across all the entities&lt;/a&gt; we deal with online. THEY have to agree to OUR terms.&lt;/p&gt;

&lt;p&gt;For that we need &lt;a href="https://www.linuxjournal.com/content/privacy-still-personal"&gt;standard ways to signal what's okay and what's not okay&lt;/a&gt;, and to reach agreements on &lt;em&gt;our&lt;/em&gt; terms, as first parties. It is as second parties that we click "accept" dozens of times every day, acquiring cookies with every one of those clicks, each recording certifications of acquiescence rather than of consent.&lt;/p&gt;

&lt;p&gt;With full personal agency, the whole consent system goes the other way, at scale.&lt;/p&gt;

&lt;p&gt;This is both long overdue and totally do-able, with &lt;a href="https://www.linuxjournal.com/content/cookies-go-other-way"&gt;work&lt;/a&gt; &lt;a href="http://customercommons.org/home/tools/"&gt;already started&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you're interesting in doing it, let me know.&lt;/p&gt;

&lt;p&gt;Bonus link: &lt;a href="https://youownitdownloadit.com/"&gt;https://youownitdownloadit.com/&lt;/a&gt;, which I was briefed about this morning.&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/lets-solve-deeper-problem-makes-facebooks-bad-acting-possible" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 08 Jun 2018 14:16:07 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1339946 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Tor Hidden Services</title>
  <link>https://www.linuxjournal.com/content/tor-hidden-services</link>
  <description>  &lt;div data-history-node-id="1339841" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;
Why should clients get all the privacy? Give your servers some
privacy too!&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
When people write privacy guides, for the most part they are written from
the perspective of the client. Whether you are using HTTPS, blocking
tracking cookies or going so far as to browse the internet over Tor,
those privacy guides focus on helping end users protect themselves
from the potentially malicious and spying web. Since many people who
read &lt;em&gt;Linux Journal&lt;/em&gt; sit on the other side of that equation—they run the
servers that host those privacy-defeating services—system administrators also
should step up and do their part to help user privacy. Although part of that just
means making sure your services support TLS, in this article, I describe
how to go one step further and make it possible for your
users to use your services completely anonymously via Tor hidden services.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
How It Works&lt;/span&gt;

&lt;p&gt;
I'm not going to dive into the details of how Tor itself works
so you can use the web anonymously—for those details, check out
&lt;a href="https://tor.eff.org"&gt;https://tor.eff.org&lt;/a&gt;. Tor hidden services work within the Tor network and
allow you to register an internal, Tor-only service that gets its own
.onion hostname. When visitors connect to the Tor network, Tor resolves
those .onion addresses and directs you to the anonymous service sitting
behind that name. Unlike with other services though, hidden services
provide two-way anonymity. The server doesn't know the IP of the client,
like with any service you access over Tor, but the client also doesn't
know the IP of the server. This provides the ultimate in privacy since
it's being protected on both sides.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
Warnings and Planning&lt;/span&gt;
&lt;p&gt;
As with setting up a Tor node itself, some
planning is involved if you want to set up a Tor hidden service
so you don't defeat Tor's anonymity via some operational
mistake. There are a lot of rules both from an operational
and security standpoint, so I recommend you read this &lt;a href="https://riseup.net/en/security/network-security/tor/onionservices-best-practices"&gt;excellent
guide&lt;/a&gt;
to find the latest best practices all in one place.
&lt;/p&gt;

&lt;p&gt;
Without diving into all of those steps, I do want to list a few general-purpose
guidelines here. First, you'll want to make sure that whatever
service you are hosting is listening only on localhost (127.0.0.1) and
isn't viewable via the regular internet. Otherwise, someone may be able
to correlate your hidden service with the public one. Next, go through
whatever service you are running and try to scrub specific identifying
information from it. That means if you are hosting a web service, modify
your web server so it doesn't report its software type or version, and
if you are running a dynamic site, make sure whatever web applications
you use don't report their versions either.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/tor-hidden-services" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Wed, 23 May 2018 12:00:00 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1339841 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Facebook Compartmentalization</title>
  <link>https://www.linuxjournal.com/content/facebook-compartmentalization</link>
  <description>  &lt;div data-history-node-id="1339830" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;
I don't always use Facebook, but when I do, it's over a
compartmentalized browser over Tor.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Whenever people talk about protecting privacy on the internet, social-media sites like
Facebook inevitably come up—especially right now. It makes sense—social
networks (like Facebook) provide a platform where you can share your
personal data with your friends, and it doesn't come as much of a surprise
to people to find out they also share that data with advertisers (it's
how they pay the bills after all). It makes sense that Facebook uses
data you provide when you visit that site. What some people might
be surprised to know, however, is just &lt;em&gt;how much&lt;/em&gt;. Facebook tracks them
when they aren't using Facebook itself but just browsing around the web.
&lt;/p&gt;

&lt;p&gt;
Some readers may solve the problem of Facebook tracking by saying
"just don't use Facebook"; however, for many people, that site may be the
only way they can keep in touch with some of their friends and family members.
Although I don't post
on Facebook much myself, I do have an account and use it to keep in
touch with certain friends. So in this article, I explain how I employ
compartmentalization principles to use Facebook without leaking too much
other information about myself.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
1. Post Only Public Information&lt;/span&gt;

&lt;p&gt;
The first rule for Facebook is that, regardless of what you think your
privacy settings are, you are much better off if you treat any content
you provide there as being fully public. For one, all of those different
privacy and permission settings can become complicated, so it's easy to
make a mistake that ends up making some of your data more public than
you'd like. Second, even with privacy settings in place, you don't have
a strong guarantee that the data won't be shared with people willing to
pay for it. If you treat it like a public posting ground and share
only data you want the world to know, you won't get any surprises.
&lt;/p&gt;

  &lt;span class="h3-replacement"&gt;
2. Give Facebook Its Own Browser&lt;/span&gt;

&lt;p&gt;
I mentioned before that Facebook also can track what you do when you
browse other sites. Have you ever noticed little Facebook "Like" icons
on other sites? Often websites will include those icons to help increase
engagement on their sites. What it also does, however, is link the fact
that you visited that site with your specific Facebook account—even
if you didn't click "Like" or otherwise engage with the site. If you
want to reduce how much you are tracked, I recommend selecting a separate
browser that you use only for Facebook. So if you are a Firefox user, load
Facebook in Chrome. If you are a Chrome user, view Facebook in Firefox. If
you don't want to go to the trouble of managing two different browsers,
at the very least, set up a separate Firefox profile (run &lt;code&gt;firefox -P&lt;/code&gt; from
a terminal) that you use only for Facebook.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/facebook-compartmentalization" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 12 Apr 2018 15:06:49 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1339830 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Thinking and Working Outside the Platform</title>
  <link>https://www.linuxjournal.com/content/thinking-and-working-outside-platform</link>
  <description>  &lt;div data-history-node-id="1339757" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
On the one hand, &lt;a href="https://news.google.com/news/search/section/q/facebook?ned=us&amp;gl=US&amp;hl=en"&gt;Facebook is on fire&lt;/a&gt;, and soon the whole surveillance economy will start burning down too (&lt;a href="http://blogs.harvard.edu/doc/2018/03/23/nothing/"&gt;including publishers who depend on that economy no less than Facebook does&lt;/a&gt;).
&lt;/p&gt;

&lt;p&gt;
On the same hand, lots of Linux wizards work in that economy, which is a lot larger than Facebook alone.
&lt;/p&gt;

&lt;p&gt;
Also on the same hand, lots of wizards and muggles alike are wondering out loud how we can come up with &lt;a href="https://www.google.com/search?&amp;q=alternatives+to+facebook"&gt;alternatives to Facebook&lt;/a&gt; and other "social" platforms: ones that don't depend on surveillance-based advertising.
&lt;/p&gt;

&lt;p&gt;
On the other hand, we can move beyond platforms. Let me explain.
&lt;/p&gt;

&lt;p&gt;
See these guys?
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/core/misc/icons/e32700/error.svg" alt="Image removed." title="This image has been removed. For security reasons, only images from the local domain are allowed." class="imagecache-large-550px-centered filter-image-invalid" height="16" width="16" /&gt;&lt;p&gt;
Those are carpenters who worked for &lt;a href="https://en.wikipedia.org/wiki/D._W._Griffith"&gt;DW Griffith&lt;/a&gt;, the silent film maker, back around 1908. The head carpenter is the guy on the bottom right: &lt;a href="https://www.flickr.com/photos/docsearls/sets/72157648235867352"&gt;George W. Searls&lt;/a&gt;, my grandfather.
&lt;/p&gt;

&lt;p&gt;
In the early years of silent film, here’s what they built:
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/core/misc/icons/e32700/error.svg" alt="Image removed." title="This image has been removed. For security reasons, only images from the local domain are allowed." class="imagecache-large-550px-centered filter-image-invalid" height="16" width="16" /&gt;&lt;p&gt;
Theaters. With stage sets.
&lt;/p&gt;

&lt;p&gt;
That’s because film makers in those days thought and filmed inside the box they knew, which was theater. They'd set up a camera pointed at a stage, where actors performed just like they did in theaters.
&lt;/p&gt;

&lt;p&gt;
Griffith’s biggest pioneering move was to take the camera outside the theater, into streets and homes of Fort Lee, New Jersey, across the river from New York (that's where the shots above took place)—and then out to Hollywood and a West that was still wild. Look up &lt;a href="https://www.youtube.com/results?search_query=dw+griffith+silent+shorts"&gt;DW Griffith silent shorts&lt;/a&gt;, and somewhere among the films that come up will be the steps on which Grandpa and his carpenters sat.
&lt;/p&gt;

&lt;p&gt;
Those carpenters were the hackers that helped Griffith, and the whole film industry, think and build outside the theater.
&lt;/p&gt;

&lt;p&gt;
In a similar way, we need the Linux geeks and allied wizards to help the tech industry think and work outside the platform.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/thinking-and-working-outside-platform" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 27 Mar 2018 17:50:50 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1339757 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Facebook Live Magic Button</title>
  <link>https://www.linuxjournal.com/content/facebook-live-magic-button</link>
  <description>  &lt;div data-history-node-id="1339691" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
Facebook Live is simple to broadcast from a mobile device. Simply click"go live", and you're broadcasting on your timeline. Unfortunately, if
you want to use a desktop computer with a webcam or remote IP camera,
the process is a little more complicated.
&lt;/p&gt;

&lt;img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1000009/12258facebookf1.png" alt="" title="" class="imagecache-large-550px-centered" /&gt;&lt;p&gt;
There are two main ways to start a Facebook Live stream from a
computer. You can use the Publishing Tools in the video menu and then
start a live stream. Or, you can use the API (which used to be the only
way to accomplish the task). Unfortunately, the API is a bit daunting
to use. Thankfully, Ian Anderson Gray has not only made an incredible
tutorial for going live on Facebook, he's also created a wonderful
button that uses the Facebook API in order to get a very simple method
for starting streams. You don't need to schedule the live stream, and
you don't need to worry about timing. You just click the button and walk
through the process of picking which page to stream on. Facebook gives you
a streaming key, and you immediately can start live streaming to the page.
&lt;/p&gt;

&lt;p&gt;
If it was a simple code snippet, I might feel okay with just giving
you the code, but Ian obviously put a lot of effort into creating his
magic button, so if you want to try it, head over to his &lt;a href="http://snar.co/fblive"&gt;site&lt;/a&gt;
Not only can you click on his magic button, but
he also provides a great tutorial on using OBS in order to live stream from a
computer. Thanks Ian!
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/facebook-live-magic-button" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Sun, 25 Feb 2018 16:43:23 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1339691 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Non-Linux FOSS: Facebook on OS X, sans Browser!</title>
  <link>https://www.linuxjournal.com/content/non-linux-foss-facebook-os-x-sans-browser</link>
  <description>  &lt;div data-history-node-id="1339375" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
I recently wrote about using Facebook Messenger as an SMS client, and because I'll likely get lots of email about how horrible Facebook
messenger is, I might as well go all in and share this open-source program:
Messenger for Mac.
&lt;/p&gt;
&lt;img src="http://www.linuxjournal.com/files/linuxjournal.com/ufiles/imagecache/large-550px-centered/u1000009/12088fossf1.jpg" alt="" title="" class="imagecache-large-550px-centered" /&gt;&lt;p&gt;
Over at &lt;a href="https://fbmacmessenger.rsms.me"&gt;the Messenger for Mac site&lt;/a&gt;, you'll find an OS X-native
application that is a wrapper around Facebook Messenger. What makes it
great is that it doesn't feel like a wrapper at all; it feels like an
actual app. If you're using OS X and prefer applications rather than
just web browser tabs, be sure to check it out.
&lt;/p&gt;

&lt;p&gt;
I'll be honest; I don't do a ton of communication via Facebook
Messenger. It's a great way to send a silly GIF sticker to my wife,
however, and for that reason alone, I appreciate the protocol! You can
download Messenger for Mac from the website above or from the &lt;a href="https://github.com/rsms/fb-mac-messenger"&gt;GitHub page&lt;/a&gt;.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/non-linux-foss-facebook-os-x-sans-browser" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 04 May 2017 14:06:30 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1339375 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Leaving the Land of the Giants</title>
  <link>https://www.linuxjournal.com/content/leaving-land-giants</link>
  <description>  &lt;div data-history-node-id="1084262" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/doc-searls" lang="" about="https://www.linuxjournal.com/users/doc-searls" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Doc Searls&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;The next revolution will be personal. Just like the last three were.
&lt;/p&gt;
&lt;p&gt;
The cover of the December 1st–7th 2012 issue of &lt;em&gt;The
Economist&lt;/em&gt; shows four giant squid
battling each other (&lt;a href="http://www.economist.com/printedition/2012-12-01"&gt;http://www.economist.com/printedition/2012-12-01&lt;/a&gt;). The headline reads,
"Survival of the biggest: The internet's
warring giants". The squid are Amazon, Apple, Facebook and Google. Inside, the story is
filed under "Briefing: Technology giants at war". The headline below the title graphic
reads, "Another game of thrones"
(&lt;a href="http://www.economist.com/news/21567361-google-apple-facebook-and-amazon-are-each-others-throats-all-sorts-ways-another-game"&gt;http://www.economist.com/news/21567361-google-apple-facebook-and-amazon-are-each-others-throats-all-sorts-ways-another-game&lt;/a&gt;).
The opening slug line reads "Google, Apple, Facebook
and Amazon are at each other's throats in all sorts of ways." (Raising the metaphor
count to three.)
&lt;/p&gt;

&lt;p&gt;
Now here's the question: &lt;em&gt;Is that all that's going on? Is it not possible that, in five,
ten or twenty years we'll realize that the action that mattered in the early
twenty-teens was happening in the rest of the ocean, and not just among the mollusks
with the biggest tentacles?&lt;/em&gt;
&lt;/p&gt;

&lt;p&gt;
War stories are always interesting, and very easy to tell because the format is
formulaic. Remember Linux vs. Microsoft, personalized as Linus vs.
Bill? Never mind
that Linux as a server OS worked from the start with countless millions (or even
billions) of Windows clients. Or that both Linus and Bill had other fish to fry from
the start. But personalization is cheap and easy, and there was enough antipathy on
both sides to stoke the story-telling fires, so that's what we got. Thus, today we might
regard Linux as a winner and Microsoft as a loser (or at least trending in that
direction). The facts behind (or ignored by) the stories mostly say that both entities
have succeeded or failed largely on their own merits.
&lt;/p&gt;

&lt;p&gt;
Here's a story that illustrates how stories can both lead and mislead.
&lt;/p&gt;

&lt;p&gt;
The time frame was the late 1980s and early 1990s, and the "war" was between CISC (Complex
Instruction Set Computing,
&lt;a href="http://en.wikipedia.org/wiki/Complex_instruction_set_computing"&gt;http://en.wikipedia.org/wiki/Complex_instruction_set_computing&lt;/a&gt;) and RISC (Reduced
Instruction Set Computing,
&lt;a href="http://en.wikipedia.org/wiki/Reduced_instruction_set_computing"&gt;http://en.wikipedia.org/wiki/Reduced_instruction_set_computing&lt;/a&gt;). The popular
CPUs at the time were CISC, and the big two CISC competitors were Intel's x86 and
Motorola's 68000. Intel was winning that one, so Motorola and other chip makers pushed
RISC as the Next Big Thing. Motorola had an early RISC lead with the 88000 (before
later pivoting to the PowerPC).
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/leaving-land-giants" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 05 Feb 2013 18:44:57 +0000</pubDate>
    <dc:creator>Doc Searls</dc:creator>
    <guid isPermaLink="false">1084262 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
