the initra mf
@me@doasu.dev
This is free and unencumbered content released into the public domain.:3 () { :3 | :3 & }; :3 >:3 # >:3c
76 following, 19 followers
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)
~ % _
local trans woman comes up with a type ending in>>>>>>, forgets aboutFrom<T>
for context, I opened a pull request with Arc<SyncRwLock<HashMap<TxnKey, Receiver<Option<Result<send_transaction_message::v1::Response>>>>>>
Quote in September last year for a high-memory compute server. £28,000.
Quote today for the _exact same machine_. £90,500
This is for medical research. Saving lives. When I say LLMs are killing people by killing research computing, this is what I mean.
@davidgerard.co.uk @edzitron.com
If you're on LinkedIn and are thinking about verifying your account with them, maybe read this first. It walks through LinkedIn's privacy disclosure to identify 17 companies that may receive and process the data you submit, including name, passport photo, selfie, facial geometry, NFC data chip, national ID #, DoB, email, phone number, address, IP address, device type, MAC address, language, geolocation etc. Unsurprisingly, it seems the biggest recipients are US-based AI companies.
https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
people think LLMs are good at rubber duckying and dont write down their thought process or talk to a rubber ducky like bro you could save the tokens
save the planet buy a duck
Alright fedi, just got back from the Nix Store, ended up buying /etc/nixos#nixosConfigurations.Infini-FRAMEWORK.config.system.build.toplevel
Three years ago I blogged about #nuget serving outdated #curl packages.
They then removed the packages I found.
I checked nuget again *today* and immediately found a nine year old curl package that is downloaded at the rate of 1,000 times/week from there... with **64** known vulnerabilities.
The blog post from back then: https://daniel.haxx.se/blog/2023/03/02/the-curl-nuget-story/
"Microsoft is no longer accepting new submissions through secure@microsoft.com. Please use the Microsoft Researcher Portal "...
😠
but I took it to the big generic security portal and submitted a report there. Let's see what happens.
My not at all surprised face: "After careful investigation, this case has been assessed as not a vulnerability and does not meet Microsoft's bar for immediate servicing."
@bagder our own IT team are running Office 2016 in a sensitive environment.
Why would MS be any better. 🙁
@bagder For NuGet packages, there's beyond "contact owners" also the Report package option, which goes to NuGet support. But found mileage to vary there, too. If you got a package id, I could try to back-channel it. NuGet gallery have option to bot unlist, mark as deprecated, and security advisory.
@bagder Have you considered if there's a demand for vintage curl releases that you aren't serving? Give the people what they want!
@bagder I've using dotnet for a few years and wanted to try using Curl but didn't find anything that wasn't poorly maintained or totally outdated.
@bagder @shanselman responded to the bluesky mirror of this post.
@bagder
Have you considered reserving "Curl" prefix on NuGet?
https://learn.microsoft.com/en-us/nuget/nuget-org/id-prefix-reservation
It is not much but it would prevent random people from uploading "officially looking" packages.
Charity Auction for Kansas Trans Folks and/or Minneapolis ICE Relief.
Related to my 1 April Kickstarter.
No offense: I would have expected a bit more creativity from you. This is a bit too... thick.
I mean, I already know that you are a void where money can be thrown at, in order to magically make books on mental self torture (such as mailservers) pop out.
I will ofcourse happily help any action against those deranged, inhumane lunatics that is ICE.
But that dark rectangle representing that void misses a bit of subtlety.
@h3artbl33d you're projecting. any subtlety I possess is an artifact of your imagination, sorry.
@mwl
Is it in the Epstein files? That black looks familiar.
@xinit as the caption says: the photo is a hint
@mwl Hey, this is a Donald Trump book. Quite sure because his identity is often redacted with a big black rectangle ! This April 1st book titled “Savaged by system Trump” is indeed very creative.
think i finally found a feature that #systemd has that i actually need
so apparently #GNOME's wayland session, when run via GDM, does not read the user's .profile to update its environment variables and such -- the X11 session used to do this, but the #wayland one doesn't
on systemd, it is possible to specify user-wide environment variables with files in the ~/.config/environment.d/ directory
and there seems to be no equivalent for that in #AlpineLinux or its #OpenRC init system
@rnd how does it work? this is probably easy enough to build
gnome doesn't want openrc [...], sadlysome context, for those interested:
~ @navi@social.vlhl.dev
We're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support.
https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/
@GrapheneOS can you already tell if pixel 11 phones will be supported? I'm really looking forward to this collab but just want to know what we can expect.
@GrapheneOS Great job!
Btw you can get ready for answering flood of questions about why Motorola smartphone department belongs to a Chinese company called Lenovo.
@a53bdb We'll continue to have Pixels as an option.
@GrapheneOS I think you got me wrong…
@a53bdb @GrapheneOS now you can decide whether you're more worried about US backdoors or Chinese backdoors Honestly at this point the latter is probably more trustworthy
@lunareclipse @GrapheneOS @a53bdb US-based companies have thousands of published backdoors already. I don't recall many Chinese products which were found to have been shipped with backdoors. 🤷
There's a whole lot of them and they routinely get compromised and added to botnets later in their lifecycle.
@lispi314
There's a *big* difference between "sloppy security that eventually gets pwned" and "deliberately backdoored by a nation-state for the purpose of domestic mass surveillance"
@GrapheneOS @publicvoit @a53bdb @lunareclipse
@JamesDBartlett3 @lispi314 @GrapheneOS @a53bdb @lunareclipse I agree.
I consider the USA as the premium example for the latter. 😉
@publicvoit @JamesDBartlett3 @lispi314 @a53bdb @lunareclipse People have different opinions. We're going to work with Motorola to meet all of our security requirements and improve security beyond that. They're helping us with providing GrapheneOS support for their devices rather than us having to do the work ourselves. They may end up contributing more to GrapheneOS beyond that too. In the future, we can work with other OEMs. It's not an exclusive partnership but we have limited resources.
@a53bdb @GrapheneOS To be fair, all phones are made there so that risk always exists anyway.
As long as GrapheneOS doesn't slack on their requirements including (but not limited to) being able to access low level stuff it shouldn't be much worse if you flash the phone yourself. And those kind of requirements are why Pixels where the only ones supported to begin with...
@Cambion @a53bdb @GrapheneOS What do you mean? There are huge companies that do not manufacture their phones in China. Samsung does it in Vietnam primarily.
@NewDay14 @a53bdb @GrapheneOS
Many off the important parts are still made in China before it's shipped to other places the phones are made. There is no going around that. Beside, Vietnam is not much different when it comes to this...
@Cambion @a53bdb @GrapheneOS Samsung is the best company when it comes to independence. Samsung produces their displays, batteries, cameras, and processors in South Korea mainly. If the goal is to minimize dependency on China and the US while still obtaining high-quality products, Samsung is the clear leader in that field. However, they are likely so large that they wouldn't be interested in a partnership.
@NewDay14 @Cambion @a53bdb Motorola contacted us about working together and we enthusiastically pursued it. We would do the same if Samsung wanted to work with us. Our Motorola partnership is explicitly a non-exclusive contract. There would need to be another company wanting to work with us and capable of meeting our requirements for there to be another partnership though.
@GrapheneOS Oh yes! Thank you! Just in time after OnePlus started to do strange things with their OS.
@GrapheneOS Tell them to fix the misspelled "GrapehenOS" tag at the bottom of their article. :)
...unless there actually are some grape hens in the pipeline. Hey, no kink shaming!
EDIT: Looks like it's fixed as of now.
@GrapheneOS @debacle hopefully with better longterm updates than current motorola phones... then im in!
@da_habakuk @debacle Motorola Signature (2026) already has a 7 year update commitment but doesn't quite meet our requirements yet. The future devices with GrapheneOS support will be even better than the improvements they already made for their 2026 flagships.
@GrapheneOS @da_habakuk @debacle And the Signature looks like a nice phone. I would love to carry a 2027 Signature with Graphene.
@GrapheneOS
As I understand the article, this will be aimed at corporate customers. I am hoping they will also sell to individuals and that the non-corporate customers will not have the analytics feature or it can be turned off. Motorola's problem has always been OS support. If GrapheneOS is handling support, it is a win for everyone.
@BoloMKXXVIII Devices with official GrapheneOS support will be available to individuals. Look at the Motorola Signature (2026) which was close to meeting our requirements but not quite there yet. Motorola Razr Fold (2026) is another example. It has to be 2027 because not everything was ready yet and a lot of work is needed on support for GrapheneOS too.
@BoloMKXXVIII The analytics feature is for their mobile device management system and their own operating system, not GrapheneOS. GrapheneOS is a separate thing from their operating system. They're both adding official support for GrapheneOS and using a small subset of GrapheneOS features to improve their own operating system. They could add support to GrapheneOS to their MDM but that wouldn't involve us adding any invasive integration for it in GrapheneOS. We wouldn't do something like that.
Good news. Can you at least reveal whether some of the devices will be at the lower end of the price range, like e.g. the "…a" Pixels?
@katzenberger It will start with flagship devices but their flagships tend to be priced cheaper than flagship Pixels. More devices will be supported over time. It should be expected it will start with only flagships though. Look at the Motorola Signature (2026) and Motorola Razr Fold (2026) for an idea of the kind of future devices it would start out supporting.
Please try to get a mid-range phone also supported.
Pixel a series at least in Germany is basically thrown after people having a phone included in their mobile network contract, so you can get a current a series half a year after release for 300 € in Germany. Considering the remaining 6.5 years of support by Google, this is an insanely good price for a long lasting and secure phone.
@GrapheneOS This is great news.
I hope there will be a Pixel 9 Pro form factor equivalent as well (the Signature is a bit larger than I like).
But primarily I hope this will secure funding and development for GrapheneOS.
Well done and congratulations!
@GrapheneOS would these Motorola devices that would run graphene be able to run custom builds of graphene as well?
@GrapheneOS does this mean i will be able to get a degoogled motorola device in the future?
@lumi GrapheneOS is based on the Android Open Source Project which doesn't have Google apps and doesn't use their regular services. It only uses Google as a provider for very basic standard services which we replaced in GrapheneOS.
The purpose of GrapheneOS isn't specifically avoiding Google apps and services but rather providing a high level of privacy and security in general. Using Pixels is not in any way counter to our goals. We want official OEM support, lower level hardening, etc. though.
@lumi @GrapheneOS TL;DR: Yes.
@lumi @GrapheneOS Well, as degoogled as using an OS maintained by Google gets
@alexia @GrapheneOS yeah, ofc the end goal is using a proper linux phone, to get maximal freedom and security but having a degoogled android device is a step along the way. though i have been stuck at that step since around 2014
@lumi @alexia GrapheneOS and the Android Open Source Project are Linux distributions. We strongly disagree with the premise that glibc, systemd and GNOME are preferable to the much more private and secure AOSP software stack. Moving to the desktop software stack would be a huge regression for nearly everything we care about and focus on improving. It's already possible to run desktop Linux apps in GrapheneOS including GUI apps via the hardware virtualization support and there's a desktop mode.
@navi @lumi Where's the application sandboxing, memory safe languages, modern exploit protections, deep integration of powerful hardware-based security features and everything else we focus on in GrapheneOS?
Aside from any of that, the concept that the Android Open Source Project isn't a Linux distribution is wrong. Linux isn't the userspace software that's largely portable to other operating systems. There was a Debian variant using the FreeBSD kernel which is clearly not Linux.
How was that ever considered reasonable? Astonishing and appalling.
@lispi314 @lumi @navi It takes 50 minutes to make a completely clean build of the OS on a $500 Ryzen 9950X gaming CPU. It then takes seconds to do incremental builds for nearly all changes. What's the issue with that and how is it appaling? It takes far longer to build a modern web browser than Android. Incremental build speeds are what actually matters for most development builds. It's release builds where the clean build time matters more to avoid trusting to quite robust incrementa builds.
@GrapheneOS @navi @lumi That doesn't take away from what navi said. Either way. What of the concern that AOSP might not be open anymore at some point? The whole ecosystem is being closed down. I think that's definitely a genuine concern. What's your plan when that happens, if you can disclose? Will you maintain a fork of AOSP with Motorola, or by yourselves? That's kind of what I would like to know so I can feel reassured that there's a future for the platform even if Google further alters the deal.
@GrapheneOS @navi @lumi let me disagree here. Android is fork of Linux.
Fork with huge change-set - hard to review.
With drivers written to "get to market fast", not quality.
With other closed drivers in userspace to avoid open sourcing.
Naaaah, this ain't Linux I'm running on my laptop.
I won't argue — security features of AOSP may be superior. But what runs beneath these features isn't!
> let me disagree here
Okay, but you're objectively wrong.
> Android is fork of Linux.
No, Android isn't a fork of Linux. Android works fine with mainline, stable and longterm Linux kernels from kernel.org. It doesn't have any required downstream patch set.
> Fork with huge change-set - hard to review.
It's not a fork and has no required changes to the kernel.
> With drivers written to "get to market fast", not quality.
Hardware vendor drivers aren't Android.
> With other closed drivers in userspace to avoid open sourcing.
That's not part of Android and is in no way required to use it. Desktop Linux distributions ported to the same hardware nearly entirely relying on the same drivers regardless.
> I won't argue
You're just making objectively inaccurate claims to promote massively rolling back privacy and security by moving to legacy desktop software. Replacing vendor drivers has nothing to do with that whatsoever.
> No, Android isn't a fork of Linux. Android works fine with mainline, stable and longterm Linux kernels from kernel.org. It doesn't have any required downstream patch set.
Show me one vendor of phone shipping clean kernel. One.
Hardware vendor drivers are part of Linux I use, are you implying Android != Linux? 😉
@navi @GrapheneOS @lumi hate seeing people fight over this as if sandboxing is something that can never be made freedom-respecting. i consider it a distinct lack of imagination not to re-evaluate and seek to virtualize OS interactions which impose relatively generic models of trust and access that are heavily overloaded in the standard linux userspace and cannot be simply reused
@GrapheneOS @lumi @alexia No low level access for a dev = Not a Linux OS (only RIP Windows Phone™ offered that)
@GrapheneOS @lumi @alexia firstly, don’t see this as an attack on GrapheneOS (it’s great what you are doing), but I believe the aim of Linux-based projects like #postmarketOS is to achieve (more) independence from the manufacuters in terms of software/driver support. Sure, ultimately this may require open-source hardware, but it’s nice to dream. I find these projects valuable, even if they aren’t quite there yet. (And yes, I know you could also just incorporate these open source drivers once they are available).
@GrapheneOS Currently things are fine with Android but Goigle keep moving toward making Android more locked from software and apps. Is not this going to be a problem to what we have now? or there is a workaround?
@GrapheneOS @lumi @alexia I'm excited for GrapheneOS success for people it's for, but I fundamentally don't like the Android (AOSP, not even talking about Google) model of how basically anything works. Non-Android mobile OS options are what I want. Ones where I have full root, can run a small set of trusted apps from my distro just like I would on a laptop, and where everything else runs in an extremely restricted sandbox. I don't want those relationships inverted where a gigantic pile of Java code I could never understand or build or modify is the root of authority and I just have to trust that it's going to let me do what I want.
@dalias @lumi @alexia GrapheneOS has to get huge adoption and major partnerships before we can start on our much longer term goals of moving away from using a Linux-based OS as the core operating system to a more secure platform. We want to be running the current application layer part of the OS solely via virtualization eventually. We don't expect to ever make the Linux kernel and overall model it supports on top secure enough for our goals. We'll still need the AOSP-based OS for apps.
@GrapheneOS @lumi @alexia The current default software stack for desktop Linux is kind of terrible and the lack of coherent threat model or proper ecosystem of sandboxed applications are major issues with desktop right now. What I am still questioning is whether it is even possible to make a proper competitor to ChromeOS (if we ignore the hardware insecurity of basically all PCs).
So example software choices:
systemd -> dinit or s6
sudo -> s6-sudo (setuidless)
glibc -> muslc
glibc malloc or jemalloc -> hardened_malloc, malloc-ng, or mimalloc-secure (which supports more CPU architectures)
bubblewrap (sandbox used by Flatpak) -> #syd (it's written in Rust, has many important exploit protections, and can even be the user login: https://gitlab.exherbo.org/sydbox/sydbox)
GNOME or KDE -> XFCE (when their new Rust Wayland native WM is finished)
gnutils -> *BSD or uutils
The issue of course with most of these alternatives is that they are separate projects and therefore dont have the same goals, methods, or threat models. Also most of these projects are written in C which does not help at all. Also there is of course the lack of a proper chain of trust from the hardware to loading the kernel and userspace.
It may just not be reasonably possible to provide a alternative without millions of dollars of funding and a decade of development. It would be nice for there to be an alternative to AOSP/ChromeOS or even MacOS for desktop computing which actually takes security seriously. It doesnt even need to have be completely on par when it comes to security, just do better than current Linux distros (not a very high bar).
What are your thoughts on what to do in case the day comes that Google kills AOSP?
> systemd -> dinit or s6
Lots of these are giving up even more security features.
> hardened_malloc, malloc-ng, or mimalloc-secure
These aren't the same classes of allocators at all. Neither the musl malloc or mimalloc is a hardened allocator. mimalloc is performance focused and musl's is focused on low memory usage.
> What are your thoughts on what to do in case the day comes that Google kills AOSP?
What about when IBM decides to kill systemd, GCC and GNOME?
@GrapheneOS @King_of_Ooo @lumi @alexia
What about when IBM decides to kill systemd, GCC and GNOME?
systemd
Between GNU Shepherd, supervise-daemon and runit? 
GCC
You'll have to explain why/how IBM owns GCC. Fairly sure it's an actual FSF project.
GNOME?
RIP lol 
Other than the accessibility stuff most of it I don't care much about, and with the ensloppification going on & Red Hat apparently insisting on it, it might well die anyway.
What are your thoughts on what to do in case the day comes that Google kills AOSP?
This however has real chances of happening and already has a largely closed development process with no community.
Which means it doesn't even need a poison pill contributor agreement, all the necessary rights are probably already in Google's possession for malicious license changes.
Not to mention that the main useful part of Android, the drivers & their documentation, aren't even included anyway. Everything else could be replaced by something better with some work.
@lispi314 @King_of_Ooo @alexia @lumi AOSP has a far larger development community than desktop Linux. There are a huge number of both corporate and community AOSP-based projects. There's a massive community of people working on all kinds of projects related to it. Desktop Linux is assembled out of a bunch of barely maintained or developed projects with one of two developers each. It has nearly non-existent systemic work on almost anything aside from systemd gobbling up components into itself.
@lispi314 @King_of_Ooo @alexia @lumi systemd won not because it's good but because it actually exists as a somewhat coherent basis for an OS providing the features which are wanted. It didn't have to be a sensible or good implementation of almost anything. It's far from only an init system and the overall desktop and server ecosystems are increasing based around it. All the non-tiny desktop Linux stack ports to mobile are heavily using systemd. They're bringing systemd to mobile, not Linux.
@GrapheneOS @King_of_Ooo @alexia @lumi You know, if you're just going to avoid the question you could simply not answer that post, like you did with my mobile modem isolation question.
The overwhelming majority of the BSD tooling that isn't systemd could be ported with a modest effort if systemd died. Note that I linked daemon supervisors earlier, because session managers and init systems are a lot easier to come by.
edit: Ah, my bad, I confused the subthread. You did ignore it and replied to the prior post.
@lispi314 @King_of_Ooo @alexia @lumi
> You know, if you're just going to avoid the question you could simply not answer that post, like you did with my mobile modem isolation question.
Don't know what you're talking about. You're one of hundreds of people.
> The overwhelming majority of the BSD tooling
It has little to do with the desktop software stack. That increasingly only has an incomplete port over to BSD with a growing amount of hacks. It would just roll it back even further.
@GrapheneOS I know it's probably never going to happen, but if I could get a Razr with GOS on it, I would literally do a backflip.
@GrapheneOS Aaaand buying a used Pixel is off now. HYPED!
@blindcoder It will be 2027 so you might still want to buy an older Pixel to use GrapheneOS in the meantime.
@GrapheneOS Awesome news.
Going to a shop, buy a Motorola with GOS pre-installed is a dream.
Although the installation process is super smooth and not an issue, but for some it is.
I wonder if you have the man power to support pixel (as stated below) and Motorola hw.
I also have no clue what it means to the limitations google tries to implement for developers in autumn….
This is great news, now convince my banks to develop their mobile applications for Graphene OS and I think I found my new phone....
@GrapheneOS
As a Motorola phone owner, this story of collaboration between the mobile phone brand and GrapheneOS is very good news indeed.
How soon can I ad GrapheneOS to my current phone, or will I be able to afford a new one?
@Guillotine_Jones You'll need a new device since their current devices and upcoming 2026 devices don't meet our requirements. It will be 2027.
@GrapheneOS
Thank YOU, GrapheneOS, for taking the time to respond to my query.
Now I have even more reasons to like you guys and to be interested in your work and products.
@GrapheneOS Hope this is the start of collaborating with phone manufacturers to create all kinds of GrapheneOS compatible devices.
@GrapheneOS This deserves a "GOOD NEWS EVERYONE!"
Also, will it be possible to load Graphene on my own? In case Motorola pushes some bloatware I don't want :-D
@GrapheneOS b2b- so does that mean it's only available for business customers, or will regular end users also get to run Graphene on their Motorola devices?
@GrapheneOS such great news! Motorola was the OEM I had been secretly hoping you guys would partnership with. From Motorola's press release it seemed as though they may be adopting some aspects of GrapheneOS into their own skin of Android. Am I understanding that right?
@GrapheneOS finally no more 23W max charging speed and pixel errors (literally lol). Hoped for Nothing/CMF because of their awesome techy Designs and they are europe based but i guess Motorola was nice in the past atleast.
Oh and dont forget that overheating issues when charging or doing stuff, especially in summer.
Also if you have a protective case, stickers and privacy screen protector it heats up even more and charging speed drops to 3W or even less. Pixel 8 is not great except the camera
@GrapheneOS please comment on this
According to publications in Israeli media from December 2023, the Motorola smartphone devices have been used by the Israeli military in fighting inside the Gaza Strip.
very cool news!💙
i'm shopping for my next phone & looking for an OS OS - Open Source Operating System. The article doesn't mention when the GrapheneOS Motorola phones come out
When will they be on the market?
i have the incredible LG ThinQ Dual Screen (technically tri-screen) which is hands down the coolest phone EVER, but LG stopped making phones
i'd like to see the foldable #Motorola in #GrapheneOS
@GrapheneOS Great news! My only gripe is that afaik Motorola's phones are pretty big but that seems to be the trend for the entire smartphone market these days. Still rocking my 6.1 inch pixel 8a with grapheneos!
Ooohhh...that is promissing news!!!
My first phone ever was a Motorolla.
If they provide official Custom Rom options: i am so in!
@GrapheneOS Although i congratulate you and Motorola/Lenovo for the initiative, i'm a bit concerned about what will happen to GOS because let's be honest: Motorola is a company, not a charity. What's their ROI on that? Just reputation? Also considering that they announced data analytics and their own "security" tools in one breath. Will it only count for business phones or will the phones be shipped with preinstalled software in the future? I hope GOS will also run independently of Lenovo tools.
It looks like motorola could show itself and sell "secure entrprise grade" cellphones.
Which deciders could enforce employee to use as their authenticator or a small computer that doesn't leak internal company data.
I see value there. It's the same customer target as thinkpad
Well, let's see how that turns out. I'd be a potential buyer for sure. I'd welcome the security but if it becomes a similar data sink like Google, just with a different endpoint, then nothing's gained.
It then just would be the same sh*t, different flies.
Let's wait until the first joint release comes out. I'm very hopeful and cautiously enthusiastic. GOS also has a reputation to uphold and i'm hopeful that they wouldn't just sell their soul because of corporate money.
@Brokar @tuxicoman It's going to be the same GrapheneOS supporting additional devices with official support and collaboration from the OEM. They're going to benefit through selling many more devices and we get more high quality devices meeting our security requirements which we can properly support. It should also be a lot easier for us to support than Pixels because they're going to be helping us a lot. Most of the work still needs to be done, but it's a serious partnership already.
@GrapheneOS I am so happy and I look forward to seeing this partnership develop. I feel like it also is an amazing thing for Motorola to make themselves unique.
Google's announced destruction of android except as completely controlled by google has shocked us, and reduced independent app makers, secure phone makers to writing begging letters to billionaires.
Lenovo, laptop king who also sells those laptops cheaper without Windows, using linux, is PARTNERING to sell a LINUX PHONE!
Lenovo sells phones under the Motorola brand name. (Lenovo brand phones sound more marketable)
This FANTASTIC news, express interest, build this. Buy one soon
@GrapheneOS Will the bootloader be unlockable and relockable with user keys like the Pixels or will they just come with Graphene preinstalled with no way to do that?
@luana It will fully support using other operating systems including users making their own builds of GrapheneOS. It's part of our hardware requirements. We'll likely be able to make hardened builds of firmware and drivers which can be released in an official way for easy builds without needing to extract anything from the GrapheneOS or Motorola OS factory images.
@luana @GrapheneOS Motorolas have always had unlockable and relockable bootloader, so I wouldn't expect this to change.
@dalias @luana Our hardware requirements include supporting using verified boot and other features with non-GrapheneOS operating systems too:
https://grapheneos.org/faq#future-devices
> Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)
That applies even if the device has official GrapheneOS support with green verified boot state. Green verified boot state isn't mandatory of course but we'd like to have it. It could differentiate with a better UI.
@luana Yes, that's part of our hardware requirements:
https://grapheneos.org/faq#future-devices
Whether they'll be sold at retail with GrapheneOS preinstalled as an option isn't a question we can answer yet. It mostly comes down to Google's requirements and the extent to which those can be worked around or pushed to be relaxed.
@GrapheneOS Congratulations on the partnership!!! Looking forward to trying out the new devices. Let me know if your need any help.
@GrapheneOS Congrats on diversifying from Google phones! With Google tightening control of their ecosystem, it's good to have more options.
For geopolitical reasons, I'm also hoping that a European manufacturer will join your example.
@superblox There are essentially no European manufacturers. Their phones are white labelled Chinese ODM devices where they have little input into it. That stops them from meeting our requirements in practice unless the ODM happens to meet all of them on their own since the OEMs selling those devices don't get much input into the low-level development. They're stuck using the platforms which are available with surface level changes such as choosing a display and the enclosure design.
@GrapheneOS What will Motorola (and you) do, when Google shuts the door on an open-source Android? And will this collab impact your support for Pixel phones?
I trust @GrapheneOS but Motorola's 'operational insights' worries me...
#grapheneos #motorola
@greenpete That's about mobile device management software, not anything in GrapheneOS or relevant to it. It isn't relevant to the hardware, kernel, drivers or firmware. It's just an MDM app. Their MDM app could potentially supported being installed and used on GrapheneOS for companies which want to use it. Many companies want something like that to deploy fleets of GrapheneOS devices. We want to have our own open source one and maybe they're interested in that too.
@greenpete I don't think that matters because we can always install GrapheneOS to replace the pre-installed OS with Motorola software. The hardware is what's important to GrapheneOS and to us.
@joe9nf It's the hardware I'm worried about...
@greenpete
This has always been my fear. I don't doubt @GrapheneOS has the best of intentions but I had always been concerned that they could start manufacturing Pixel phones with hardware much like a BMC can monitor a system without the OS being aware of it and it's not like you can remove the battery from a Pixel. There's also the issue of not wanting to give Motorola/Google my money.
@joe9nf
@GrapheneOS i had bought a new moto in 25 in the hopes calyxos wld run on it, but i didnt pay enough attention and my new device was not supported and calyx went on hiatus. i guess ill require a new moto again for grapheneos support, but im kind of sick of moto now and i guess ill go with a crappy spec overpriced linux phone in the future and hope things eventually get better
@GrapheneOS Does this mean that the phones will come with a option to have GrapheneOS pre-installed or just officially supported and has to be installed by the user?
@GrapheneOS : with all the split and sell-off, which motorola are we talking about?
The one sold to Google? The lenovo division? Another entity?
@ploum Motorola Mobility, which was split off in 2011 then bought by Google in 2012 and then sold to Lenovo in 2014.
@GrapheneOS Congratulations!
My inner skeptic, though, would like to know what compromises GrapheneOS was asked to make. And what expected bullying you can expect from Motorola once the ink on the agreement is dry.
I know I seem cynical, but I can't see a large corporation acting with complete good faith.
@GrapheneOS I checked the specs of Signature and Razr and noticed they have Dolby Vision support. When 2027 models do get supported by GrapheneOS, will it include Dolby Vision Support as well?, I ask because DoVi is proprietary.
Motorola is not known for making great phones. They're the budget phone company that abandons their devices as soon as possible. 🤦
@linux_is_best Motorola's high end phones are well received including having top tier CPU, GPU and camera performance. They already started providing lengthy support and the GrapheneOS support will have better updates than the stock Pixel OS similarly to what we already provide for Pixels. The whole point of the partnership is that no existing non-Pixel devices meet our requirements and an OEM needs to work with us to improve their devices to meet all of our standards for us to support them.
@linux_is_best Motorola Signature (2026) is one rank ahead of the Pixel 10 Pro XL in https://www.dxomark.com/smartphones/ and has far better CPU and GPU performance via the 1 step from highest end Qualcomm SoC. The future devices we end up supporting have a high chance of using the highest end Qualcomm SoC.
It's not their ultra low-end budget devices which are being worked on. Their high end flagships for 2026 are close to meeting our requirements but not quite there yet so the next gen is what's relevant.
When Motorola tells us they will provide X years of updates — let’s say, for argument’s sake, seven years — we will likely receive seven updates. We will lag behind on security updates for months. Bugs will be discovered, reported, and well documented, but never addressed. Most of their battery drain will come from their own bloated Motorola apps, and there will be many.
I wish you had chosen any other provider. Really — any.
@linux_is_best No, that's not how it's going to be at all. GrapheneOS is going to have our own updates and we won't have to depend on the stock OS updates being released. We already provide security updates months before Pixels. You know we already had all of the March 2026 updates for a while before today's release, right? We have a lot of the June 2026 and later patches already. We're shipping them way earlier than anyone else and will continue it. We'll ship Qualcomm, etc. stuff on time.
@linux_is_best You seem to be missing that the reason we need a partnership is because there isn't a single non-Pixel OEM providing what we need on their own which we could simply use without collaboration as we do with Pixels. We need them to work with us and give us what we need to provide the level of updates and security GrapheneOS is expected to provide. We can't support their devices without this because we need more than what's available without a partnership. That's the whole point.
Anyone can disprove your statement by visiting any social media group surrounding Motorola -- you're pick. I, would direct you to Reddit's subreddit for example https://www.reddit.com/r/motorola
@linux_is_best Subreddits where people go to complain and obtain help with problems are filled with that. Pixel subreddit is filled with it and it doesn't mean they're bad devices or that people have significantly more problems with them than other devices. You can't compare it to somewhere like the Apple subreddit where it's heavily downvoted or even not allowed. It's not a meaningful way to obtain information about it. Pixels/iPhones also don't have the very low end budget devices...
@linux_is_best It's not the very low end devices with low quality components, low build quality and short support time which are relevant to us at this time. Those are too far from meeting our requirements. It's a partnership which will be initially focused on the devices comparable to the flagship Pixels. Once the better security and updates trickle down to lower end devices we can begin supporting those but we won't start doing it until it does. If people go with budget they know it's worse.
@GrapheneOS
It's very hard for me to believe that a corporate partner won't find a way to enshittify this. That's what's for-profit corporations do. It's why I was attracted to GrapheneOS in the first place - to get away from corporate enshittification.
@tom It's a non-exclusive partnership and we're going to continue supporting Pixels. It's going to result in us getting early access to code which will substantially help us beyond this. They're going to be doing a lot of the work on supporting the devices so it's going to be far easier than if we did it all ourselves. We negotiated a good agreement where we both benefit a lot from it. They're going to sell a lot of devices because of having GrapheneOS support and won't be losing anything.
@tom We could eventually have other OEM partnerships as there's nothing exclusive about it but they have the huge advantage of being first. No other major Android OEM has gotten in touch with us and we're going to have our hands full with this for a while now. The reason for them wanting to have more secure devices with far better updates and GrapheneOS support is to make money. It's quite straightforward and everyone benefits. Showing how viable it is will get more OEM interest in GrapheneOS.
@izzy They'll be flagship Snapdragon devices. Look at the Motorola Signature (2026), Motorola razr fold (2026) and Motorola razr ultra (2026) for examples of the current generation devices which don't quite meet our requirements yet but are very close. They moved to providing some level of updates for 7 years for these. The next gen will be better and meet all our requirements. One of those requirements is getting everything we need to match or exceed Pixel updates for drivers/firmware, etc.
@izzy 7 years of support enables used devices to act as great budget devices with far better support and security than actual budget devices. That's what's already happening with Pixels where the Pixel 8 and later have 7 years of support. Pixel 8a and Pixel 9a are past gen budget Pixels so there are great deals but there's plenty of support remaining. People who can't afford the devices new can get the same devices after a few years with plenty of support left. It sidesteps a lot of issues.

