forked from varia/varia.website
many many many Varia's websites, work in progress: https://many.vvvvvvaria.org
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
132 lines
17 KiB
132 lines
17 KiB
5 years ago
|
<!DOCTYPE html>
|
||
|
|
<html lang="nl">
|
||
|
|
<head>
|
||
|
|
<title>Varia Centrum voor Alledaagse Technologie</title>
|
||
|
|
<meta charset="utf-8" />
|
||
|
|
<link rel="icon" href="varia.zone/favicon.ico" type="image/x-icon">
|
||
|
|
<link rel="shortcut icon" href="varia.zone/favicon.ico" type="image/x-icon">
|
||
|
|
<meta property="og:title" content="re: social media critique: next steps?"/>
|
||
|
|
<meta property="og:url" content="varia.zone/drafts/sm-critique-next-steps-en.html" />
|
||
|
|
<meta property="og:description" content="In january of 2018 a discussion on Nettime took place on the question what next steps for social media critique could be. As criticism of large social media platforms becomes increasingly commonplace in popular media and even from within Silicon Valley itself, the discussion centered around the question of what the role of critical communities like nettime could be. Since the discussion missed some context on recent developments from the non-GAFA/Free Software developments in this field media I've replied with some comments." />
|
||
|
|
<meta property="og:site_name" content="Varia" />
|
||
|
|
<meta property="og:article:author" content="Roel Roscam Abbing" />
|
||
|
|
<meta property="og:article:published_time" content="2018-01-28T00:00:00+01:00" />
|
||
|
|
<meta name="twitter:card" content="summary_large_image">
|
||
|
|
<meta name="twitter:title" content="re: social media critique: next steps?">
|
||
|
|
<meta name="twitter:description" content="In january of 2018 a discussion on Nettime took place on the question what next steps for social media critique could be. As criticism of large social media platforms becomes increasingly commonplace in popular media and even from within Silicon Valley itself, the discussion centered around the question of what the role of critical communities like nettime could be. Since the discussion missed some context on recent developments from the non-GAFA/Free Software developments in this field media I've replied with some comments.">
|
||
|
|
<meta property="og:image" content="https://varia.zone/images/de_varia.png" />
|
||
|
|
<meta name="twitter:image" content="https://varia.zone/images/de_varia.png" >
|
||
|
|
|
||
|
|
<link rel="stylesheet" type="text/css" href="/./theme/css/fork-awesome/css/fork-awesome.min.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="/./theme/css/pygment.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="/./theme/css/main.css" />
|
||
|
|
|
||
|
|
|
||
|
|
<meta name="keywords" content=", article, " />
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body id="index" class="home">
|
||
|
|
<div class="buttons top left">
|
||
|
|
<i class="fa fa-home fa-fw"></i> <a href="/">home</a>
|
||
|
|
<i class="fa fa-info-circle fa-fw"></i> <a href="/pages/about.html">over</a>
|
||
|
|
</div>
|
||
|
|
<div class="buttons top">
|
||
|
|
<li><em>varia</em> komt in vele vormen: </li>
|
||
|
|
<li><i class="fa fa-envelope "></i> <a href="https://we.lurk.org/postorius/lists/varia.we.lurk.org/" target="_blank">mailinglijst </a></li>
|
||
|
|
<li><i class="fa fa-rss "></i> <a href="feeds/all-nl.rss.xml" type="application/rss+xml">RSS feed </a></li>
|
||
|
|
<!-- <li><a href="#"><i class="fa fa-rss "></i>.ics kalendar</a></li> -->
|
||
|
|
<li class="active"><a href="/">Nederlands</a></li>
|
||
|
|
<li><a href="/en/">English</a></li>
|
||
|
|
<br>
|
||
|
|
</div>
|
||
|
|
<div class="buttons top">
|
||
|
|
|
||
|
|
</div>
|
||
|
|
<header id="banner">
|
||
|
|
<div id="title">
|
||
|
|
<p><a class="h-card" rel="me" href="/pages/about.html"><em>varia</em></a> (Gouwstraat 3, Rotterdam) is een ruimte voor het ontwikkelen van collectieve benaderingen rondom alledaagse technologie. <em>varia</em> leden onderhouden en faciliteren een <a href="/pages/collective-infrastructures.html">collectieve infrastructuur</a> om vragen, meningen, aanpassingen, hulp en actie te genereren. We gebruiken vrije software, organiseren evenementen en werken samen in verschillende constellaties. <em>varia</em> leert gaandeweg, maakt <a href="https://etherdump.vvvvvvaria.org/">notities</a>, is <a href="/en">meertalig</a> en kan gecontacteerd worden via <a href="mailto:info@varia.zone">info[@]varia.zone</a>.</p>
|
||
|
|
</div>
|
||
|
|
</header>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<section id="content" class="body h-entry">
|
||
|
|
<div class="entry-title p-name">
|
||
|
|
re: social media critique: next steps?
|
||
|
|
</div>
|
||
|
|
<div class="article-info">
|
||
|
|
<div class="featured-image u-photo">
|
||
|
|
</div>
|
||
|
|
<div class="event-details">
|
||
|
|
<div> 28 January 2018</div>
|
||
|
|
</div>
|
||
|
|
<div class="post-info">
|
||
|
|
<div class="article-authors">
|
||
|
|
|
||
|
|
Roel Roscam Abbing
|
||
|
|
</div>
|
||
|
|
<a style="visibility:hidden;" rel="author" class="p-author h-card">Roel Roscam Abbing</a>
|
||
|
|
<time class="dt-published" datetime="2018-01-28 00:00:00+01:00"></time>
|
||
|
|
<a class="u-url" href="drafts/sm-critique-next-steps-en.html"></a>
|
||
|
|
<span class="categories">
|
||
|
|
<span itemprop="articleSection">
|
||
|
|
<a href="/category/article.html" rel="category">article</a>
|
||
|
|
</span>
|
||
|
|
</span>
|
||
|
|
<div class="article-translation">
|
||
|
|
<a href=""></a>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="entry-content-container">
|
||
|
|
<div class="entry-content e-content">
|
||
|
|
<p>In january of 2018 a discussion on <a href="https://nettime.org/Lists-Archives/nettime-l-1801/msg00045.html">Nettime</a> took place on the question what next steps for social media critique could be. As criticism of large social media platforms becomes increasingly commonplace in popular media and even from within Silicon Valley itself, the discussion centered around the question of what the role of critical communities like nettime could be. Since the discussion missed some context on recent developments from the non-GAFA<sup id=sf-sm-critique-next-steps-1-back class=simple-footnote>1</sup><span class=simple-footnote-container><span class=simple-footnote-content>[1] Google/Amazon/Facebook/Apple</span></span>/Free Software developments in this field media I've replied with some comments.</p>
|
||
|
|
<blockquote>
|
||
|
|
<p>This is in the end what Silicon Valley tries to prevent at all cost:
|
||
|
|
resistance and exodus. How can such a momentum be unleashed?</p>
|
||
|
|
</blockquote>
|
||
|
|
<p>So aside from the discussion of who listens (or didn't listen) to whose opinion it can be interesting to have a closer look at action and momentum.</p>
|
||
|
|
<p>Three projects caught my attention and I think could be an interesting case for this 'next steps' discussion:</p>
|
||
|
|
<p>Mastodon (2016) en Conversations (2014) and Peertube (2015)<sup id=sf-sm-critique-next-steps-2-back class=simple-footnote>2</sup><span class=simple-footnote-container><span class=simple-footnote-content>[2] These are the dates of the project's source code first appearing in public, they are still actively updated and used.</span></span></p>
|
||
|
|
<p>All three are projects that during the past twelve months have somehow reinvigorated (the work on, attention for) their underlying protocols. Protocols that have been proclaimed dead or unsuccessful for many years. And probably will be for more to come.</p>
|
||
|
|
<p>The first one, Mastodon <sup id=sf-sm-critique-next-steps-3-back class=simple-footnote>3</sup><span class=simple-footnote-container><span class=simple-footnote-content>[3] <a href="https://joinmastodon.org/">https://joinmastodon.org/</a></span></span>, you may have read about or even tried out. It is essentially a twitter clone / alternative. Technically it is based on Ostatus, which is a protocol to distribute status updates across networks. Ostatus is the protocol that powered early 'alternative 2.0 style' social networks such as Friendica and Lorea. The latter was a product of and important site of organization for the Spanish Indignados and 15M movements. Mastodon also supports ActivityPub which is the likely successor of Ostatus as a protocol for
|
||
|
|
further ongoing work on so-called federated publishing. The interesting thing is that Mastodon managed to attract a good chunk of the recent Twitter refugees. These where mostly voices which aren't white, loud or extreme right wing and for those reasons felt themselves increasingly out of place on twitter. Mastodon communities managed to involve so many of these people by focusing on developing tools for community moderation, content warnings and the ability to block other instances in the network. As a result (the english language) Mastodon became a site that is predominantly populated by the queer, PoC, left and artistic, or anyone that would otherwise be at risk of being on the receiving end of the Gamergate-style interactions on twitter. The decentralized nature of
|
||
|
|
Mastodon has created a culture of 'thematic mastodon servers (see https://instances.social/list) that have become a large part of what makes the network interesting and relevant to its several hundredthousand users.</p>
|
||
|
|
<p>Conversations <sup id=sf-sm-critique-next-steps-4-back class=simple-footnote>4</sup><span class=simple-footnote-container><span class=simple-footnote-content>[4] <a href="https://conversations.im/">https://conversations.im</a></span></span> is a messaging application that is based on the very old XMPP protocol. This is a chat protocol
|
||
|
|
which has at one point also been the underlying technology of both Google and Facebook chat before they closed it down and made it proprietary. From the onset Conversations focused on a combination of user friendliness, security and ultimately visual design to be on par with mobile messengers such as whatsapp and telegram. The work of Conversations has reinvigorated the XMPP protocol. Partly because it focused on implementing the double-ratchett encryption algorithm almost immediately after it was open-sourced. This is the modern userfriendly end-to-end encryption algorithm developed by Moxie Marlinspike for Signal and licensed to companies like Whatsapp. Another effect of the work of Conversations is that the decades old protocol has been updated in the span of a few years to work very well for mobile usage. For me one of the interesting aspects of the development of Conversations is the role that modern thinking on UIs, design and user friendliness played in its popularity. This especially becomes apparent in the very technical and awkward world of XMPP software. The developer has mentioned multiple times that he 'bases' his design on that of his GAFA 'competitors'. Apropos tactical media, this project's appropriation of corporate design, yet very clear and solid political stance (see https://gultsch.de/objection.html) leading to an increase in popularity and community involvement is an interesting development.</p>
|
||
|
|
<p>Lastly, Peertube <sup id=sf-sm-critique-next-steps-5-back class=simple-footnote>5</sup><span class=simple-footnote-container><span class=simple-footnote-content>[5] <a href="https://github.com/Chocobozzz/PeerTube">Peertube website</a></span></span> is an attempt at making the hosting of video content accessible to small organizations. The sheer amount of infrastructure and thus capital required to set up an alternative to the monopoly position of Youtube, forces any project trying to replace Youtube to use peer-to-peer technologies. Peertube does so by trying to implement WebTorrents. Like the older 'BitTorrent' protocol it is based on, WebTorrent tries to mitigate the sheer amount of data and bandwith involved with exchanging online media, by making sure these are streamed from many sources at once. Unlike torrents, which need separate applications, WebTorrents run in familiar web browsers. One could say the conceptual forbearer of this approach was a project called Popcorn Time (2014). An app that convinced many with its good UI and design to do 'Netflix-like' streaming on top of the torrent network. Again this is something that lead to a reinvigoration of the decaying (use-wise) torrenting protocol. (I'd also argue though, that Popcorn Time was simultaneously the nail in the coffin for torrenting because of the individualistic streaming mentality built into it. This also meant the definite end of what remained of -collectivist?- seeding/sharing culture on public trackers.)</p>
|
||
|
|
<p>The position of the Peertube as a viable alternative or successful project is the most tenuous of the three. However, one might argue that our definition of success in this context should also be readjusted - away from the Silicon Valley, venture capitalist sense of success using metrics like usage counts, market cap, patent value etc. By nature of being built upon open, compatible and federative technologies, developments happening in all three projects could, and probably will, end up supporting one another. They do so to the extent that one project could even become an integral part of the other. As an example both Mastodon and Peertube use the same underlying ActivityPub, allowing one to become the underlying video delivery function of the other. As was the case with Friendica, Lorea and Mastodon, projects might stop but then become stepping stones and inspirations for newer generations of projects. In this sense definitions of success should consider the quality of longer term technological ecosystems within larger socio-political contexts.</p>
|
||
|
|
<p>So the striking things for me to take away from these projects are:</p>
|
||
|
|
<p>All three projects have managed to reinvigorate 'decaying' protocols in large part through their focus on UX, language and interestingly design. Which seems to me a huge opportunity for the arts which has been left largely unused in the first round of social media critique. Perhaps the model of artistic production in this domain should move away from the artists being on the forefront, sensing out emerging tendencies and taking the spotlight by creating mostly harmless critical and speculative works around these tendencies. Next steps for artistic social media critique should instead take a much more humble and supportive role contributing expertise, time and exposure to people working in and with these ecosystems.</p>
|
||
|
|
<p>All three projects are based on federation. Which is the idea that various actors maki g up a network decide to cooperate in a collective fashion. Distributing responsibility and power as they do so. The future of social media has to be federated or there won't be any (for those privileged enough to retreat..). I think the case of Mastodon, where
|
||
|
|
servers in the Ostatus federation are experimenting with blocking hostile content altogether from other servers in the federation (while still maintaining technical compatibility) are interesting experiments. For one, the debates over on-line harassment and fake news show that the grand 'electronic agoras', where one can find anyone and everyone
|
||
|
|
clearly aren't conducive to productive interchange of ideas. Perhaps smallish, self caring communities are a good answer to the profit driven model of infinite interconnectedness.</p>
|
||
|
|
<p>Lastly, I think it is no coincidence that two out of three of the projects have Germans leading development and all three are European based projects. I guess the following is anecdotal and partial evidence. Yet, I've not seen Google and Facebook run full page advertorials in leading daily newspapers except in the German ones. Ostensibly, part of
|
||
|
|
an attempt on their side to prevent mass user exodus out of discomfort with the platform. It is in part German historical sensibility that leads to this kind of sensitivity on the issues of privacy, but it is also a sensitivity that is actively nurtured in public discourse. No Silicon Valley apologies are required for there to be scepsis. At the
|
||
|
|
same time the European context apparently provides good enough living conditions for people to risk investing time in this kind of work. Risk which is also partly mitigated by initiatives such as German Prototype Fund and other European funding streams. However, testament to the fact that these projects have healthy communities and are part of wider ecosystems of support is that all projects finance themselves from diverse revenue streams, user contributions being the main one.</p>
|
||
|
|
<p>So I'd say next steps for a social media critique would be to be more involved in (and involve more) these communities. To use positions of power to create opportunities for people working on these projects. While the center of development of these projects is Western-Europe they have many contributors outside of Europe as well, that could benefit even more from such opportunities. At the same time, doing close readings of the technical underpinnings of these media will also improve understanding of what is (not) going on. Now obviously all this was a news flash from within a very specific filter bubble, but actually from there 2017 was a very promising year for alternative media.</p>
|
||
|
|
<blockquote>
|
||
|
|
<p>I still believe in vital methods to mass delete Facebook accounts.</p>
|
||
|
|
</blockquote>
|
||
|
|
<p>I'd say start doing so, but help your friends. Use your network effect
|
||
|
|
to transition together to different kind of media. This is slow and
|
||
|
|
laborious so mutual support is important. The time is always right, but
|
||
|
|
now more than ever.</p><ol class=simple-footnotes></ol>
|
||
|
|
<div class="separator"><hr></div>
|
||
|
|
</div><!-- /.entry-content -->
|
||
|
|
</div><!-- /.entry-content-container -->
|
||
|
|
</section>
|
||
|
|
<script type="text/javascript">
|
||
|
|
var footnotes = document.querySelectorAll('[id^="fnref-"]');
|
||
|
|
for(var i in footnotes){
|
||
|
|
if(i < footnotes.length){
|
||
|
|
console.log(footnotes[i]);
|
||
|
|
var id = footnotes[i].id.replace('fnref-','fn-');
|
||
|
|
footnotes[i].innerHTML = footnotes[i].innerHTML + '<span>['+ parseInt(Number(i)+1) + '] '+ document.getElementById(id).innerHTML +'</span>';
|
||
|
|
}
|
||
|
|
}
|
||
|
|
document.getElementsByClassName('footnote')[0].remove();
|
||
|
|
</script>
|
||
|
|
</body>
|
||
|
|
</html>
|