1,748 karma · joined March 23, 2016
aspe:keyoxide.org:VCUCH7HSNW3ZCAQWTMUZKAXFQ4
[1]: https://grapheneos.social/@GrapheneOS/117194007157499435
Unfortunately some of those Swype nicities are patented [1], so other keyboards can't use them.
Caveat here being that GitHub is exploring charging a usage-based fee for self-hosted GitHub Action runners [1]. While they've halted it for now, it's something worth being aware of as you assess your costs. This is probably a drop in the bucket compared to the order of magnitude savings you've described.
[1]: https://github.blog/changelog/2025-12-16-coming-soon-simpler...
[1]: https://github.blog/news-insights/company-news/an-update-on-...
prune-local = "!git fetch -p && for branch in $(git branch -vv | awk '/: gone]/{if ($1!=\"\*\") print $1}'); do git branch -d $branch; done"
1. Fetch the latest from my remote, removing any remote tracking branches that no longer exist2. Enumerate local branches, selecting each that has been marked as no longer having a remote version (ignoring the current branch)
3. Delete the local branch safely
That being said, here's a repo of popular licenses that have been modified to restrict such uses: https://github.com/non-ai-licenses/non-ai-licenses
IANAL, so I can't speak to how effective or enforceable any of those are.
I joined a Zed hackathon at RustConf 2024 where I built the "Open in split" functionality from the file fuzzy picker. A member of the engineering team who was floating around helping folks had us exclusively work through the included collaboration features. It was a great tour of the editor, and did not feel tacked on.
> On Oct. 15, the Post heralded the military's push for a new generation of smaller nuclear reactors. "No 'microreactor' currently operates in the United States, but it's a worthy gamble that could provide benefits far beyond its military applications," the Post wrote in its editorial.
> A year ago, Amazon bought a stake in X-energy to develop small nuclear reactors to power its data centers. And through his own private investment fund, Bezos has a stake in a Canadian venture seeking nuclear fusion technology.
and
> Three days after the nuclear power editorial, the Post weighed in on the need for local authorities in Washington, D.C., to speed the approval of the use of self-driving cars in the nation's capital. The editorial was headlined: "Why D.C. is stalling on self-driving cars: Safety is a phony excuse for slamming the brakes on autonomous vehicles."
> Fewer than three weeks before, the Amazon-owned autonomous car company Zoox had announced D.C. was to be its next market.
Edit to respond to your edit: these are the opinion pages, not reporting.
[1]: https://openssf.org/blog/2025/09/23/open-infrastructure-is-n...
> The technology that underpins this initial version of secure backups will also serve as the foundation for more secure backup options in the near future. Our future plans include letting you save a secure backup archive to the location of your choosing, alongside features that let you transfer your encrypted message history between Android, iOS, and Desktop devices.
Someone had to make a decision as to when the updated app would ship. They did not make a wise choice.
[1]: https://wezfurlong.org/wezterm/config/lua/keyassignment/Scro...
1. If I'm interacting with the URL/address input, I'm either entering a full URL, or searching through my local history to jump to a previously-visited page (or, in Firefox, a tab I may have open on another device). I don't want that shipped off to my search provider for autocomplete suggestions.
2. If I'm interacting with the search input, I want autocomplete suggestions. Additionally, because it retains the value of the last term I searched for, I can use it as a shortcut to jump back to the results if I no longer have the tab handy.
I think Github handled this well by letting you choose between a few canned shortcuts, or disabling the feature altogether [1]. Since I seldom print, I opted to bind the command palette to "CTRL + P"
> Honestly, I think the web platform could use a standard API for defining shortcuts, with browsers providing a UI to manage or disable them. Maybe I'm still over-engineering here.
I'd agree with this sentiment. It's hard, but an obvious (IMO) pain point that has numerous sites reinventing the wheel and needing to introduce some state to save user preferences.