the initra mf
@me@doasu.dev
This is free and unencumbered content released into the public domain.:3 () { :3 | :3 & }; :3 >:3 # >:3c
82 following, 23 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)
~ % _
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
@GrapheneOS Oh yes! Thank you! Just in time after OnePlus started to do strange things with their OS.
@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
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.
@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.
@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 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.
@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.
@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
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! 😀
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 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
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?
@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 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
Can’t wait to find out how this upgrade enhances my dishwasher’s performance.
At least it’s not adding new AI features, I guess…
8941dc91-867e-4412-afd5-4698d32477be:t_blink: » 🌐
@someone_else@infosec.exchange
@dan
- "My dishwasher is on the internet!"
- "Why is on the internet?"
- "To download software updates!"
- "Why does it need software updates?"
- "To fix security vulnerabilities!"
- "Why would it have security vulnerabilities?"
- "Because it's on the internet!"
Fun fact: in the last three months, Continuwuity has gone from 300 to 900 publicly-discoverable deployments. 25% of all new Matrix deployments are Continuwuity.
It's only a 10-month old project! That's crazy. It's not what I expected to happen with a side project I picked up at the end of my second year at uni with a bunch of random internet people when I wanted my strange IRC/discord/whatsapp replacement to keep working.
Thanks so much for all the support! At this point, I should be taking a break - but I know that I'll sneak in a few features into the upcoming releases that the wonderful team & community we've built will be making. It's a project we built to be bigger than any one person from the start, because it's a part of so many people.
Got reminded today how awful DRM can be. Huge thanks to @mwl for selling ebooks without it — I’m happy to pay for books, just don’t make me wrestle with Adobe IDs. Thanks for keeping it simple, Michael!
It's Paczki Day!
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.
@thalia The late Steve Hosgood built a (single-tasking) 6809-based 6th edition Unix "OMU" (One Man Unix), this might be interesting for the CoCo 3 port. OMU was later also ported to 68k-based systems.
Alan Cox put up a copy of the tarfiles on github:
@me_ Interesting. UNIX is so versatile! I had assumed it was a derivative of Research UNIX, but it's a fresh kernel. Some utilities like ed were ported from UNIX V7 sources, but omitted from the release. If I ever do this, I'd make a port, not a reimplementation.
@thalia There's so much crazy Unix-related stuff - I just found Retro Unix, a Unix kernel written in nasm assembly for 8086 and 386.
"Retro UNIX 8086 [...] has been developed by Erdogan Tan as a [...] derivation of original UNIX v1 [...].
Source code has been ported from PDP-11 [...] to Microsoft Macro Assembler [...] and original unix source code has been modified for IBM PC/AT compatibility [...], without [...] removing original UNIX v1 multitasking [...] features."
@me_ Fun! This reminds me that I've also thought of porting PDP-7 UNIX to the PDP-1 to run on a PiDP-1. I've also been working on porting UNIX utilities with compatibility modes for all versions to Rust. So many things to do!
@thalia Please keep us updated - all of these sound like great projects! Perhaps you can motivate some of your students to support you? I have a bit of a hard time finding students interested in OS hacking here in Bamberg, unfortunately...
@me_ I’m just a grad student and although I’m a TA for the xv6-64 OS class, no one except my grad student friends come to my office hours, haha.
These are weekend projects for me. My current is porting the PDP-11 assembler to Rust, supporting all versions in its lineage, and pedantically replicating bugs, except for those with non-determinism. I’m making good progress.
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/
@thalia There's also a port of 6th edition Unix to the TI990, the minicomputers from which the TI99/4A's TMS9900 CPU was derived...
Plasma Setup has had its first release, as part of KDE's Plasma 6.6 release! I'm so excited for people to start using it 🎉 😁
https://merritt.codes/blog/2026/02/17/2026/_plasma-setup-release
i got fired 😕
#getfedihired
over 30% of devs got the boot.
hit me up for #frontend #wcag #accessibillity #css #semanticWeb #informationArchitecture #solutionArchitect #componentLibraries
😳any help and pointers much appreciated. Primarily Oslo hybrid.
We've just released Continuwuity v0.5.5. Continuwuity is a chat server for communities that speaks Matrix - and as you can probably guess we've exploded in popularity over the past week or two. The amount of people in our community rooms doubled!
This release is mostly about bugfixes, but there are two things to get excited about. The first is that the last blocker for calling in the Element X mobile apps has been squished! If you've set up the prerequisite service, you can now make calls from your phone.
The other is that we've greatly improved the first run experience - registering a first account is easier, and contexual help is presented where possible.
I would heavily encourage reading the changelog, and upgrading. Again, welcome to all of our new community members!
https://forgejo.ellis.link/continuwuation/continuwuity/releases/tag/v0.5.5
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
kde needs to expand its branding outside of just software. i suggest we start with produce. we need kogurt, kheese, frozen kizza, vegekables, etc. this is how we will get mass user adoption
RE: https://meow.social/@chirpbirb/116014711339837040
We might not have frozen kizza in the store, but we have a lot of fancy accessories and clocks 😍
https://www.cafepress.com/shop/KDE
Hear @bagder , Founder of The cURL project, discuss the rise of AI Slop in open source on @redmonk 's MonkCast. As one of the most vocal #oss maintainers confronting this issue (curl recently ended its bug bounty program due to the surge of low-quality AI submissions), Daniel offers a candid perspective on what AI code generation means for maintainers, contributors, and the future of open source: "it's important to not get stuck on the AI part but on the abuse part." https://redmonk.com/videos/daniel-stenberg-ai-onslop/
I SWEAR piracy is easier than buying games on steam i swear to god
@navi what settings do you use to run signalis wo piracy :(
Anyone wants to run a web forum with me?
I'm thinking of somewhere where we could talk about our projects, get inspired by others' work and generally keep eachother sane.
It's probably a bad idea but...
@q3k did you know about https://forum.malleable.systems/ ?
@jackdaniel Nope. I can't stand Discourse, but I guess it's proof that something like this could work.
@q3k I built this 'Virtual HackForge' thing a few months back at https://vhf.dragonhive.net which has (matrix-backed) chat, a forum, a project gallery, tool library and much more. it's opensource and anyone can host it. though it should be said i did use a fair amount of LLM assistance to create it, even though it's got a completely decoupled architecture (so it's easy to remove parts) and made a lot of unit tests and such. but haven't really dared to advertise it so far
@anthropy That's a super cool concept! But it's not what I'm really looking for, I want a damn 00's/10's forum. :)
@q3k that's definitely a mood, good old phpBB and such!
I wonder if there are modern comparable alternatives to it. I wouldn't mind helping with it honestly, I'm a bit busy and all over the place, but I'm happy to help where I can
@anthropy The software hasn't gone away, you can still just host phpBB or even (over)pay for IPB (https://invisioncommunity.com/buy/self-hosted/).
@q3k seems like there are a lot of other options still alive as well: https://alternativeto.net/software/phpbb/?license=opensource&platform=self-hosted
it's neat to see these still living 10-20 years later lol, I recall playing with a lot of these, like Vanilla, SMF, MyBB, NodeBB, etc
@q3k I wouldn't mind running something like that (I already run a legacy MyBB forum for an old project), but I'm kinda worried about accessibility, specifically on mobile.
Things like Mastodon and IRC have a protocol that you can build a client for. All forum software that I know just has a web interface, and one that sucks ass on mobile. And if it's a pain to use... then people aren't gonna use it. :/
@siguza I think excluding (or penalizing) mobile users might actually be a good thing? It would prevent this from being a site you doomscroll or otherwise feel compelled to interact with in short bursts. I would like most interactions on that forum to be done by people sitting comfortably at a computer and being able to put time into their thoughts.
Screenreader accessibility is another thing though, definitely would want to find something that works well in this regard.
@q3k I guess I'm worrying more about the moderator side... it's bad enough when you get spam in GitHub issues and the "block" button is rendered off-screen on the mobile website... 🙄
@siguza Right, good point, that's something to triple check before making a decision.
@q3k on my old MyBB forum, the way I deal with spam is to put users with 0 posts into a user group whose posts need manual approval. And if they reach a post count of 1, they're auto-promoted to a group that doesn't require that anymore. This has caught 100% of all spam since at least 2020.
But yeah, specifically usability of mod tools... though that ServeTheHome forum looked like the UI was at least usable on mobile, so maybe the mod tools are too?
@siguza Very interesting approach.
Not sure what STH uses for software, didn't see any 'Powered by' in the footer, would be curious to know.
But I also really like the look of MyBB (at a glance), much more than phpBB/SMF. Do you have any other complaints about it, other than the moderation issue? Because so far I _think_ it's the highest on my shortlist of software to try.
@q3k not really... feature-wise it's been pretty good. There are some features (like star ratings on posts, or user reputation) that I'd disable today, and I'm not sure whether you can do those by default? But I'm 99% sure you could with a plugin.
Only thing I'm not sure about is the development process... if you wanna look at https://en.wikipedia.org/wiki/MyBB#History_and_development
But I imagine other forum software isn't gonna look much better there...
@siguza I'm more than fine with hacking in/out features as needed and maintaining a patchset over some stock software. I think customization is what makes these things fun and creates unique communities.
Yeah, I've seen the slowed down release cadence, not great... but as long as it's not super full of security holes that need regular patching then I'm probably fine with that? And as far as I've read up, MyBB seems to have an ok track record in this regard.
@q3k my brain instantly went to phpbb3 (as we used to do it in the 2010s) but that's far away from user-friendly and doomscrolly
@q3k I would very gladly join one!
I've been thinking about setting up a forum on and off for ages; shit, just yesterday I've talked about that with some friends, lol. I don't think I'm a great person to *run* a forum, but I do miss all the "cool" places online I used to visit bakc in the day. I want a place to see others talking about their projects, and to talk about what I'm working on too.
Are you using #Codeberg to host your favorite AI-assisted and otherwise vibecoded project because your desire for dopamine has utterly destroyed your willingness to learn new things? Do you neither care about how you're "flooding the room" of the free software ecosystem nor about the greater societal implications, insisting that "it is what it is"?
Check out #GitHub, the world's most popular AI-first platform! Copilot, annoying maintainers with slop, you'll fit just right in!
d1d7c7d7 (sophie (the one with the blue profile picture)) [any] » 🌐
@sophie@social.translunar.academy
What do people usually say on here? I don't want to be rude
@ivy@sk.girlthi.ng do you want a fediverse etiquette crash course ?
@evening@alico.nexus That'd be lovely!
@ivy@sk.girlthi.ng okay so the most important rules are: things that need content warning: things that are commonly put behind content warnings (but it varies / it's less of an obligation): other than these rules, the community is very welcoming and friendly. you can post whatever you want, people will follow you if they want to see it.
- always use content warnings when posting things that require content warnings
- add alt text to images (especially when posting on public)
- don't be a bigot (but I don't think I need to say that)
- try not to boost posts that break these rules
- the obvious (sexually explicit content, gore... )
- kink
- politics
- sensitive or heavy subjects, discussions of prejudice or bigotry
- physical and mental health
- food (especially meat)
- selfies. specifically eye contact
- posts that are long / not screen-reader friendly