NepoRC 2.13.7 is starting up enbyOS
 * Mounting gender filesystem ...
mount: wrong fs type, bad option, bad superblock on /dev/null, missing codepage or helper program
 * Setting pronouns to they/them ...
 * Setting timezone to UTC+2 ...
Starting about-me runlevel
 * Greeting user ...
Welcome to my page! (doasu.dev)
snac login: me
Password:
Last login: this week (localhost)
 ~ % _

@carl is at #39c3 today. Come and get some stickers!

Alt...

The KDE banner under a blue light.

Alt...

The KDE booth at #39c3 with stickers.

C3 stands for CheeseCake Congress

#39c3

Alt...

Two baking sheets of cheesecake. one of them is almost fully eaten.

Can someone explain to me why my smart home hub #Homey only responds to WiFi pings when I touch it? Is it just... lonely?

Perypetie z zespołem "wsparcia" mObywatela

TL;DR
Deweloperzy mObywatela nie zamierzają zapewniać wsparcia dla systemów bez usług Google.
Sama aplikacja działa, jednak uruchamia się z dużym opóźnieniem.

Jakiś czas temu postanowiłem zgłosić problem z działaniem aplikacji mObywatel. Zgłoszenie dotyczyło działania aplikacji na telefonie z Androidem bez zainstalowanych usług Google.

Zgłoszony problem polega na dwuminutowym opóźnieniu w otwieraniu aplikacji. Spowodowane jest to poprzez timeout przy nieudanej próbie odnalezienia usług Google w sysyemie. Do zgłoszenia oczywiście dołączyłem logi, na których widać czarno na białym, co jest powodem opisanego problemu.

Po dłuższym czasie i po wysłaniu ponaglenia dostałem pytanie o udzielenie dodatkowych informacji, tj. miałem podać m. in. swój PESEL.

W międzyczasie wsparcie uparcie pisało, że aplikacja musi być zainstalowana ze sklepu play. Wyjaśniłem, że tak właśnie jest w moim przypadku, a sklep i usługi zostały usunięte po instalacji mObywatela.

Przy okazji przyczepili się, że mam nieaktualną wersję aplikacji (tak długo odpowiadali, że wersja zdążyła się zdezaktualizowaclć 🤣)

Skończyło się na deklaracji:
"Nie planujemy zapewniać wsparcia dla systemów operacyjnych bez usług Google."

Pod linkiem znajdziecie plik tekstowy zawierający całą korespondencję.

https://wolnoscwkieszeni.pl/wp-content/uploads/2025/12/mobywatel.txt
#mobywatel

commit 9e90019bed44a55bff6cdd8deabb51322568c640
Author: q66 <q66@chimera-linux.org>
Date:   Wed Nov 26 20:04:17 2025 +0100
    cbuild: add 'eepy' template option
    Help low energy no-output long running builds avoid getting killed
    by buildbot by meowing into the stdout every hour.
diff --git a/Packaging.md b/Packaging.md
index 5368df342..233e493fb 100644
--- a/Packaging.md
+++ b/Packaging.md
@@ -1816,6 +1816,11 @@ [...]
+* `eepy` *(false)* Sometimes a build gets low energy and doesn't output
+  anything in a few hours. That does not mean it will not finish however,
+  just gotta give it time. Apply to templates that are known to take
+  more than 4 hours to make cbuild meow to stdout every hour and prevent
+  our infrastructure from terminating the build.
[...]

we need to make chimera package management gayer so that every time you run apk, lunduke's blood pressure goes up

Companies spend a lot of money convincing us to trust them.

We^W Countries other than the US have government bodies regulating drug companies, because we can't trust them.

Tech spends the same "trust me" money, but has no regulatory oversight.

Can't blame folks outside tech for not understanding the risks. Blame the companies. Spread the story that the companies can't be trusted and that the cloud is a lie.

And in the name of Dog, back up your digital life on media you control!

https://hey.paris/posts/appleid/

I'm currently running another poll on the usage of Wayland vs Xorg, last time we reached 14k response so feel free to vote if you'd like https://www.youtube.com/post/UgkxTMaPjQ7nsH-qZHvkvQbX6yQiVjy1u1tR

Today we have Xaver Hugl on the show to talk about @kde future on Wayland, why they're dropping the X11 session and much more #Linux #KDE #OpenSource

Video: https://www.youtube.com/watch?v=AZgaUtqz2nU

Audio: https://creators.spotify.com/pod/profile/tech-over-tea/episodes/The-Future-Of-KDE-Plasma-Is-Wayland--Xaver-Hugl-e3c8jon

@fabio Your claims about Android and the Android Open Source Project are extremely misinformed. AOSP has not made any part of the cross-platform OS closed source. The only changes to what's published was specifically for Pixels. They still provide most of what they did before for Pixels.

A huge portion of the coverage of Android in tech media is inaccurate from people who don't understand it. Android releases were always developed behind closed doors and released as open source on launch day.

New on my #Gentoo blog: One #jobserver to rule them all

"""
A common problem with running Gentoo builds is concurrency. Many packages include extensive build steps that are either fully serial, or cannot fully utilize the available CPU threads throughout. This problem becomes less pronounced when running building multiple packages in parallel, but then we are risking overscheduling for packages that do take advantage of parallel builds.

Fortunately, there are a few tools at our disposal that can improve the situation. Most recently, they were joined by two experimental system-wide jobservers: #guildmaster and #steve. In this post, I’d like to provide the background on them, and discuss the problems they are facing.
"""

https://blogs.gentoo.org/mgorny/2025/11/30/one-jobserver-to-rule-them-all/

Inevitable moment:

f4e4ddaf69337 dev-build/steve: is no longer simple

#Gentoo

@cyberlyra @fabio

> Only a SMALL fraction of SFOS is closed source

No, that's wrong. Most of the OS code that's specific to SailfishOS is closed source. It's the parts which come from elsewhere and aren't specific to it which aren't closed source. Their project is mostly closed.

> It does NOT have worse privacy and seurity than Android.

No, SailfishOS objectively has extremely poor privacy and security compared to the Android Open Source Project. It brings desktop insecurity to mobile.

A question one could ask is whether there could be a way in Forgejo/${FORGE} to keep those synchronised...
You can already use workflows for that, though.

CC: @ross@rossabaker.com

Willoughby: the rat, the myth, the legend.

I asked him what his legend is, and he just yawned at me. Apparently I'm supposed to know? #petRats #rats

Alt...

cute pet rat lounging in a hammock

CC: @outfrost@mastodon.social @Gusted@social.linux.pizza

We now have experimental support for the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold.

Our initial 2025112500 release for these is available through our web installer or releases page on our staging site:

https://staging.grapheneos.org/install/web
https://staging.grapheneos.org/releases#devices

fun!!

(I only contributed documentation to OpenRC so far ~.~)