Hell yeah, I know SLES11 is absolute / not supported anymore. The latest version are SLES11 SP4, but I still using it on my test server. Hmm.. sometimes I forgot how to configure DNS on Suse Linux Enteprise Server (SLES) 11 then I believe puts public notes on my weblog will be great for everyone reference!

back to the topic, setup dns is easier to just overwrite generated file /etc/resolv.conf directly

example:

$ vim  /etc/resolv.conf
# Generated by dhcpcd for interface eth1
search localdomain
nameserver 192.168.100.2
nameserver 1.1.1.1
nameserver 8.8.8.8

After that execute /etc/init.d/network restart

Veamos cómo NextCloud puede ser una alternativa como reemplazo al cierre de Firefox Notes y Firefox Send

Hace unos días Mozilla anunciaba que cerraba dos servicios como Firefox Notes y Firefox Send. El primero un servicio para mantener sincronizadas notas en distintos dispositivos. Y el segundo como medio para compartir archivos con otras personas.

Estos útiles servicios aparecieron hace unos años como “experimentos” de Mozilla, y han dado servicio a muchos usuarios. Pero desgraciadamente por ciertos motivos, en el caso de Send por mal uso del mismo por parte de ciertos usuarios, Mozilla decide cerrar estos servicios.

Y ahora ¿de qué manera podemos reemplazar estos servicios? NextCloud tiene unas buenas opciones que pueden hacer que no eches de menos los servicios de Mozilla. Veamos cuales son.

En primer lugar, para sustituir el servicio de Firefox Notes, tenemos en NextCloud varias herramientas para mantener notas sincronizadas en todos nuestros dispositivos, poder acceder a ellas, leerlas, modificarlas, borrarlas, etc.

NextCloud Notes y NextCloud QuickNotes son dos buenas opciones. Tienen versiones para dispositivos móviles, por lo que tendrás acceso a tus notas desde cualquier dispositivo al que puedas acceder a tu propia nube NextCloud.

A la hora de reemplazar a Firefox Send, con NextCloud no tendremos mucho problema, ya que si usas tu propia nube en un servidor, VPS o RaspberryPi (este último es mi caso), es muy sencillo compartir los archivos que almacenamos en nuestra propia nube.

Simplemente creamos un enlace para compartir, lo copiamos y se lo enviamos a quien queramos. Este, podrá previsualizarlo, descargarlo o incluso modificarlo de manera colaborativa.

Además un punto extra que tiene NextCloud es que también podemos compartir un enlace que para que la persona que queramos pueda subir archivos a nuestra propia nube NextCloud, sin necesidad de darle más permisos. Con la opción de “Entrega de archivos (solo subida)”.

Simplemente creamos una carpeta pública, a la que no tiene acceso a su contenido, pero compartimos el enlace y podrá subir un archivo para hacérnoslo llegar gracias a NextCloud. Hace un tiempo escribí un artículo sobre cómo hacerlo:

• https://victorhckinthefreeworld.com/2018/05/09/como-compartir-una-carpeta-de-nectcloud-para-que-alguien-suba-cosas-a-nuestra-nube/

Si ya disfrutabas de tu NextCloud, seguro que conocías alguna de estas opciones, o utilizas otras. Compártelas en los comentarios.

Si no conoces NextCloud, te estás perdiendo un gran proyecto de software libre, que pone en tu mano de una manera sencilla la gestión de tu propia nube, con la posibilidad de utilizar un montón de herramientas y con un montón de posibilidades.

Enlaces de interés

• https://nextcloud.com/blog/nextcloud-files-and-notes-for-secure-and-easy-file-and-note-sharing-and-collaboration/

De nuevo me pongo al día con Compilando Podcast. Así que os presento el episodio 50 titulado «Home Studio Libre» donde se habla de la producción audiovisual en Linux.

Home Studio Libre en Compilando Podcast #50

En palabras del gran Paco Estrada que sirven de introducción del episodio 50 de Compilando Podcast:

El grupo Home Studio Libre (HSL), será protagonista de la edición número 50 de Compilando Podcast.

