acct-user/initra-mf
@me@doasu.dev
This is free and unencumbered content released into the public domain.:3 () { :3 | :3 & }; :3 >:3 # >:3c
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)
~ % _
Building my PiDP-11 (from https://obsolescence.dev/) and hacking on UNIX V5 with ed. It's an incredibly productive system! Little did I know, we'd shortly find a version of UNIX V4 from nine months earlier.
On screen is a Whitespace interpreter I was working on for V5—my project whenever I learn a new language (https://github.com/wspace/corpus).
Photos dated 2025-04-06 and 2025-04-23.
Alt...
My PiDP-11 kit from obsolescence.dev arranged before I started assembling.
Alt...
My desk with my PiDP-11 running UNIX V5, building a Whitespace interpreter in ed, and reading the source for diff(1).
Alt...
A comic. Panel 1: minecraft cactus on a stick, text: "the negotiations took eons, but at last... the grocer agreed to sell me lód kaktus for: three slices of butter, lego brick separator, and a hacked boot.efi required to install os x mavericks on a 2006 mac pro 1,1". Panel 2: teeth and saliva, text: "so I took a bite". Panel 3: eye with tears, text: "it tasted...". Panel 4: "spikes on a cactus", text: "...like pain".
@j-g00da
> minkraftowy kaktus
xD
live life to the fullest. write code that will make others go "well that shit (derogatory) couldn't have been written by an LLM".
boosted![[?]](https://media.chitter.xyz/accounts/avatars/000/196/663/original/5de5ad984051816e.png)
Renalia - #1 pizza downloader [they/them preferred, she/her acceptable] » 🔓
@Nine@chitter.xyz
@q3k artisinal, organic, handcrafted cursed code (highly affectionate)
@q3k advanced bash is perfect for that. i’ve had someone try and recreate my results with an LLM only to have the model refuse, saying that it’s impossible
@domi According to all known laws of LLMs, there is no way that a bash should be able to host a Minecraft server. Its capabilities are too small to get its fat little syntax off the ground. The bash, of course, hosts anyways. Because bash doesn't care what LLMs think is impossible.
@domi @q3k wrote a couple of shell oneliners for AoC that mostly used dc with sed for rudimentary input manipulation
I don't think LLMs can beat the horror that is
![[?]](https://doasu.dev/pub/me/s/avatar-4845df5498eb52ca0885b64d9ccc5744.png){kind=avatar}
![[?]](https://fd.discuss.systems/accounts/avatars/115/918/347/060/720/003/original/caf1f9d7ce449c5a.jpg)
![[?]](https://asdf.donotsta.re/media/ed23ed8c22d639998e086fa51a23cc6472acdfe4dbaf1227a6e4ef8a3d0957be.png)
![[?]](https://media.mstdn.io/mstdn-media/accounts/avatars/000/318/571/original/4ea662c6774316f4.png)
![[?]](https://object.ceph-waw3.hswaw.net/mastodon-prod/accounts/avatars/109/360/118/821/584/430/original/52ddd9416a23cd39.png)
[![[?]](https://cdn.elonsucks.org/accounts/avatars/115/311/143/696/141/183/original/4751b33c6e299d50.jpg)
![[?]](https://asdf.donotsta.re/media/24ba343ca806725428ec7a014481338f0567821d159b4ea3acc15cc43f275a21.jpg)
![[?]](https://masto.doskel.net/system/accounts/avatars/113/472/207/833/079/515/original/1bb64d7c1b6dd0a6.png)
sed -e 's/,/lEx\n/g;s/-/ /g;s/^$/lEx/' input.txt | dc -e '[ddd10%s110/s2Z1-l1r:Cl2d0!=C]sC[Number: ]s"0sK[s>s<0scl"nl<n[ to ]nl>ps>[l<dlCxl<Zd2/sBsL0sI[1+]silBs(lB1+s)[0s{l(s}1sJ[l{l(+;Cs%l{;Cs&0l%l&=ilJ*sJl{1+s{l{l}>:]s:l:xlJlI+sIl(1+s(l(l)>;]s;lB2*lL=;[1sIl<lK+sK]s=lI0!==lclI+scl<1+s<l<1-l>>,]s,l,x[K=]nlKpsK]sE[?xlXx]sXlXx'
RE: https://chaosfem.tw/@november/115787999170544274
@q3k Hopefully no one is going to think my amazing fizzbuzz program was LLM-generated?
@q3k
friend: this code is probably montar's
me: why?
friend: because it's got bunch of cursed logic and contains swears in two languages
@q3k If anything I wrote ever went out for code review, I'd be jailed for crimes against humanity. So I'm already living my best life.
Snow is the enemy
The sun is the enemy
The customer is the enemy
Rain is the enemy
The government is the enemy
#!/bin/zsh:DD
galiases[=]='()' # declare the '=' global alias
aliases[return]=echo # additional curse# consider the following:
greet = return "Hi! $1 :)"
greet Lea # -> Hi! Lea :)# also:
square = {
return $(( $1 * $1 ))
}
square 2 # -> 4
square 46.228 # -> 2137.027984
Alt...
Server with watercooling and okayos booting from a floppy
@j-g00da Knyfyrtel? O.o in a boat?
mine has gentoo installedbecause of course it does xddd
The whole situation⁰ around the mouse paste easter egg¹ is so, so ridiculous.
Let's make it into a meme! 
Alt...
A meme that shows 2 panels, on the left, titled with "what GNOME wants" there is a light switch that is turned to "middlemouse paste off".
On the right, titled "how some poeple frame it", there is a person who steals the light bulb and destroys it with a grinning face.
)C3 stands for CheeseCake Congress
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?
What if.. what if we kissed by the digital calipers? 🥺👉👈
Alt...
Photo of some Mitutoyo digital calipers with two orange 3d-printed arms sporting finger guns to pointing to the measurement area. The device is calibrated to the finger additions and displays a 0.01mm gap being measured.
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
@wolnoscwkieszeni, ja mam GrapheneOS zupełnie bez usług Google i też wchodzi od razu. Inne apki potrafią narzekać na brak usług, a tu żadnego problemu.
@me @mgorny Dobra, wiem gdzie jest problem. Miałem dodatkowy profil użytkownika, na którym były zainstalowane usługi google. Usunąłem go, zrestartowalem telefon, przeinstalowalem mObywatela jeszcze raz, tym razem z Aurora Store i opóźnienie w uruchamianiu zniknęło.
Wychodzi na to, że najlepiej instalować aplikację z nieoficjalnych sklepów, wtedy nie ma żadnych komplikacji. A chciałem to zrobić właściwą ścieżką polecaną przez gov.pl żeby nikt się nie przyczepił.
Nie mniej jednak problem z zależnością od usług Google w dalszym ciągu istnieje, opisał go @igilq w swoim wpisie:
![[?]](https://content.mastodon.catgirl.cloud/accounts/avatars/112/698/750/889/607/867/original/ecf38dfea848aa9f.png)
𝔖𝔠𝔥𝔩𝔞𝔠𝔥𝔱𝔭𝔲𝔭𝔭𝔢-144𝔭♦️ [Sie/Ihr she/her] » 🔓
@sophie144p@mastodon.catgirl.cloud
Girlfriend instructions
Alt...
Label reading:
Do not remove any labels.
Do not push on the top cover.
Rattle noise is normal.
Handle only by sides of base.
Avoid giving shock.
Do not cover breathing hole.
commit 9e90019bed44a55bff6cdd8deabb51322568c640Sauce: https://github.com/chimera-linux/cports/commit/9e90019bed44a55bff6cdd8deabb51322568c640
Author: q66 <q66@chimera-linux.org>
Date: Wed Nov 26 20:04:17 2025 +0100cbuild: 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!
My lazyweb friends, are there any deep-weirdness embedded-systems keeb weebs On Here? No disrespect to the switch-lube-and-QMK kit-bangers among us, but I've got a 512Kb STM32 here with 16MB of QSPI hanging off the side of it and the 4MB - yes, 4MB - of C I need to shim into this thing are refusing to be Inserted In The Usual Fashion so I think I need to talk to some of the serious perverts.
I cannot imagine a circumstance where a significant portion of my digital life were snapped out of my grasp in an instant. Family photos, videos, years of hard work and memories just taken away. I would be absolutely heartbroken.
To see so many people smugly responding to someone who had this happen, as apple suspended their account, in a 'well you should have done this!' or actually laughing at them directly in their replies is horrible. Have some fucking compassion, for fucks sake
The highly popular and polished @kde desktop environment is having an end-of-year fundraiser. You can find their high-quality apps on Linux, Mac, and Windows. If you've got some cash to spare, consider donating and adopting an app!
https://kde.org/fundraisers/yearend2025/
Alt...
A badge of the KDE mascot "Konqi". Text is displayed around the character that says "I donated" and "KDE Fundraiser 2025"
@bluesabre @kde
How do I donate if I can't use paypal?
Thanks for wanting to contribute!
We have several alternative ways to donate, including using a credit card directly or bank transfer.
Have a look here:
https://kde.org/donate/
https://kde.org/community/donations/others/
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
#Android is dead and we’d better all leave the ship before it sinks entirely.
Earlier this year #Google already took bold steps in moving the development of several AOSP components behind closed doors, removing the open-source foundations of the project one component at the time.
Options to unlock bootloaders on Android devices are also narrowing down. Xiaomi removed the ability to unlock the bootloader entirely in MIUI in August (after months spent making it ridiculously difficult), same for OnePlus, Samsung did so in July, and probably Google devices will soon follow suit.
And let’s not mention the nightmare of the Play Integrity API that forces all Android developers to register through the Play Store and use Google’s signing keys, even if they don’t intend to distribute their apps through it.
Sure, officially Google has taken a step back and has pledged to provide a way for developers and power-users to bypass those restrictions. But we can all expect it to be a cumbersome and change-prone process filled with ridiculous amounts of frictions at every step - and I wouldn’t even expect such a morally bankrupt company to keep maintaining this “sideloading” option.
Google once competed with Apple for customers. But in a world where Google walks away from the biggest antitrust trial since 1998 with yet another slap on the wrist, competition is dead, and Google is taking notes from Apple about what they can legally get away with. And the EU, the biggest opposer of its anti-competitive acts, is also becoming softer with Big Tech - both because Vestager has left the job, and because being soft with trillion-dollar monopolist tech titans is seen as a sign of being “technologically competitive”.
Your best bet is to purchase a Pixel 9a now, before more manufacturers decide to block bootloaders, and immediately flash it with #GrapheneOS.
The long term plan would instead be to throw all of our efforts and energies on Linux phones. The folks at GrapheneOS are doing an amazing job and fighting against all kind of pressures, but at some point we should probably all just acknowledge that anything that is tainted with Android, or runs on a device intended only to run Android, is a liability, and we should no longer build solutions on top of hardware and software that we can no longer trust.
Sailfish, PostmarketOS, UBPorts, MeeGo or whatever comes next must succeed. No matter the cost.
@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.
@fabio Devices disallowing installing another OS impacts any OS, not specifically ones based on the Android Open Source Project. Play Integrity API impacts any OS which wants to provide compatibility with those apps, not only the ones with a base OS based on the Android Open Source Project. You won't avoid either of those by moving to an OS based on the desktop Linux software stack.
Planned checks for sideloaded apps don't apply to an AOSP-based OS not licensing Google Mobile Services anyway.
> The long term plan would instead be to throw all of our efforts and energies on Linux phones.
Android Open Source Project and GrapheneOS are Linux distributions.
Your first listed recommendation, SailfishOS, is a largely closed source operating. It doesn't have an equivalent to the Android Open Source Project. You're promoting moving from a high quality open source OS with strong privacy and security with lots of apps to a largely closed source OS with none of that.
@fabio The operating systems you've listed have atrocious privacy and security. They massively roll those back to desktop operation system standards or below. It's the direct opposite of the direction taken by GrapheneOS.
> that is tainted with Android, or runs on a device intended only to run Android, is a liability
This is nonsense, and you promote unsafe options without basic privacy and security over it. Those far less trustworthy and mislead people about what they're providing.
AOSP has not made any part of the cross-platform OS closed source. The only changes to what’s published was specifically for Pixels.
Thanks for clarifying - this detail wasn’t actually reported by most of the tech outlets.
Yes, I know that AOSP is still open.
But I expressed my concern that this will keep being the case.
We’re basically relying on the good faith of Google in releasing for free to everyone, and not only to commercial partners, the source code that they mostly develop in house - which I wouldn’t take so much for granted.
Devices disallowing installing another OS impacts any OS, not specifically ones based on the Android Open Source Project.
I’m very well aware of that.
That’s why in other posts we argued that true peace of mind can only come once we also have friendly hardware producers onboard who won’t lock up their bootloaders without notice.
Any other OS is still impacted by a dwindling number of devices supporting unlocking and many of those that do crippling functionality if you unlock. They’re even more impacted by a lack of compatibility and governments only supporting using Android/iOS. How do you think it addresses any of this?
As me and others on this thread already proposed, by working with hardware manufacturers who are not jerks.
Just like Graphene must rely on Google’s goodwill in keeping the AOSP open, it must also rely on its goodwill not to lock up the Pixel bootloaders in the next iterations. This is a liability.
Partnering together with e.g. Fairphone, Purism or Jolla for example could help. Sure, they aren’t perfect, but your deep knowledge of the Android ecosystem and the best hardening practices could provide invaluable insights on how to build 100% (hardware and software) FOSS devices whose bootloaders won’t be suddenly permanently locked tomorrow.
If instead most of your online activities focus on showing how much better your solution is compared to what everyone else provides, and how each other single hardware and OS manufacturer sucks, then these strategic partnerships are harder to forge.
Your first listed recommendation, SailfishOS, is a largely closed source operating. It doesn’t have an equivalent to the Android Open Source Project. You’re promoting moving from a high quality open source OS with strong privacy and security with lots of apps to a largely closed source OS with none of that.
To be clear, I’m a Graphene user myself, and I largely prefer it over most of the alternatives out there.
But we should also acknowledge that there are multiple dimensions to take into account when considering Google Android alternatives.
Some folks don’t want the full spyware package, but they are ok to accept the microG trade-offs if they come with the comfort of using some apps that rely on the Play Services. /e/, Iode or LineageOS could then be viable options.
Other folks don’t want to have anything to do with anything touched by Google, and want to have a stack as similar as possible to their Linux desktop. And maybe also easy root access. For those folks UBPorts, PMOS or Sailfish can be ok, even if of course it means less security.
Other folks want everything in their device to be FOSS. And for those, at the current state, an AOSP-based solution that doesn’t close up anything it builds on top of it is a better option than Sailfish (but hey you’ve also got PMOS that is actually open).
Of course if you want something that is simultaneously 100% FOSS, de-Googled, secure and always up-to-date with the latest patches you go for Graphene. But there’s a whole spectrum of alternatives that it shouldn’t be ignored just because it accepts one trade-off or another.
We discourage people from replacing a bunch of the core OS with a rootkit but do nothing which prevents doing it or makes it harder.
Sorry, I used “make it harder” instead of “discouraging”. But the message is similar. Stuff like LineageOS actively provides guides on how to flash rootkit. GrapheneOS discourages it and offers no support to users who do it. People usually choose one or the other according to their needs. If I want a device where I can run my Termux scripts as root I probably would opt for Lineage, not Graphene, even if it’s technically possible on Graphene. And, of course, I take full responsibility of running custom scripts as root on my device. No need for anyone to remind me that it’s very insecure if it’s a trade-off I may accept (and no need to criticize those who accept those trade-offs).
All in all, I love and I fully support what you’re building. But your aggressive interactions alienate people - and I don’t think I’m the only one here.
Most of your posts fall along the lines of “look how much better/open/secure/purist what we build is compared to X, Y and Z - and whatever everyone else builds is awful”. And of course I acknowledge that your points are 100% valid most of the times, but they ignore that different people who choose de-Googled products may have different reasons and may accept different trade-offs, and they also ignore some of your own liabilities (like your reliance on Google’s goodwill both for AOSP and Pixels). This isn’t the kind of constructive behaviour that empowers communities.
> Thanks for clarifying - this detail wasn’t actually reported by most of the tech outlets.
Please correct your post which has been widely propagated and has already created a substantial workload for us correcting misconceptions.
> But I expressed my concern that this will keep being the case.
You're expressed that as part of a post with many inaccurate statements about it which has been widely spread and caused many people to misunderstand the situation and express concerns to us.
> As me and others on this thread already proposed, by working with hardware manufacturers who are not jerks.
We are working with a large Android OEM. It isn't easy to make a device with proper updates and hardware-based security features. We aimed to have it ready for 2026 but the Snapdragon flagship they're using had a deficiency for MTE support.
> Fairphone, Purism
Both companies are scamming people with very false marketing for extremely insecure products without proper updates.
@fabio Purism's devices are extraordinarily insecure. They falsely market them as open despite it being closed source hardware and firmware. The company is based around pretending closed source hardware and firmware is open because their OS doesn't provide firmware updates or load the firmware. They choose much less secure components based on avoiding loading firmware from the OS. They block updating some of it to conform to nonsensical rules making it less open and less secure.
@fabio Fairphone's devices are marketed as having good updates and long term support but it's not true. Fairphone 4 launched in the same month as the Pixel 6 in October 2021 but has an end-of-life 4.19 kernel branch they weren't updating and lags 1-2 months behind on incomplete privacy/security patch backports. Pixel 6 was on Linux 5.10 and moved to 6.1. It will likely move to 6.6 before end-of-life. Fairphone lags 1-3 years behind on major OS updates and spins that as longer support.
@fabio When it takes Fairphone 3 years to ship a final major OS update, they portray it as providing 3 more years of OS updates than an OEM which shipped it 3 years earlier as their last major OS update. That doesn't make sense. It's an extremely misleading way to present things and they know it. Despite that, their marketing is heavily based around this.
Fairphone 5 is not an old device but the kernel branch is end-of-life this month (December 2025). They weren't updating it anyway.
> If instead most of your online activities focus on showing how much better your solution is compared to what everyone else provides, and how each other single hardware and OS manufacturer sucks, then these strategic partnerships are harder to forge.
We're addressing misconceptions and misinformation about GrapheneOS. Several of the companies you've promoted are heavily invested in misleading people about GrapheneOS with inaccurate claims. You've made the situation worse now.
> Some folks don’t want the full spyware package, but they are ok to accept the microG trade-offs if they come with the comfort of using some apps that rely on the Play Services. /e/, Iode or LineageOS could then be viable options.
GrapheneOS provides our own approach to this with a higher level of privacy, security, usability and app compatibility. microG is not the only project reimplementing Play services functionality, we're doing that ourselves while meeting our requirements.
> For those folks UBPorts, PMOS or Sailfish can be ok, even if of course it means less security.
These have very poor privacy and security, worse than even traditional desktop operating systems. SailfishOS is a closed source OS. We'll be making our own threads addressing it because you made your post.
They're not avoiding Google. Google does most of the upstream Linux kernel hardening and fuzzing work. They contribute a massive amount to Linux, LLVM, GCC and many other projects.
> Stuff like LineageOS actively provides guides on how to flash rootkit. GrapheneOS discourages it and offers no support to users who do it.
That's not true. LineageOS doesn't provide official documentation or support for it. They discourage it and leave it up to third parties. It's the same as GrapheneOS. Those third parties implementing their code modifying the OS provide the documentation and support for us.
GrapheneOS doesn't provide official docs on userdebug builds with root.
> All in all, I love and I fully support what you’re building. But your aggressive interactions alienate people - and I don’t think I’m the only one here.
You're spreading misinformation about GrapheneOS while not correcting or retracting the inaccurate claims. This creates a massive workload for us needing to answer many people's panicked questions and concerns because of misinformation you're propagating. If you don't want us publishing as many threads about us, take down your post.
@fabio Defending ourselves from people endlessly spreading misinformation about GrapheneOS is not aggression. Countering false marketing from for-profit companies enriching themselves from scamming people with false marketing including misinformation about GrapheneOS is not aggression. You claim that when we post accurate information about these things, it's somehow aggression. It's somehow fine for you to spread misinformation and refuse to correct or retract it but not for us to address it.
> This isn’t the kind of constructive behaviour that empowers communities.
You're misinforming people at scale with misinformation about GrapheneOS and the overall topic. You're doing the opposite of supporting actual privacy and security on mobile devices or independence from Google either. You're creating a substantial workload for us, taking away time from development and harming our ability to improve and expand the project. Using it while doing this makes it worse, not better.
@fabio If you leave up your post, we'll be publishing a detailed thread debunking the misconceptions, misinformation and the false marketing of the products which are being promoted. We'll explain the lack of privacy, security, usability and compatibility of those products along with the false marketing used to promote them. We'll explain that SailfishOS is in fact largely closed source contrary to the Android Open Source Project. Each of the products you've promoted can be addressed.
@fabio Posting accurate information to counter misconceptions, misinformation and false marketing which directly brings up GrapheneOS is not aggression. If you don't want us having to address these things then please stop creating the work for us. Your top-level post is highly inaccurate and should be taken down and retracted. We'll have to spend substantial time addressing the misconceptions you've propagated regardless of what you do now, but you could make it into much less work for us.
Purism’s devices are extraordinarily insecure.
Fairphone’s devices are marketed as having good updates and long term support but it’s not true.
These have very poor privacy and security
You see the pattern here - and also in most of the other things you publish?
I mean, from a technical point of view you’re 100% right. But does it give you the right to constantly criticize so much others who are trying to solve the same problem?
Have you even talked to some folks from Fairphone, Purism or Jolla to understand if it’s even possible to help one another?
Remember that hardware manufacturers who don’t allow users to unlock their bootloaders and companies who try to push their “Integrity APIs” are supposed to be the enemies here. Not Fairphone.
They’re not avoiding Google. Google does most of the upstream Linux kernel hardening and fuzzing work. They contribute a massive amount to Linux, LLVM, GCC and many other projects.
So by using Linux I’m not avoiding Google because Google engineers also contribute to the Linux kernel? Do you realize that this doesn’t make any sense?
You should take down the highly inaccurate post you made and publish corrections for the majority inaccuracies. Otherwise, we’ll wait for peak hours and publish a thread directly addressing the misinformation, the unsafe products which are being promoted and how those products are falsely marketed in order to scam people for profit. If you don’t want us heavily investing in writing about this then stop propagating misinformation about GrapheneOS with the clear goal of promoting those.
I had a lot of respect for you folks and for your work, but you’ve taken it all away.
I still respect your work, to be clear, and I’m still a happy Graphene user.
But I’m not sure if I respect someone who repeatedly threatens users on the Fediverse if they don’t take down their posts and spends all of their communication resources bitching about everyone else.
I have edited the post to remove the link to the article that claimed that AOSP is being dismantled because it was objectively inaccurate.
But everything else (from hardware manufacturers pulling back on unlocked bootloaders, to the Integrity API, to Google’s alarming monopolistic strategies, to the fact that relying on Google’s goodwill is a liability) is true. Why should I pull it down? And, in case you didn’t notice, I also stated in it:
Your best bet is to purchase a Pixel 9a now, before more manufacturers decide to block bootloaders, and immediately flash it with #GrapheneOS.
Why do you want me to pull it down then?
Why have you been shouting “misinformation”, “misconception”, “false news” DOZENS of times in this thread?
Why don’t you chill down and take a deep breath before hammering on the keyboard and giving everyone else the impression of a toxic bunch who hates everyone else?
Because I also said that my long-term wish is to have a full Linux phone with open hardware and mainline kernel and I also mentioned a few of the alternatives?
Do you realize how toxic you sound to anyone who reads your messages?
> You see the pattern here - and also in most of the other things you publish?
We're responding to misinformation about GrapheneOS with accurate information.
> But does it give you the right to constantly criticize so much others who are trying to solve the same problem?
They've been heavily attacking GrapheneOS for years, often in a similar way to what you're doing above. The projects you're promoting have each attacked GrapheneOS repeatedly and we've addressed those attacks.
> Have you even talked to some folks from Fairphone, Purism or Jolla to understand if it’s even possible to help one another?
Yes, we have. Fairphone and Jolla have repeatedly attacked GrapheneOS. Fairphone is closely partnered with a company engaging in extremely malicious attacks on GrapheneOS including libel and harassment towards our team. We can post archive links proving the founder of /e/ and Murena has been attacking our team with libel/harassment in the past week if you want.
> Not Fairphone.
Fairphone is a GMS partner part of the anti-competitive Play Integrity API system too.
Fairphone is the company partnered with Murena and standing by them as they heavily attack GrapheneOS with misinformation and our team with libel and harassment.
See this horrible site?
https://12bytes.org/tags/conspiracy/
Here's one of many examples of the founder of /e/ and Murena pushing harassment content from there in the past week:
> So by using Linux I’m not avoiding Google because Google engineers also contribute to the Linux kernel? Do you realize that this doesn’t make any sense?
Google is one of main companies writing the core Linux kernel. The overall core Linux kernel is primarily made by a dozen large tech companies. Google is heavily involved far beyond that. You say you want to avoid them but you're using an OS family where they're easily doing a majority of exploit protection work and much more.
@fabio The stable and LTS Linux kernels on kernel.org are a Google-funded project. Greg KH works for Google. Those kernels are heavily based around the needs of Android and specifically Pixels. Support was increased to 6 years from 2 because Google thought they needed it for the Pixel 6. It was then dropped back down to 2 because they successfully began upgrading to newer kernel branches. Other Android OEMs including Fairphone don't bother to ship most LTS updates let alone switching branches.
> But I’m not sure if I respect someone who repeatedly threatens users on the Fediverse if they don’t take down their posts and spends all of their communication resources bitching about everyone else.
We've said that if you aren't going to correct or retract it, we'll be posting accurate information to counter it. Responding to inaccurate information with accurate information is hardly a drastic move and is an explanation of how we're going to address it rather than a threat.
@fabio The rest of what you've posted is also largely inaccurate and it's completely fair for us to respond to it with accurate information. That's not toxic and it's not a threat. It's what we should be expected to do.
Multiple of the groups you're promoting are heavily invested in directing harassment towards our team with fabricated stories and blatant bullying. We've provided an example from this week:
https://12bytes.org/tags/conspiracy/
https://archive.is/SWXPJ
https://archive.is/n4yTO
> Do you realize how toxic you sound to anyone who reads your messages?
The false narrative you're pushing about us is part of ongoing libel and harassment towards our team. By participating in lying about what we've said and done, you're directly responsible for a portion of the future harassment towards our team including further violence. There have been numerous swatting attacks and ongoing extreme harassment from the communities of the groups you're supporting this way.
@fabio We can post some threads with large numbers of archive links proving the leadership of /e/ and Murena are heavily involved in libel and bullying towards our team over the long term. We have archives showing multiple Fairphone employees boosting and liking harassment content. We can similarly show that multiple postmarketOS team members are involved and have repeatedly spread Kiwi Farms harassment content. Meanwhile, you claim posting accurate info to debunk attacks on us is toxic.
@fabio If you want to talk about toxic, how about Murena leadership and Fairphone employees spreading Kiwi Farms harassment content towards our team while claiming we're toxic with no actual basis as you're doing here? You're participating in attacking us with narratives aimed at causing harm to not only the GrapheneOS project but also our team. These endless attempts at portraying us as the aggressors while endlessly calling our work a dead end and deriding is extremely tiring.
@fabio Responding to misinformation about GrapheneOS from people like yourself endlessly dismissing, downplaying and deriding our work by posting accurate information in response to misinformation about it is not aggression and it's not toxic. Baselessly claiming us toxic as part of the overall narratives being used to direct harassment towards our team and harm the GrapheneOS project is in fact what's toxic. You're trying to silence us with abusive behavior while pretending it's us doing it.
@fabio Why is Fairphone closely partnered with a company fully controlled by someone who relentlessly engages in spreading misinformation, misleading people about his products and attacking GrapheneOS with libel and harassment? Why are a couple Fairphone employees regularly boosting and favoring the content on the fediverse? Do you think it's aggressive or toxic for us to post proof of this harassment such as the example we've provided here? We can provide dozens of similar examples in 1 thread.
@fabio The reason we don't regularly post about the harassment directed towards our team is because we don't want to help them spread harassment content. A small number of people exposed to it join extreme harassment towards our team including attempts at physically harming our team members with swatting attacks and potentially other future escalations of violence. We therefore don't actually directly try to defend ourselves from it in most cases but rather just archive it and ignore it.
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/
@cyberlyra @GrapheneOS @fabio echoing the building everyone up part, those gorillas will tear us apart if given half a chance.
@joshua @cyberlyra @fabio Jolla is a for-profit company misleading people about what they providing. Their OS has extraordinarily poor privacy and security compared to the Android Open Source Project or iOS. Their own OS code is mostly closed source and there isn't an open source subset that's usable. Jolla has spent years falsely claiming the Android Open Source Project isn't Linux and misleading people into believing a largely closed source distribution is more open than an open source one.
@joshua @cyberlyra @fabio They've mislead people about privacy and security to an extreme, convincing people that a device lacking a proper sandbox, permission model, exploit protections, widespread use of memory safe language and many modern security features is more private and secure. They have their own invasive services too.
Informing people about the reality of their products is our response to years of misinformation about the GrapheneOS project from their team and community.
> We should be building each other up, not tearing each other down.
Companies selling phony privacy products which do not provide basic privacy or security patches, do not have a modern privacy/security model and do not have modern exploit or privacy protections aren't above being criticized due to portraying themselves as part of open source. They've put massive effort into misleading people about the Android Open Source Project and OSes like GrapheneOS based on it.
@GrapheneOS @joshua @cyberlyra @fabio huh, you're being pretty bloody aggressive. What exactly is your major beef?
Jolla is a for-profit company. I would expect most companies to be for-profit so as to continue operating. When has Jolla stated AOSP isn't Linux?
The OS has sandboxing and a permission model. What invasive services?
Personally I'm most interested in whether an OS can offer a beneficial experience. Given your tact against a small company, I would now rate you lower.
@Setok @joshua @cyberlyra @fabio
> aggressive
We're responding with factual information a thread with misinformation about GrapheneOS promoting an unsafe product as a better long term alternative.
> for-profit so as to continue operating.
Organizations don't need to be run primarily based on earning profits for shareholders to continue operating. An operating doing that is not putting their users first.
> When has Jolla stated AOSP isn't Linux?
It's a core part of their marketing.
@Setok @joshua @cyberlyra @fabio
> The OS has sandboxing and a permission model. What invasive services?
It has incomplete optional sandboxing a very legacy approach to a permission model.
It doesn't provide proper privacy or security patches, doesn't have modern exploit protections, doesn't have full system MAC/MLS policies, lacks verified boot, lacks secure element integration needed for working encryption for most users and more, lacks broad use of memory safe languages and much more.
@Setok @joshua @cyberlyra @fabio SailfishOS has been marketed through pretending AOSP and operating systems based on it aren't Linux. They've misrepresented what they offer as more open when their code is largely closed source. We have every right to address inaccurate claims about GrapheneOS from a company and their supporters. If people claim GrapheneOS is a dead end and worthless to promote products, why shouldn't we be welcome to respond to that with factual information about both OSes?
@Setok @joshua @cyberlyra @fabio If only these companies and their supporters were capable of marketing their products without putting down GrapheneOS, we wouldn't be talking about it in the first place. If it's happening enough then we'll make an article about it which can be improved over time and shared instead of mostly writing case-by-case responses.
@GrapheneOS @joshua @cyberlyra @fabio please point to where Jolla has made any claims about GrapheneOS.
@GrapheneOS @joshua @cyberlyra @fabio we can quibble the details, and it's up to users if those details are important. I'm sure your product is particularly safe on privacy. Second to none, in fact (it is, after all, your core value prop). But I hope you can thus admit that it is not factually correct to state unequivocally that they don't have sandboxing or a permission model (as you did).
@GrapheneOS @joshua @cyberlyra @fabio you were responding to someone who wasn't even talking about your product, and with a highly negative tone. Definitely looks aggressive.
Jolla has very obviously other goals than 'pure profit at any cost'.
I've been tracking Jolla since Day -1. Can't remember them ever talking about AOSP publicly. I'm sure I might've missed something. Their website doesn't mention AOSP anywhere. So hardly 'core'.
I feel you're merely shining a bad light on yourself here.
@GrapheneOS @Setok @joshua @cyberlyra @fabio graphene account posters please hear me: I am one of your full-throated fans... But why the HECK are you coming out of the gate all aggro?
I agree with many of your points, but have we not sent how fast attitude and arrogance can scare people off?
C'mon let's start out civil OK?
@john @Setok @joshua @cyberlyra @fabio There's nothing civil about the personal attacks being made towards our team by multiple people in this thread participating in Kiwi Farms harassment claiming one of us is insane, delusional, paranoid and more. That's ongoing on the SailfishOS forum which is linking here where people are referencing harassment content.
Jolla should do something about their forum being used to direct hate towards us with false claims and personal attacks towards our team.
@GrapheneOS @Setok @joshua @cyberlyra @fabio did any of he people in this thread do those things?
Post a link here if they did, I want to know!
If not, don't alienate more folks OK?
@john @Setok @joshua @cyberlyra @fabio
> did any of he people in this thread do those things?
Yes, our statements have been repeatedly misrepresented and lied about here. Our team has repeatedly been personally attacked, including references to ongoing harassment. Here's the SailfishOS forum thread directing people here:
There are multiple posts there making personal attacks with libel/bullying using one of our real names and referencing harassment content.
> 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.
> I understand there are a lot of purity tests in F/OSS.
SailfishOS is closed source. It's not a small portion of their code that's closed source but rather most of the code that's specific to it. It has no equivalent to the Android Open Source Project. There isn't a subset of the OS without their proprietary services, etc. but rather it's only usable as a closed source project building on open source ones. The open code is the Linux kernel and other stuff from elsewhere.
SailfishOS objectively has extremely poor privacy and security compared to the Android Open Source Project. It's a fact.While I wholeheartedly appreciate your providing sources to your arguments, saying "It's a fact." doesn't make them any truer.
On the contrary, in my opinion it is detrimental to your argument, because that statement not only means nothing, but is also often used by people who don't have any meaningful evidence and reach for this to falsely 'reinforce' their position.
I suggest omitting statements like these, and just presenting information supporting your claim. (Like you already do :))
Anyways, just thought I'd share.
Keep up the great work!!
@me They're stating something as if it's a fact when it's the other way around. People can find lots of places to read about how mobile operating systems including the Android Open Source Project and iOS moved to a much more private and secure model for applications and the OS itself along with heavily hardening it against attacks compared to desktop operating systems. They're far from perfect but they're much better than desktop OSes. The topic has been AOSP, not Google Mobile Services Android.
They're stating something as if it's a fact when it's the other way around.It is, indeed, often the case.
Regards~
![[?]](https://chaosfemtw.files.fedi.monster/accounts/avatars/113/774/540/108/444/816/original/91df9bdad88a32d2.png)
![[?]](https://media.infosec.exchange/infosec.exchange/accounts/avatars/111/282/881/834/880/460/original/1256379fb887bfe9.png)
![[?]](https://cdn.masto.host/mastodongamedevplace/accounts/avatars/115/585/008/875/521/606/original/213edabad8525153.jpg)
![[?]](https://cdn.masto.host/mastodongamedevplace/accounts/avatars/109/293/102/962/600/037/original/3cc38ea5d7090565.png)
![[?]](https://trains-official.eu/files/584c5102-8c1e-4f60-86b0-d63764ea7fad.webp)
![[?]](https://files.mastodon.social/accounts/avatars/109/256/498/642/901/778/original/55592df60384fb7e.jpeg)
![[?]](https://fedi.666666420.xyz/files/webpublic-86978155-33d2-42a2-8a4f-071d25794ef1.png)
![[?]](https://files.mastodon.social/accounts/avatars/000/039/207/original/972a88b4292b90af.jpg)
![[?]](https://files.mastodon.online/accounts/avatars/108/194/113/592/119/036/original/de91fb7f7e33fbf5.jpg)
![[?]](https://diaspodon.fr/system/accounts/avatars/000/062/366/original/e9e03a1546395d07.jpg)
![[?]](https://files.functional.cafe/accounts/avatars/000/028/056/original/db7f6886229ca6c5.jpg)
![[?]](https://s3.v5.yokai.cafe/blobcatfiles/b9a9c3b0473e34e98394dd89db7d56e6ebdc17d55aee147cdd9252dc522fb8e7.webp)
![[?]](https://social.vlhl.dev/media/1c22c422a931cc354becf41803fc444339d76cb7bd45f6158b93f374da9673ed.jpg)
![[?]](https://media.mstdn.social/accounts/avatars/000/293/265/original/e1f9455b9463c337.jpg)
![[?]](https://hessen.social/system/accounts/avatars/107/563/777/355/832/623/original/a9925f7e45a93f88.gif)
![[?]](https://media.haz.pink/accounts/avatars/111/070/892/665/450/553/original/ccf45c51e2daf3ba.png)
![[?]](https://cdn.masto.host/floss/accounts/avatars/109/129/003/918/936/187/original/bdd9fdc335b00516.png)
![[?]](https://is-a.cat/system/accounts/avatars/108/216/665/500/594/474/original/fc6273639ed7abe5.jpg)
![[?]](https://assets.chaos.social/accounts/avatars/000/082/271/original/63ec5c65f20c33ec.jpg)
![[?]](https://media.infosec.exchange/infosec.exchange/accounts/avatars/109/327/540/940/053/921/original/cbe5c5d93f8edb3a.jpg)
![[?]](https://pcdn.mastodon.com.pl/accounts/avatars/115/238/452/641/349/772/original/c3e39937d9159145.png)
![[?]](https://pol.social/system/accounts/avatars/110/394/901/928/545/366/original/b57ec6007edc1526.jpeg)
![[?]](https://gts.chimera-linux.org/fileserver/01A71J5YG4QW98CSGP6W2082EV/attachment/original/01KAC3FP0AR33812WJF1GZQQ1F.png)
![[?]](https://cdn.hosted.spacebear.ee/sb-53d788bcd8441bb97cfb7a64f2552521/accounts/avatars/109/331/059/732/420/534/original/6ee41c3fffb95318.jpg)
![[?]](https://files.mastodon.social/accounts/avatars/000/028/257/original/b707847cdbe52b17.jpeg)
![[?]](https://cdn.masto.host/glitterkittencouk/accounts/avatars/000/000/001/original/a53be675e7fc137c.jpg)
![[?]](https://cdn.masto.host/floss/accounts/avatars/109/256/806/202/191/660/original/38fa8ce5d8972556.jpg)
![[?]](https://files.mastodon.social/accounts/avatars/115/704/064/172/906/068/original/40557d365ac3f056.jpg)
![[?]](https://media.mstdn.social/accounts/avatars/000/148/272/original/2a2f1c1f0b428022.png)
![[?]](https://static.manganiello.eu/manganiello-social-media/e793b081ae62b526111b68aa58716cfb1933e61978454ebcb43cf797ee1c30aa.png)
![[?]](https://grapheneos.social/system/accounts/avatars/109/415/078/265/909/169/original/c74b93c7870e37a0.png)
![[?]](https://cache.treehouse.systems/accounts/avatars/110/628/855/321/239/565/original/02818afb40ed82f7.jpeg)
![[?]](https://cdn.masto.host/hooraycomputer/accounts/avatars/114/022/566/916/394/080/original/60354a95d0ffbd26.jpeg)
![[?]](https://cdn.hosted.spacebear.ee/sb-ed3c34ca02ab8b2b6d74c8f71352ef68/accounts/avatars/109/321/441/812/404/144/original/82e7044f7689ffe2.jpeg)
![[?]](https://cdn.masto.host/vyrsesocial/accounts/avatars/109/429/110/572/904/358/original/035bbd19c8eb7783.png)