Hace unos días que o spresenté las charlas de Akademy-es 2025 es el momento de comentar que también ha sido publicado el programa de Opensouthcode 2025, un evento multisala lleno de grandes ponencias que se convertirá en un problema si queremos aprovechar al máximo este evento.

Publicado el programa de Opensouthcode 2025

El próximo 20 y 21 junio , en la activa ciudad de Málaga, se celebra la Opensouthcode 2025 un evento para promocionar y dar a conocer las tecnologías abiertas: software/hardware libre y opensource.

El evento se celebra en La Térmica (Avda. Los Guindos, ) y su programa puede tener muchos adjetivos menos el de discreto ya que nos esperan 6 salas con unas 10 charlas o talleres en cada una, desde las 10 de la mañana hasta las 20 horas, y eso solo para el viernes ya que el sábado tendremos otra jornada igual de intensa.

Es imposible comentar en esta entrada todas las charlas que nos esperan pero por dar una pincelada yo destaco charlas como:

• Desarrollar videojuegos en .NET nunca fue tan… ¿fácil? por Ricardo Guzmán Velasco
• Java 30: Meetup especial de MálagaJUG para celebrar el 30 aniversario de Java por Jorge Hidalgo
• Crea tus apps, con Flutter (Una introducción al framework y los primeros pasos para aprender) por Elena G Blanco
• Robótica e Inteligencia Artificial con HuskyLens y micro:bit por Manuel Valencia
• Tech for kids – Despertando la curiosidad de mis hijos por la tecnología por Raúl Jiménez Ortega
• Model Context Protocol: el nuevo chico guapo del barrio de la IA y la relevancia de los protocolos abiertos por Estefanía Ríos y Patri
• Taller de creación del videojuego oficial del OpenSouthCode por Victor Suarez
• Astro, un soplo de aire fresco por Braulio

Y eso sin contar, que en la sala Benamocarra tendrás toda la programación de Akademy-es.

Más información: Opensouthcode 2025 de Málaga

La entrada Publicado el programa de Opensouthcode 2025 se publicó primero en KDE Blog.

Table of Contents

• 1) Overview
• 2) Introduction to SELinux
  • SELinux booleans
• 3) The problem with emulating Windows games
• 4) Finding an elegant solution
  • Implementation
• 5) Closing Remarks
• 6) References

1) Overview

OpenSUSE Tumbleweed recently switched to using SELinux by default. While generally well received, this change caused problems in particular when playing Windows games through Proton or Wine. This post will provide context and introduce the solution the openSUSE SELinux team came up with.

Section 2 gives an overview of SELinux and introduces the primitives necessary to understand the issue and solution. Section 3 takes a closer look at the root cause of the problem and the manual steps needed to work around the issue in the past. Section 4 discusses the requirements for a better solution and how it was implemented in the end. Section 5 closes with information on how to report SELinux bugs and how to reach the openSUSE SELinux team.

2) Introduction to SELinux

OpenSUSE Tumbleweed switched to SELinux as the default Mandatory Access Control mechanism for new installations in February 2025.

The central reason for the change was that we consider SELinux the more encompassing solution: security problems with a program do not pose a threat to the whole system, rather a system compromise can be confined to the affected program or daemon.

SELinux provides a powerful and detailed language to describe expected application behaviour. Allowing to confine a process, referred to as a SELinux domain, by limiting access to required system resources and describing the interaction with other domains. A large catalog of domains is already available via the upstream SELinux policy.

SELinux booleans

Common behaviour of a piece of software might be allowed by default for the domain, but very specific scenarios might be prohibited, especially when negatively impacting security. SELinux booleans provide a way for the user to enable such optional functionality in the SELinux policy.

To give an example: the Apache HTTP daemon is used to serve web pages. In certain situations it might be needed that these webpages are stored in the user’s home directory, but as a default it is not advisable that a network facing daemon has access to the home directories. To address these different usage scenarios a boolean called httpd_enable_homedirs exists. The user can turn on the boolean if the HTTP daemon needs to access the home directories of users to serve web pages.

3) The problem with emulating Windows games

Playing Windows games on Linux with SELinux enabled did not work without manual intervention by the user. This is related to the way Windows libraries have been developed and are used by emulation software. To allow the software for emulating Windows games to work, for example Steam with Proton or Lutris with Wine, a boolean called selinuxuser_execmod needs to be enabled:

sudo setsebool -P selinuxuser_execmod 1