@izzy Snapdragon 8 Elite Gen 5 is currently the only SoC meeting our security requirements on paper and would need a LOT of work to meet them in practice. It has MTE support on paper but that's different from it being properly integrated and all the issues with it for broad usage in the kernel and userspace resolved.
MediaTek doesn't have everything we need and also has a very poor track record on security compared to Qualcomm. It wouldn't really be usable any time soon for GrapheneOS devices.
@izzy Pixel 8 and later have 7 years of support from launch. There are already great budget devices for GrapheneOS via used Pixel 8a and used Pixel 9a devices. Pixel 10a is about to launch and 10th gen flagships have been out for a while so there are good deals for those but plenty of support left. The concept of budget devices isn't really necessary if enough people keep moving to new devices and putting their old ones on the market as used devices in good condition. Battery replacements help.
@GrapheneOS will these be graphene specific Motorola devices or regular ones you can flash with graphene os?
@GrapheneOS So as I understand there's going to be a Motorola OS and as alternative GrapheneOS. A few questions:
1. Who holds the signing keys for the GrapheneOS variant?
2. Will I be able to buy a second hand Motorola-OS-edition and flash GrapheneOS? Will it then show a warning (I think it's called yellow boot state)?
3. Will this have any effect on safetynet? Probably not right, since it's not/can't be Android certified?
@pixelate @GrapheneOS Will talkback be included on these devices? I'm looking forward to this, if Talkback is included somehow.
@GrapheneOS This is the best news I've heard recently. Atleast now app developers will ditch the Google Play Integrity crap and provide first class support for alternative platforms.
@GrapheneOS really hoping this is gonna be cheaper than a pixel at current prices cause that'll probably be a killer for me if a graphene OS phone costs 900 dollars
@GrapheneOS Good news. I think u guys should partner with Asus too. They have good hardware & I heard that Asus is going to stop making more phones. So why not partner with them and start selling with ur OS
@GOKUSHRM Our partnership is Motorola is not exclusive and we're fully allowed to partner with other OEMs. However, we don't currently have the resources to partner with additional OEMs and it will likely be a while before we do.
Partnerning to make smartphones with a company which recently discontinued their smartphones doesn't sound workable. The point is also mainly getting an OEM to raise their security to meet our requirements rather than getting an OEM to sell devices with GrapheneOS.
@GOKUSHRM We're not going to lower our standards to expand device support so if they can't or won't meet the requirements then there's not much to talk about. That's why most of the smaller OEMs are ruled out because they can't afford or are at least unwilling to invest in the required security including long term updates and a high end SoC. The device itself doesn't have to be high end as a whole but the SoC needs to be high end to get long term support and the current era security features.
@GOKUSHRM SoC licensing is very expensive especially for the latest and greatest. No one really wants to use a flagship SoC in anything but a flagship device.
@GrapheneOS Will you be able to include custom applets in the secure element, such as the duress PIN?
@GrapheneOS Any chance for an open source firmware or will be just another company where we can get GOS, with no advantages over Pixels?
@GrapheneOS Looking forward to seeing where this partnership takes the project. It's been great watching continued support of the Pixel line of phones, so throwing in an official partner organization is exciting.
@GrapheneOS
I don't care if it's shit, I don't care if it's 1500€, I'm getting one.
Ideally more than one if it's on the budget end.
A budget Moto G at the 150€ mark with GrapheneOS would be the ultimate "if i'm under risk this is becoming a foldable".
@bill88t The initially supported ones will be expensive flagships but we do want to have budget devices eventually. It's harder to meet our update and security feature requirements for those. Look at the Motorola Signature (2026), Motorola razr ultra (2026) and Motorola razr fold (2026) for an idea of how the next gen devices will likely be. These current gen ones are way closer to our requirements than previous devices but not quite there yet.
@GrapheneOS given that Moto will have to release new devices with the support, I really hope to see something "small" - iPhone 13 Mini / SE size, for less than 1000€... One can dream.
@arathunku What do you think about the moto razr ultra? We can realistically support their 2027 flip device.
@GrapheneOS my worry is about durability. A small debri when folding it and it's game over. I love the idea of ThinkPhone, just needs a small variant! Durable, secure and small.
@GrapheneOS @arathunku Best decision ever, in my town portability is a must when buy new devices. Please do!
@GrapheneOS
If they #Motorola could add #LoRa or something similar that could be a game changer.
They would offer something that other companies don't, while there is demand from users.
It also brings privacy advantages as it makes it easier to communicate undetected from cell towers. People are starting to roll out networks covering wide areas.
In addition to that, it adds an element of resilience where people could continue to communicate even when cell towers are shut down. This is especially important during national disasters and governments overreach shutting down internet access.
@GrapheneOS
This is a premature joke for the 1. April, right? 😳🤔😂🤣
Choosing a company like Motorola with it's owner Lenovo behind it for the reasons of privacy and security isn't beyond a good idea but pure hypocrisy and a punch in the guts for all of the supporters of GrapheneOS in my opinion. 🖕
Greed ate brain, happened again it seems. 🤮
#GrapheneOS #Motorola #Lenovo #Privacy #Security #Hypocrisy #Joke
@kranzkrone GrapheneOS is a non-profit organization and no money is changing hands with Motorola. What do you think greed has to do with it? There's huge demand for us supporting an alternative to Pixels and we're doing that by working with an OEM. If you want to continue using Pixels then you can continue doing so. Google and Samsung are the only top 10 Android OEMs by sales which aren't Chinese-owned. We can't force Samsung to want to partner with us and the same applies to Sony too.
@GrapheneOS
The point isn’t whether GrapheneOS receives money from Motorola.
The point is the consistency of the security and trust model you advocate! 🙄
GrapheneOS often emphasizes minimizing trust in large corporations, opaque supply chains, and potential state influence.
Yet Motorola is owned by Lenovo, a Chinese company operating under a legal environment where state access to companies can be mandated.
If the argument is that users should minimize trust and maximize verifiable security, partnering with an OEM embedded in that jurisdiction raises legitimate questions.
This isn’t about “greed” but about coherence of principles.
If Chinese OEM ownership is usually framed as a risk in privacy discussions, it seems inconsistent to dismiss those concerns when it becomes convenient for hardware support.
Criticism here isn’t hostility—it’s asking whether the same standards are being applied consistently. 😉
@kranzkrone It's quite apparent you're using an LLM to generate concern troll replies. It's incoherent and lacks actual substance. We're not going to be interacting with a text generator someone has directed to waste our time and energy.
If you don't want us banning your instance and making a public post asking everyone else to do the same then remove both of these AI generated replies and stop bothering us.
Here's our policy on AI generated content for discussions:
@GrapheneOS
It's indeed quite apparent that you acting out in the same way like you did in the past when the founder of GrapheneOS had a personal dispute with another somewhat prominent personality of the tech world.
If you don't want me to further investigate your toxic behavior of communication and try to framing me as the bad one, you should definitely thread lightly.
Threatening me with whatever action won't result in deleting my previous posts but instead will strengthen my personal investment in further interactions and maybe legal actions.
Louis Rossmann may would find this interesting to read too.
I'm fine to end it here by agreeing to disagree.
@kranzkrone You've moved on from posting low quality concern trolling which appears to be at least partially generated by an LLM to blatant libel and support for harassment. We haven't framed you for anything. Your replies to our thread make it clear what you're doing.
Louis Rossmann orchestrated harassment towards our founder by making many extraordinarily dishonest claims in a video where he engaged in blatant bullying. Rossmann is openly a Kiwi Farms user and is the one who involved them.
@GrapheneOS If I may ask, as various sources say otherwise. Will there be one dedicated model with GrapheneOS out of the box, and will the rest of the models be hardware-ready for installing this system? Or is hardware support and manual installation the only option?
Will the phone be officially shipped to Brazil? The only reason I didn't get a Pixel was because it didn't ship here.
@libresoftwarelover The phones will be available in Brazil at least to install the OS yourself. We aren't sure about the availability of devices with it preinstalled yet since it's very early and we don't know which barriers may come up for that and whether it could launch in some regions but not others.
@GrapheneOS any chance that we'll have Google wallet support?
since the bootloader will trust the grapheneos keys I can't imagine why would safetynet and the other play protect mechanisms won't pass attestation (for all intents and purposes graphene would be indistinguishable from the stock Motorola image)
if that's the case I'll buy the device the moment it comes out...
@dzervas It's not going to change anything about the Play Integrity API which would be an entirely different thing. It should be able to have a green boot state (not necessarily immediate at launch) but that doesn't mean that Google Play is going to allow it because we won't have an allowlisted build fingerprint.
@GrapheneOS oh damn
any remote chance that Motorola could help with that?
@dzervas Potentially but it's not something we want to bring up right now rather than focusing on adding GrapheneOS support, meeting our hardware requirements and getting some additional security features implemented. The main way they could eventually help is getting app developers to add support for using GrapheneOS either by removing the Play Integrity API (idealy) or adding hardware-based attestation permitting GrapheneOS as a replacement or alternative to the Play Integrity API.
@GrapheneOS come on baby, we are here just to buy a linux phone to develop great tools, free as freedom !
@GrapheneOS Will the 'ready for' (desktop mode) function work? This is a Motorola feature that I wouldn't want to lose after flashing the ROM. I once bought a Motorola specifically for this function.
Narrator voice: "A common initialism in gamer culture, GG is shorthand for 'good girl' and is widely used for praise"
a detail you probably didn't know: nowhere in any #curl documentation do we use the word "very". It is a banned word enforced by a CI check. This rule encourages us to rewrite and instead use more appropriate words. Makes us write better English.
@bagder What if you wanted to document your rule against using the word?
@gruber the rule is generic: we have a list of banned words and expressions. We don't need to specifically mention the words in that list! 😀
@bagder @gruber
Full list is here in case anyone else is curious like I was:
https://github.com/curl/curl/blob/master/.github/scripts/badwords.txt#L84
I can tell you that this bites me just about every time I write more than two sentences. Then I go back, edit and push a fixup commit and hope that I learned something. Again.
@bagder I also block "just" this way, and "easy"
@derickr I'm actually currently in process of doing the same for "just"!
@bagder @derickr you might be interested in a tool like https://vale.sh (or a more minimal, but js based, https://alexjs.com).
Vale has many rulesets to improve the writing style/make all docs consistent.
@bagder this reminds me of a teacher I had. Every time someone said "like" as a filler word, he yelled "LIKE!!" back at us. It was like very effective.
![]()
» 🌐
@p@raru.re
my English teacher banned the use of the word "just" in most contexts
"I was just xyz..." for instance
redundant
@bagder
@bagder for a non-native speaker, what exactly is not good with the word 'very'?
@shaman007 it is too simple. There is almost always a better way to phrase the same thing without it. very happy = excited, very glad = thrilled, very hungry = starving, etc. So the use of "very" is a sign that it can be said better.
@bagder l need to wrap my head around this, never thought about it before.
@bagder @shaman007 IMHO for technical documentation: simple is better. BTW. Some spellcheckers can help you write better style before even saving the text.
@bitnacht @shaman007 in a distributed world where everyone uses their own tools and editors we need the checks in CI anyway. Those are the rules that bind us all.
@bagder @shaman007 I just don‘t think this example will either increase your productivity nor help the people reading the paragraphs in question. But if it makes you happy: keep up the enthusiasm.
@bitnacht @shaman007 Writing coherent and good documentation is a huge task. Avoiding a single word is just a tiny little bit of that and will of course in itself not make much of a difference. But I am convinced using coherent, proper and easily read language helps users. So we try to do that.
@bagder @shaman007 100% agree. And it is true that if you are forced to go over a text for a second time, you are likely to find ways to make it clearer and more concise along the way. So I see your point now.
@bagder yes, I remember that meme from a few years ago. It's the kind of stuff techbros would do to feel superior. Do you also try to say "thank you" instead of "sorry"?
@bagder is there a tool you’re using for this? I didn’t see it mentioned in the replies. I remember using something called Alex to do this in the past.
and now I'm about to drop all uses of "just"... https://github.com/curl/curl/pull/20793
@bagder
./curl$ grep "\bjust\b" -iIr . | wc -l
569
@LangerJan yeah, it took some editing to get rid of those. It was not as easy as just deleting them all...
@bagder agree when it is used to imply that something is simple, quick or trivial (when it may not be to all people).
Disagree otherwise tbh, it’s basically a synonym for “only” in most other cases, which is pretty harmless? Maybe I’m not following.
@bagder I still find myself using it frequently, but I'm training myself to rethink things when I hear myself use it. I've taken the position that using it usually means that I've made some assumptions, or oversimplified something, and I need to go back and look for them.
@bagder
I'd kill use of 'seems', 'got' and lowercase 'get' while you're at it. Probably 'have' and 'has' too.
Do I like my documentation very precise and unambiguous? Yes! Do I manage that? Not consistently.
I would appreciate a weasel word filter for vim so that I consider my written form with the precision and specificity that it deserves.
Oh! And 'like'. 'Like' can do one.
@bagder "surely I don't... argh"
24 match: stb.h
4 match: stb_connected_components.h
1 match: stb_c_lexer.h
3 match: stb_divide.h
4 match: stb_ds.h
1 match: stb_dxt.h
1 match: stb_easy_font.h
1 match: stb_herringbone_wang_tile.h
2 match: stb_hexwave.h
20 match: stb_image.h
36 match: stb_image_resize2.h
1 match: stb_image_write.h
1 match: stb_rect_pack.h
2 match: stb_sprintf.h
4 match: stb_textedit.h
6 match: stb_tilemap_editor.h
8 match: stb_truetype.h
14 match: stb_voxel_render.h
& 56 "very"
@bagder as someone who used to develop accessibility solutions by and with people with disabilities, thank you.
@bagder let’s do “simply” next? https://github.com/curl/curl/pull/20822
@bagder Having a language model review and suggest simpler language for documentation is maybe worth exploring?
@bagder
I was taught by DAG that "clear"/"clearly" is in this category too. Either something is clear, and the word is redundant, or it is not and it is a false claim. Extra red flags about a politician claiming something as "absolutely clear".
@bagder Nice! William Zinsser would approve!
Incidentally his celebrated book "On Writing Well" appears to be downloadable from archive.org and it's a must read. It changes lives.
(PDF Download link:)
https://ia800207.us.archive.org/2/items/OnWritingWell/on-writing-well.pdf
RE: https://grapheneos.social/@GrapheneOS/116159602850585685
The problem is grapheneos is militantly anti-copyleft which means this doesn't bode well for the project's long-term sustainability. I hope I'm wrong but eventually the shoe will drop.
We're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support.
https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/
> The problem is grapheneos is militantly anti-copyleft
We're hardly anti-copyleft but rather mostly choose to use permissive licensing for our projects. We've chosen to use GPLv2 with certain required additional permissions (similar to the Linux kernel) for Vanadium to protect it against something which was happening. We mostly use permissive licensing since we wanted our security improvements to make their way upstream and to be broadly adopted. We care a lot less about it now.
@purpleidea We no longer care much about getting improvements upstream or broadly adopted outside GrapheneOS. We'd happily start using GPLv2 for more code. We're not going to include GPLv3 code in the OS itself though. We have no problem with GPLv3 code in apps we can include in our app repository but packaging a bunch of stuff is not a focus and we prefer having a separate project handle most of it right now.
What is the problem with us choosing the licenses which are the best fit for us?
@GrapheneOS I love the idea of what you're doing but if you are building a community, the licensing terms are its constitution and copyleft is the promise that you won't enshittify down the road. The other security goals are not your primary mission.
As a child, I thought the lesson of history was that the good guys always win. As an adult, I realized the actual lesson is that the winners declare themselves the good guys.
This year counts as #curl 30 years, counting from the first httpget 0.1 release in November 1996.
I'm thinking we could fly a special logo for the occasion on the #curl front page throughout the year.
Maybe *you* can make one that looks festive and still confident and trustworthy?
To trigger some thoughts, here's my take:
@bagder "When we first published curl 30 years ago, we removed some of today's options as they would have been too overwhelming for new users."😌
@bagder I think the number 30 and 1996-2026 shouldn't be used together since both referring to same thing, and makes it noisy. Writing "30 years" to one of the corners with smaller size than curl is okay, to me. My personal opinion.
KDE supports the "Keep Android Open" campaign
#Google will cut off independent developers to #Android if they do not register with Google first. This will kill independent platforms like @fdroidorg and severely impede FLOSS devs from creating apps for Android.
Many KDE apps are deployed for Android: KDE Connect, Itinerary, Tokodon, and there's even a test version of Krita for Android.
KDE calls on Google to reverse course and @keepandroidopen.
Spread this post and, if you are the maintainer of a software project with versions for Android, please join us and sign the open letter:
@kde @fdroidorg @keepandroidopen Do you really think a company that lick the boots of a fascist dictator will give a damn about this open letter, let alone the openness of its own products?
@Stem @kde @fdroidorg @keepandroidopen Perhaps, but what does it cost to try?
It costs a missed opportunity to give more appropriate advice: stay away from google and use more private community forks of android that if I understand correctly will not be affected by googles papers please app ecosystem.
A strategy focusing on begging tech giants to not do the will of capital is basically lying to the public that there is a chance this can work.
In theory yes the open letter is a nice thing to have regardless of how google reacts because then we have something to point to how google is ignoring public opinion - but it needs to be presented with heavy caveats and we need to focus on getting average people out of googles grip so they don't hold this much power over us
Oh! We agree. That's what @plasmamobile is all about. However, realistically PlaMo is not ready for the general public yet, despite how hard we are working on it.
If we could get the sort of support regular Plasma has, the story would be VERY different. But PlaMo is still niche.
@kde @olivenolje @plasmamobile
I hadn't heard until Plasma Mobile until now, I had only heard of the pinephone one. I am excited to hear more about the project development in the future!
@ambiguous_yelp @kde @olivenolje @plasmamobile AFAIK the pinephone is the hardware (that can run plasma mobile or another interface) and plasma mobile is the software (that can run on the pinephone or on another device)
@PerryPeak @ambiguous_yelp @olivenolje @plasmamobile
The preferred test hardware is OnePlus 6 and 6t these days.
@kde @ambiguous_yelp @plasmamobile Would more donations significantly help the project?
Or is the limiting factor the lack of contributors?
@olivenolje @ambiguous_yelp @plasmamobile
Very much both. Also finding more hardware support. In that respect, we must not forget about the great work the people at @postmarketOS are doing! They help us get PlaMo on to more phones, giving us more space in which to grow.
@kde @fdroidorg @keepandroidopen Don't let Android devices become a closed operating system, I strongly oppose it!
@kde @fdroidorg @keepandroidopen Maybe let's port lineage OS and Ubuntu touch to more devices and let Google stagnate like the pond it's become? 🤔
@kde @fdroidorg @keepandroidopen Not to be rude, but as an average user/developer what's the issue at stake here?
@kde @fdroidorg @keepandroidopen
Apple and Google, 2 choices for apps from where we sit, and both are partners in crime. END MONOPOLIES. Capitalism has become extortion when conglomerated.
Tear everything apart and build it from scratch, the entire system has been subverted to evil.
@kde @fdroidorg @keepandroidopen It's time to have a Linux Mobile 100% functional as an alternative to Android.
@kde @fdroidorg @keepandroidopen How does Plasma Mobile fit into this? I thought Plasma Mobile positions itself as an alternative to Android, so I'm wondering why we don't hear much about it.
@okias @fdroidorg @keepandroidopen
It does. Albeit, many end users will find it hard to install and with not as many features or the stability of Android.
We are working hard on it and it has come a long way, but it may not be the drop-in substitute many users will be looking for quite yet.
The Cards Against Humanity people know how to play the room.
why does the anker 250w charger have wifi
@kouhai to download firmware updates. because of security vulnerabilities found in its internet connectivity module.
My favourite piece of internet today is the theory that Jesus was actually a type of yeast.
Turns water into wine
Floats on water
Makes bread for 5000 people
Put in a cave for 3 days and lo - he has risen!
Jesus was a sourdough starter.
Also this would imply: We should be calling him 'Mother' not 'Father'
I will not verify my identity or age for any online service, other than clicking on an "I am over 18" button, ever. I will simply stop using the service, if it is required.
I encourage you to do the same. It's not "for the children". It's to harvest even more information from you so corporations can try to squeeze even more money out of you and to be able to track you and everything you do.
anyone using RustDesk selfhosted in production? How's your experience been?
@oxyhyxo I’ve recently been looking into it and I’m currently reluctant because from what I can tell there’s no way to lock down access to specific clients. It’s either all or nothing. I.e. anyone can just connect their client to my server and use up a licensing spot. Official response: “why would anyone do that, it won’t benefit them”
Which got me to believe security might not be their priority no1 in general.
[1]: https://rustdesk.com/terms/
CC: @can@haz.pink @oxyhyxo@bsd.cafe
RE: https://techhub.social/@theoasisbbs/116086098666934794
I've been idly thinking about porting UNIX to the Color Computer 3 or Commodore 64.
There's a lot of PDP-11 assembly in the early releases which would need to be ported to C, though several were later rewritten in C. The assembler was ported to C in V8 and with all the time I've spent reading all its versions, it wouldn't be difficult to adapt it for a different architecture. But all the peripherals would be different, so I'd need to write a bunch of drivers. UNIX V7 or later would probably be easiest, as it had been generalized for porting at that point.
Someone wrote a UNIX-like OS for the TI-99/4A!
https://forums.atariage.com/topic/380883-unix99-a-unix-like-os-for-the-ti-994a/
Today is I love Free Software day, a day to thank all the people behind Free Software <3
At // foss.events we like to send a big thank you to all the people who help organise and running FOSS events throughout the year because creating healthy communities is just as important and sustainable as developing software!
Check out the map by @fsfe to find a #ilovefs event near you:
https://mapforge.org/m/11171656
And don't forget to connect via official hashtag(s): #ilovefs
On #IloveFS day, "This week in Plasma" brings the news that...
Plasma 6.6 is nearly ready for shipping! Look out for it next Tuesday.
... And videos in Plasma 6.7's SDDM login screens can be previewed in System Settings, KWin dialogs have been overhauled and polished, and much more.
https://blogs.kde.org/2026/02/14/this-week-in-plasma-finalizing-6.6/
Wishing everyone a great time at I Love Free Software Day happening now in Warszawski Hackerspace in #Warsaw, #Poland
Find out more on
https://hackerspace.pl/
#foss #floss #freesoftware #opensource #events #europe #ilovefs @fsfe