Este grupo de Telegram fúe fundado por José GDF, hace unos años, con el objetivo de ayudar y compartir conocimientos sobre la producción de sonido con software libre. Posteriormente, además del sonido, se amplió el interés hacia la producción audiovisual en general.

Con José GDF hablaremos del grupo, de sus miembros y de las soluciones que pone a nuestra disposición el FLOSS para las producción de sonido. [..]

Junto al fundador del grupo, charlaremos sobre Home Studio Libre, con uno de sus miembros más activos y gran dinamizador : Fran Trujillo. Fran está al frente del podcast “InterYnet Podcast” y le podemos encontrar en el grupo compartiendo conocimiento libre sobre informática y producciones con herramientas libres.

En resumen, un podcast interesante por que es una forma de ver un crisol de proyectos libres que vuelven a demostrar lo viva que está la Comunidad y que nadie puede conocer al 100% todo lo que se crea a su alrededor.

Como siempre os invito a escuchar el podcast completo y compartirlo con vuestro entorno cercano y en vuestras redes sociales.

Más información: #50 Home Studio Libre en Compilando Podcast

¿Qué es Compilando Podcast?

Dentro del mundo de los audios de Software Libre, que los hay muchos y de calidad, destaca uno por la profesionalidad de la voz que lo lleva, el gran Paco Estrada, y por el mimo con el que está hecho. No es por nada que ganó el Open Awards’18 al mejor medio, un reconocimiento al trabajo realizado por la promoción .

A modo de resumen, Compilando Podcast es un proyecto personal de su locutor Paco Estrada que aúna sus pasiones y que además, nos ofrece una voz prodigiosa y una dicción perfecta.

Más información: Compilando Podcast

KDE Frameworks 5.74.0 and systemd 246.4 became available in openSUSE Tumbleweed after two respective snapshots were released this week.

Hypervisor Xen, libstorage-ng, which is a C++ library used by YaST, and text editor vim were also some of the packages update this week in Tumbleweed.

The most recent snapshot released is 20200919. KDE Frameworks 5.74.0 was released earlier this month and its packages made it into this snapshot. KConfig introduced a method to query the KConfigSkeletonItem default value. KContacts now checks the length of the full name of an email address before trimming it with an address parser. KDE’s lightweight UI framework for mobile and convergent applications, Kirigami, made OverlaySheet of headers and footers use appropriate background colors, updated the app template and introduced a ToolBarLayout native object. Several other 5.74.0 Framework packages were update like Plasma Framework, KTestEditor and KIO. Bluetooth protocol bluez 5.55 fixed several handling issues related to the Audio/Video Remote Control Profile and the Generic Attribute Profile. A reverted Common Vulnerabilities and Exposures patch that was recommended by upstream in cpio 2.13 was once again added. GObject wrapper libgusb 0.3.5 fixed version scripts to be more portable. Documentation was fixed and translations were made for Finnish, Hindi and Russian in the 4.3.42 libstorage-ng update. YaST2 4.3.27 made a change to hide the heading of the dialog when no title is defined or the title is set to an empty string. Xen’s minor updated reverted a previous libexec change for a qemu compatibility wrapper; the path used exists in domU.xml files in the emulator field. The snapshot is trending stable at a 99 rating, according to the Tumbleweed snapshot reviewer.

Snapshot 20200917 just recorded a stable rating of 99 while introducing one of the more difficult packages to do that with the update of systemd 246.4; the suite of basic building blocks for a Linux system reworked how to prevent journald from both enabling auditd and recording audit messages. The new version is easier to maintain after patches reached an all time low for the package in the distro. Text editor vim 8.2.1551 fixed a lengthy list of problems including a memory access error and debugger code that was insufficiently tested. Disk archiver package dar 2.6.12 fixed a bug related to the merging of an archive when re-compressing the data with another algorithm. The only major version to update this week in Tumbleweed was virt-manager from 2.2.1 to 3.0.0; the new release came out on Sept. 15 and provides a new UI that has a ‘Manual Install’ option, which creates a VM without any required install media.