But enabling this boolean has consequences for the general security of the system. The user_selinux manpage states for selinuxuser_execmod:

If you want to allow all unconfined executables to use libraries requiring text relocation that are not labeled textrel_shlib_t, you must turn on the selinuxuser_execmod boolean.

But why exactly is the boolean problematic and required a manual change before? Executable stack is used by hackers as a building block in their exploitation techniques. A lot of research went into finding mitigation strategies to make it harder for malicious actors to run successful exploits. One central measure was Executable-space protection, and Text relocation touches a part of that mitigation. If the boolean is enabled it allows modification of the executable code portions of the affected libraries, and could result in successful exploitation of the processes using these libraries.

4) Finding an elegant solution

OpenSUSE Tumbleweed is a general-purpose Linux distribution, targeting a multitude of use cases, be it as a server, running on embedded devices, as container host or as a desktop system. Some Tumbleweed users require their desktop system to run emulations software for Windows games.

In general we try to take a Secure by Default approach when we take decisions affecting security. For openSUSE Tumbleweed we decided to disable selinuxuser_execmod by default, because we think it provides a risk to the security of the system if all unconfined executables can use libraries with text relocation.

In software security we usually want to make it as hard as possible for malicious actors to exploit a target. Accomplishing this feat is not easy, because some attack scenarios rely on normal system behavior that can be used or exploited by attackers. An approach to mitigate this in defensive software security is a concept known as Defense in Depth, where different protective mechanisms are used to provide a layered defense, making a successful exploit as hard as possible.

A central requirement for a solution was not to cause a negative impact on the security of other use cases, which do not require emulation of Windows games. Enabling selinuxuser_execmod by default for all Tumbleweed installations was no option. It would take away a protection mechanism and therefor weaken the Defense in Depth approach.
Manually setting the boolean was needed to get the emulation layer for Windows to function properly. To arrive at that solution the user needed a certain level of familiarity with the administration of SELinux. A transparent, but selective solution, that would need no intervention from the user would be ideal to implement.

Implementation

We decided to introduce a new dependency to packaged gaming software in openSUSE Tumbleweed. If a user installs the RPM version of Lutris or Steam, then the RPM selinux-policy-targeted-gaming will now be installed as well, enabling the boolean on the user system automatically. This solution improves usability for the users who install gaming software and does not compromise the security of other use cases of the distribution.

A user preferring the Flatpak versions of Steam or Lutris can manually install the new package:

sudo zypper in selinux-policy-targeted-gaming

As we do not control the Flatpak applications, we can not add any dependencies to them. As an alternative the user can also still set the boolean manually.

5) Closing Remarks

The openSUSE SELinux team is committed to keeping openSUSE users safe with SELinux, and to fixing problems that SELinux may cause to the community. To facilitate changes with SELinux we rely on users to work with us and provide feedback, so that we understand what the current problematic areas are. If you encounter problems with SELinux feel free to open a bug or reach out over the mailing list.

6) References

• Tumbleweed Adopts SELinux as Default
• openSUSE Bugreport SELinux
• openSUSE SELinux Mailing List

La Comunidad KDE es una comunidad responsable y no solo se preocupa en lanzar novedades sino que también en mejorarlas. Me complace presentar la segunda actualización de KDE Gear 25.04 que apareció hace casi dos meses. Más estabilidad, mejores traducciones y pequeñas mejoras para las aplicaciones de nuestro entornos de trabajo.

Segunda actualización de KDE Gear 25.04

A pesar de lo que puedan pensar muchas personas, las aplicaciones no son perfectas. Entre las líneas de código se pueden colar errores de tipografía o que el usuario realice alguna opción que en un principio no estaba prevista por los desarrollador, por poner solo un par de ejemplos de imperfecciones.

Este no es un problema del Software Libre ya que el Software actual funciona de esta manera ya que no se piensa en él como un producto final que se encierra en una caja y se olvida. En la actualidad se sabe que el Software está vivo y sería estúpido ir guardando las mejoras sin dejarlas a disposición del gran público.

Con esto se gana en rapidez y evolución pero puede aumentar el número de errores (por norma general) leves, los cuales son subsanables con pequeñas actualizaciones.

La Comunidad KDE lo tiene claro: grandes lanzamientos cada cuatro meses y actualizaciones mensuales para subsanar errores.

