@moses_izumi @cas @postmarketOS Any you want: https://wiki.postmarketos.org/wiki/Category:Interface

Get out

If you hate DHH and vibe coding, come help Redox. Here he is throwing a temper tantrum over our no-AI policy:

https://x.com/dhh/status/2097559561993326752

DHH says "The number of Linux distros and projects that have these batty Al policies is baffling. Like rejecting the railroad because you like to pet donkeys. Oh well, more tokens for Omarchy!"

Followed by a screenshot of Redox OS's AI policy which forbids LLM generated contributions.

https://gitlab.redox-os.org/redox-os/redox/-/blob/master/CONTRIBUTING.md?ref_type=heads#ai-policy

@McNeely @cas @moses_izumi @greytheearthling @elementary @postmarketOS Historically it kind of was. But nowadays pmOS is about increasing the longevity of consumer devices in general, not just phones but also tablets, computers and even TV boxes.

@cas @moses_izumi @postmarketOS It is important to read the context behind dropping x86: https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/9521

@elly @moses_izumi @cas @postmarketOS why isn't it our main focus? Our main focus is to extend the longevity of consumer devices, this can be desktops, laptops, phones, smartwatches, TV boxes, anything that can run linux really. Unlike what people say, we are not purely a mobile-focused distro

@moses_izumi @postmarketOS It will.

@cas @moses_izumi @postmarketOS like, the reason we dropped armhf also had nothing to do with how old it is. It had entirely everything to do with maintenance of that arch not being very good, and very few devices to justify the trouble.

@cas @moses_izumi @postmarketOS No, x86 was not dropped because it was broken. It was dropped because there aren't many x86 devices supported at the moment and so we were building packages for an architecture that had no device ports.

It will come back probably when I get around to doing a generic x86 port (which I actually was interested in doing).

> ofc it's a catch-22 a bit but imho our focus and compute is better spent pushing the envelope forward than languishing in obsolete tech (especially when it's clear that the tech doesn't tie into our mission).

the goal of postmarketOS is to extend the life of consumer devices. I really don't see why extending the life of old x86 devices wouldn't count? It's clear that it does tie into our mission, so?

I never thought this would pay off, but here we are.

My date of certificate expiry is now automation actually triggered.

#manjaro #linux #manjarolinux #ssl #tls

@thomholwerda AFAIK Qt tends to be lighter on resources due to having a focus on low-power embedded hardware.

That said GNOME runs just fine on a 4th gen i5 with no animation skipping? Would be useful to know what hardware you are running it on.

the #pkgconf maintainers would like to talk to humans, not bots which have gone on a wild ride. this wastes our time as maintainers, and is why pkgconf does not allow LLM-generated contributions, especially agentic ones.

https://github.com/pkgconf/pkgconf/pull/592

(I'm tired, boss)

suddenly felt like I was transported to an alternate reality

You may fascinate a hacker with 20 year-old e-waste

On a fun topic: what in the world is postmarketOS? (wrong answers only)

I really need to get around to deleting my account

#getOffGithub

This month's annoyance: people non-consensually assigning me tickets in their organisation's ticket tracker.

As #PuTTY maintainer, I'm often asked to fill in annoying government paperwork, usually from someone else's country. "All the software our organisation uses must comply with the National Foo Directive, so please fill in this huge questionnaire to confirm that you do."

Often without bothering to even mention which nation's National Foo Directive it is. Often without noticing that a lot of the questions are obviously meaningless (e.g. assuming the product is hardware, or a cloud service, or something). And _always_ without thinking through the difference between a commercial software vendor (who has a financial incentive to do this kind of paperwork, and can employ staff to do it out of the revenue stream from selling the software itself) and an unpaid free software maintainer (LOL no).

In the past, this has generally involved an email from some actual employee tasked with going through the Big Spreadsheet of all the software that (they know) they're using. So you can reply to the person and explain their misunderstanding. (Generally I wait until the followup email before bothering, in case they manage to engage their own brain before then, which sometimes they do.)

But a new and unwelcome development is that they're starting to do it by automated ticketing systems, so I get an email saying "[employee] has assigned you a task" and I have no doubt it's going to carry on automatically pestering without any way of making it listen to reason. Probably I have no choice but to start blocking these ticketing systems' email addresses.

I've (finally) got the talk recording from Open Source Summit Japan 2025 ("We need an open-source phone OS - postmarketOS!") on my YouTube channel, as always with proper subtitles!

https://youtu.be/Wi5DpVYozUc

#postmarketOS #MobileLinux #LinuxMobile

Real hacker.

77-year-old Carl Gunn legally blocks a Flock license plate camera in St. Petersburg, Florida, by sitting on a public sidewalk and holding a 12-foot pool skimmer pole with a “DOWN WITH FLOCK CAMERAS” sign. Because he remains on public property and never touches the equipment, police confirmed his protest is lawful. #flock