<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>LibreOffice &amp;mdash; Webmink In Draft</title>
    <link>https://the.webm.ink/tag:LibreOffice</link>
    <description>Things cooking in the Minkiverse. They move elsewhere when the oven pings.</description>
    <pubDate>Sat, 25 Apr 2026 15:33:49 +0100</pubDate>
    <item>
      <title>Una visión para LibreOffice</title>
      <link>https://the.webm.ink/una-vision-para-libreoffice</link>
      <description>&lt;![CDATA[(English)&#xA;&#xA;Me presento de nuevo a la reelección para la junta de The Document Foundation (TDF) como candidato independiente. Lo más importante que necesita TDF es una visión unificadora para el futuro de #LibreOffice, la principal herramienta de preparación de documentos #OpenSource. He aquí el esbozo de una visión que propondría a los Administradores y a la Junta Directiva en caso de ser elegido, obviamente evolucionada en colaboración con ellos.!--more--&#xA;&#xA;¿Hacia dónde elegimos ir?&#xA;&#xA;TDF existe para servir al público globalmente, no a las necesidades de ninguna corporación. En consecuencia, TDF no debería destinar el dinero donado a ofrecer a ninguna empresa una alternativa a Microsoft Office, ni a ningún proveedor de servicios una alternativa a Google Docs, ni a subvencionar innecesariamente a las empresas que se benefician de cada una de ellas.&#xA;Las actuales herramientas ofimáticas en línea son un servicio para los proveedores de la nube y los usuarios corporativos, pero tienen un valor limitado al servicio de la misión de TDF porque está fuera del alcance de casi cualquier usuario implantarlo por sí mismo. En lugar de animarnos a depender de los proveedores de servicios (incluso de buena fe), TDF debería limitar el compromiso con las versiones de servidor a desplegar una copia de Collabora Online como un peldaño para la evolución de TDF.&#xA;Sin embargo, LibreOffice de Escritorio debe ser capaz de interoperar con él, tanto a través del formato de archivo como en tiempo real.&#xA;&#xA;P2P LibreOffice&#xA;&#xA;Lo que más necesitamos es la colaboración peer-to-peer integrada en LibreOffice Desktop sin necesidad de un proveedor en la nube.&#xA;Lo ideal sería que también fuera interoperable con Collabora Online™, a través de una conexión en tiempo real&#xA;Necesitamos una plataforma neutral para que todas las versiones sean interoperables.&#xA;También deberíamos empezar a mirar más allá del paradigma del &#34;documento&#34;. Incluso los archivos adjuntos al correo electrónico son cada vez más raros; debemos tener en cuenta los sistemas de archivos distribuidos, los sistemas fediverse y otros contenedores de contenido.&#xA;Así que, como mínimo, también necesitamos soporte dentro de LibreOffice para sistemas de archivos distribuidos como IPFS, de modo que no dependamos de un sistema de archivos alojado para la colaboración. &#xA;También tiene que ser accesible sólo con un navegador, tal vez a través de un cliente Javascript ligero. &#xA;TDF debería estar gastando directamente su importante saldo de efectivo donado para hacer de LibreOffice una herramienta accesible y a prueba de futuro para todos los ciudadanos en todos los países y todos los idiomas, no en licitaciones a proveedores corporativos para arreglar errores que se necesitan arreglar pero que se no pueden arreglar económicamente.&#xA;&#xA;Posibles caminos hacia el P2P&#xA;Esto podría lograrse adaptando la capacidad de acceso remoto de Collabora Online e integrándola en el Libreoffice de escritorio. &#xA;Se necesitaría un rediseño para que funcione para los usuarios normales sin intervención técnica, posiblemente utilizando librerías IPv6 como LibreCast. &#xA;Si estuviera disponible una versión accesible desde el navegador (WASM parece posible), también podría ser factible permitir a un usuario sin LibreOffice instalado colaborar peer-to-peer - en respuesta a una invitación individual - con sólo un navegador.&#xA;&#xA;Una vez elegido, propondría esto como punto de partida para el Patronato y trataría de trabajar con los administradores para hacerlo evolucionar hacia una dirección consensuada para la Fundación.&#xA;&#xA;Para discutir este post por favor responda desde Mastodon etc. (busque la URL) e incluya @webmink@meshed.cloud ya que WriteFreely todavía no muestra las respuestas.&#xA;&#xA;----&#xA;&#xA;Many thanks to Miguel Ángel for the translation of the original.&#xA;&#xA;Follow @webmink@the.webm.ink to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include @webmink@meshed.cloud as WriteFreely still doesn&#39;t display replies. a href=&#34;/About&#34;More/a.]]&gt;</description>
      <content:encoded><![CDATA[<p><em>(<a href="https://the.webm.ink/a-vision-for-libreoffice">English</a>)</em></p>

<p>Me <a href="https://community.documentfoundation.org/t/more-nominations-for-the-elections-of-the-tdf-board-of-directors/11772/3?u=webmink">presento</a> de nuevo a la reelección para la junta de The Document Foundation (TDF) como candidato independiente. Lo más importante que necesita TDF es una visión unificadora para el futuro de <a href="https://the.webm.ink/tag:LibreOffice" class="hashtag"><span>#</span><span class="p-category">LibreOffice</span></a>, la principal herramienta de preparación de documentos <a href="https://the.webm.ink/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a>. He aquí el esbozo de una visión que propondría a los Administradores y a la Junta Directiva en caso de ser elegido, obviamente evolucionada en colaboración con ellos.</p>

<h2 id="hacia-dónde-elegimos-ir">¿Hacia dónde elegimos ir?</h2>
<ul><li>TDF existe para servir al público globalmente, no a las necesidades de ninguna corporación. En consecuencia, TDF no debería destinar el dinero donado a ofrecer a ninguna empresa una alternativa a Microsoft Office, ni a ningún proveedor de servicios una alternativa a Google Docs, ni a subvencionar innecesariamente a las empresas que se benefician de cada una de ellas.</li>
<li>Las actuales herramientas ofimáticas en línea son un servicio para los proveedores de la nube y los usuarios corporativos, pero tienen un valor limitado al servicio de la misión de TDF porque está fuera del alcance de casi cualquier usuario implantarlo por sí mismo. En lugar de animarnos a depender de los proveedores de servicios (incluso de buena fe), TDF debería limitar el compromiso con las versiones de servidor a desplegar una copia de Collabora Online como un peldaño para la evolución de TDF.</li>
<li>Sin embargo, LibreOffice de Escritorio debe ser capaz de interoperar con él, tanto a través del formato de archivo como en tiempo real.</li></ul>

<h2 id="p2p-libreoffice">P2P LibreOffice</h2>
<ul><li>Lo que más necesitamos es la colaboración peer-to-peer integrada en LibreOffice Desktop sin necesidad de un proveedor en la nube.</li>
<li>Lo ideal sería que también fuera interoperable con Collabora Online™, a través de una conexión en tiempo real</li>
<li>Necesitamos una plataforma neutral para que todas las versiones sean interoperables.</li>
<li>También deberíamos empezar a mirar más allá del paradigma del “documento”. Incluso los archivos adjuntos al correo electrónico son cada vez más raros; debemos tener en cuenta los sistemas de archivos distribuidos, los sistemas <a href="https://en.wikipedia.org/wiki/Fediverse">fediverse</a> y otros contenedores de contenido.</li>
<li>Así que, como mínimo, también necesitamos soporte dentro de LibreOffice para sistemas de archivos distribuidos como <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a>, de modo que no dependamos de un sistema de archivos alojado para la colaboración.</li>
<li>También tiene que ser accesible sólo con un navegador, tal vez a través de un cliente Javascript ligero.</li>
<li>TDF debería estar gastando directamente su importante saldo de efectivo donado para hacer de LibreOffice una herramienta accesible y a prueba de futuro para todos los ciudadanos en todos los países y todos los idiomas, no en licitaciones a proveedores corporativos para arreglar errores que se necesitan arreglar pero que se no pueden arreglar económicamente.</li></ul>

<h2 id="posibles-caminos-hacia-el-p2p">Posibles caminos hacia el P2P</h2>
<ul><li>Esto podría lograrse adaptando la capacidad de acceso remoto de Collabora Online e integrándola en el Libreoffice de escritorio.</li>
<li>Se necesitaría un rediseño para que funcione para los usuarios normales sin intervención técnica, posiblemente utilizando librerías IPv6 como LibreCast.</li>
<li>Si estuviera disponible una versión accesible desde el navegador (WASM parece posible), también podría ser factible permitir a un usuario sin LibreOffice instalado colaborar peer-to-peer – en respuesta a una invitación individual – con sólo un navegador.</li></ul>

<p>Una vez elegido, propondría esto como punto de partida para el Patronato y trataría de trabajar con los administradores para hacerlo evolucionar hacia una dirección consensuada para la Fundación.</p>

<p><em>Para discutir este post por favor responda desde Mastodon etc. (busque la URL) e incluya <a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a> ya que WriteFreely todavía no muestra las respuestas.</em></p>

<hr>

<p><em>Many thanks to Miguel Ángel for the translation of the <a href="https://the.webm.ink/a-vision-for-libreoffice">original</a>.</em></p>

<p><em>Follow <code><a href="https://the.webm.ink/@/webmink@the.webm.ink" class="u-url mention">@<span>webmink@the.webm.ink</span></a></code> to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include <code><a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a></code> as WriteFreely still doesn&#39;t display replies. <a href="/About">More</a>.</em></p>
]]></content:encoded>
      <guid>https://the.webm.ink/una-vision-para-libreoffice</guid>
      <pubDate>Sun, 17 Dec 2023 23:32:51 +0000</pubDate>
    </item>
    <item>
      <title>A Vision for LibreOffice</title>
      <link>https://the.webm.ink/a-vision-for-libreoffice</link>
      <description>&lt;![CDATA[(Español)&#xA;&#xA;I am standing for re-election to the board of The Document Foundation (TDF) as an independent candidate again. The most important thing TDF needs is a uniting vision for the future of #LibreOffice, the leading #OpenSource document preparation tool. Here is the outline of a vision I would propose to the Trustees and Board if elected, obviously evolved collaboratively with them.!--more--&#xA;&#xA;Where are we choosing to go?&#xA;TDF exists to serve the public globally, not the needs of any corporation. Consequently TDF should not be directing donated money to give any company an alternative to Microsoft Office, nor to give any service provider an alternative to Google Docs, nor to unnecessarily subsidise the companies benefiting from each.&#xA;Today&#39;s online office tools are a service for cloud providers and corporate users, but of limited value in serving the mission of TDF because it is beyond the means of almost any user to deploy it themselves. Rather than encouraging us to become dependent on (even good-faith) service providers, TDF should limit engagement with server versions to deploying a copy of Collabora Online as a stepping-stone for TDF&#39;s evolution.&#xA;LibreOffice Desktop needs to be able to interoperate with it however, both via file format and in real-time.&#xA;&#xA;P2P LibreOffice&#xA;What we most need is peer-to-peer collaboration built in to desktop LibreOffice without the requirement for a cloud provider&#xA;Ideally it should be interoperable with Collabora Online™ too, via real-time connection&#xA;We need this on a platform-neutral basis so every version is interoperable&#xA;We should also start looking beyond the &#34;document&#34; paradigm. Even e-mail attachments are becoming rarer; we need to consider distributed filesystems, fediverse systems and other content containers.&#xA;So as a minimum we also need support within LibreOffice for distributed filesystems such as IPFS so we are not dependent on a hosted filesystem for collaboration.&#xA;It also needs to be accessible just with a browser, maybe via a Javascript slim client.&#xA;TDF should be directly spending its significant donated cash balance to make LibreOffice a future-proof and accessible tool for every citizen in every country and every language, not on tenders to corporate suppliers to fix bugs that they need fixed but can&#39;t fix economically.&#xA;&#xA;Possible paths to P2P&#xA;This could be achieved by adapting the remote access capability from Collabora Online and integrating it into desktop Libreoffice&#xA;It would need redesign to make it work for ordinary users without technical intervention, possibly using IPv6 libraries such as LibreCast.&#xA;If a browser-accessible build were available (WASM seems possible), it might also be feasible to allow a user without LibreOffice installed to collaborate peer-to-peer -- in response to an individual invitation -- with just a browser.&#xA;&#xA;Once elected I would propose this as a starting point for the Board and seek to work with the Trustees to evolve it to a consensus direction for the Foundation.&#xA;&#xA;Follow @webmink@the.webm.ink to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include @webmink@meshed.cloud as WriteFreely still doesn&#39;t display replies. a href=&#34;/About&#34;More/a.]]&gt;</description>
      <content:encoded><![CDATA[<p><em>(<a href="https://the.webm.ink/una-vision-para-libreoffice">Español</a>)</em></p>

<p>I am <a href="https://community.documentfoundation.org/t/more-nominations-for-the-elections-of-the-tdf-board-of-directors/11772/3?u=webmink">standing</a> for re-election to the board of The Document Foundation (TDF) as an independent candidate again. The most important thing TDF needs is a uniting vision for the future of <a href="https://the.webm.ink/tag:LibreOffice" class="hashtag"><span>#</span><span class="p-category">LibreOffice</span></a>, the leading <a href="https://the.webm.ink/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a> document preparation tool. Here is the outline of a vision I would propose to the Trustees and Board if elected, obviously evolved collaboratively with them.</p>

<h2 id="where-are-we-choosing-to-go">Where are we choosing to go?</h2>
<ul><li>TDF exists to serve the public globally, not the needs of any corporation. Consequently TDF should not be directing donated money to give any company an alternative to Microsoft Office, nor to give any service provider an alternative to Google Docs, nor to unnecessarily subsidise the companies benefiting from each.</li>
<li>Today&#39;s online office tools are a service for cloud providers and corporate users, but of limited value in serving the mission of TDF because it is beyond the means of almost any user to deploy it themselves. Rather than encouraging us to become dependent on (even good-faith) service providers, TDF should limit engagement with server versions to deploying a copy of Collabora Online as a stepping-stone for TDF&#39;s evolution.</li>
<li>LibreOffice Desktop needs to be able to interoperate with it however, both via file format and in real-time.</li></ul>

<h2 id="p2p-libreoffice">P2P LibreOffice</h2>
<ul><li>What we most need is peer-to-peer collaboration built in to desktop LibreOffice without the requirement for a cloud provider</li>
<li>Ideally it should be interoperable with Collabora Online™ too, via real-time connection</li>
<li>We need this on a platform-neutral basis so every version is interoperable</li>
<li>We should also start looking beyond the “document” paradigm. Even e-mail attachments are becoming rarer; we need to consider distributed filesystems, <a href="https://en.wikipedia.org/wiki/Fediverse">fediverse</a> systems and other content containers.</li>
<li>So as a minimum we also need support within LibreOffice for distributed filesystems such as <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a> so we are not dependent on a hosted filesystem for collaboration.</li>
<li>It also needs to be accessible just with a browser, maybe via a Javascript slim client.</li>
<li>TDF should be directly spending its significant donated cash balance to make LibreOffice a future-proof and accessible tool for every citizen in every country and every language, not on tenders to corporate suppliers to fix bugs that <em>they</em> need fixed but can&#39;t fix economically.</li></ul>

<h2 id="possible-paths-to-p2p">Possible paths to P2P</h2>
<ul><li>This could be achieved by adapting the remote access capability from Collabora Online and integrating it into desktop Libreoffice</li>
<li>It would need redesign to make it work for ordinary users without technical intervention, possibly using IPv6 libraries such as LibreCast.</li>
<li>If a browser-accessible build were available (WASM seems possible), it might also be feasible to allow a user without LibreOffice installed to collaborate peer-to-peer — in response to an individual invitation — with just a browser.</li></ul>

<p>Once elected I would propose this as a starting point for the Board and seek to work with the Trustees to evolve it to a consensus direction for the Foundation.</p>

<p><em>Follow <code><a href="https://the.webm.ink/@/webmink@the.webm.ink" class="u-url mention">@<span>webmink@the.webm.ink</span></a></code> to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include <code><a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a></code> as WriteFreely still doesn&#39;t display replies. <a href="/About">More</a>.</em></p>
]]></content:encoded>
      <guid>https://the.webm.ink/a-vision-for-libreoffice</guid>
      <pubDate>Wed, 13 Dec 2023 23:36:09 +0000</pubDate>
    </item>
    <item>
      <title>LibreOffice on ChromeOS</title>
      <link>https://the.webm.ink/libreoffice-on-chromeos</link>
      <description>&lt;![CDATA[If you are using an Intel-powered Chromebook, did you know you can install LibreOffice on it, as a local app? It&#39;s extremely easy!&#xA;&#xA;Enable the Linux subsystem and AppImage support&#xA;In the Linux folder, create a folder called Applications&#xA;Download the AppImage build of LibreOffice into the folder&#xA;&#xA;That&#39;s it! ChromeOS will (probably) do the rest. Go to the applications menu (press the search button on the keyboard) and look in the &#34;Linux Applications&#34;   group to launch LibreOffice. It&#39;s as easy as a Mac! !--more--&#xA;&#xA;---&#xA;In more detail:&#xA;&#xA;To enable the Linux subsystem:&#xA;ChromeOS is running on a Linux kernel but uses a container to sandbox locally-installed app. That capability is off by default.&#xA;&#xA;Go to Settings (there are various routes you can take - the easiest is via the Settings icon on the app menu)&#xA;In the left navigation, click Advanced and select Developers&#xA;Enable the Linux Development Environment from this menu&#xA;&#xA;To enable AppImage&#xA;&#xA;AppImage uses the FUSE file system to access, so install FUSE.&#xA;&#xA;To create the Applications folder:&#xA;This is optional - you could just put all your AppImage files into the Linux folder, but I find it easier to separate them out into their own folder. Linux apps can only see the Linux folder and its contents, so you can&#39;t put AppImage files anywhere else. Your documents will also need to live in or below the Linux folder.&#xA;&#xA;Open the Files app&#xA;Under &#34;My Files&#34; in the left navigation, click on &#34;Linux files&#34;&#xA;Create a new folder (for example by pressing Ctrl+E) and name it Applications&#xA;&#xA;To download the AppImage&#xA;&#xA;On the LibreOffice web site, go to https://www.libreoffice.org/download/appimage/&#xA;For most people, the &#34;Fresh, Standard&#34; image is the best choice to download.&#xA;Place the download in your new Applications folder under the Linux folder.&#xA;If you have not previously installed Java you will probably have install a JRE.&#xA;&#xA;ChromeOS should spot the AppImage file, create an icon for the application on the applications menu and connect it to the supported file types. If it does not, sorry - you will have to make the AppImage executable and run it from a command prompt.&#xA;&#xA;I&#39;m working on instructions for the &#34;hard&#34; things in this list, which I had overlooked because my ChromeBook was already set up suitably.&#xA;&#xA;----&#xA;Notes, Tags and Mentions&#xA;&#xA;#Linux #OpenSource #LibreOffice #Desktop #OpenOffice #FOSS #FLOSS&#xA;@libreoffice@fosstodon.org&#xA;It&#39;s possible that my instructions miss a step or are affected by other AppImage tools I have installed. If so, please let me know and I&#39;ll fix it!&#xA;I have a number of other desktop apps installed via this route, and then use AppImage Updater to keep them current (as long as the metadata in the package is correct).&#xA;&#xA;Follow @webmink@the.webm.ink to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include @webmink@meshed.cloud as WriteFreely still doesn&#39;t display replies. a href=&#34;/About&#34;More/a.]]&gt;</description>
      <content:encoded><![CDATA[<p>If you are using an Intel-powered Chromebook, did you know you can install LibreOffice on it, as a local app? It&#39;s extremely easy!</p>
<ol><li>Enable the Linux subsystem and AppImage support</li>
<li>In the Linux folder, create a folder called Applications</li>
<li>Download the AppImage build of LibreOffice into the folder</li></ol>

<p>That&#39;s it! ChromeOS will (probably) do the rest. Go to the applications menu (press the search button on the keyboard) and look in the “Linux Applications”   group to launch LibreOffice. It&#39;s as easy as a Mac! </p>

<hr>

<p><em>In more detail:</em></p>

<h2 id="to-enable-the-linux-subsystem">To enable the Linux subsystem:</h2>

<p>ChromeOS is running on a Linux kernel but uses a container to sandbox locally-installed app. That capability is off by default.</p>
<ol><li>Go to Settings (there are various routes you can take – the easiest is via the Settings icon on the app menu)</li>
<li>In the left navigation, click Advanced and select Developers</li>
<li>Enable the Linux Development Environment from this menu</li></ol>

<h2 id="to-enable-appimage">To enable AppImage</h2>
<ol><li>AppImage uses the FUSE file system to access, so install FUSE.</li></ol>

<h2 id="to-create-the-applications-folder">To create the Applications folder:</h2>

<p>This is optional – you could just put all your AppImage files into the Linux folder, but I find it easier to separate them out into their own folder. Linux apps can only see the Linux folder and its contents, so you can&#39;t put AppImage files anywhere else. Your documents will also need to live in or below the Linux folder.</p>
<ol><li>Open the Files app</li>
<li>Under “My Files” in the left navigation, click on “Linux files”</li>
<li>Create a new folder (for example by pressing Ctrl+E) and name it Applications</li></ol>

<h2 id="to-download-the-appimage">To download the AppImage</h2>
<ol><li>On the LibreOffice web site, go to <a href="https://www.libreoffice.org/download/appimage/">https://www.libreoffice.org/download/appimage/</a></li>
<li>For most people, <a href="https://appimages.libreitalia.org/LibreOffice-fresh.standard-x86_64.AppImage">the “Fresh, Standard” image</a> is the best choice to download.</li>
<li>Place the download in your new Applications folder under the Linux folder.</li>
<li>If you have not previously installed Java you will probably have install a JRE.</li></ol>

<p>ChromeOS should spot the AppImage file, create an icon for the application on the applications menu and connect it to the supported file types. If it does not, sorry – you will have to make the AppImage executable and run it from a command prompt.</p>

<p>I&#39;m working on instructions for the “hard” things in this list, which I had overlooked because my ChromeBook was already set up suitably.</p>

<hr>

<h3 id="notes-tags-and-mentions">Notes, Tags and Mentions</h3>
<ul><li><a href="https://the.webm.ink/tag:Linux" class="hashtag"><span>#</span><span class="p-category">Linux</span></a> <a href="https://the.webm.ink/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a> <a href="https://the.webm.ink/tag:LibreOffice" class="hashtag"><span>#</span><span class="p-category">LibreOffice</span></a> <a href="https://the.webm.ink/tag:Desktop" class="hashtag"><span>#</span><span class="p-category">Desktop</span></a> <a href="https://the.webm.ink/tag:OpenOffice" class="hashtag"><span>#</span><span class="p-category">OpenOffice</span></a> <a href="https://the.webm.ink/tag:FOSS" class="hashtag"><span>#</span><span class="p-category">FOSS</span></a> <a href="https://the.webm.ink/tag:FLOSS" class="hashtag"><span>#</span><span class="p-category">FLOSS</span></a></li>
<li><a href="https://the.webm.ink/@/libreoffice@fosstodon.org" class="u-url mention">@<span>libreoffice@fosstodon.org</span></a></li>
<li>It&#39;s possible that my instructions miss a step or are affected by other AppImage tools I have installed. If so, please let me know and I&#39;ll fix it!</li>
<li>I have a number of other desktop apps installed via this route, and then use <a href="https://appimage.github.io/AppImageUpdate/">AppImage Updater</a> to keep them current (as long as the metadata in the package is correct).</li></ul>

<p><em>Follow <code><a href="https://the.webm.ink/@/webmink@the.webm.ink" class="u-url mention">@<span>webmink@the.webm.ink</span></a></code> to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include <code><a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a></code> as WriteFreely still doesn&#39;t display replies. <a href="/About">More</a>.</em></p>
]]></content:encoded>
      <guid>https://the.webm.ink/libreoffice-on-chromeos</guid>
      <pubDate>Mon, 21 Aug 2023 13:05:25 +0100</pubDate>
    </item>
  </channel>
</rss>