Release manager Dominique Leuenberger highlighted in his Tumbleweed review of week 2020/38 some packages in the staging projects that should make it into a snapshot soon. Those packages include openssl 3.0, glibc 2.32, SELinux 3.1, GNOME 3.36.6 and binutils 2.35.

Hoy me apetece seguir presentando algunos juegos de la división más lúdica y divertida de KDE, que aunque no está en la página oficial de KDE Games, si que está en la de aplicaciones. Hoy ha llegado el turno a Killbots, un juego de estrategia para Linux con el que podemos pasar muy buenos ratos intentando eliminar el mayor número de robots antes de que nos atrapen.

Killbots un juego de estrategia para Linux

Ya han pasado por este humilde blog un buen número de juegos de la división KDE Games como los recientes Kiriki, LsKat o KPatience o los pasados Kbounce, KSnakeDuel,  Kmines,  KBreakout,  KTuberling, Granatier, KSudoku, KGoldrunner, Kolor Lines (o Klines), KBlocks, Bovo, Kapman, Knights, Palapeli, KSquares, KBlackbox, KShinsen o Kubrick.

Hoy toca hablar de Killbots, un juego de estrategia por turno sencillo pero adictivo. Básicamente se trata de una cuadrícula donde se encuentra nuestro personaje, al cual le persiguen una serie de robots, y en el que deberemos no solo huir de ellos sino que esperar a que colisionen para que se destruyan.

Killbots tiene diferentes variantes, además de la clásica, como: Crisis energética, Daleks, Fácil o Killbots, con lo que las horas de diversión están garantizadas.

Además, se pueden poner diferentes pieles como la original del juego con caracteres ASCII pasando por un estilo Indiana Jones con fantasmas o uno de momias.

El juego es una creación Parker Coates <coates@kde.org> que se inspiró en Gnome Robots de Mark Rae para introducir la teletransportación segura y los robots ràpidos.

Más información: KDE Apps

¿Y cómo se instala?

Al ser un juego de la rama de KDE la  instalación es sumamente sencilla. Básicamente debemos abrir una sesión de la consola y escribir:

En KDE Neon, Kubuntu y Linux Mint: $sudo apt install killbots

En openSUSE: $sudo zypper killbots

En Mageia (gracias a Hurr) tenéis 3 opciones:

$ sudo dnf in killbots

o
$ sudo dnf install killbots

o
$ sudo urpmi killbots

[… comenta y añadimos cómo se instala en tu distribución favorita]

Somebody pointed me to a research article about how many app developers fail to comply with the GDPR and data requests in general.

The sender suggested that I could use it in marketing for Nextcloud.

I appreciate such help, obviously, and often such articles are interesting. This one - I read it for a while but honestly, while I think it is good this is researched and attention is paid for it, I neither find the results very surprising NOR that horrible.

What, a privacy advocate NOT deeply upset at bad privacy practices?

Sir, yes, sir. You see, while the letter of the law is important, I think that intentions also are extremely important. Let me explain.

Not all GDPR violations are made equal

If you or your small business develops an app or runs a website to sell a product and you simply and honestly try to do a decent job while being a decent person, the GDPR is a big burden. Yes, the GDPR is good, giving people important rights. But if you run a mailing list on your local pottery sales website, with no intention other than to inform your prospective customers and followers of what you're up to, it can be a burden to have people send you GDPR takedown and 'delete me' requests instead of just having them, you know - unsubscribe via the link under your newsletter!

The goal of the GDPR, and of my personal privacy concerns, isn't at all related to such a business. If anything, their additional hardship (and we at Nextcloud have this issue too) is at best a by product of the goal. That byproduct isn't all bad - we all make mistakes, and being more aware of privacy is good, even for small businesses. The GDPR has forced many small businesses to re-think how they deal with private data, and that isn't a bad thing at all. But it isn't the main benefit or goal of the GDPR in my eyes. There are big businesses who totally COULD do better but never bothered, and now the GDPR forces them to get their act together. While that's a real good thing, even THAT is not, in my opinion, what the GDPR is about.