Por ello me congratula compartir con vosotros la segunda actualización de KDE ⚙️ Gear 25.04 que nos ofrece más de 180 errores resueltos entre aplicaciones, librerías y widgets, algo que mejora el rendimiento del sistema.

Aquí podéis encontrar la lista completa de cambios de KDE Gear 25.04.2, pero por poner unos cuantos ejemplos de los errores que sea han resuelto tenemos:

• kdenlive: Corregidos los efectos de clip de papelera que desaparecen tras desactivar un clip de la línea de tiempo (Confirmado, corrige error nº 439194)
• knights: Al guardar la partida, usar la extensión adecuada «pgn» en caso de que no se proporcionara ninguna extensión (Commit, corrige bug #502963)
• kreversi: Corregir la disponibilidad inconsistente de deshacer tras finalizar la partida (Commit, corrige bug #351812)

Más información: KDE Gear 25.04.02

La entrada Segunda actualización de KDE ⚙️ Gear 25.04 se publicó primero en KDE Blog.

In recent months, I observed an increase in performance issues with partial short outages, particularly of web applications performing expensive operations such as database or shell queries. The origin was always easy to map to an amount of requests larger than what some backend applications are able to handle. Whilst part of the requests do originate from legitimate users, a large amount is found to originate from obscure sources - particularly AI related crawlers seem to dominate. Whereas traditional search engine crawlers, which we do encourage to scan our websites to allow for more users to find them, scan with few requests spread over a long time frame, these new crawlers tend to issue thousands of requests, sometimes in less than a day. With multiple companies pursuing the same practices, this quickly adds up to requests and subsequently load which is not sensible to scale for, particularly given the lack of obvious benefit for the general public.
Over time I implemented various measures to reduce the amount of undesired requests based on the observed patterns, whilst aiming to maintain a stable experience for legitimate requests. These measures include rate limiting (with more fine grained limits for particularly "expensive" sites and paths), wide blocking of source networks from cloud providers and AI related companies, blocking of user agent patterns and blocking of "dumb" requests (for example, we stopped routing requests targeting various script file types to backends which do not speak the matching language). Monitoring did show these measures to help with reducing the immediate request load, however new patterns quickly emerged. A new phenomena are large amounts of requests spread over a large amount of different source networks. Especially with source networks identifying as serving residential traffic, blocking is not possible without risking the lockout of legitimate users. A new method needed to be found.

Of course, we are not the only organization affected by this. The recent influx of AI related crawlers impacting web services caused various operators to implement additional protections, and the most visible one to users are challenge websites, making the user land on an intermediate page before being redirected to the desired location. Whilst these come in various forms, I mostly observe ones asking for a captcha and ones computing a proof-of-work task in the client. The latter came particular popular with the release of Anubis [0], an open source software making it easy for operators to equip their website with a proof-of-work challenge protection. Anubis reached a certain level of fame by big websites deploying it and tech related news outlets talking about it. Most naturally, I looked into Anubis as a solution for our situation as well. The proof-of-work concept was particularly interesting, as automated challenges are less annoying to users and have less accessibility concerns than manual captcha based ones.

As for Anbuis, it acts as a reverse proxy and serves a pre-defined challenge website. It also ships with excludes for known-good search engine crawlers.
In our setup, which consists of internet-facing HAProxy servers routing traffic to backend application/web servers, this would introduce another proxy traffic would flow through. Upon discussion with @darix, we figured it would be beneficial to instead utilize SPOE, the HAProxy Stream Process Ofloading Engine, to "ask" Anubis to challenge problematic clients, but then to pass the result back to HAProxy to directly route the traffic as before. Following the upstream discussion we initiated, I prepared a patch for this [1] - as I was idling for a while before opening a PR, someone else picked up the work and improved upon it, bringing the implementation to a usable shape [2] - however, it has not yet been completed and merged by the time of writing. More importantly, also as part of the upstream discussion, a user suggested to swap out the Go library I used for the SPOP implementation in Anubis with a more performant one [3] - haproxy-go [4]. The same comment [3] lead me to discover the same user having developed a software similar to Anubis, which already implements the suggested library and specifically targets HAProxy native deployments: Berghain [5]. Whilst the user experience is similar to Anubis - one gets served a challenge website to complete an automated proof-of-work computation before being redirected to the desired location, the background implementation is different. It operates tightly integrated with HAProxy by utilizing the SPOE - first to construct a challenge for clients (that is, if a client is intended to be challenged, which is decided using standard HAProxy ACLs), then to verify the challenge response, which is stored in a cookie on the client. The challenge page (which is a combination of HTML, CSS, JS) itself is served directly by HAProxy from memory.

This seemed like what we were looking for:

• no additional reverse proxy, preservance of existing HAProxy based routing
• decision which clients to challenge using HAProxy ACLs, which we already use in our setup and can easily extend upon
• can be configured to not impact web service availability if the challenge service is offline
• easy branding using HTML + SCSS (Anubis in its default build does not allow for any branding - however they seem to have a version for paying customers and open source projects which allows to swap the imagery)

The project seemed to be in an early stage, with not much activity as compared to Anubis, however initial testing seemed promising. After opening an issue with a minor flaw, the upstream maintainer messaged me - as it turns out, they have similar ideas and are very nice to chat with. Over the last days, various improvements landed in Berghain - I contributed some patches [6], which were pleasantly reviewed and integrated, and the upstream maintainer helped as well, with answering questions in chat and solving bugs [7].

For branding, I made a fork [8] in which the sources of the web page are modified. An upstream discussion to decouple this, allowing theming to reside separately, was started [9], but ideas on achieving this are still pending. As the web sources are deemed to not change as often, the maintenance effort should not be too bad for the time being - I rebase our branch with the upstream one when there are changes, and add the customizations as a patch in our package [10].

With this, all seems to be set for deployment. However, there were some challenges (pun intended) which had to be considered:

• users should not be unnecessarily "annoyed"
  => cover websites and paths only selectively when there is need for additional protection due to excess application load
• the challenge requires JavaScript, don't unnecessarily harm users which do not have JavaScript enabled, and, most importantly, don't break legitimate command line tooling and scripts
  => cover only websites and paths which would require JavaScript anyways (i.e. no API paths)
• if the configured validity period expires while the user is filling out a form, accidental form resubmission might be triggered
  => cover only GET requests
• legitimate search engine crawlers should not be inhibited
  => adapt lists of user agent + source network combinations from Anubis

These points were easily solved using HAProxy ACLs. Of course, the exemptions also leave more room for malicious actors to work around the protection. Whilst this is a concern, most bots are found to be "dumb", hence the enablement can be expected to significantly help with the current situation even with the constraints at hand. Over time, solutions allowing for tighter limitations might be investigated and developed. Particularly interesting was a discussion with the maintainer of Berghain which brought up some ideas to challenge clients without JavaScript, however there is no concrete plan for this yet.

With all that being said, the protection has now been deployed and enabled for two services [11] - including progress.opensuse.org, where you are reading this article right now. Enablement for more services will follow over time as needed, when needed.

With all the considerations which went into this implementation, I hope for the impact on legitimate users to be minimal. If you notice any undesired breakage as a result of this nonetheless, please do open an issue in our tracker [12] explaining the circumstances, and I will try to work out a solution.

[0] https://anubis.techaro.lol
[1] https://github.com/TecharoHQ/anubis/issues/236#issuecomment-2784919382
[2] https://github.com/TecharoHQ/anubis/pull/460
[3] https://github.com/TecharoHQ/anubis/issues/236#issuecomment-2801861198
[4] https://github.com/DropMorePackets/haproxy-go
[5] https://github.com/DropMorePackets/berghain
[6] https://github.com/DropMorePackets/berghain/issues?q=author%3Atacerus
[7] https://github.com/DropMorePackets/berghain/commit/6080b227008a759c267a973202cf2b4edff38e31, https://github.com/DropMorePackets/haproxy-go/commit/c1707895ddabaa9c11d4e0b99e2cba040a0a3330
[8] https://github.com/openSUSE/berghain
[9] https://github.com/DropMorePackets/berghain/issues/26
[10] https://build.opensuse.org/package/show/openSUSE:infrastructure/berghain
[11] https://progress.opensuse.org/projects/opensuse-admin/repository/salt/revisions/3257c222f1c92c96c1d3caaeb7c14604fefad54a
[12] https://progress.opensuse.org/projects/opensuse-admin/issues (in case of issues with using the tracker directly, create a ticket via admin@o.o)

Edit after 1 day:

it was suggested to attach some graphs showing how the load went down after this deployment - here are the graphs behind progress.o.o as an example (times in the graphs are in CEST):

Recopilación y traducción del boletín mensual de noticias relacionadas con el software libre publicado por la Free Software Foundation.

La Free Software Foundation (FSF) es una organización creada en Octubre de 1985 por Richard Stallman y otros entusiastas del software libre con el propósito de difundir esta filosofía, frente a las restricciones y abusos a los usuarios por parte del software privativo.

La Fundación para el software libre (FSF) se dedica a eliminar las restricciones sobre la copia, redistribución, entendimiento, y modificación de programas de computadoras. Con este objeto, promociona el desarrollo y uso del software libre en todas las áreas de la computación, pero muy particularmente, ayudando a desarrollar el sistema operativo GNU.

Mensualmente publican un boletín (supporter) con noticias relacionadas con el software libre, sus campañas, o eventos. Una forma de difundir los proyectos, para que la gente conozca los hechos, se haga su propia opinión, y tomen partido si creen que la reivindicación es justa!!

• En este enlace podéis leer el original en inglés: https://www.fsf.org/free-software-supporter/2025/june
• Y traducido en español (cuando el equipo de traducción lo tengamos disponible) en este enlace: https://www.fsf.org/free-software-supporter/2025/junio

Puedes ver todos los números publicados en este enlace: http://www.fsf.org/free-software-supporter/free-software-supporter

¿Te gustaría aportar tu ayuda en la traducción y colaborar con la FSF? Lee el siguiente enlace:

• https://victorhckinthefreeworld.com/2016/12/22/quieres-ayudar-a-traducir-el-boletin-mensual-de-la-free-software-foundation/

Por aquí te traigo un extracto de algunas de las noticias que ha destacado la FSF este mes de junio de 2025.

No más licencias impuestas: ¡recupere el costo de su licencia de Windows!

Del 29 de mayo por la Free Software foundation

La mayoría de las computadoras portátiles que se venden en este momento vienen con un sistema operativo Microsoft Windows preinstalado que lo controla, y no es fácil para que los usuarios opten por no participar. Esto no solo es una violación de la libertad del usuario, sino que también le cuesta económicamente al usuario que se queda atascado pagando por una licencia de Windows que no desea.

La nueva iniciativa Refund4Freedom tiene como objetivo ayudar a los usuarios a recuperar el costo de una licencia de Windows al comprar un nuevo dispositivo y presionar para que se ponga fin a esta práctica que limita la libertad. Siga leyendo para saber qué puede hacer la próxima vez que usted o alguien que conozca compre una computadora nueva.

• https://fsfe.org/news/2025/news-20250529-01.en.html
  

Por qué los fabricantes de consolas pueden bloquear legalmente su consola de juegos

Del 22 de mayo por Kyle Orland

Nintendo es uno de los mayores perpetradores de bloqueos de consolas (hacer que una consola quede permanentemente inutilizable en su totalidad o en parte), y actualmente tienen la capacidad legal para hacerlo (y Sony y Microsoft no son mucho mejores). Cuando un propietario bloquea su dispositivo y/o el software que lo hace funcionar, está intentando controlarlo y limitar sus derechos de usuario.

Los usuarios como usted deberían tener derecho a hacer lo que deseen con su dispositivo personal, incluso modificarlo para que funcione para usted. Dígale a sus representantes estatales y nacionales que debería tener el poder legal para modificar su dispositivo sin ser castigado por su fabricante.

• https://arstechnica.com/gaming/2025/05/why-console-makers-can-legally-brick-your-game-console/

«End of 10» para los usuarios de Windows 10: El entorno quiere que uses GNU/Linux

Del 15 de mayo por Christine Hall

Instalar un sistema operativo libre en un dispositivo que no es libre es un paso muy importante hacia la libertad, pero rara vez permite al usuario ejercer su libertad al máximo. Si alguien trae un dispositivo que no fue desarrollado pensando en la libertad e intenta instalar un sistema operativo libre, a menudo habrá al menos un par de cosas que no funcionarán correctamente.

Esto se debe a que la mayoría de los dispositivos contienen componentes que no funcionarán a menos que el sistema operativo instalado contenga algunos controladores o firmware que no son libres.

Aunque hay formas de sortear estas limitaciones, como el uso de un adaptador USB para el componente que no funciona, es algo que hay que planificar al hacer el cambio de un sistema operativo no libre a uno gratuito.

Si planea participar en un festival de instalación en su área, haga todo lo posible por mantenerse informado y compartir su conocimiento con otros sobre las opciones y limitaciones que conlleva instalar un sistema operativo libre en un dispositivo que no es libre.

• https://endof10.org/es/
• https://www.gnu.org/philosophy/install-fest-devil

Estas son solo algunas de las noticias recogidas este mes, ¡¡pero hay muchas más muy interesantes!! si quieres leerlas todas (cuando estén traducidas) visita este enlace:

• https://www.fsf.org/free-software-supporter/2025/junio

Y todos los números del «supporter» o boletín de noticias de 2025 en español, francés, portugués e inglés aquí:

• https://www.fsf.org/free-software-supporter/2025

Me congratula presentaros el episodio 46 de KDE Express, titulado » Noticias y calor pre Akademy-es Málaga» donde David Marzal sigue llevando en solitario estas más que interesantes píldoras. Un hurra por él.

Episodio 46 de KDE Express: Noticias y calor pre Akademy-es Málaga

Comenté hace ya bastante tiempo que había nacido KDE Express, un audio con noticias y la actualidad de la Comunidad KDE y del Software Libre con un formato breve (menos de 30 minutos) que complementan los que ya generaba la Comunidad de KDE España, aunque ahora estamos tomándonos un tiempo de respiro por diversos motivos, con sus ya veteranos Vídeo-Podcast que todavía podéis encontrar en Archive.org, Youtube, Ivoox, Spotify y Apple Podcast.

De esta forma, a lo largo de estos 45 episodios, promovidos principalmente por David Marzal, nos han contado un poco de todo: noticias, proyectos, eventos, etc., convirtiéndose (al menos para mi) uno de los podcast favoritos que me suelo encontrar en mi reproductor audio.

En palabras de David el nuevo episodio de KDE Express,esta vez con noticias cortas pero jugosas

Episodio 46 recopilatorio de las noticias de estas semanas.

Artículo original en https://kdeexpress.gitlab.io/46/

• Plasma 6.4 deja de incorporar novedades y se centra en pulirse para un lanzamiento estable
  • El plasmoide de volumen mostrará la app y el audio que está sonando.
  • El icono de Lector de Pantalla en la configuración de accesibilidad ha cambiado a uno más representativo.
  • Asistente de calibración HDR y posibilidad de simular HDR en pantallas que lo soporten
  • Fondos de escritorios dinámicos según la hora del día
  • Discover ya no muestra por defecto los fondos de escritorios y las extensiones al buscar a no ser que busques desde el aparatado de add-on
• Plasma 6.5
  • Mejorada la accesibilidad de la navegación con teclado del widget de volumen, la página de Flatpat en la configuración del sistema y en Discover.
• KDE frameworks 6.15:
  • Los diálogos de nuevo fichero o carpeta han sido retocados estéticamente. Y el de carpeta ahora te deja elegir un icono directamente.
  • Transferir ficheros ahora se asegura de inhibir la suspensión del equipo para evitar problemas en la copia.
  • Se muestran mejor los thumbnails/miniaturas en unidades de red.
  • Mejorada la accesibilidad de la navegación con teclado en la configuración del sistema.
• Distros
  • FreeBSD 14.3 Beta 3 incorpora los paquetes de Plasma 6 a sus imágenes de DVD
  • Rhino, una Rolling Release basada en Ubunutu que usa XFCE por defecto, empieza a probar una sesión con Plasma
  • La SteamOS que es el sistema operativo que viene con la SteamDeck, comparado en otros dispositivos que iban con Windows, parece que los supera con creces.
    • Y GefoceNOW, la plataforma de juego en streaming de NVIDIA ya está dispnible en la Deck instalandolo a traves de la sesión de escritorio Plasma.
• Techpaladin es un nuevo patron de KDE e.V
• Qt empieza a dar soporte a otros lenguajes de programación como Rust, Kotlin/Java y Swift
• Firefox 136 trajo las pestañas verticales, 137 la agrupación de pestañas y 138 el selector de profiles. Ahora llega Firefox 139 con fondos de pantalla configurables.
  • Recomiendo el podcast de 24H24L con una interesante reflexión sobre apoyar a Firefox Mozilla a pesar de su imperfección.

Y, como siempre, os dejo aquí el listado de los episodios. ¡Disfrutad!

Por cierto, también podéis encontrarlos en Telegram: https://t.me/KDEexpress

La entrada Episodio 46 de KDE Express: Noticias y calor pre Akademy-es Málaga se publicó primero en KDE Blog.

Otro script en Bash para escuchar la emisora que queramos de Somafm desde la terminal de nuestro sistema GNU/Linux

Este script en Bash utiliza curl, jq, fzf y mpv para mostrar, buscar y reproducir cualquiera de las emisoras de distinta temática que ofrece soma.fm.

Ya hace unos años compartí en el blog otro script en Bash para poder buscar y escuchar música de somafm en nuestra terminal:

• https://victorhckinthefreeworld.com/2023/08/29/como-escuchar-somafm-en-la-terminal-con-este-escript-en-bash/

Hoy quiero traer otro script en Bash con la misma funcionalidad y que muestra los datos de una manera más elegante, aunque la funcionalidad es la misma. Eso sí, requiere que tengas instalado curl, jq, fzf y mpv para que funcione el script.

El script lo tienes disponible en un repositorio en Codeberg, del usuario scy que fue quien lo compartió en Mastodon y donde lo descubrí.

El script no puede ser más sencillo, comparto por aquí el código:

#!/bin/sh
set -e


reformat() {
	jq -r '.channels[] | "\u001b[36m\(.id)\u001b[0m\t\u001b[1m\(.title)\u001b[0m\t\u001b[33m\(.genre)\u001b[0m\t\(.listeners)\t\(.playlists[] | select((.format == "aac" or .format == "aacp") and .quality == "highest") | .url)\t\(.description)"'
}


choose() {
	fzf --delimiter '\t' --ansi --tabstop=23 --with-nth 2,1,3 \
		--preview 'echo {2} "  " "("{1}")"; echo Genre: {3}; echo; echo {6}; echo; echo {5}; echo Currently {4} listeners.' \
		--bind 'enter:become(mpv {5})'
}


curl -s https://somafm.com/channels.json | reformat | choose

Guarda el script en un archivo, por ejemplo somafm.sh y dale atributos de ejecución (ya sabes chmod +x somafm.sh) y ejecútalo en tu terminal mediante ./somafm.sh

Te mostrará una lista de todas las emisoras disponibles e información, mediante fzf filtra la que quieres, pulsas enter y a disfrutar de la música.

The openSUSE Conference 2025 in Nuremberg from June 26 - 28 is shaping up to be a great gathering for the open source software community.

There are three packed days of presentations, workshops and discussion along with three keynotes.

This year’s conference features SUSE CEO Dirk-Peter van Leeuwen who will recognize the openSUSE community’s 20-year journey. Peer Heinlein, who founded the Heinlein Group, which includes companies like Heinlein Support, mailbox.org, OpenTalk, and OpenCloud, will provide another keynote on the same day and his talk will focus on the risks users face when using proprietary software. Another keynote from Tropic Square’s CEO Jan Pleskač will spotlight the growing need to extend open source hardware.

The conference is offering a broad look at where openSUSE is heading and what challenges are emerging for the project’s development and how the open-source communities can resolve them.

There are several sessions drawing attention like “Public Money? Public Code!” and a series of presentations addressing Cyber Resilience Act (CRA) and Network and Information Security 2 Directive (NIS2) readiness. These sessions explored how European cybersecurity regulations are impacting small to medium open-source vendors and what steps are needed to align with the evolving legal landscape.

On the technical side, integration and automation sessions continue. One talk demonstrated how Uyuni can be tightly woven into existing infrastructure management tools like Ansible and Terraform. Another session unveiled a tool called container-snap, a prototype designed to bring atomic OS updates through OCI images, which helps eliminate the risk of broken upgrades.

The Leap 16.0 Beta will have a dedicated session, and the future of SUSE Linux Enterprise will be discussed in a talk titled “From ALP to SLES16”.

Workshops on LLMs will show how to run large language models locally and turn them into functional agents and a popular penguin AI project called Kowalski should capture some attention at the conference.

Underlying many talks is a shared urgency around user empowerment. The “End of 10 Install Workshop” sessions are aimed at encouraging users to install openSUSE on aging or repurposed hardware based on Microsoft’s end-of-life date for Windows 10.

The full schedule of the openSUSE Conference 2025 is available at events.opensuse.org.

While most Java-based drivers have been deprecated in syslog-ng years ago, we have recently removed all of them in preparation to syslog-ng 4.9.0. Right now, the only Java-based driver remaining is HDFS, so we want to ask the syslog-ng community if the HDFS destination is still needed for them.

Read more at https://www.syslog-ng.com/community/b/blog/posts/deprecating-java-based-drivers-from-syslog-ng-is-hdfs-next