perro
/
perrotuerto.blog
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Publicación de 4 y arreglo de título de 3

This commit is contained in:
Nika Zhenya 2019-07-04 11:05:25 -05:00
parent ad4d5adbb2
commit f87ff9bfd8
19 changed files with 1884 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
config/build/pot2pos
View File

@ -17,7 +17,7 @@ pot_dir = 'content/pot/'
pot_path = ''
po_dir = 'content/po/'
po_name = ''
locales = ['en', 'es']
locales = ['en', 'es', 'nb']
# Displays help
if ARGV[0] =~ /-h/

6
content/html/en/003_dont-come.html
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>Don't come with those tales</title>
<title>Don't Come with Those Tales</title>
<meta charset="utf-8" />
<meta name="application-name" content="Publishing is Coding: Change My Mind">
<meta name="description" content="Blog about free culture, free software and free publishing.">
@ -25,7 +25,7 @@
<a onclick="mode(this)">N</a>
</div>
<section>
<h1 id="dont-come-with-those-tales">Don't come with those tales</h1>
<h1 id="dont-come-with-those-tales">Don't Come with Those Tales</h1>
<blockquote class="published">
<p>Published: 2019/05/05, 20:00</p>
</blockquote>
@ -73,7 +73,7 @@
</section>
<footer>
<p class="left no-indent">All content is under <a href="../../../content/html/en/_fork.html">Open and Free Publishing License (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Last build of this page: 2019/07/01, 10:32.</p>
<p class="left no-indent">Last build of this page: 2019/07/04, 11:03.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/en/rss.xml">RSS</a></span> | <a href="../../../content/html/en/003_dont-come.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/003_dont-come.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/003_dont-come.html"><span class="versalita">NB</span></a></p>
</footer>

106
content/html/en/004_backup.html Normal file
View File

@ -0,0 +1,106 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>Who Backup Whom?</title>
<meta charset="utf-8" />
<meta name="application-name" content="Publishing is Coding: Change My Mind">
<meta name="description" content="Blog about free culture, free software and free publishing.">
<meta name="keywords" content="publishing, blog, book, ebook, methodology, foss, libre-software, format, markdown, html, epub, pdf, mobi, latex, tex, culture, free culture, philosophy">
<meta name="viewport" content="width=device-width, user-scalable=0">
<link rel="shortcut icon" href="../../../icon.png">
<link rel="alternate" type="application/rss+xml" href="https://perrotuerto.blog/feed/" title="Publishing is Coding: Change My Mind">
<link type="text/css" rel="stylesheet" href="../../../css/styles.css">
<link type="text/css" rel="stylesheet" href="../../../css/extra.css">
<script type="application/javascript" src="../../../js/functions.js"></script>
</head>
<body>
<header>
<h1><a href="https://perrotuerto.blog/content/html/en/">Publishing is Coding: Change My Mind</a></h1>
<nav> <p> <a href="../../../content/html/en/_links.html">Links</a> | <a href="../../../content/html/en/_about.html">About</a> | <a href="../../../content/html/en/_contact.html">Contact</a> | <a href="../../../content/html/en/_fork.html">Fork</a> | <a href="../../../content/html/en/_donate.html">Donate</a> </p>
</nav>
</header>
<div id="controllers">
<a onclick="zoom(true)">+</a>
<a onclick="zoom(false)">−</a>
<a onclick="mode(this)">N</a>
</div>
<section>
<h1 id="who-backup-whom">Who Backup Whom?</h1>
<blockquote class="published">
<p>Published: 2019/07/04, 11:00</p>
</blockquote>
<p>Among publishers and readers is common to heard about “digital copies.” This implies that ebooks tend to be seen as backups of printed books. How the former became a copy of the original—even tough you first need a digital file in order to print—goes something like this:</p>
<ol>
<li>
<p>Digital files (<span class="smallcap">DF</span>s) with appropriate maintenance could have higher probabilities to last longer that its material peer.</p>
</li>
<li>
<p>Physical files (<span class="smallcap">PF</span>s) are limited due geopolitical issues, like cultural policies updates, or due random events, like environment changes or accidents.</p>
</li>
<li>
<p><i>Therefore</i>, <span class="smallcap">DF</span>s are backups of <span class="smallcap">PF</span>s because <i>in theory</i> its dependence is just technical.</p>
</li>
</ol>
<p>The famous digital copies arise as a right of private copy. What if one day our printed books get ban or burn? Or maybe some rain or coffee spill could fuck our books collection. Who knows, <span class="smallcap">DF</span>s seem more reliable.</p>
<p>But there are a couple suppositions in this argument. (1) The technology behind <span class="smallcap">DF</span>s in one way or the other will always make data flow. Maybe this is because (2) one characteristic—part of its “nature”—of information is that nobody can stop its spread. This could also implies that (3) hackers can always destroy any kind of digital rights management system.</p>
<p>Certainly some dudes are gonna be able to hack the locks but at a high cost: every time each <a href="https://en.wikipedia.org/wiki/Cipher">cipher</a> is revealed, another more complex is on the way—<em>Barlow <a href="https://www.wired.com/1994/03/economy-ideas/">dixit</a></em>. We cannot trust that our digital infrastructure would be designed with the idea of free share in mind… Also, how can we probe information wants to be free without relying in its “nature” or making it some kind of autonomous subject?</p>
<p>Besides those issues, the dynamic between copies and originals creates an hierarchical order. Every <span class="smallcap">DF</span> is in a secondary position because it is a copy. In a world full of things, materiality is and important feature for commons and goods; for several people <span class="smallcap">PF</span>s are gonna be preferred because, well, you can grasp them.</p>
<p>Ebook market shows that the hierarchy is at least shading. For some readers <span class="smallcap">DF</span>s are now in the top of the pyramid. We could say so by the follow argument:</p>
<ol>
<li>
<p><span class="smallcap">DF</span>s are way more flexible and easy to share.</p>
</li>
<li>
<p><span class="smallcap">PF</span>s are very rigid and not easy to access.</p>
</li>
<li>
<p><i>Therefore</i>, <span class="smallcap">DF</span>s are more suitable for use than <span class="smallcap">PF</span>s.</p>
</li>
</ol>
<p>Suddenly, <span class="smallcap">PF</span>s become hard copies that are gonna store data as it was published. Its information is in disposition to be extracted and processed if need it.</p>
<p>Yeah, we also have a couple assumptions here. Again (1) we rely on the stability of our digital infrastructure that it would allow us to have access to <span class="smallcap">DF</span>s no matter how old they are. (2) Reader's priorities are over files use—if not merely consumption—not on its preservation and reproduction (<span class="smallcap">P&#38;R</span>). (3) The argument presume that backups are motionless information, where bookshelves are fridges for later-to-use books.</p>
<p>The optimism about our digital infrastructure is too damn high. Commonly we see it as a technology that give us access to zillions of files and not as a <span class="smallcap">P&#38;R</span> machinery. This could be problematic because some times file formats intended for use aren't the most suitable for <span class="smallcap">P&#38;R</span>. For example, the use of <span class="smallcap">PDF</span>s as some kind of ebook. Giving to much importance to reader's priorities could lead us to a situation where the only way to process data is by extracting it again from hard copies. When we do that we also have another headache: fixes on the content have to be add to the last available hard copy edition. But, can you guess where are all the fixes? Probably not. Maybe we should start to think about backups as some sort of <i>rolling update</i>.</p>
<figure>
<img src="../../../img/p004_i001.jpg" alt="Programando Libreros while she scans books which DFs are not suitable for P&#38;R or are simply nonexistent; can you see how it is not necessary to have a fucking nice scanner?"/>
<figcaption>
Programando Libreros while she scans books which <span class="smallcap">DF</span>s are not suitable for <span class="smallcap">P&#38;R</span> or are simply nonexistent; can you see how it is not necessary to have a fucking nice scanner?
</figcaption>
</figure>
<p>As we imagine—and started to live in—scenarios of highly controlled data transfer, we have to picture a situation where for some reason our electric power is off or running low. In that context all the strengths of <span class="smallcap">DF</span>s become pointless. They may not be accessible. They may not spread. Right now for us is hard to imagine. Generation after generation the storaged <span class="smallcap">DF</span>s in <span class="smallcap">HDD</span>s would be inherit with the hope of being used again. But over time those devices with our cultural heritage would become rare objects without any apparent utility.</p>
<p>The aspects of <span class="smallcap">DF</span>s that made us see the fragility of <span class="smallcap">PF</span>s would disappear in its concealment. Can we still talk about information if it is on a potential stage—we know data is there, but it is inaccessible because we don't have means for view them? Or does information already implies technical resources for its access—i.e. there is not information without a subject with technical skills to extract, process and use the data?</p>
<p>When we usually talk about information we already suppose it is there, but many times it is not accessible. So the idea of potential information could be counterintuitive. If information isn't actual we just consider that it doesn't exist, not that it is on some potential stage.</p>
<p>As our technology is developing we assume that we would always have <i>the possibility</i> of better ways to extract or understand data. Thus, that there are bigger chances to get new kinds of information—and take profit from it. Preservation of data relies between those possibilities, as we usually backup files with the idea that we could need to go back again.</p>
<p>Our world become more complex by new things forthcoming to us, most of the times as new characteristics of things we already know. Preservation policies implies an epistemic optimism and not only a desire to keep alive or incorrupt our heritage. We wouldn't backup data if we don't already believe we could need it in a future where we can still use it.</p>
<p>With this exercise it could be clear a potentially paradox of <span class="smallcap">DF</span>s. More accessibility tends to require more technical infrastructure. This could imply major technical dependence that subordinate accessibility of information to the disposition of technical means. <i>Therefore</i>, we achieve a situation where more accessibility is equal to more technical infrastructure and—as we experience nowadays—dependence.</p>
<p>Open access to knowledge involves at least some minimum technical means. Without that, we can't really talk about accessibility of information. Contemporary open access possibilities are restricted to an already technical dependence because we give a lot of attention in the flexibility that <span class="smallcap">DF</span>s offer us for <i>its use</i>. In a world without electric power, this kind of accessibility becomes narrow and an useless effort.</p>
<figure>
<img src="../../../img/p004_i002.jpg" alt="Programando Libreros and Hacklib while they work on a project intended to P&#38;R old Latin American SciFi books; sometimes a V-shape scanner is required when books are very fragile."/>
<figcaption>
Programando Libreros and Hacklib while they work on a project intended to <span class="smallcap">P&#38;R</span> old Latin American SciFi books; sometimes a V-shape scanner is required when books are very fragile.
</figcaption>
</figure>
<p>So, <i>who backup whom?</i> In our actual world, where geopolitics and technical means restricts flow of data and people at the same time it defends internet access as a human right—some sort of neo-Enlightenment discourse—<span class="smallcap">DF</span>s are lifesavers in a condition where we don't have more ways to move around or scape—not only from border to border, but also on cyberspace: it is becoming a common place the need to sign up and give your identity in order to use web services. Let's not forget that open access of data can be a course of action to improve as community but also a method to perpetuate social conditions.</p>
<p>Not a lot of people are as privilege as us when we talk about access to technical means. Even more concerning, there are hommies with disabilities that made very hard for them to access information albeit they have those means. Isn't it funny that our ideas as file contents can move more “freely” than us—your memes can reach web platform where you are not allow to sign in?</p>
<p>I desire more technological developments for freedom of <span class="smallcap">P&#38;R</span> and not just for use as enjoyment—no matter is for intellectual or consumption purposes. I want us to be free. But sometimes use of data, <span class="smallcap">P&#38;R</span> of information and people mobility freedoms don't get along.</p>
<p>With <span class="smallcap">DF</span>s we achieve more independence in file use because once it is save, it could spread. It doesn't matter we have religious or political barriers; the battle take place mainly in technical grounds. But this doesn't made <span class="smallcap">DF</span>s more autonomous in its <span class="smallcap">P&#38;R</span>. Neither implies we can archive personal or community freedoms. They are objects. <i>They are tools</i> and whoever use them better, whoever owns them, would have more power.</p>
<p>With <span class="smallcap">PF</span>s we can have more <span class="smallcap">P&#38;R</span> freedom. We can do whatever we want with them: extract their data, process it and let it free. But only if we are their owners. Often that is not the case, so <span class="smallcap">PF</span>s tend to have more restricted access for its use. And, again, this doesn't mean we can be free. There is not any cause and effect relationship between what object made possible and how subjects want to be free. They are tools, they are not master or slaves, just means for whoever use them… but for which ends?</p>
<p>We need <span class="smallcap">DF</span>s and <span class="smallcap">PF</span>s as backups and as everyday objects of use. The act of backup is a dynamic category. Backed up files are not inert and they aren't only substrates waiting to be use. Sometimes we are going to use <span class="smallcap">PF</span>s because <span class="smallcap">DF</span>s have been corrupted or its technical infrastructure has been shut down. In other occasions we would use <span class="smallcap">DF</span>s when <span class="smallcap">PF</span>s have been destroyed or restricted.</p>
<figure>
<img src="../../../img/p004_i003.jpg" alt="Due restricted access to PFs, sometimes it is necessary a portable V-shape scanner; this model allows us to handle damaged books while we can also storage it in a backpack."/>
<figcaption>
Due restricted access to <span class="smallcap">PF</span>s, sometimes it is necessary a portable V-shape scanner; this model allows us to handle damaged books while we can also storage it in a backpack.
</figcaption>
</figure>
<p>So the struggle about backups—and all that shit about “freedom” on <span class="smallcap">FOSS</span> communities—it is not only around the “incorporeal” realm of information. Nor on the technical means that made digital data possible. Neither in the laws that transform production into property. We have others battle fronts against the monopoly of the cyberspace—or as Lingel <a href="http://culturedigitally.org/2019/03/the-gentrification-of-the-internet/">says</a>: the gentrification of the internet.</p>
<p>It is not just about software, hardware, privacy, information or laws. It is about us: how we build communities and how technology constitutes us as subjects. <i>We need more theory</i>. But a very diversified one because being on internet it is not the same for an scholar, a publisher, a woman, a kid, a refugee, a non-white, a poor or an old lady. This space it isn't neutral nor homogeneous nor two-dimensional. It has wires, it has servers, it has exploited employees, it has buildings, <i>it has power</i> and it has, well, all that things the “real world” has. Not because you use a device to access means that you can always decide if you are online or not: you are always online as an user as a consumer or as data.</p>
<p><i>Who backup whom?</i> As internet is changing us as printed text did, backed up files aren't storages of data, but <i>the memory of our world</i>. Is it still a good idea to leave the work of <span class="smallcap">P&#38;R</span> to a couple hardware and software companies? Are we now allow to say that the act of backup implies files but something else too?</p>
<script type="text/javascript" src="../../../hashover/comments.php"></script>
</section>
<footer>
<p class="left no-indent">All content is under <a href="../../../content/html/en/_fork.html">Open and Free Publishing License (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Last build of this page: 2019/07/04, 11:04.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/en/rss.xml">RSS</a></span> | <a href="../../../content/html/en/004_backup.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/004_backup.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/004_backup.html"><span class="versalita">NB</span></a></p>
</footer>
</body>
</html>

8
content/html/en/index.html
View File

@ -33,7 +33,11 @@
</div>
<section>
<div class="post">
<p><a href="003_dont-come.html">3. Don't come with those tales</a></p>
<p><a href="004_backup.html">4. Who Backup Whom?</a></p>
<p>[Published: 2019/07/04, 11:00]</p>
</div>
<div class="post">
<p><a href="003_dont-come.html">3. Don't Come with Those Tales</a></p>
<p>[Published: 2019/05/05, 20:00]</p>
</div>
<div class="post">
@ -47,7 +51,7 @@
</section>
<footer>
<p class="left no-indent">All content is under <a href="../../../content/html/en/_fork.html">Open and Free Publishing License (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Last build of this page: 2019/07/01, 10:34.</p>
<p class="left no-indent">Last build of this page: 2019/07/04, 11:04.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/en/rss.xml">RSS</a></span> | <a href="../../../content/html/en/index.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/index.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/index.html"><span class="versalita">NB</span></a></p>
</footer>

2
content/html/es/003_dont-come.html
View File

@ -73,7 +73,7 @@
</section>
<footer>
<p class="left no-indent">Todo el contenido está bajo <a href="../../../content/html/es/_fork.html">Licencia Editorial Abierta y Libre (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Última modificación de esta página: 2019/07/01, 10:32.</p>
<p class="left no-indent">Última modificación de esta página: 2019/07/04, 11:03.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/es/rss.xml">RSS</a></span> | <a href="../../../content/html/en/003_dont-come.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/003_dont-come.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/003_dont-come.html"><span class="versalita">NB</span></a></p>
</footer>

106
content/html/es/004_backup.html Normal file
View File

@ -0,0 +1,106 @@
<!DOCTYPE html>
<html lang="es">
<head>
<title>¿Quién respalda a quién?</title>
<meta charset="utf-8" />
<meta name="application-name" content="Publishing is Coding: Change My Mind">
<meta name="description" content="Blog about free culture, free software and free publishing.">
<meta name="keywords" content="publishing, blog, book, ebook, methodology, foss, libre-software, format, markdown, html, epub, pdf, mobi, latex, tex, culture, free culture, philosophy">
<meta name="viewport" content="width=device-width, user-scalable=0">
<link rel="shortcut icon" href="../../../icon.png">
<link rel="alternate" type="application/rss+xml" href="https://perrotuerto.blog/feed/" title="Publishing is Coding: Change My Mind">
<link type="text/css" rel="stylesheet" href="../../../css/styles.css">
<link type="text/css" rel="stylesheet" href="../../../css/extra.css">
<script type="application/javascript" src="../../../js/functions.js"></script>
</head>
<body>
<header>
<h1><a href="https://perrotuerto.blog/content/html/es/">Publishing is Coding: Change My Mind</a></h1>
<nav> <p> <a href="../../../content/html/es/_links.html">Enlaces</a> | <a href="../../../content/html/es/_about.html">Acerca</a> | <a href="../../../content/html/es/_contact.html">Contacto</a> | <a href="../../../content/html/es/_fork.html">Bifurca</a> | <a href="../../../content/html/es/_donate.html">Dona</a> </p>
</nav>
</header>
<div id="controllers">
<a onclick="zoom(true)">+</a>
<a onclick="zoom(false)">−</a>
<a onclick="mode(this)">N</a>
</div>
<section>
<h1 id="quien-respalda-a-quien">¿Quién respalda a quién?</h1>
<blockquote class="published">
<p>Publicado: 2019/07/04, 11:00</p>
</blockquote>
<p>Entre editores y lectores es común escuchar sobre las «copias digitales». Esto implica que los libros electrónicos tienden a verse como respaldos de los libros impresos. La manera en como el primero se convierte en una copia del original —aunque primero necesites un archivo digital para poder imprimir— es algo similar a lo siguiente:</p>
<ol>
<li>
<p>Los archivos digitales (<span class="smallcap">AD</span>) con un apropiado mantenimiento pueden tener mayores probabilidades de durar más que su correlato material.</p>
</li>
<li>
<p>Los archivos físicos (<span class="smallcap">AF</span>) están constreñidos por cuestiones geopolíticas, como las modificaciones en las políticas culturales, o por eventos aleatorios, como los cambios en el medio ambiente o los accidentes.</p>
</li>
<li>
<p><i>Por lo tanto</i>, los <span class="smallcap">AD</span> son el respaldo de los <span class="smallcap">AF</span> porque <i>en teoría</i> su dependencia solo es técnica.</p>
</li>
</ol>
<p>La famosa copia digital emerge como un derecho a la copia privada. ¿Qué tal si un día nuestros impresos son censurados o quemados? O quizá una lluvia o un derrame de café puede chingar nuestra colección de libros. Quién sabe, los <span class="smallcap">AD</span> parecen ser más confiables.</p>
<p>Pero hay un par de suposiciones en este argumento. (1) La tecnología detrás de los <span class="smallcap">AD</span> de una manera u otra siempre hará que los datos fluyan. Tal vez esto se debe a que (2) una característica —parte de su «naturaleza»— de la información es que nadie puede detener su propagación. Esto puede implicar que (3) los <i>hackers</i> siempre pueden destruir cualquier tipo de sistema de gestión de derechos digitales.</p>
<p>Sin duda algunas personas van a poder <i>hackear</i> las cerraduras pero a un costo muy alto: cada vez que un <a href="https://es.wikipedia.org/wiki/Algoritmo_criptogr%C3%A1fico">algoritmo criptográfico</a> es revelado, otro más complejo ya viene en camino —<em>Barlow <a href="https://biblioweb.sindominio.net/telematica/barlow.html">dixit</a></em>—. No podemos confiar en la idea de que nuestra infraestructura digital será diseñada para compartir libremente… Además, ¿cómo se puede probar que la información quiere ser libre sin recaer en su «naturaleza» o tornarla en alguna clase de sujeto autónomo?</p>
<p>Por otra parte, la dinámica entre las copias y los originales genera un orden jerárquico. Cada <span class="smallcap">AD</span> se encuentra en una posición secundaria porque es una copia. En un mundo lleno de cosas, la materialidad es una característica relevante para los bienes comunes y las mercancías; muchas personas van a preferir los <span class="smallcap">AF</span> ya que, bueno, puedes asirlos.</p>
<p>El mercado de los libros electrónicos muestra que esta jerarquía al menos se está matizando. Para ciertos lectores los <span class="smallcap">AD</span> ahora están en la cúspide de la pirámide. Se puede señalar este fenómeno con el siguiente argumento:</p>
<ol>
<li>
<p>Los <span class="smallcap">AD</span> son mucho más flexibles y sencillos de compartir.</p>
</li>
<li>
<p>Los <span class="smallcap">AF</span> son muy rígidos y no hay facilidad para su acceso.</p>
</li>
<li>
<p><i>Por lo tanto</i>, los <span class="smallcap">AD</span> son más convenientes que los <span class="smallcap">AF</span>.</p>
</li>
</ol>
<p>De repente los <span class="smallcap">AF</span> mutan en las copias duras donde los datos serán guardados tal cual fueron publicados. Si se requiere, su información está a disposición para la extracción y el procesamiento.</p>
<p>Sí, aquí también tenemos un par de suposiciones. De nuevo (1) confiamos en la estabilidad de nuestra infraestructura digital que nos permitirá tener acceso a nuestros <span class="smallcap">AD</span> sin importar que tan viejos estén. (2) La prioridad de los lectores es sobre el uso de los archivos —si no su mero consumo— y no su preservación y reproducción (<span class="smallcap">P&#38;R</span>). (3) El argumento asume que los respaldos son información inmóvil, donde los estantes son refrigeradores para los libros que después se usarán.</p>
<p>El optimismo respecto a nuestra infraestructura digital es muy alto. Por lo general la vemos como una tecnología que nos da acceso a chorrocientos archivos y no como una maquinaria para la <span class="smallcap">P&#38;R</span>. Esto puede ser problemático porque en ciertos casos los formatos de archivos que fueron diseñados para su uso común no son los más adecuados para su <span class="smallcap">P&#38;R</span>. Como ejemplo tenemos el uso de <span class="smallcap">PDF</span> a modo de libros electrónicos. Si le damos mucha importancia a la prioridad de los lectores, como consecuencia podemos llegar a una situación donde la única manera de procesar los datos es el retorno a su extracción a partir de las copias duras. Cuando lo llevamos a cabo de esa manera tenemos otro dolor de cabeza: las correcciones del contenido tienen que ser añadidas a la última edición disponible en copia dura. Pero ¿puedes adivinar dónde están todas estas correcciones? Lo más seguro es que no. A lo mejor deberíamos por empezar a pensar los respaldos como algún tipo de <i>actualización continua</i>.</p>
<figure>
<img src="../../../img/p004_i001.jpg" alt="Programando Libreros mientras escanea libros cuyos AD no son aptos para la P&#38;R o simplemente no existen; ¿ves cómo no es necesario tener un pinche escáner bueno?"/>
<figcaption>
Programando Libreros mientras escanea libros cuyos <span class="smallcap">AD</span> no son aptos para la <span class="smallcap">P&#38;R</span> o simplemente no existen; ¿ves cómo no es necesario tener un pinche escáner bueno?
</figcaption>
</figure>
<p>Tal como imaginas —y comenzamos a vivir en— escenarios con un alto control en la transferencia de datos, podemos fantasear con una situación donde por alguna razón nuestras fuentes de energía eléctrica no están disponibles o tienen poco abastecimiento. En este contexto todas las fortalezas de los <span class="smallcap">AD</span> pierden sentido. A lo mejor no serán accesibles. Quizá no podrán propagarse. Por el momento es difícil de concebir. Generación tras generación los <span class="smallcap">AD</span> guardados en discos duros mutarán en una herencia que hace patente la esperanza de volver a usarlos de nuevo. Pero con el tiempo estos dispositivos, que contienen nuestro patrimonio cultural, se convertirán en objetos extraños sin utilidad aparente.</p>
<p>Las características de los <span class="smallcap">AD</span> que nos hacen ver la fragilidad de los <span class="smallcap">AF</span> van a desaparecer en su ocultamiento. ¿Aún podemos hablar de información si esta es potencial —sabemos que los datos están ahí, pero son inaccesibles ya que no tenemos los medios para verlos—? ¿O acaso la información ya implica los recursos técnicos para su acceso —es decir, no existe la información sin un sujeto con las capacidades técnicas para extraer, procesar y usar los datos—?</p>
<p>Cuando por lo común hablamos sobre la información, ya suponemos que está ahí pero en varias ocasiones no es accesible. Así que la idea de información potencial podría ser contraintuitiva. Si la información no está en acto, de manera llana consideramos que es inexistente, no que se encuentra en algún estado potencial.</p>
<p>A la par que nuestra tecnología está en desarrollo, nosotros asumimos que siempre habrá <i>la posibilidad</i> de dar con mejores maneras para extraer e interpretar los datos; y, por ello, que existen más oportunidades de cosechar nuevos tipos de información —y de obtener ganancias con ello—. La preservación de los datos yace entre estas posibilidades debido a que casi siempre respaldamos archivos con la idea de que los podríamos necesitar de nuevo.</p>
<p>Nuestro mundo se vuelve más complejo por las nuevas cosas que están a nuestra disposición, en muchos casos como nuevas características de cosas que ya conocemos. Las políticas de preservación implican un optimismo epistémico y no solo un anhelo de mantener nuestro patrimonio vivo o incorrupto. No respaldaríamos datos si antes no creyéramos que podríamos necesitarlos en un futuro donde aún podemos utilizarlos.</p>
<p>Con este ejercicio se puede ver con claridad una posible paradoja de los <span class="smallcap">AD</span>. Para tener más acceso se tiende a requerir una mayor infraestructura técnica. Esto puede implicar una mayor dependencia tecnológica que subordina la accesibilidad de la información a la disposición de los medios técnicos. <i>Por lo tanto</i>, nos encontramos con una situación donde una mayor accesibilidad es proporcional a una mayor infraestructura tecnológica y —tal como lo vemos en nuestros días— dependencia.</p>
<p>El acceso abierto al conocimiento supone al menos unos requerimientos técnicos mínimos. Sin ello no podemos en realidad hablar de accesibilidad de la información. Las posibilidades del acceso abierto contemporáneo están restringidas a una dependencia tecnológica ya existente porque le prestamos más atención a la flexibilidad que los <span class="smallcap">AD</span> nos ofrecen para <i>su uso</i>. En un mundo sin fuentes de energía eléctrica este tipo de acceso se vuelve estrecho y un esfuerzo inútil.</p>
<figure>
<img src="../../../img/p004_i002.jpg" alt="Programando Libreros y Hacklib mientras trabajan en un proyecto cuyo objetivo es la P&#38;R de libros viejos de ciencia ficción latinoamericana; en ciertas ocasiones un escáner en forma de V es necesario cuando los libros son muy frágiles."/>
<figcaption>
Programando Libreros y Hacklib mientras trabajan en un proyecto cuyo objetivo es la <span class="smallcap">P&#38;R</span> de libros viejos de ciencia ficción latinoamericana; en ciertas ocasiones un escáner en forma de V es necesario cuando los libros son muy frágiles.
</figcaption>
</figure>
<p>Así que, <i>¿quién respalda a quién?</i> En nuestro mundo, donde la geopolítica y los medios técnicos restringen el flujo de los datos y las personas al mismo tiempo que defiende al acceso a internet como un derecho humano —un tipo de discurso neoilustrado—, los <span class="smallcap">AD</span> son el salvavidas en una situación donde no tenemos otras formas de movernos alrededor o de escapar —no solo de frontera en frontera, sino también en el ciberespacio: se está volviendo un lugar común la necesidad de inscripción y de cesión de tu identidad con el fin de usar servicios <i>web</i>—. Vale la pena recordar que el acceso abierto a los datos puede ser un camino para mejorar como comunidad pero también podría constituirse en un método para perpetuar las condiciones sociales.</p>
<p>No muchas personas tienen el privilegio que gozamos cuando hablamos sobre el acceso a los medios técnicos. Incluso de manera más desconcertante hay compas con incapacidades que les complican el acceso a la información aunque cuenten con los medios. ¿Acaso no es gracioso que nuestras ideas vertidas en un archivo puedan moverse de manera más «libre» que nosotros —tus memes pueden llegar a plataformas <i>web</i> donde tu presencia no está autorizada—?</p>
<p>Deseo más desarrollos tecnológicos en pos de la libertad de la <span class="smallcap">P&#38;R</span> y no solo de su uso como goce —no importa si es con fines intelectuales o de consumo—. Quiero que seamos libres. Pero en algunos casos las libertades sobre el uso de datos, la <span class="smallcap">P&#38;R</span> de la información y la movilidad de las personas no se llevan bien.</p>
<p>Con los <span class="smallcap">AD</span> obtenemos una mayor independencia en el uso de los archivos porque una vez que han sido guardados, pueden propagarse. No importan las barreras políticas o religiosas; la batalla toma lugar principalmente en el campo técnico. Pero esto no le da a los <span class="smallcap">AD</span> una mayor autonomía en su <span class="smallcap">P&#38;R</span>. Tampoco implica que podamos obtener libertades personales o comunitarias. Los <span class="smallcap">AD</span> son objetos. <i>Los <span class="smallcap">AD</span> son herramientas</i> y cualquiera que los use mejor, cualquiera que sea su dueño, tendrá más poder.</p>
<p>Con los <span class="smallcap">AF</span> cabe la oportunidad de que tengamos más libertad para su <span class="smallcap">P&#38;R</span>. Podemos hacer cualquier cosa que queramos con ellos: extraer sus datos, procesarlos y liberarlos. Pero solo si somos sus propietarios. En muchos casos no es el caso, así que los <span class="smallcap">AF</span> tienden a tener un acceso más restringido para su uso. Y, de nueva cuenta, esto no implica que podamos ser libres. No existe una relación causa y efecto entre lo que un objeto hace posible y la manera en como un sujeto quiere ser libre. Los <span class="smallcap">AF</span> son herramientas, no son amos ni esclavos, solo un medio para cualquiera que los use… pero ¿con qué fines?</p>
<p>Necesitamos los <span class="smallcap">AD</span> y a los <span class="smallcap">AF</span> como respaldos y como objetos de uso diario. El acto de respaldar es una categoría dinámica. Los archivos respaldados no son inertes ni son sustratos que esperan ser usados. En algunos casos vamos a usar los <span class="smallcap">AF</span> porque los <span class="smallcap">AD</span> han sido corrompidos o su infraestructura tecnológica ha sido suspendida. En otras ocasiones vamos a usar los <span class="smallcap">AD</span> cuando los <span class="smallcap">AF</span> han sido destruidos o restringidos.</p>
<figure>
<img src="../../../img/p004_i003.jpg" alt="Debido a la restricción en el acceso a los AF, a veces es necesario un escáner portable en forma de V; este modelo nos permite manejar libros deteriorados así como podemos guardarlo en una mochila."/>
<figcaption>
Debido a la restricción en el acceso a los <span class="smallcap">AF</span>, a veces es necesario un escáner portable en forma de V; este modelo nos permite manejar libros deteriorados así como podemos guardarlo en una mochila.
</figcaption>
</figure>
<p>Así que la lucha en relación con los respaldos —y a toda esa mierda acerca de la «libertad» en las comunidades del <i>software</i> libre y del código abierto— no es solo en torno al reino «incorpóreo» de la información. Tampoco sobre los medios técnicos que posibilitan los datos digitales. Ni mucho menos respecto a las leyes que transforman la producción en propiedad. Tenemos otros frentes de batalla en contra del monopolio del ciberespacio —o como Lingel <a href="http://culturedigitally.org/2019/03/the-gentrification-of-the-internet/">dice</a>: la gentrificación del internet.</p>
<p>No es solo acera del <i>software</i>, del <i>hardware</i>, de la privacidad, de la información o de las leyes. Se trata de nosotros: sobre cómo construimos comunidades y cómo la tecnología nos constituye como sujetos. <i>Necesitamos más teoría</i>. Pero una diversificada porque estar en internet no es lo mismo para un académico, un editor, una mujer, un niño, un refugiado, una persona no-blanca, un pobre o una anciana. Este espacio no es neutral ni homogéneo ni bidimensional. Se compone de cables, posee servidores, implica la explotación laboral, se conserva en edificios, <i>tiene poder</i> y, bueno, goza de todas las cosas del «mundo real». Que uses un dispositivo para su acceso no significa que en cualquier momento puedes decidir si estás conectado o no: siempre estás en línea sea como usuario, como consumidor o como dato.</p>
<p><i>¿Quién respalda a quién?</i> Así como el internet nos está cambiando tal cual lo hizo la imprenta, lo archivos respaldados no son datos guardados sino <i>la memoria de nuestro mundo</i>. ¿Aún es buena idea dejar el trabajo de su <span class="smallcap">P&#38;R</span> a un par de compañías de <i>hardware</i> y de <i>software</i>? ¿Podemos ya decir que el acto de respaldar implica archivos pero también algo más?</p>
<script type="text/javascript" src="../../../hashover/comments.php"></script>
</section>
<footer>
<p class="left no-indent">Todo el contenido está bajo <a href="../../../content/html/es/_fork.html">Licencia Editorial Abierta y Libre (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Última modificación de esta página: 2019/07/04, 11:04.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/es/rss.xml">RSS</a></span> | <a href="../../../content/html/en/004_backup.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/004_backup.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/004_backup.html"><span class="versalita">NB</span></a></p>
</footer>
</body>
</html>

6
content/html/es/index.html
View File

@ -32,6 +32,10 @@
<a onclick="mode(this)">N</a>
</div>
<section>
<div class="post">
<p><a href="004_backup.html">4. ¿Quién respalda a quién?</a></p>
<p>[Publicado: 2019/07/04, 11:00]</p>
</div>
<div class="post">
<p><a href="003_dont-come.html">3. No vengas con esos cuentos</a></p>
<p>[Publicado: 2019/05/05, 20:00]</p>
@ -47,7 +51,7 @@
</section>
<footer>
<p class="left no-indent">Todo el contenido está bajo <a href="../../../content/html/es/_fork.html">Licencia Editorial Abierta y Libre (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Última modificación de esta página: 2019/07/01, 10:34.</p>
<p class="left no-indent">Última modificación de esta página: 2019/07/04, 11:04.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/es/rss.xml">RSS</a></span> | <a href="../../../content/html/en/index.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/index.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/index.html"><span class="versalita">NB</span></a></p>
</footer>

2
content/html/nb/003_dont-come.html
View File

@ -29,7 +29,7 @@
</section>
<footer>
<p class="left no-indent">Alt innholdet er lisensiert <a href="../../../content/html/nb/_fork.html">Licencia Editorial Abierta y Libre (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Siste endring av denne siden: 2019/07/01, 10:32.</p>
<p class="left no-indent">Siste endring av denne siden: 2019/07/04, 11:03.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/nb/rss.xml">RSS</a></span> | <a href="../../../content/html/en/003_dont-come.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/003_dont-come.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/003_dont-come.html"><span class="versalita">NB</span></a></p>
</footer>

37
content/html/nb/004_backup.html Normal file
View File

@ -0,0 +1,37 @@
<!DOCTYPE html>
<html lang="nb">
<head>
<title> Título </title>
<meta charset="utf-8" />
<meta name="application-name" content="Publishing is Coding: Change My Mind">
<meta name="description" content="Blog about free culture, free software and free publishing.">
<meta name="keywords" content="publishing, blog, book, ebook, methodology, foss, libre-software, format, markdown, html, epub, pdf, mobi, latex, tex, culture, free culture, philosophy">
<meta name="viewport" content="width=device-width, user-scalable=0">
<link rel="shortcut icon" href="../../../icon.png">
<link rel="alternate" type="application/rss+xml" href="https://perrotuerto.blog/feed/" title="Publishing is Coding: Change My Mind">
<link type="text/css" rel="stylesheet" href="../../../css/styles.css">
<link type="text/css" rel="stylesheet" href="../../../css/extra.css">
<script type="application/javascript" src="../../../js/functions.js"></script>
</head>
<body>
<header>
<h1><a href="https://perrotuerto.blog/content/html/nb/">Publishing is Coding: Change My Mind</a></h1>
<nav> <p> <a href="../../../content/html/nb/_links.html">Lenker</a> | <a href="../../../content/html/nb/_about.html">Om</a> | <a href="../../../content/html/nb/_contact.html">Kontakt</a> | <a href="../../../content/html/nb/_fork.html">Forgren</a> | <a href="../../../content/html/nb/_donate.html">Doner</a> </p>
</nav>
</header>
<div id="controllers">
<a onclick="zoom(true)">+</a>
<a onclick="zoom(false)">−</a>
<a onclick="mode(this)">N</a>
</div>
<section>
<script type="text/javascript" src="../../../hashover/comments.php"></script>
</section>
<footer>
<p class="left no-indent">Alt innholdet er lisensiert <a href="../../../content/html/nb/_fork.html">Licencia Editorial Abierta y Libre (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Siste endring av denne siden: 2019/07/04, 11:04.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/nb/rss.xml">RSS</a></span> | <a href="../../../content/html/en/004_backup.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/004_backup.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/004_backup.html"><span class="versalita">NB</span></a></p>
</footer>
</body>
</html>

2
content/html/nb/index.html
View File

@ -35,7 +35,7 @@
</section>
<footer>
<p class="left no-indent">Alt innholdet er lisensiert <a href="../../../content/html/nb/_fork.html">Licencia Editorial Abierta y Libre (<span class="smallcap">LEAL</span>)</a>.</p>
<p class="left no-indent">Siste endring av denne siden: 2019/07/01, 10:34.</p>
<p class="left no-indent">Siste endring av denne siden: 2019/07/04, 11:04.</p>
<p class="left no-indent"><a target="_blank" href="https://hosted.weblate.org/engage/publishing-is-coding-change-my-mind/?utm_source=widget"><img class="auto-width" style="margin:0;" src="https://hosted.weblate.org/widgets/publishing-is-coding-change-my-mind/-/svg-badge.svg" /></a></p>
<p class="left no-indent"><span class="smallcap"><a target="_blank" href="https://perrotuerto.blog/feed/nb/rss.xml">RSS</a></span> | <a href="../../../content/html/en/index.html"><span class="versalita">EN</span></a> | <a href="../../../content/html/es/index.html"><span class="versalita">ES</span></a> | <a href="../../../content/html/nb/index.html"><span class="versalita">NB</span></a></p>
</footer>

2
content/md/004_backup.md
View File

@ -1,6 +1,6 @@
# Who Backup Whom?
> @published 2019/07/03, 13:00 {.published}
> @published 2019/07/04, 10:00 {.published}
Among publishers and readers is common to heard about “digital
copies.” This implies that ebooks tend to be seen as backups

4
content/po/en/003_dont-come.po
View File

@ -7,7 +7,7 @@ msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2019-05-06 10:33-0500\n"
"PO-Revision-Date: 2019-07-04 11:03-0500\n"
"Language-Team: none\n"
"Language: en\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
@ -15,7 +15,7 @@ msgstr ""
#: content/md/003_dont_come.js:1
msgid "# Don't come with those tales"
msgstr "# Don't come with those tales"
msgstr "# Don't Come with Those Tales"
#: content/md/003_dont_come.js:2
msgid "> @published 2019/05/05, 20:00 {.published}"

477
content/po/en/004_backup.po Normal file
View File

@ -0,0 +1,477 @@
msgid ""
msgstr ""
"Project-Id-Version: 004_backup 1.0\n"
"Report-Msgid-Bugs-To: Nika Zhenya <nika.zhenya@cliteratu.re>\n"
"POT-Creation-Date: 2019-07-04 07:49-0500\n"
"Last-Translator: Automatically generated\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2019-07-04 11:04-0500\n"
"Language-Team: none\n"
"Language: en\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"
#: content/md/004_backup.js:1
msgid "# Who Backup Whom?"
msgstr "# Who Backup Whom?"
#: content/md/004_backup.js:2
msgid "> @published 2019/07/04, 10:00 {.published}"
msgstr "> @published 2019/07/04, 11:00 {.published}"
#: content/md/004_backup.js:3
msgid ""
"Among publishers and readers is common to heard about “digital copies.” This "
"implies that ebooks tend to be seen as backups of printed books. How the "
"former became a copy of the original---even tough you first need a digital "
"file in order to print---goes something like this:"
msgstr ""
"Among publishers and readers is common to heard about “digital copies.” This "
"implies that ebooks tend to be seen as backups of printed books. How the "
"former became a copy of the original---even tough you first need a digital "
"file in order to print---goes something like this:"
#: content/md/004_backup.js:8
msgid ""
"1. Digital files (+++DF+++s) with appropriate maintenance could\n"
" have higher probabilities to last longer that its material\n"
" peer.\n"
"2. Physical files (+++PF+++s) are limited due geopolitical\n"
" issues, like cultural policies updates, or due random events,\n"
" like environment changes or accidents.\n"
"3. _Therefore_, +++DF+++s are backups of +++PF+++s because _in\n"
" theory_ its dependence is just technical."
msgstr ""
"1. Digital files (+++DF+++s) with appropriate maintenance could\n"
" have higher probabilities to last longer that its material\n"
" peer.\n"
"2. Physical files (+++PF+++s) are limited due geopolitical\n"
" issues, like cultural policies updates, or due random events,\n"
" like environment changes or accidents.\n"
"3. _Therefore_, +++DF+++s are backups of +++PF+++s because _in\n"
" theory_ its dependence is just technical."
#: content/md/004_backup.js:16
msgid ""
"The famous digital copies arise as a right of private copy. What if one day "
"our printed books get ban or burn? Or maybe some rain or coffee spill could "
"fuck our books collection. Who knows, +++DF+++s seem more reliable."
msgstr ""
"The famous digital copies arise as a right of private copy. What if one day "
"our printed books get ban or burn? Or maybe some rain or coffee spill could "
"fuck our books collection. Who knows, +++DF+++s seem more reliable."
#: content/md/004_backup.js:20
msgid ""
"But there are a couple suppositions in this argument. (1) The technology "
"behind +++DF+++s in one way or the other will always make data flow. Maybe "
"this is because (2) one characteristic---part of its “nature”---of "
"information is that nobody can stop its spread. This could also implies that "
"(3) hackers can always destroy any kind of digital rights management system."
msgstr ""
"But there are a couple suppositions in this argument. (1) The technology "
"behind +++DF+++s in one way or the other will always make data flow. Maybe "
"this is because (2) one characteristic---part of its “nature”---of "
"information is that nobody can stop its spread. This could also implies that "
"(3) hackers can always destroy any kind of digital rights management system."
#: content/md/004_backup.js:26
msgid ""
"Certainly some dudes are gonna be able to hack the locks but at a high cost: "
"every time each [cipher](https://en.wikipedia.org/wiki/Cipher) is revealed, "
"another more complex is on the way---_Barlow [dixit](https://www.wired."
"com/1994/03/economy-ideas/)_. We cannot trust that our digital "
"infrastructure would be designed with the idea of free share in mind… Also, "
"how can we probe information wants to be free without relying in its "
"“nature” or making it some kind of autonomous subject?"
msgstr ""
"Certainly some dudes are gonna be able to hack the locks but at a high cost: "
"every time each [cipher](https://en.wikipedia.org/wiki/Cipher) is revealed, "
"another more complex is on the way---*Barlow [dixit](https://www.wired."
"com/1994/03/economy-ideas/)*. We cannot trust that our digital "
"infrastructure would be designed with the idea of free share in mind… Also, "
"how can we probe information wants to be free without relying in its "
"“nature” or making it some kind of autonomous subject?"
#: content/md/004_backup.js:33
msgid ""
"Besides those issues, the dynamic between copies and originals creates an "
"hierarchical order. Every +++DF+++ is in a secondary position because it is "
"a copy. In a world full of things, materiality is and important feature for "
"commons and goods; for several people +++PF+++s are gonna be preferred "
"because, well, you can grasp them."
msgstr ""
"Besides those issues, the dynamic between copies and originals creates an "
"hierarchical order. Every +++DF+++ is in a secondary position because it is "
"a copy. In a world full of things, materiality is and important feature for "
"commons and goods; for several people +++PF+++s are gonna be preferred "
"because, well, you can grasp them."
#: content/md/004_backup.js:39
msgid ""
"Ebook market shows that the hierarchy is at least shading. For some readers +"
"++DF+++s are now in the top of the pyramid. We could say so by the follow "
"argument:"
msgstr ""
"Ebook market shows that the hierarchy is at least shading. For some readers +"
"++DF+++s are now in the top of the pyramid. We could say so by the follow "
"argument:"
#: content/md/004_backup.js:42
msgid ""
"1. +++DF+++s are way more flexible and easy to share.\n"
"2. +++PF+++s are very static and not easy to access.\n"
"3. _Therefore_, +++DF+++s are more suitable for use than +++PF+++s."
msgstr ""
"1. +++DF+++s are way more flexible and easy to share.\n"
"2. +++PF+++s are very rigid and not easy to access.\n"
"3. _Therefore_, +++DF+++s are more suitable for use than +++PF+++s."
#: content/md/004_backup.js:45
msgid ""
"Suddenly, +++PF+++s become hard copies that are gonna store data as it was "
"published. Its information is in disposition to be extracted and processed "
"if need it."
msgstr ""
"Suddenly, +++PF+++s become hard copies that are gonna store data as it was "
"published. Its information is in disposition to be extracted and processed "
"if need it."
#: content/md/004_backup.js:48
msgid ""
"Yeah, we also have a couple assumptions here. Again (1) we rely on the "
"stability of our digital infrastructure that it would allow us to have "
"access to +++DF+++s no matter how old they are. (2) Reader's priorities are "
"over files use---if not merely consumption---not on its preservation and "
"reproduction (+++P&R+++). (3) The argument presume that backups are "
"motionless information, where bookshelves are fridges for later-to-use books."
msgstr ""
"Yeah, we also have a couple assumptions here. Again (1) we rely on the "
"stability of our digital infrastructure that it would allow us to have "
"access to +++DF+++s no matter how old they are. (2) Reader's priorities are "
"over files use---if not merely consumption---not on its preservation and "
"reproduction (+++P&R+++). (3) The argument presume that backups are "
"motionless information, where bookshelves are fridges for later-to-use books."
#: content/md/004_backup.js:55
msgid ""
"The optimism about our digital infrastructure is too damn high. Commonly we "
"see it as a technology that give us access to zillions of files and not as a "
"+++P&R+++ machinery. This could be problematic because some times file "
"formats intended for use aren't the most suitable for +++P&R+++. For "
"example, the use of +++PDF+++s as some kind of ebook. Giving to much "
"importance to reader's priorities could lead us to a situation where the "
"only way to process data is by extracting it again from hard copies. When we "
"do that we also have another headache: fixes on the content have to be add "
"to the last available hard copy edition. But, can you guess where are all "
"the fixes? Probably not. Maybe we should start to think about backups as "
"some sort of _rolling update_."
msgstr ""
"The optimism about our digital infrastructure is too damn high. Commonly we "
"see it as a technology that give us access to zillions of files and not as a "
"+++P&R+++ machinery. This could be problematic because some times file "
"formats intended for use aren't the most suitable for +++P&R+++. For "
"example, the use of +++PDF+++s as some kind of ebook. Giving to much "
"importance to reader's priorities could lead us to a situation where the "
"only way to process data is by extracting it again from hard copies. When we "
"do that we also have another headache: fixes on the content have to be add "
"to the last available hard copy edition. But, can you guess where are all "
"the fixes? Probably not. Maybe we should start to think about backups as "
"some sort of _rolling update_."
#: content/md/004_backup.js:67
msgid ""
"![Programando Libreros while she scans books which +++DF+++s are not "
"suitable for +++P&R+++ or are simply nonexistent; can you see how it is not "
"necessary to have a fucking nice scanner?](../../../img/p004_i001.jpg)"
msgstr ""
"![Programando Libreros while she scans books which +++DF+++s are not "
"suitable for +++P&R+++ or are simply nonexistent; can you see how it is not "
"necessary to have a fucking nice scanner?](../../../img/p004_i001.jpg)"
#: content/md/004_backup.js:70
msgid ""
"As we imagine---and started to live in---scenarios of highly controlled data "
"transfer, we have to picture a situation where for some reason our electric "
"power is off or running low. In that context all the strengths of +++DF+++s "
"become pointless. They may not be accessible. They may not spread. Right now "
"for us is hard to imagine. Generation after generation the storaged +++DF++"
"+s in +++HDD+++s would be inherit with the hope of being used again. But "
"over time those devices with our cultural heritage would become rare objects "
"without any apparent utility."
msgstr ""
"As we imagine---and started to live in---scenarios of highly controlled data "
"transfer, we have to picture a situation where for some reason our electric "
"power is off or running low. In that context all the strengths of +++DF+++s "
"become pointless. They may not be accessible. They may not spread. Right now "
"for us is hard to imagine. Generation after generation the storaged +++DF++"
"+s in +++HDD+++s would be inherit with the hope of being used again. But "
"over time those devices with our cultural heritage would become rare objects "
"without any apparent utility."
#: content/md/004_backup.js:79
msgid ""
"The aspects of +++DF+++s that made us see the fragility of +++PF+++s would "
"disappear in its concealment. Can we still talk about information if it is "
"potential information---we know the data is there, but it is inaccessible "
"because we don't have the means for view them? Or does information already "
"implies the technical resources for its access---i.e. there is not "
"information without a subject with technical skills to extract, process and "
"use the data?"
msgstr ""
"The aspects of +++DF+++s that made us see the fragility of +++PF+++s would "
"disappear in its concealment. Can we still talk about information if it is "
"on a potential stage---we know data is there, but it is inaccessible because "
"we don't have means for view them? Or does information already implies "
"technical resources for its access---i.e. there is not information without a "
"subject with technical skills to extract, process and use the data?"
#: content/md/004_backup.js:86
msgid ""
"When we usually talk about information we already suppose is there, but many "
"times is not accessible. So the idea of potential information could be "
"counterintuitive. If the information isn't actual we just consider that it "
"doesn't exist, not that it is on some potential stage."
msgstr ""
"When we usually talk about information we already suppose it is there, but "
"many times it is not accessible. So the idea of potential information could "
"be counterintuitive. If information isn't actual we just consider that it "
"doesn't exist, not that it is on some potential stage."
#: content/md/004_backup.js:91
msgid ""
"As our technology is developing we assume that we would always have _the "
"possibility_ of better ways to extract or understand data. Thus, that there "
"are bigger chances to get new kinds of information---and take a profit from "
"it. Preservation of data relies between those possibilities, as we usually "
"backup files with the idea that we could need to go back again."
msgstr ""
"As our technology is developing we assume that we would always have _the "
"possibility_ of better ways to extract or understand data. Thus, that there "
"are bigger chances to get new kinds of information---and take profit from "
"it. Preservation of data relies between those possibilities, as we usually "
"backup files with the idea that we could need to go back again."
#: content/md/004_backup.js:97
msgid ""
"Our world become more complex by new things forthcoming to us, most of the "
"times as new characteristics of things we already know. Preservation "
"policies implies an epistemic optimism and not only a desire to keep alive "
"or incorrupt our heritage. We wouldn't backup data if we don't already "
"believe we could need it in a future where we can still use it."
msgstr ""
"Our world become more complex by new things forthcoming to us, most of the "
"times as new characteristics of things we already know. Preservation "
"policies implies an epistemic optimism and not only a desire to keep alive "
"or incorrupt our heritage. We wouldn't backup data if we don't already "
"believe we could need it in a future where we can still use it."
#: content/md/004_backup.js:103
msgid ""
"With this exercise could be clear a potentially paradox of +++DF+++s. More "
"accessibility tends to require more technical infrastructure. This could "
"imply major technical dependence that subordinate accessibility of "
"information to the disposition of technical means. _Therefore_, we achieve a "
"situation where more accessibility is equal to more technical infrastructure "
"and---as we experience nowadays---dependence."
msgstr ""
"With this exercise it could be clear a potentially paradox of +++DF+++s. "
"More accessibility tends to require more technical infrastructure. This "
"could imply major technical dependence that subordinate accessibility of "
"information to the disposition of technical means. _Therefore_, we achieve a "
"situation where more accessibility is equal to more technical infrastructure "
"and---as we experience nowadays---dependence."
#: content/md/004_backup.js:110
msgid ""
"Open access to knowledge involves at least some minimum technical means. "
"Without that, we can't really talk about accessibility of information. "
"Contemporary open access possibilities are restricted to an already "
"technical dependence because we give a lot of attention in the flexibility "
"that +++DF+++s offer us for _its use_. In a world without electric power, "
"this kind of accessibility becomes narrow and an useless effort."
msgstr ""
"Open access to knowledge involves at least some minimum technical means. "
"Without that, we can't really talk about accessibility of information. "
"Contemporary open access possibilities are restricted to an already "
"technical dependence because we give a lot of attention in the flexibility "
"that +++DF+++s offer us for _its use_. In a world without electric power, "
"this kind of accessibility becomes narrow and an useless effort."
#: content/md/004_backup.js:117
msgid ""
"![Programando Libreros and Hacklib while they work on a project intended to +"
"++P&R+++ old Latin American SciFi books; sometimes a V-shape scanner is "
"required when books are very fragile.](../../../img/p004_i002.jpg)"
msgstr ""
"![Programando Libreros and Hacklib while they work on a project intended to +"
"++P&R+++ old Latin American SciFi books; sometimes a V-shape scanner is "
"required when books are very fragile.](../../../img/p004_i002.jpg)"
#: content/md/004_backup.js:120
msgid ""
"So, _who backup whom?_ In our actual world, where geopolitics and technical "
"means restricts flow of data and people at the same time it defends internet "
"access as a human right---some sort of neo-Enlightenment discourse---+++DF++"
"+s are lifesavers in a condition where we don't have more ways to move "
"around or scape---not only from border to border, but also on cyberspace: it "
"is becoming a common place the need to sign up and give your identity in "
"order to use web services. Let's not forget that open access of data can be "
"a course of action to improve as community but also a method to perpetuate "
"social conditions."
msgstr ""
"So, _who backup whom?_ In our actual world, where geopolitics and technical "
"means restricts flow of data and people at the same time it defends internet "
"access as a human right---some sort of neo-Enlightenment discourse---+++DF++"
"+s are lifesavers in a condition where we don't have more ways to move "
"around or scape---not only from border to border, but also on cyberspace: it "
"is becoming a common place the need to sign up and give your identity in "
"order to use web services. Let's not forget that open access of data can be "
"a course of action to improve as community but also a method to perpetuate "
"social conditions."
#: content/md/004_backup.js:130
msgid ""
"Not a lot of people are as privilege as us when we talk about access to "
"technical means. Even more concerning, they are hommies with disabilities "
"that made very hard for them to access information albeit they have those "
"means. Isn't it funny that our ideas as file contents can move more “freely” "
"than us---your memes can reach web platform where you are not allow to sign "
"in?"
msgstr ""
"Not a lot of people are as privilege as us when we talk about access to "
"technical means. Even more concerning, there are hommies with disabilities "
"that made very hard for them to access information albeit they have those "
"means. Isn't it funny that our ideas as file contents can move more “freely” "
"than us---your memes can reach web platform where you are not allow to sign "
"in?"
#: content/md/004_backup.js:136
msgid ""
"I desire more technological developments for freedom of +++P&R+++ and not "
"just for use as enjoyment---no matter is for intellectual or consumption "
"purposes. I want us to be free. But sometimes use of data, +++P&R+++ of "
"information and people mobility freedoms don't get along."
msgstr ""
"I desire more technological developments for freedom of +++P&R+++ and not "
"just for use as enjoyment---no matter is for intellectual or consumption "
"purposes. I want us to be free. But sometimes use of data, +++P&R+++ of "
"information and people mobility freedoms don't get along."
#: content/md/004_backup.js:141
msgid ""
"With +++DF+++s we achieve more independence in file use because once it is "
"save, it could spread. It doesn't matter we have religious or political "
"barriers; the battle take place mainly in technical grounds. But this "
"doesn't made +++DF+++s more autonomous in its +++P&R+++. Neither implies we "
"can archive personal or community freedoms. They are objects. _They are "
"tools_ and whoever use them better, whoever owns them, would have more power."
msgstr ""
"With +++DF+++s we achieve more independence in file use because once it is "
"save, it could spread. It doesn't matter we have religious or political "
"barriers; the battle take place mainly in technical grounds. But this "
"doesn't made +++DF+++s more autonomous in its +++P&R+++. Neither implies we "
"can archive personal or community freedoms. They are objects. _They are "
"tools_ and whoever use them better, whoever owns them, would have more power."
#: content/md/004_backup.js:148
msgid ""
"With +++PF+++s we can have more +++P&R+++ accessibility. We can do whatever "
"we want with them: extract their data, process it and let it free. But only "
"if we are their owners. Often that is not the case, so +++PF+++s tend to "
"have more restricted access for its use. And, again, this doesn't mean we "
"can be free. There is not any cause and effect between what object made "
"possible and how subjects want to be free. They are tools, they are not "
"master or slaves, just means for whoever use them… but for which ends?"
msgstr ""
"With +++PF+++s we can have more +++P&R+++ freedom. We can do whatever we "
"want with them: extract their data, process it and let it free. But only if "
"we are their owners. Often that is not the case, so +++PF+++s tend to have "
"more restricted access for its use. And, again, this doesn't mean we can be "
"free. There is not any cause and effect relationship between what object "
"made possible and how subjects want to be free. They are tools, they are not "
"master or slaves, just means for whoever use them… but for which ends?"
#: content/md/004_backup.js:157
msgid ""
"We need +++DF+++s and +++PF+++s as backups and as everyday objects of use. "
"The act of backup is a dynamic category. Backed up files are not inert and "
"they aren't only a substrate waiting to be use. Sometimes we are going to "
"use +++PF+++s because +++DF+++s have been corrupted or its technical "
"infrastructure has been shut down. In other occasions we would use +++DF+++s "
"when +++PF+++s have been destroyed or restricted."
msgstr ""
"We need +++DF+++s and +++PF+++s as backups and as everyday objects of use. "
"The act of backup is a dynamic category. Backed up files are not inert and "
"they aren't only substrates waiting to be use. Sometimes we are going to use "
"+++PF+++s because +++DF+++s have been corrupted or its technical "
"infrastructure has been shut down. In other occasions we would use +++DF+++s "
"when +++PF+++s have been destroyed or restricted."
#: content/md/004_backup.js:164
msgid ""
"![Due restricted access to +++PF+++s, sometimes it is necessary a portable V-"
"shape scanner; this model allows us to handle damaged books while we can "
"also storage it in a backpack.](../../../img/p004_i003.jpg)"
msgstr ""
"![Due restricted access to +++PF+++s, sometimes it is necessary a portable V-"
"shape scanner; this model allows us to handle damaged books while we can "
"also storage it in a backpack.](../../../img/p004_i003.jpg)"
#: content/md/004_backup.js:167
msgid ""
"So the struggle about backups---and all that shit about “freedom” on +++FOSS+"
"++ communities---it is not only around the “incorporeal” realm of "
"information. Nor on the technical means that made digital data possible. "
"Neither in the laws that transform production into property. We have others "
"battle fronts against the monopoly of the cyberspace---or as Lingel [says]"
"(http://culturedigitally.org/2019/03/the-gentrification-of-the-internet/): "
"the gentrification of the internet."
msgstr ""
"So the struggle about backups---and all that shit about “freedom” on +++FOSS+"
"++ communities---it is not only around the “incorporeal” realm of "
"information. Nor on the technical means that made digital data possible. "
"Neither in the laws that transform production into property. We have others "
"battle fronts against the monopoly of the cyberspace---or as Lingel [says]"
"(http://culturedigitally.org/2019/03/the-gentrification-of-the-internet/): "
"the gentrification of the internet."
#: content/md/004_backup.js:174
msgid ""
"It is not just about software, hardware, privacy, information or laws. It is "
"about us: how we build communities and how technology constitutes us as "
"subjects. _We need more theory_. But a very diversified one because being on "
"internet it is not the same for an scholar, a publisher, a woman, a kid, a "
"refugee, a non-white, a poor or an old person. This space it is not neutral, "
"homogeneous and two-dimensional. It has wires, it has servers, it has "
"exploited employees, it has buildings, _it has power_ and it has, well, all "
"that things the “real world” has. Not because you use a device to access "
"means that you can always decide if you are online or not: you are always "
"online as an user as a consumer or as data."
msgstr ""
"It is not just about software, hardware, privacy, information or laws. It is "
"about us: how we build communities and how technology constitutes us as "
"subjects. _We need more theory_. But a very diversified one because being on "
"internet it is not the same for an scholar, a publisher, a woman, a kid, a "
"refugee, a non-white, a poor or an old lady. This space it isn't neutral nor "
"homogeneous nor two-dimensional. It has wires, it has servers, it has "
"exploited employees, it has buildings, _it has power_ and it has, well, all "
"that things the “real world” has. Not because you use a device to access "
"means that you can always decide if you are online or not: you are always "
"online as an user as a consumer or as data."
#: content/md/004_backup.js:186
msgid ""
"_Who backup whom?_ As internet is changing us as printed text did, backed up "
"files it isn't the storage of data, but _the memory of our world_. Is it "
"still a good idea to leave the work of +++P&R+++ to a couple of hardware and "
"software companies? Are we now allow to say that the act of backup implies "
"files but something else too? "
msgstr ""
"_Who backup whom?_ As internet is changing us as printed text did, backed up "
"files aren't storages of data, but _the memory of our world_. Is it still a "
"good idea to leave the work of +++P&R+++ to a couple hardware and software "
"companies? Are we now allow to say that the act of backup implies files but "
"something else too? "

506
content/po/es/004_backup.po Normal file
View File

@ -0,0 +1,506 @@
msgid ""
msgstr ""
"Project-Id-Version: 004_backup 1.0\n"
"Report-Msgid-Bugs-To: Nika Zhenya <nika.zhenya@cliteratu.re>\n"
"POT-Creation-Date: 2019-07-04 07:49-0500\n"
"Last-Translator: Automatically generated\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2019-07-04 11:04-0500\n"
"Language-Team: none\n"
"Language: es\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 2.2.1\n"
#: content/md/004_backup.js:1
msgid "# Who Backup Whom?"
msgstr "# ¿Quién respalda a quién?"
#: content/md/004_backup.js:2
msgid "> @published 2019/07/04, 10:00 {.published}"
msgstr "> @published 2019/07/04, 11:00 {.published}"
#: content/md/004_backup.js:3
msgid ""
"Among publishers and readers is common to heard about “digital copies.” This "
"implies that ebooks tend to be seen as backups of printed books. How the "
"former became a copy of the original---even tough you first need a digital "
"file in order to print---goes something like this:"
msgstr ""
"Entre editores y lectores es común escuchar sobre las «copias digitales». "
"Esto implica que los libros electrónicos tienden a verse como respaldos de "
"los libros impresos. La manera en como el primero se convierte en una copia "
"del original ---aunque primero necesites un archivo digital para poder "
"imprimir--- es algo similar a lo siguiente:"
#: content/md/004_backup.js:8
msgid ""
"1. Digital files (+++DF+++s) with appropriate maintenance could\n"
" have higher probabilities to last longer that its material\n"
" peer.\n"
"2. Physical files (+++PF+++s) are limited due geopolitical\n"
" issues, like cultural policies updates, or due random events,\n"
" like environment changes or accidents.\n"
"3. _Therefore_, +++DF+++s are backups of +++PF+++s because _in\n"
" theory_ its dependence is just technical."
msgstr ""
"1. Los archivos digitales (+++AD+++) con un apropiado mantenimiento\n"
" pueden tener mayores probabilidades de durar más que su correlato\n"
" material.\n"
"2. Los archivos físicos (+++AF+++) están constreñidos por cuestiones\n"
" geopolíticas, como las modificaciones en las políticas culturales, o por "
"eventos\n"
" aleatorios, como los cambios en el medio ambiente o los accidentes.\n"
"3. _Por lo tanto_, los +++AD+++ son el respaldo de los +++AF+++ porque\n"
" _en teoría_ su dependencia solo es técnica."
#: content/md/004_backup.js:16
msgid ""
"The famous digital copies arise as a right of private copy. What if one day "
"our printed books get ban or burn? Or maybe some rain or coffee spill could "
"fuck our books collection. Who knows, +++DF+++s seem more reliable."
msgstr ""
"La famosa copia digital emerge como un derecho a la copia privada. ¿Qué tal "
"si un día nuestros impresos son censurados o quemados? O quizá una lluvia o "
"un derrame de café puede chingar nuestra colección de libros. Quién sabe, "
"los +++AD+++ parecen ser más confiables."
#: content/md/004_backup.js:20
msgid ""
"But there are a couple suppositions in this argument. (1) The technology "
"behind +++DF+++s in one way or the other will always make data flow. Maybe "
"this is because (2) one characteristic---part of its “nature”---of "
"information is that nobody can stop its spread. This could also implies that "
"(3) hackers can always destroy any kind of digital rights management system."
msgstr ""
"Pero hay un par de suposiciones en este argumento. (1) La tecnología detrás "
"de los +++AD+++ de una manera u otra siempre hará que los datos fluyan. Tal "
"vez esto se debe a que (2) una característica ---parte de su «naturaleza»--- "
"de la información es que nadie puede detener su propagación. Esto puede "
"implicar que (3) los _hackers_ siempre pueden destruir cualquier tipo de "
"sistema de gestión de derechos digitales."
#: content/md/004_backup.js:26
msgid ""
"Certainly some dudes are gonna be able to hack the locks but at a high cost: "
"every time each [cipher](https://en.wikipedia.org/wiki/Cipher) is revealed, "
"another more complex is on the way---_Barlow [dixit](https://www.wired."
"com/1994/03/economy-ideas/)_. We cannot trust that our digital "
"infrastructure would be designed with the idea of free share in mind… Also, "
"how can we probe information wants to be free without relying in its "
"“nature” or making it some kind of autonomous subject?"
msgstr ""
"Sin duda algunas personas van a poder _hackear_ las cerraduras pero a un "
"costo muy alto: cada vez que un [algoritmo criptográfico](https://es."
"wikipedia.org/wiki/Algoritmo_criptogr%C3%A1fico) es revelado, otro más "
"complejo ya viene en camino ---*Barlow [dixit](https://biblioweb.sindominio."
"net/telematica/barlow.html)*---. No podemos confiar en la idea de que "
"nuestra infraestructura digital será diseñada para compartir libremente… "
"Además, ¿cómo se puede probar que la información quiere ser libre sin recaer "
"en su «naturaleza» o tornarla en alguna clase de sujeto autónomo?"
#: content/md/004_backup.js:33
msgid ""
"Besides those issues, the dynamic between copies and originals creates an "
"hierarchical order. Every +++DF+++ is in a secondary position because it is "
"a copy. In a world full of things, materiality is and important feature for "
"commons and goods; for several people +++PF+++s are gonna be preferred "
"because, well, you can grasp them."
msgstr ""
"Por otra parte, la dinámica entre las copias y los originales genera un "
"orden jerárquico. Cada +++AD+++ se encuentra en una posición secundaria "
"porque es una copia. En un mundo lleno de cosas, la materialidad es una "
"característica relevante para los bienes comunes y las mercancías; muchas "
"personas van a preferir los +++AF+++ ya que, bueno, puedes asirlos."
#: content/md/004_backup.js:39
msgid ""
"Ebook market shows that the hierarchy is at least shading. For some readers +"
"++DF+++s are now in the top of the pyramid. We could say so by the follow "
"argument:"
msgstr ""
"El mercado de los libros electrónicos muestra que esta jerarquía al menos se "
"está matizando. Para ciertos lectores los +++AD+++ ahora están en la cúspide "
"de la pirámide. Se puede señalar este fenómeno con el siguiente argumento:"
#: content/md/004_backup.js:42
msgid ""
"1. +++DF+++s are way more flexible and easy to share.\n"
"2. +++PF+++s are very static and not easy to access.\n"
"3. _Therefore_, +++DF+++s are more suitable for use than +++PF+++s."
msgstr ""
"1. Los +++AD+++ son mucho más flexibles y sencillos de compartir.\n"
"2. Los +++AF+++ son muy rígidos y no hay facilidad para su acceso.\n"
"3. _Por lo tanto_, los +++AD+++ son más convenientes que los +++AF+++."
#: content/md/004_backup.js:45
msgid ""
"Suddenly, +++PF+++s become hard copies that are gonna store data as it was "
"published. Its information is in disposition to be extracted and processed "
"if need it."
msgstr ""
"De repente los +++AF+++ mutan en las copias duras donde los datos serán "
"guardados tal cual fueron publicados. Si se requiere, su información está a "
"disposición para la extracción y el procesamiento."
#: content/md/004_backup.js:48
msgid ""
"Yeah, we also have a couple assumptions here. Again (1) we rely on the "
"stability of our digital infrastructure that it would allow us to have "
"access to +++DF+++s no matter how old they are. (2) Reader's priorities are "
"over files use---if not merely consumption---not on its preservation and "
"reproduction (+++P&R+++). (3) The argument presume that backups are "
"motionless information, where bookshelves are fridges for later-to-use books."
msgstr ""
"Sí, aquí también tenemos un par de suposiciones. De nuevo (1) confiamos en "
"la estabilidad de nuestra infraestructura digital que nos permitirá tener "
"acceso a nuestros +++AD+++ sin importar que tan viejos estén. (2) La "
"prioridad de los lectores es sobre el uso de los archivos ---si no su mero "
"consumo--- y no su preservación y reproducción (+++P&R+++). (3) El argumento "
"asume que los respaldos son información inmóvil, donde los estantes son "
"refrigeradores para los libros que después se usarán."
#: content/md/004_backup.js:55
msgid ""
"The optimism about our digital infrastructure is too damn high. Commonly we "
"see it as a technology that give us access to zillions of files and not as a "
"+++P&R+++ machinery. This could be problematic because some times file "
"formats intended for use aren't the most suitable for +++P&R+++. For "
"example, the use of +++PDF+++s as some kind of ebook. Giving to much "
"importance to reader's priorities could lead us to a situation where the "
"only way to process data is by extracting it again from hard copies. When we "
"do that we also have another headache: fixes on the content have to be add "
"to the last available hard copy edition. But, can you guess where are all "
"the fixes? Probably not. Maybe we should start to think about backups as "
"some sort of _rolling update_."
msgstr ""
"El optimismo respecto a nuestra infraestructura digital es muy alto. Por lo "
"general la vemos como una tecnología que nos da acceso a chorrocientos "
"archivos y no como una maquinaria para la +++P&R+++. Esto puede ser "
"problemático porque en ciertos casos los formatos de archivos que fueron "
"diseñados para su uso común no son los más adecuados para su +++P&R+++. Como "
"ejemplo tenemos el uso de +++PDF+++ a modo de libros electrónicos. Si le "
"damos mucha importancia a la prioridad de los lectores, como consecuencia "
"podemos llegar a una situación donde la única manera de procesar los datos "
"es el retorno a su extracción a partir de las copias duras. Cuando lo "
"llevamos a cabo de esa manera tenemos otro dolor de cabeza: las correcciones "
"del contenido tienen que ser añadidas a la última edición disponible en "
"copia dura. Pero ¿puedes adivinar dónde están todas estas correcciones? Lo "
"más seguro es que no. A lo mejor deberíamos por empezar a pensar los "
"respaldos como algún tipo de _actualización continua_."
#: content/md/004_backup.js:67
msgid ""
"![Programando Libreros while she scans books which +++DF+++s are not "
"suitable for +++P&R+++ or are simply nonexistent; can you see how it is not "
"necessary to have a fucking nice scanner?](../../../img/p004_i001.jpg)"
msgstr ""
"![Programando Libreros mientras escanea libros cuyos +++AD+++ no son aptos "
"para la +++P&R+++ o simplemente no existen; ¿ves cómo no es necesario tener "
"un pinche escáner bueno?](../../../img/p004_i001.jpg)"
#: content/md/004_backup.js:70
msgid ""
"As we imagine---and started to live in---scenarios of highly controlled data "
"transfer, we have to picture a situation where for some reason our electric "
"power is off or running low. In that context all the strengths of +++DF+++s "
"become pointless. They may not be accessible. They may not spread. Right now "
"for us is hard to imagine. Generation after generation the storaged +++DF++"
"+s in +++HDD+++s would be inherit with the hope of being used again. But "
"over time those devices with our cultural heritage would become rare objects "
"without any apparent utility."
msgstr ""
"Tal como imaginas ---y comenzamos a vivir en--- escenarios con un alto "
"control en la transferencia de datos, podemos fantasear con una situación "
"donde por alguna razón nuestras fuentes de energía eléctrica no están "
"disponibles o tienen poco abastecimiento. En este contexto todas las "
"fortalezas de los +++AD+++ pierden sentido. A lo mejor no serán accesibles. "
"Quizá no podrán propagarse. Por el momento es difícil de concebir. "
"Generación tras generación los +++AD+++ guardados en discos duros mutarán en "
"una herencia que hace patente la esperanza de volver a usarlos de nuevo. "
"Pero con el tiempo estos dispositivos, que contienen nuestro patrimonio "
"cultural, se convertirán en objetos extraños sin utilidad aparente."
#: content/md/004_backup.js:79
msgid ""
"The aspects of +++DF+++s that made us see the fragility of +++PF+++s would "
"disappear in its concealment. Can we still talk about information if it is "
"potential information---we know the data is there, but it is inaccessible "
"because we don't have the means for view them? Or does information already "
"implies the technical resources for its access---i.e. there is not "
"information without a subject with technical skills to extract, process and "
"use the data?"
msgstr ""
"Las características de los +++AD+++ que nos hacen ver la fragilidad de los ++"
"+AF+++ van a desaparecer en su ocultamiento. ¿Aún podemos hablar de "
"información si esta es potencial ---sabemos que los datos están ahí, pero "
"son inaccesibles ya que no tenemos los medios para verlos---? ¿O acaso la "
"información ya implica los recursos técnicos para su acceso ---es decir, no "
"existe la información sin un sujeto con las capacidades técnicas para "
"extraer, procesar y usar los datos---?"
#: content/md/004_backup.js:86
msgid ""
"When we usually talk about information we already suppose is there, but many "
"times is not accessible. So the idea of potential information could be "
"counterintuitive. If the information isn't actual we just consider that it "
"doesn't exist, not that it is on some potential stage."
msgstr ""
"Cuando por lo común hablamos sobre la información, ya suponemos que está ahí "
"pero en varias ocasiones no es accesible. Así que la idea de información "
"potencial podría ser contraintuitiva. Si la información no está en acto, de "
"manera llana consideramos que es inexistente, no que se encuentra en algún "
"estado potencial."
#: content/md/004_backup.js:91
msgid ""
"As our technology is developing we assume that we would always have _the "
"possibility_ of better ways to extract or understand data. Thus, that there "
"are bigger chances to get new kinds of information---and take a profit from "
"it. Preservation of data relies between those possibilities, as we usually "
"backup files with the idea that we could need to go back again."
msgstr ""
"A la par que nuestra tecnología está en desarrollo, nosotros asumimos que "
"siempre habrá _la posibilidad_ de dar con mejores maneras para extraer e "
"interpretar los datos; y, por ello, que existen más oportunidades de "
"cosechar nuevos tipos de información ---y de obtener ganancias con ello---. "
"La preservación de los datos yace entre estas posibilidades debido a que "
"casi siempre respaldamos archivos con la idea de que los podríamos necesitar "
"de nuevo."
#: content/md/004_backup.js:97
msgid ""
"Our world become more complex by new things forthcoming to us, most of the "
"times as new characteristics of things we already know. Preservation "
"policies implies an epistemic optimism and not only a desire to keep alive "
"or incorrupt our heritage. We wouldn't backup data if we don't already "
"believe we could need it in a future where we can still use it."
msgstr ""
"Nuestro mundo se vuelve más complejo por las nuevas cosas que están a "
"nuestra disposición, en muchos casos como nuevas características de cosas "
"que ya conocemos. Las políticas de preservación implican un optimismo "
"epistémico y no solo un anhelo de mantener nuestro patrimonio vivo o "
"incorrupto. No respaldaríamos datos si antes no creyéramos que podríamos "
"necesitarlos en un futuro donde aún podemos utilizarlos."
#: content/md/004_backup.js:103
msgid ""
"With this exercise could be clear a potentially paradox of +++DF+++s. More "
"accessibility tends to require more technical infrastructure. This could "
"imply major technical dependence that subordinate accessibility of "
"information to the disposition of technical means. _Therefore_, we achieve a "
"situation where more accessibility is equal to more technical infrastructure "
"and---as we experience nowadays---dependence."
msgstr ""
"Con este ejercicio se puede ver con claridad una posible paradoja de los ++"
"+AD+++. Para tener más acceso se tiende a requerir una mayor infraestructura "
"técnica. Esto puede implicar una mayor dependencia tecnológica que subordina "
"la accesibilidad de la información a la disposición de los medios técnicos. "
"_Por lo tanto_, nos encontramos con una situación donde una mayor "
"accesibilidad es proporcional a una mayor infraestructura tecnológica y ---"
"tal como lo vemos en nuestros días--- dependencia."
#: content/md/004_backup.js:110
msgid ""
"Open access to knowledge involves at least some minimum technical means. "
"Without that, we can't really talk about accessibility of information. "
"Contemporary open access possibilities are restricted to an already "
"technical dependence because we give a lot of attention in the flexibility "
"that +++DF+++s offer us for _its use_. In a world without electric power, "
"this kind of accessibility becomes narrow and an useless effort."
msgstr ""
"El acceso abierto al conocimiento supone al menos unos requerimientos "
"técnicos mínimos. Sin ello no podemos en realidad hablar de accesibilidad de "
"la información. Las posibilidades del acceso abierto contemporáneo están "
"restringidas a una dependencia tecnológica ya existente porque le prestamos "
"más atención a la flexibilidad que los +++AD+++ nos ofrecen para _su uso_. "
"En un mundo sin fuentes de energía eléctrica este tipo de acceso se vuelve "
"estrecho y un esfuerzo inútil."
#: content/md/004_backup.js:117
msgid ""
"![Programando Libreros and Hacklib while they work on a project intended to +"
"++P&R+++ old Latin American SciFi books; sometimes a V-shape scanner is "
"required when books are very fragile.](../../../img/p004_i002.jpg)"
msgstr ""
"![Programando Libreros y Hacklib mientras trabajan en un proyecto cuyo "
"objetivo es la +++P&R+++ de libros viejos de ciencia ficción "
"latinoamericana; en ciertas ocasiones un escáner en forma de V es necesario "
"cuando los libros son muy frágiles.](../../../img/p004_i002.jpg)"
#: content/md/004_backup.js:120
msgid ""
"So, _who backup whom?_ In our actual world, where geopolitics and technical "
"means restricts flow of data and people at the same time it defends internet "
"access as a human right---some sort of neo-Enlightenment discourse---+++DF++"
"+s are lifesavers in a condition where we don't have more ways to move "
"around or scape---not only from border to border, but also on cyberspace: it "
"is becoming a common place the need to sign up and give your identity in "
"order to use web services. Let's not forget that open access of data can be "
"a course of action to improve as community but also a method to perpetuate "
"social conditions."
msgstr ""
"Así que, _¿quién respalda a quién?_ En nuestro mundo, donde la geopolítica y "
"los medios técnicos restringen el flujo de los datos y las personas al mismo "
"tiempo que defiende al acceso a internet como un derecho humano ---un tipo "
"de discurso neoilustrado---, los +++AD+++ son el salvavidas en una situación "
"donde no tenemos otras formas de movernos alrededor o de escapar ---no solo "
"de frontera en frontera, sino también en el ciberespacio: se está volviendo "
"un lugar común la necesidad de inscripción y de cesión de tu identidad con "
"el fin de usar servicios _web_---. Vale la pena recordar que el acceso "
"abierto a los datos puede ser un camino para mejorar como comunidad pero "
"también podría constituirse en un método para perpetuar las condiciones "
"sociales."
#: content/md/004_backup.js:130
msgid ""
"Not a lot of people are as privilege as us when we talk about access to "
"technical means. Even more concerning, they are hommies with disabilities "
"that made very hard for them to access information albeit they have those "
"means. Isn't it funny that our ideas as file contents can move more “freely” "
"than us---your memes can reach web platform where you are not allow to sign "
"in?"
msgstr ""
"No muchas personas tienen el privilegio que gozamos cuando hablamos sobre el "
"acceso a los medios técnicos. Incluso de manera más desconcertante hay "
"compas con incapacidades que les complican el acceso a la información aunque "
"cuenten con los medios. ¿Acaso no es gracioso que nuestras ideas vertidas en "
"un archivo puedan moverse de manera más «libre» que nosotros ---tus memes "
"pueden llegar a plataformas _web_ donde tu presencia no está autorizada---?"
#: content/md/004_backup.js:136
msgid ""
"I desire more technological developments for freedom of +++P&R+++ and not "
"just for use as enjoyment---no matter is for intellectual or consumption "
"purposes. I want us to be free. But sometimes use of data, +++P&R+++ of "
"information and people mobility freedoms don't get along."
msgstr ""
"Deseo más desarrollos tecnológicos en pos de la libertad de la +++P&R+++ y "
"no solo de su uso como goce ---no importa si es con fines intelectuales o de "
"consumo---. Quiero que seamos libres. Pero en algunos casos las libertades "
"sobre el uso de datos, la +++P&R+++ de la información y la movilidad de las "
"personas no se llevan bien."
#: content/md/004_backup.js:141
msgid ""
"With +++DF+++s we achieve more independence in file use because once it is "
"save, it could spread. It doesn't matter we have religious or political "
"barriers; the battle take place mainly in technical grounds. But this "
"doesn't made +++DF+++s more autonomous in its +++P&R+++. Neither implies we "
"can archive personal or community freedoms. They are objects. _They are "
"tools_ and whoever use them better, whoever owns them, would have more power."
msgstr ""
"Con los +++AD+++ obtenemos una mayor independencia en el uso de los archivos "
"porque una vez que han sido guardados, pueden propagarse. No importan las "
"barreras políticas o religiosas; la batalla toma lugar principalmente en el "
"campo técnico. Pero esto no le da a los +++AD+++ una mayor autonomía en su ++"
"+P&R+++. Tampoco implica que podamos obtener libertades personales o "
"comunitarias. Los +++AD+++ son objetos. _Los +++AD+++ son herramientas_ y "
"cualquiera que los use mejor, cualquiera que sea su dueño, tendrá más poder."
#: content/md/004_backup.js:148
msgid ""
"With +++PF+++s we can have more +++P&R+++ accessibility. We can do whatever "
"we want with them: extract their data, process it and let it free. But only "
"if we are their owners. Often that is not the case, so +++PF+++s tend to "
"have more restricted access for its use. And, again, this doesn't mean we "
"can be free. There is not any cause and effect between what object made "
"possible and how subjects want to be free. They are tools, they are not "
"master or slaves, just means for whoever use them… but for which ends?"
msgstr ""
"Con los +++AF+++ cabe la oportunidad de que tengamos más libertad para su ++"
"+P&R+++. Podemos hacer cualquier cosa que queramos con ellos: extraer sus "
"datos, procesarlos y liberarlos. Pero solo si somos sus propietarios. En "
"muchos casos no es el caso, así que los +++AF+++ tienden a tener un acceso "
"más restringido para su uso. Y, de nueva cuenta, esto no implica que podamos "
"ser libres. No existe una relación causa y efecto entre lo que un objeto "
"hace posible y la manera en como un sujeto quiere ser libre. Los +++AF+++ "
"son herramientas, no son amos ni esclavos, solo un medio para cualquiera que "
"los use… pero ¿con qué fines?"
#: content/md/004_backup.js:157
msgid ""
"We need +++DF+++s and +++PF+++s as backups and as everyday objects of use. "
"The act of backup is a dynamic category. Backed up files are not inert and "
"they aren't only a substrate waiting to be use. Sometimes we are going to "
"use +++PF+++s because +++DF+++s have been corrupted or its technical "
"infrastructure has been shut down. In other occasions we would use +++DF+++s "
"when +++PF+++s have been destroyed or restricted."
msgstr ""
"Necesitamos los +++AD+++ y a los +++AF+++ como respaldos y como objetos de "
"uso diario. El acto de respaldar es una categoría dinámica. Los archivos "
"respaldados no son inertes ni son sustratos que esperan ser usados. En "
"algunos casos vamos a usar los +++AF+++ porque los +++AD+++ han sido "
"corrompidos o su infraestructura tecnológica ha sido suspendida. En otras "
"ocasiones vamos a usar los +++AD+++ cuando los +++AF+++ han sido destruidos "
"o restringidos."
#: content/md/004_backup.js:164
msgid ""
"![Due restricted access to +++PF+++s, sometimes it is necessary a portable V-"
"shape scanner; this model allows us to handle damaged books while we can "
"also storage it in a backpack.](../../../img/p004_i003.jpg)"
msgstr ""
"![Debido a la restricción en el acceso a los +++AF+++, a veces es necesario "
"un escáner portable en forma de V; este modelo nos permite manejar libros "
"deteriorados así como podemos guardarlo en una mochila.](../../../img/"
"p004_i003.jpg)"
#: content/md/004_backup.js:167
msgid ""
"So the struggle about backups---and all that shit about “freedom” on +++FOSS+"
"++ communities---it is not only around the “incorporeal” realm of "
"information. Nor on the technical means that made digital data possible. "
"Neither in the laws that transform production into property. We have others "
"battle fronts against the monopoly of the cyberspace---or as Lingel [says]"
"(http://culturedigitally.org/2019/03/the-gentrification-of-the-internet/): "
"the gentrification of the internet."
msgstr ""
"Así que la lucha en relación con los respaldos ---y a toda esa mierda acerca "
"de la «libertad» en las comunidades del _software_ libre y del código "
"abierto--- no es solo en torno al reino «incorpóreo» de la información. "
"Tampoco sobre los medios técnicos que posibilitan los datos digitales. Ni "
"mucho menos respecto a las leyes que transforman la producción en propiedad. "
"Tenemos otros frentes de batalla en contra del monopolio del ciberespacio ---"
"o como Lingel [dice](http://culturedigitally.org/2019/03/the-gentrification-"
"of-the-internet/): la gentrificación del internet."
#: content/md/004_backup.js:174
msgid ""
"It is not just about software, hardware, privacy, information or laws. It is "
"about us: how we build communities and how technology constitutes us as "
"subjects. _We need more theory_. But a very diversified one because being on "
"internet it is not the same for an scholar, a publisher, a woman, a kid, a "
"refugee, a non-white, a poor or an old person. This space it is not neutral, "
"homogeneous and two-dimensional. It has wires, it has servers, it has "
"exploited employees, it has buildings, _it has power_ and it has, well, all "
"that things the “real world” has. Not because you use a device to access "
"means that you can always decide if you are online or not: you are always "
"online as an user as a consumer or as data."
msgstr ""
"No es solo acera del _software_, del _hardware_, de la privacidad, de la "
"información o de las leyes. Se trata de nosotros: sobre cómo construimos "
"comunidades y cómo la tecnología nos constituye como sujetos. _Necesitamos "
"más teoría_. Pero una diversificada porque estar en internet no es lo mismo "
"para un académico, un editor, una mujer, un niño, un refugiado, una persona "
"no-blanca, un pobre o una anciana. Este espacio no es neutral ni homogéneo "
"ni bidimensional. Se compone de cables, posee servidores, implica la "
"explotación laboral, se conserva en edificios, _tiene poder_ y, bueno, goza "
"de todas las cosas del «mundo real». Que uses un dispositivo para su acceso "
"no significa que en cualquier momento puedes decidir si estás conectado o "
"no: siempre estás en línea sea como usuario, como consumidor o como dato."
#: content/md/004_backup.js:186
msgid ""
"_Who backup whom?_ As internet is changing us as printed text did, backed up "
"files it isn't the storage of data, but _the memory of our world_. Is it "
"still a good idea to leave the work of +++P&R+++ to a couple of hardware and "
"software companies? Are we now allow to say that the act of backup implies "
"files but something else too? "
msgstr ""
"_¿Quién respalda a quién?_ Así como el internet nos está cambiando tal cual "
"lo hizo la imprenta, lo archivos respaldados no son datos guardados sino _la "
"memoria de nuestro mundo_. ¿Aún es buena idea dejar el trabajo de su +++P&R++"
"+ a un par de compañías de _hardware_ y de _software_? ¿Podemos ya decir que "
"el acto de respaldar implica archivos pero también algo más? "

309
content/po/nb/004_backup.po Normal file
View File

@ -0,0 +1,309 @@
msgid ""
msgstr ""
"Project-Id-Version: 004_backup 1.0\n"
"Report-Msgid-Bugs-To: Nika Zhenya <nika.zhenya@cliteratu.re>\n"
"POT-Creation-Date: 2019-07-04 07:49-0500\n"
"Last-Translator: Automatically generated\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2019-07-04 07:49-0500\n"
"Language-Team: none\n"
"Language: nb\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: content/md/004_backup.js:1
msgid "# Who Backup Whom?"
msgstr ""
#: content/md/004_backup.js:2
msgid "> @published 2019/07/04, 10:00 {.published}"
msgstr ""
#: content/md/004_backup.js:3
msgid ""
"Among publishers and readers is common to heard about “digital copies.” This "
"implies that ebooks tend to be seen as backups of printed books. How the "
"former became a copy of the original---even tough you first need a digital "
"file in order to print---goes something like this:"
msgstr ""
#: content/md/004_backup.js:8
msgid ""
"1. Digital files (+++DF+++s) with appropriate maintenance could\n"
" have higher probabilities to last longer that its material\n"
" peer.\n"
"2. Physical files (+++PF+++s) are limited due geopolitical\n"
" issues, like cultural policies updates, or due random events,\n"
" like environment changes or accidents.\n"
"3. _Therefore_, +++DF+++s are backups of +++PF+++s because _in\n"
" theory_ its dependence is just technical."
msgstr ""
#: content/md/004_backup.js:16
msgid ""
"The famous digital copies arise as a right of private copy. What if one day "
"our printed books get ban or burn? Or maybe some rain or coffee spill could "
"fuck our books collection. Who knows, +++DF+++s seem more reliable."
msgstr ""
#: content/md/004_backup.js:20
msgid ""
"But there are a couple suppositions in this argument. (1) The technology "
"behind +++DF+++s in one way or the other will always make data flow. Maybe "
"this is because (2) one characteristic---part of its “nature”---of "
"information is that nobody can stop its spread. This could also implies that "
"(3) hackers can always destroy any kind of digital rights management system."
msgstr ""
#: content/md/004_backup.js:26
msgid ""
"Certainly some dudes are gonna be able to hack the locks but at a high cost: "
"every time each [cipher](https://en.wikipedia.org/wiki/Cipher) is revealed, "
"another more complex is on the way---_Barlow [dixit](https://www.wired."
"com/1994/03/economy-ideas/)_. We cannot trust that our digital "
"infrastructure would be designed with the idea of free share in mind… Also, "
"how can we probe information wants to be free without relying in its "
"“nature” or making it some kind of autonomous subject?"
msgstr ""
#: content/md/004_backup.js:33
msgid ""
"Besides those issues, the dynamic between copies and originals creates an "
"hierarchical order. Every +++DF+++ is in a secondary position because it is "
"a copy. In a world full of things, materiality is and important feature for "
"commons and goods; for several people +++PF+++s are gonna be preferred "
"because, well, you can grasp them."
msgstr ""
#: content/md/004_backup.js:39
msgid ""
"Ebook market shows that the hierarchy is at least shading. For some readers +"
"++DF+++s are now in the top of the pyramid. We could say so by the follow "
"argument:"
msgstr ""
#: content/md/004_backup.js:42
msgid ""
"1. +++DF+++s are way more flexible and easy to share.\n"
"2. +++PF+++s are very static and not easy to access.\n"
"3. _Therefore_, +++DF+++s are more suitable for use than +++PF+++s."
msgstr ""
#: content/md/004_backup.js:45
msgid ""
"Suddenly, +++PF+++s become hard copies that are gonna store data as it was "
"published. Its information is in disposition to be extracted and processed "
"if need it."
msgstr ""
#: content/md/004_backup.js:48
msgid ""
"Yeah, we also have a couple assumptions here. Again (1) we rely on the "
"stability of our digital infrastructure that it would allow us to have "
"access to +++DF+++s no matter how old they are. (2) Reader's priorities are "
"over files use---if not merely consumption---not on its preservation and "
"reproduction (+++P&R+++). (3) The argument presume that backups are "
"motionless information, where bookshelves are fridges for later-to-use books."
msgstr ""
#: content/md/004_backup.js:55
msgid ""
"The optimism about our digital infrastructure is too damn high. Commonly we "
"see it as a technology that give us access to zillions of files and not as a "
"+++P&R+++ machinery. This could be problematic because some times file "
"formats intended for use aren't the most suitable for +++P&R+++. For "
"example, the use of +++PDF+++s as some kind of ebook. Giving to much "
"importance to reader's priorities could lead us to a situation where the "
"only way to process data is by extracting it again from hard copies. When we "
"do that we also have another headache: fixes on the content have to be add "
"to the last available hard copy edition. But, can you guess where are all "
"the fixes? Probably not. Maybe we should start to think about backups as "
"some sort of _rolling update_."
msgstr ""
#: content/md/004_backup.js:67
msgid ""
"![Programando Libreros while she scans books which +++DF+++s are not "
"suitable for +++P&R+++ or are simply nonexistent; can you see how it is not "
"necessary to have a fucking nice scanner?](../../../img/p004_i001.jpg)"
msgstr ""
#: content/md/004_backup.js:70
msgid ""
"As we imagine---and started to live in---scenarios of highly controlled data "
"transfer, we have to picture a situation where for some reason our electric "
"power is off or running low. In that context all the strengths of +++DF+++s "
"become pointless. They may not be accessible. They may not spread. Right now "
"for us is hard to imagine. Generation after generation the storaged +++DF++"
"+s in +++HDD+++s would be inherit with the hope of being used again. But "
"over time those devices with our cultural heritage would become rare objects "
"without any apparent utility."
msgstr ""
#: content/md/004_backup.js:79
msgid ""
"The aspects of +++DF+++s that made us see the fragility of +++PF+++s would "
"disappear in its concealment. Can we still talk about information if it is "
"potential information---we know the data is there, but it is inaccessible "
"because we don't have the means for view them? Or does information already "
"implies the technical resources for its access---i.e. there is not "
"information without a subject with technical skills to extract, process and "
"use the data?"
msgstr ""
#: content/md/004_backup.js:86
msgid ""
"When we usually talk about information we already suppose is there, but many "
"times is not accessible. So the idea of potential information could be "
"counterintuitive. If the information isn't actual we just consider that it "
"doesn't exist, not that it is on some potential stage."
msgstr ""
#: content/md/004_backup.js:91
msgid ""
"As our technology is developing we assume that we would always have _the "
"possibility_ of better ways to extract or understand data. Thus, that there "
"are bigger chances to get new kinds of information---and take a profit from "
"it. Preservation of data relies between those possibilities, as we usually "
"backup files with the idea that we could need to go back again."
msgstr ""
#: content/md/004_backup.js:97
msgid ""
"Our world become more complex by new things forthcoming to us, most of the "
"times as new characteristics of things we already know. Preservation "
"policies implies an epistemic optimism and not only a desire to keep alive "
"or incorrupt our heritage. We wouldn't backup data if we don't already "
"believe we could need it in a future where we can still use it."
msgstr ""
#: content/md/004_backup.js:103
msgid ""
"With this exercise could be clear a potentially paradox of +++DF+++s. More "
"accessibility tends to require more technical infrastructure. This could "
"imply major technical dependence that subordinate accessibility of "
"information to the disposition of technical means. _Therefore_, we achieve a "
"situation where more accessibility is equal to more technical infrastructure "
"and---as we experience nowadays---dependence."
msgstr ""
#: content/md/004_backup.js:110
msgid ""
"Open access to knowledge involves at least some minimum technical means. "
"Without that, we can't really talk about accessibility of information. "
"Contemporary open access possibilities are restricted to an already "
"technical dependence because we give a lot of attention in the flexibility "
"that +++DF+++s offer us for _its use_. In a world without electric power, "
"this kind of accessibility becomes narrow and an useless effort."
msgstr ""
#: content/md/004_backup.js:117
msgid ""
"![Programando Libreros and Hacklib while they work on a project intended to +"
"++P&R+++ old Latin American SciFi books; sometimes a V-shape scanner is "
"required when books are very fragile.](../../../img/p004_i002.jpg)"
msgstr ""
#: content/md/004_backup.js:120
msgid ""
"So, _who backup whom?_ In our actual world, where geopolitics and technical "
"means restricts flow of data and people at the same time it defends internet "
"access as a human right---some sort of neo-Enlightenment discourse---+++DF++"
"+s are lifesavers in a condition where we don't have more ways to move "
"around or scape---not only from border to border, but also on cyberspace: it "
"is becoming a common place the need to sign up and give your identity in "
"order to use web services. Let's not forget that open access of data can be "
"a course of action to improve as community but also a method to perpetuate "
"social conditions."
msgstr ""
#: content/md/004_backup.js:130
msgid ""
"Not a lot of people are as privilege as us when we talk about access to "
"technical means. Even more concerning, they are hommies with disabilities "
"that made very hard for them to access information albeit they have those "
"means. Isn't it funny that our ideas as file contents can move more “freely” "
"than us---your memes can reach web platform where you are not allow to sign "
"in?"
msgstr ""
#: content/md/004_backup.js:136
msgid ""
"I desire more technological developments for freedom of +++P&R+++ and not "
"just for use as enjoyment---no matter is for intellectual or consumption "
"purposes. I want us to be free. But sometimes use of data, +++P&R+++ of "
"information and people mobility freedoms don't get along."
msgstr ""
#: content/md/004_backup.js:141
msgid ""
"With +++DF+++s we achieve more independence in file use because once it is "
"save, it could spread. It doesn't matter we have religious or political "
"barriers; the battle take place mainly in technical grounds. But this "
"doesn't made +++DF+++s more autonomous in its +++P&R+++. Neither implies we "
"can archive personal or community freedoms. They are objects. _They are "
"tools_ and whoever use them better, whoever owns them, would have more power."
msgstr ""
#: content/md/004_backup.js:148
msgid ""
"With +++PF+++s we can have more +++P&R+++ accessibility. We can do whatever "
"we want with them: extract their data, process it and let it free. But only "
"if we are their owners. Often that is not the case, so +++PF+++s tend to "
"have more restricted access for its use. And, again, this doesn't mean we "
"can be free. There is not any cause and effect between what object made "
"possible and how subjects want to be free. They are tools, they are not "
"master or slaves, just means for whoever use them… but for which ends?"
msgstr ""
#: content/md/004_backup.js:157
msgid ""
"We need +++DF+++s and +++PF+++s as backups and as everyday objects of use. "
"The act of backup is a dynamic category. Backed up files are not inert and "
"they aren't only a substrate waiting to be use. Sometimes we are going to "
"use +++PF+++s because +++DF+++s have been corrupted or its technical "
"infrastructure has been shut down. In other occasions we would use +++DF+++s "
"when +++PF+++s have been destroyed or restricted."
msgstr ""
#: content/md/004_backup.js:164
msgid ""
"![Due restricted access to +++PF+++s, sometimes it is necessary a portable V-"
"shape scanner; this model allows us to handle damaged books while we can "
"also storage it in a backpack.](../../../img/p004_i003.jpg)"
msgstr ""
#: content/md/004_backup.js:167
msgid ""
"So the struggle about backups---and all that shit about “freedom” on +++FOSS+"
"++ communities---it is not only around the “incorporeal” realm of "
"information. Nor on the technical means that made digital data possible. "
"Neither in the laws that transform production into property. We have others "
"battle fronts against the monopoly of the cyberspace---or as Lingel [says]"
"(http://culturedigitally.org/2019/03/the-gentrification-of-the-internet/): "
"the gentrification of the internet."
msgstr ""
#: content/md/004_backup.js:174
msgid ""
"It is not just about software, hardware, privacy, information or laws. It is "
"about us: how we build communities and how technology constitutes us as "
"subjects. _We need more theory_. But a very diversified one because being on "
"internet it is not the same for an scholar, a publisher, a woman, a kid, a "
"refugee, a non-white, a poor or an old person. This space it is not neutral, "
"homogeneous and two-dimensional. It has wires, it has servers, it has "
"exploited employees, it has buildings, _it has power_ and it has, well, all "
"that things the “real world” has. Not because you use a device to access "
"means that you can always decide if you are online or not: you are always "
"online as an user as a consumer or as data."
msgstr ""
#: content/md/004_backup.js:186
msgid ""
"_Who backup whom?_ As internet is changing us as printed text did, backed up "
"files it isn't the storage of data, but _the memory of our world_. Is it "
"still a good idea to leave the work of +++P&R+++ to a couple of hardware and "
"software companies? Are we now allow to say that the act of backup implies "
"files but something else too? "
msgstr ""

306
content/pot/004_backup.pot Normal file
View File

@ -0,0 +1,306 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: 004_backup 1.0\n"
"Report-Msgid-Bugs-To: Nika Zhenya <nika.zhenya@cliteratu.re>\n"
"POT-Creation-Date: 2019-07-04 07:49-0500\n"
"Last-Translator: Nika Zhenya <nika.zhenya@cliteratu.re>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: content/md/004_backup.js:1
msgid "# Who Backup Whom?"
msgstr ""
#: content/md/004_backup.js:2
msgid "> @published 2019/07/04, 10:00 {.published}"
msgstr ""
#: content/md/004_backup.js:3
msgid ""
"Among publishers and readers is common to heard about “digital copies.” This "
"implies that ebooks tend to be seen as backups of printed books. How the "
"former became a copy of the original---even tough you first need a digital "
"file in order to print---goes something like this:"
msgstr ""
#: content/md/004_backup.js:8
msgid ""
"1. Digital files (+++DF+++s) with appropriate maintenance could\n"
" have higher probabilities to last longer that its material\n"
" peer.\n"
"2. Physical files (+++PF+++s) are limited due geopolitical\n"
" issues, like cultural policies updates, or due random events,\n"
" like environment changes or accidents.\n"
"3. _Therefore_, +++DF+++s are backups of +++PF+++s because _in\n"
" theory_ its dependence is just technical."
msgstr ""
#: content/md/004_backup.js:16
msgid ""
"The famous digital copies arise as a right of private copy. What if one day "
"our printed books get ban or burn? Or maybe some rain or coffee spill could "
"fuck our books collection. Who knows, +++DF+++s seem more reliable."
msgstr ""
#: content/md/004_backup.js:20
msgid ""
"But there are a couple suppositions in this argument. (1) The technology "
"behind +++DF+++s in one way or the other will always make data flow. Maybe "
"this is because (2) one characteristic---part of its “nature”---of "
"information is that nobody can stop its spread. This could also implies that "
"(3) hackers can always destroy any kind of digital rights management system."
msgstr ""
#: content/md/004_backup.js:26
msgid ""
"Certainly some dudes are gonna be able to hack the locks but at a high cost: "
"every time each [cipher](https://en.wikipedia.org/wiki/Cipher) is revealed, "
"another more complex is on the way---_Barlow [dixit](https://www.wired."
"com/1994/03/economy-ideas/)_. We cannot trust that our digital "
"infrastructure would be designed with the idea of free share in mind… Also, "
"how can we probe information wants to be free without relying in its "
"“nature” or making it some kind of autonomous subject?"
msgstr ""
#: content/md/004_backup.js:33
msgid ""
"Besides those issues, the dynamic between copies and originals creates an "
"hierarchical order. Every +++DF+++ is in a secondary position because it is "
"a copy. In a world full of things, materiality is and important feature for "
"commons and goods; for several people +++PF+++s are gonna be preferred "
"because, well, you can grasp them."
msgstr ""
#: content/md/004_backup.js:39
msgid ""
"Ebook market shows that the hierarchy is at least shading. For some readers +"
"++DF+++s are now in the top of the pyramid. We could say so by the follow "
"argument:"
msgstr ""
#: content/md/004_backup.js:42
msgid ""
"1. +++DF+++s are way more flexible and easy to share.\n"
"2. +++PF+++s are very static and not easy to access.\n"
"3. _Therefore_, +++DF+++s are more suitable for use than +++PF+++s."
msgstr ""
#: content/md/004_backup.js:45
msgid ""
"Suddenly, +++PF+++s become hard copies that are gonna store data as it was "
"published. Its information is in disposition to be extracted and processed "
"if need it."
msgstr ""
#: content/md/004_backup.js:48
msgid ""
"Yeah, we also have a couple assumptions here. Again (1) we rely on the "
"stability of our digital infrastructure that it would allow us to have "
"access to +++DF+++s no matter how old they are. (2) Reader's priorities are "
"over files use---if not merely consumption---not on its preservation and "
"reproduction (+++P&R+++). (3) The argument presume that backups are "
"motionless information, where bookshelves are fridges for later-to-use books."
msgstr ""
#: content/md/004_backup.js:55
msgid ""
"The optimism about our digital infrastructure is too damn high. Commonly we "
"see it as a technology that give us access to zillions of files and not as a "
"+++P&R+++ machinery. This could be problematic because some times file "
"formats intended for use aren't the most suitable for +++P&R+++. For "
"example, the use of +++PDF+++s as some kind of ebook. Giving to much "
"importance to reader's priorities could lead us to a situation where the "
"only way to process data is by extracting it again from hard copies. When we "
"do that we also have another headache: fixes on the content have to be add "
"to the last available hard copy edition. But, can you guess where are all "
"the fixes? Probably not. Maybe we should start to think about backups as "
"some sort of _rolling update_."
msgstr ""
#: content/md/004_backup.js:67
msgid ""
"![Programando Libreros while she scans books which +++DF+++s are not "
"suitable for +++P&R+++ or are simply nonexistent; can you see how it is not "
"necessary to have a fucking nice scanner?](../../../img/p004_i001.jpg)"
msgstr ""
#: content/md/004_backup.js:70
msgid ""
"As we imagine---and started to live in---scenarios of highly controlled data "
"transfer, we have to picture a situation where for some reason our electric "
"power is off or running low. In that context all the strengths of +++DF+++s "
"become pointless. They may not be accessible. They may not spread. Right now "
"for us is hard to imagine. Generation after generation the storaged +++DF++"
"+s in +++HDD+++s would be inherit with the hope of being used again. But "
"over time those devices with our cultural heritage would become rare objects "
"without any apparent utility."
msgstr ""
#: content/md/004_backup.js:79
msgid ""
"The aspects of +++DF+++s that made us see the fragility of +++PF+++s would "
"disappear in its concealment. Can we still talk about information if it is "
"potential information---we know the data is there, but it is inaccessible "
"because we don't have the means for view them? Or does information already "
"implies the technical resources for its access---i.e. there is not "
"information without a subject with technical skills to extract, process and "
"use the data?"
msgstr ""
#: content/md/004_backup.js:86
msgid ""
"When we usually talk about information we already suppose is there, but many "
"times is not accessible. So the idea of potential information could be "
"counterintuitive. If the information isn't actual we just consider that it "
"doesn't exist, not that it is on some potential stage."
msgstr ""
#: content/md/004_backup.js:91
msgid ""
"As our technology is developing we assume that we would always have _the "
"possibility_ of better ways to extract or understand data. Thus, that there "
"are bigger chances to get new kinds of information---and take a profit from "
"it. Preservation of data relies between those possibilities, as we usually "
"backup files with the idea that we could need to go back again."
msgstr ""
#: content/md/004_backup.js:97
msgid ""
"Our world become more complex by new things forthcoming to us, most of the "
"times as new characteristics of things we already know. Preservation "
"policies implies an epistemic optimism and not only a desire to keep alive "
"or incorrupt our heritage. We wouldn't backup data if we don't already "
"believe we could need it in a future where we can still use it."
msgstr ""
#: content/md/004_backup.js:103
msgid ""
"With this exercise could be clear a potentially paradox of +++DF+++s. More "
"accessibility tends to require more technical infrastructure. This could "
"imply major technical dependence that subordinate accessibility of "
"information to the disposition of technical means. _Therefore_, we achieve a "
"situation where more accessibility is equal to more technical infrastructure "
"and---as we experience nowadays---dependence."
msgstr ""
#: content/md/004_backup.js:110
msgid ""
"Open access to knowledge involves at least some minimum technical means. "
"Without that, we can't really talk about accessibility of information. "
"Contemporary open access possibilities are restricted to an already "
"technical dependence because we give a lot of attention in the flexibility "
"that +++DF+++s offer us for _its use_. In a world without electric power, "
"this kind of accessibility becomes narrow and an useless effort."
msgstr ""
#: content/md/004_backup.js:117
msgid ""
"![Programando Libreros and Hacklib while they work on a project intended to +"
"++P&R+++ old Latin American SciFi books; sometimes a V-shape scanner is "
"required when books are very fragile.](../../../img/p004_i002.jpg)"
msgstr ""
#: content/md/004_backup.js:120
msgid ""
"So, _who backup whom?_ In our actual world, where geopolitics and technical "
"means restricts flow of data and people at the same time it defends internet "
"access as a human right---some sort of neo-Enlightenment discourse---+++DF++"
"+s are lifesavers in a condition where we don't have more ways to move "
"around or scape---not only from border to border, but also on cyberspace: it "
"is becoming a common place the need to sign up and give your identity in "
"order to use web services. Let's not forget that open access of data can be "
"a course of action to improve as community but also a method to perpetuate "
"social conditions."
msgstr ""
#: content/md/004_backup.js:130
msgid ""
"Not a lot of people are as privilege as us when we talk about access to "
"technical means. Even more concerning, they are hommies with disabilities "
"that made very hard for them to access information albeit they have those "
"means. Isn't it funny that our ideas as file contents can move more “freely” "
"than us---your memes can reach web platform where you are not allow to sign "
"in?"
msgstr ""
#: content/md/004_backup.js:136
msgid ""
"I desire more technological developments for freedom of +++P&R+++ and not "
"just for use as enjoyment---no matter is for intellectual or consumption "
"purposes. I want us to be free. But sometimes use of data, +++P&R+++ of "
"information and people mobility freedoms don't get along."
msgstr ""
#: content/md/004_backup.js:141
msgid ""
"With +++DF+++s we achieve more independence in file use because once it is "
"save, it could spread. It doesn't matter we have religious or political "
"barriers; the battle take place mainly in technical grounds. But this "
"doesn't made +++DF+++s more autonomous in its +++P&R+++. Neither implies we "
"can archive personal or community freedoms. They are objects. _They are "
"tools_ and whoever use them better, whoever owns them, would have more power."
msgstr ""
#: content/md/004_backup.js:148
msgid ""
"With +++PF+++s we can have more +++P&R+++ accessibility. We can do whatever "
"we want with them: extract their data, process it and let it free. But only "
"if we are their owners. Often that is not the case, so +++PF+++s tend to "
"have more restricted access for its use. And, again, this doesn't mean we "
"can be free. There is not any cause and effect between what object made "
"possible and how subjects want to be free. They are tools, they are not "
"master or slaves, just means for whoever use them… but for which ends?"
msgstr ""
#: content/md/004_backup.js:157
msgid ""
"We need +++DF+++s and +++PF+++s as backups and as everyday objects of use. "
"The act of backup is a dynamic category. Backed up files are not inert and "
"they aren't only a substrate waiting to be use. Sometimes we are going to "
"use +++PF+++s because +++DF+++s have been corrupted or its technical "
"infrastructure has been shut down. In other occasions we would use +++DF+++s "
"when +++PF+++s have been destroyed or restricted."
msgstr ""
#: content/md/004_backup.js:164
msgid ""
"![Due restricted access to +++PF+++s, sometimes it is necessary a portable V-"
"shape scanner; this model allows us to handle damaged books while we can "
"also storage it in a backpack.](../../../img/p004_i003.jpg)"
msgstr ""
#: content/md/004_backup.js:167
msgid ""
"So the struggle about backups---and all that shit about “freedom” on +++FOSS+"
"++ communities---it is not only around the “incorporeal” realm of "
"information. Nor on the technical means that made digital data possible. "
"Neither in the laws that transform production into property. We have others "
"battle fronts against the monopoly of the cyberspace---or as Lingel [says]"
"(http://culturedigitally.org/2019/03/the-gentrification-of-the-internet/): "
"the gentrification of the internet."
msgstr ""
#: content/md/004_backup.js:174
msgid ""
"It is not just about software, hardware, privacy, information or laws. It is "
"about us: how we build communities and how technology constitutes us as "
"subjects. _We need more theory_. But a very diversified one because being on "
"internet it is not the same for an scholar, a publisher, a woman, a kid, a "
"refugee, a non-white, a poor or an old person. This space it is not neutral, "
"homogeneous and two-dimensional. It has wires, it has servers, it has "
"exploited employees, it has buildings, _it has power_ and it has, well, all "
"that things the “real world” has. Not because you use a device to access "
"means that you can always decide if you are online or not: you are always "
"online as an user as a consumer or as data."
msgstr ""
#: content/md/004_backup.js:186
msgid ""
"_Who backup whom?_ As internet is changing us as printed text did, backed up "
"files it isn't the storage of data, but _the memory of our world_. Is it "
"still a good idea to leave the work of +++P&R+++ to a couple of hardware and "
"software companies? Are we now allow to say that the act of backup implies "
"files but something else too? "
msgstr ""

10
feed/en/rss.xml
View File

@ -7,14 +7,20 @@
<description>Blog about free culture, free software and free publishing.</description>
<language>en</language>
<managingEditor>hi@perrotuerto.blog (Nika Zhenya)</managingEditor>
<lastBuildDate>Mon, 1 Jul 2019 10:34:00 -0500</lastBuildDate>
<lastBuildDate>Thu, 4 Jul 2019 11:04:00 -0500</lastBuildDate>
<image>
<title>Publishing is Coding: Change My Mind</title>
<url>https://perrotuerto.blog/icon.png</url>
<link>https://perrotuerto.blog/content/html/en/</link>
</image>
<item>
<title>3. Don't come with those tales</title>
<title>4. Who Backup Whom?</title>
<link>https://perrotuerto.blog/content/html/en/004_backup.html</link>
<pubDate>Thu, 4 Jul 2019 11:00:00 -0500</pubDate>
<guid isPermaLink="false">guid4</guid>
</item>
<item>
<title>3. Don't Come with Those Tales</title>
<link>https://perrotuerto.blog/content/html/en/003_dont-come.html</link>
<pubDate>Sun, 5 May 2019 20:00:00 -0500</pubDate>
<guid isPermaLink="false">guid3</guid>

8
feed/es/rss.xml
View File

@ -7,12 +7,18 @@
<description>Blog about free culture, free software and free publishing.</description>
<language>es</language>
<managingEditor>hi@perrotuerto.blog (Nika Zhenya)</managingEditor>
<lastBuildDate>Mon, 1 Jul 2019 10:34:00 -0500</lastBuildDate>
<lastBuildDate>Thu, 4 Jul 2019 11:04:00 -0500</lastBuildDate>
<image>
<title>Publishing is Coding: Change My Mind</title>
<url>https://perrotuerto.blog/icon.png</url>
<link>https://perrotuerto.blog/content/html/es/</link>
</image>
<item>
<title>4. ¿Quién respalda a quién?</title>
<link>https://perrotuerto.blog/content/html/es/004_backup.html</link>
<pubDate>Thu, 4 Jul 2019 11:00:00 -0500</pubDate>
<guid isPermaLink="false">guid4</guid>
</item>
<item>
<title>3. No vengas con esos cuentos</title>
<link>https://perrotuerto.blog/content/html/es/003_dont-come.html</link>

2
feed/nb/rss.xml
View File

@ -7,7 +7,7 @@
<description>Blog about free culture, free software and free publishing.</description>
<language>nb</language>
<managingEditor>hi@perrotuerto.blog (Nika Zhenya)</managingEditor>
<lastBuildDate>Mon, 1 Jul 2019 10:34:00 -0500</lastBuildDate>
<lastBuildDate>Thu, 4 Jul 2019 11:04:00 -0500</lastBuildDate>
<image>
<title>Publishing is Coding: Change My Mind</title>
<url>https://perrotuerto.blog/icon.png</url>