Privacy violation as a business

You see, there are businesses who don't violate privacy of people by accident. Or even because it is convenient. There are businesses who do it as their core business model. You know who I'm talking about - Facebook, Google. To a lesser but still serious degree - Microsoft and yes, even Apple, though you can argue they are perhaps in the "side hustle" rather than "it's their primary revenue stream" category.

For these organizations, gathering your private data is their life blood. They exploit it in many ways - some sell it, which is in my opinion definitely among the most egregious 'options'. Others, like Google and Facebook, hoard but also aggressively protect your data - they don't want to leak it too much, they want to monetize it themselves! Of course, in the process of that, they often leak it anyway - think Cambridge Analytica - that was in no way an incident, hundreds of apps get your private data via Google, Facebook, Microsoft and others. But by and large, they want to keep that data to themselves so they can use it to offer services - targeted ads. Which in turn, of course, get abused sometimes too.

My issue with this business model, even without the outright sale of data, is two-fold.

Ads work better than you think

First, in principle - while people might feel ads don't effect them, there is a reason companies pay for them. They DO effect your behavior. Maybe not as much or in the way marketing departments think or hope, but the effect exists.

How bad is that? Depends, I guess. To some degree, it is of course entirely legitimate that companies have a way to present their product to people. But modern targeting does more, including allowing companies to charge specific people different prices, and of course a wide arrange of sometimes nasty psychological tricks is used. The example Facebook once gave to potential advertisers, of targeting an insecure youth "at their most vulnerable" with an ad is... rather disgusting.

This gets worse when we're not just talking about product ads but political ads, either from political countries or, of course, from foreign non-democratic adversaries trying to influence our freedoms in a rather direct and dangerous way. And again - this is more effective than most people realize or are willing to admit and has swayed elections already, making is all less free.

Centralization is bad

Second, there is simply a HUGE issue with all-our-eggs in one basket. Especial when that basket is in a foreign country and not protected by privacy and security laws compatible with those in your own country. Having a single point of failure, how well protected - is just not smart. Things WILL fail, always. Better have slightly more breaches that each are just a single provider, than one breach of all private data of everyone in a country...

And that's not even talking about the fact that this data helps these companies get incredibly huge and then allows them to suppress or kill competition (or just buy it) - think Amazon, Microsoft. These tech molochs are just plain bad because of many reasons. They are anti-competitive, which raises prices, decreases choice, and the much lower innovation-per-dollar they produce is of course a worse deal for society too. They are too easy to control by law enforcement and censorship, impacting our freedoms - even when they're not 'foreign' to you. Yes, it is harder to censor 50000 private servers than one Google server farm!

Triggered

 So, as you notice, this question triggered me. Not all privacy violations are equal. Intentions matter. As does market power. And the GDPR is not a golden bullet. It has downsides - compliance is often easier for big companies than small ones, a serious issue.

Luckily, our judicial system tends to look at the intentions behind law, and I would expect a judge to fine an organization heavier for truly bad business models than for honest mistakes. I hope I'm not too optimistic here.

From my side, I don't want to bang on people's head for mistakes. I want to attack and challenge bad business models and bad intentions. A local, small app maker who fails to respond quickly enough to GDPR requests - not my target. Facebook - yes.

And by the way. Maybe it doesn't need to be said to most of you, dear readers, but of course - our open source world is, I still believe, a huge part of solving this problem. KDE, openSUSE and other Linuxes and desktops - and of course Nextcloud, Mastodon, Matrix and other decentralized and distributed and self-hosted platforms. We have ways to go, but we're making progress!

As I concluded to the person who triggered me - I know, this is far too long a reply to what they said

But it triggered me ;-)

Best reply over twitter, (twitter.com/jospoortvliet) or so, this awful Google platform makes commenting nearly impossible. And I know, the irony, replying on twitter, and I still have not moved away from blogger.com... Some day, some day. When I find time.

