flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.2K
active users

#kde

60 posts57 participants9 posts today

Já está disponível a versão final do Fedora Linux 42, trazendo o Gnome 48 na edição Workstation e a nova baseada no KDE Plasma (versão 6.3.4), promovida neste ciclo ao mesmo status da Workstation. Apesar do mesmo status, a lógica dos nomes é diferente; o povo lá está ciente da confusão e afirma que “vamos resolver isso em algum momento”.

O Anaconda, instalador do Fedora, […]

#Fediblog

https://manualdousuario.net/fedora-42/

Logo do Manual do Usuário, com fundo cinza, para redes sociais.
Manual do Usuário · Fedora Linux 42
More from Rodrigo Ghedin
#FOSS#Gnome#KDE

I have just taken the time to thoroughly read the following article

This article has led me to the conclusion that an Open{source} War will have to be waged against LLM large language model abusers of data collection.

The work of these bots is pure DDoS denial of service. An interesting set of offensive tools have been programmed and are already implemented. They have proven to be quite effective and are being refined into sophistication to literally work to knock these networks of bots offline, in a DOT MMORPG approach.

It is unthinkable that LLM bots steal our Open Source resources servers bandwidth and financial cashflow without serious repercussions!

WTF are LLM companies thinking? Even Meta has waged war against us!

LLM has waged a brutal war.

The Open Source Community is responding; even those at The Dark Side of the internet are making tools to assist everyone against Artificial Intelligence LLM DDoS attacks, which knock whole Open Source Networks offline, as we speak.

It doesn't matter if in the end it looks like a Terminator landscape globally on the IT scale. Open source will win. LLM will disappear...

#DDoS#LLM#bots

Does anyone know if there's a way to enable a sensible on-screen keyboard with #XScreensaver? (this might be a question for @jwz).

This is for use on a tablet, there's no physical keyboard unless I plug one in, and that's a hassle when you're out and about.

At the moment I'm battling the default #KDE lock screen and its rather crippled on-screen keyboard (see discuss.kde.org/t/customise-or) which is in my opinion, totally unfit for the purpose of screen locking as it does not allow convenient entry of a secure password.

Switching the lock screen to using `xscreensaver` is a very viable option: if I can enable an on-screen keyboard.

I don't mind what the on-screen keyboard is. It could be `onboard`, it could be `qtvirtualkeyboard` (I think that's what KDE is using), it could be `xvkbd`… don't care… so long as it displays a "standard" (for me that's US layout but I'll define "standard" as one matching 99% of the keyboards you can buy at a shop) key layout with letters, symbols and digits in their usual places.

I otherwise do use `xscreensaver` on non-tablets, and it is actually my preferred option. This machine though, has special needs.

KDE Discuss · Customise or replace the on-screen keyboard on the lock screen?For reference (sorry to the blind folk but I had to combine these screenshots into one because new users cannot be trusted)… this is what I’m on about: The photos are low resolution as they were taken with a smartphone camera. I also want to keep the file size down. On the left, we have the KDE lock screen with its default on-screen keyboard. To enter a reasonably secure password, one is switching between the two layouts constantly. I’ve never typed on a 100-year old teletype, but I’m pr...

A #desktopenvironment has to work properly out of the box.

If it includes cpu and storage killers like #baloo, as the desktop environment #KDE does, then it is a k.o. criteria. Then you shouldn't use it.

Dear people from KDE: please remove baloo from KDE for the time being. It's not an essential feature, and it only causes problems atm.

You can fix it, but you shouldn't include it in this broken state in "normal" releases.

Ich glaube ich muss #KDE wieder löschen/deinstallieren von meinem Laptop. Das ist ja furchtbar, wie viel CPU-Leistung und Speicherplatz #baloo braucht?!?!

Mehrere Gigabyte Speicherplatz und 100% CPU-Auslastung für >15 Minuten, der Lüfter lief auf Hochtouren.

Und das nur zum Dateien indexieren und durchsuchbar machen.

Und baloo alleine entfernen geht irgendwie nicht, weil das zur KDE desktop environment offenbar dazugehört?!

Dann doch lieber #Gnome.