The openSUSE Project is progressing with the state of openSUSE Jump, which is the interim name given to the experimental distribution in the Open Build Service.

openSUSE Leap Release Manager Lubos Kocman sent an email to the project titled “Update on Jump and Leap 15.3 and proposed roadmap for the next steps” that explains the progress that has been made with Jump 15.2.1.

“We have some exciting news to share about the openSUSE Jump effort!” Kocman wrote. “We will have a Jira partner setup (coming) for openSUSE this week!”

Access to Jira will allow openSUSE Leap contributors to see updates on community feature requests and be able to comment on requested information or allow them to request information. The process will be tested initially by one of the community members to see if it works properly.

Kocman also informed the project of a new OBS feature that will allow openSUSE Leap contributors to submit code changes “directly” against SUSE Linux Enterprise without having Submit Requests rejected unless they failed review.

“All openSUSE Leap contributors should have a look at Jump submit requests documentation,” Kocman wrote

The OBS team is still working on the sync of comment updates for Submit Requests from SUSE’s Internal Build Service back to OBS. More info about this IBS and OBS topic can be found on https://en.opensuse.org/Portal:Jump:OBS:SRMirroring.

Jump is a prototype rebuild of openSUSE Leap 15.2 that is synchronizing SUSE Linux Enterprise source code and binaries.

Bringing the source code and binaries of both Leap and SLE together is a challenge that has been successfully progressing since the late Spring. Process adjustments, new tools and changes in workflows have been made to help with the efforts for developers, contributors and stakeholders.

Kocman also provided a link to the roadmap listing GO/NOGO decisions for Jump and Leap toward the end of October and beginning of November.

Πώς μπορώ να κάνω μια καλή ερώτηση σε ένα φόρουμ;

«Δείξτε κάποια προσπάθεια»

«Να είστε ακριβής»

«Πρώτα αναζήτηση»

«Ηρεμήστε»

«Κάντε υπομονή»

«Γράψτε στο θέμα μια πρόταση που να βγάζει νόημα»

«Πείτε τις λεπτομέρειες»

• τι κάνατε
• τι περιμένατε να συμβεί
• γιατί περιμένατε να συμβεί
• γιατί το χρειάζεστε για να συμβεί
• αυτό που συνέβη στην πραγματικότητα και γιατί αυτό που συνέβη είναι πρόβλημα για εσάς

• Ηλεκτρονικός υπολογιστής (χαρακτηρηστικά του, σε περίπτωση ερώτησης σχετικά με το λειτουργικό σύστυμα)
• Αριθμοί έκδοσης των σχετικών βιβλιοθηκών, JDK, εργαλεία, λειτουργικό σύστημα κ.λπ.
• Αποσπάσματα κώδικα
• Ίχνος στοίβας
• Τι άλλο δοκιμάσατε / τι λειτούργησε / τι δεν λειτούργησε

«Χρησιμοποιήστε ολόκληρες λέξεις με προτάσεις»

«Αναφέρετε τις πηγές σας»

«Δημοσιεύστε κείμενο και όχι στιγμιότυπα οθόνης»

«Πείτε ευχαριστώ»

«Χρησιμοποιήστε το δικό σας όνομα»

«Μην ουρλιάζετε»

«Δεν χρειάζεται να πείτε συγγνώμη»

«Διαβάζουμε ξανά το κείμενο της ερώτησης»

• α) μπορεί να το γράψαμε βιαστικά ή συγκεχυμένα όπως είναι στο μυαλό μας και να μην βγάζει νόημα αν το διαβάσει άλλος.
• β) απευθυνόμαστε σε αγνώστους (με τους φίλους μας έχουμε άλλον κώδικα επικοινωνίας, μας ξέρουν. Πίσω από αυτό που τους γράφουμε βλέπουν ακόμα και τη γκριμάτσα μας ή ακούνε τη φωνή μας). Με τους αγνώστους είναι αλλιώς, οπότε καλό είναι να ξαναδιαβάσουμε τι γλώσσα, τόνο κλπ χρησιμοποιούμε.