RE: https://fosstodon.org/@frameworkcomputer/116443868461529145
Great showing from #FrameworkComputer ! The new #framework13pro looks phenomenal, exactly what id always dreamed my framework would be. Definitely picking this beauty up!
@256 Aaand I've never heard of them. :/
It's like an earlier, failed I guess? attempt at what @frameworkcomputer does.
RE: https://fosstodon.org/@frameworkcomputer/116443868461529145
Great showing from #FrameworkComputer ! The new #framework13pro looks phenomenal, exactly what id always dreamed my framework would be. Definitely picking this beauty up!
RE: https://fosstodon.org/@frameworkcomputer/116375404873416915
Framework anuncia un evento clave: el 21 de abril presentará su nueva generación de productos. Habrá streaming y plazas limitadas para asistir en persona en San Francisco. La comunidad ya especula con nuevo hardware modular y mejoras en su ecosistema.
#framework #technews #modularcomputing #openhardware #frameworkcomputer
Check out this in-progress project. A laptop with a #ThinkPad -style #butterflyKeyboard for the #Framework 13 laptop mainboard. https://github.com/Maglev-Rabbit/702_Project_Public
Well, if you've got an 11th generation Intel #Framework 13 (i.e. the first gen model) and you start encountering weird behaviours -- in my case failing to properly power on until it's plugged into AC and clock reset issues -- replace that CMOS battery! I got a freebie replacement from #FrameworkComputer and my flaky FW13 is now 100% back to normal.
I have to admit I was too chicken to get the battery replacement module... I do not trust myself with a soldering iron *that* much...
@robhughes this might be the problematic sponsorship you're referring to.
https://community.frame.work/t/framework-supporting-far-right-racists/75986
I have had a #frameworkcomputer 13 for 4-5 years now and have generally been happy with the hardware. The upgrade path and community are pretty excellent.
Their support is a pain to deal with in my experience (~1 email per day, ~7-10 business days to go from initial warranty claim back to a working system, 2 claims in 4-5 years). I've also had two i7-1260p mainboards die on me, one just last week.
My verdict is I'm going to buy another board to see if the new AMD hotness keeps me in the orbit for another 5 years. I'm feeling the #Asahi gravity pulling me towards the impressive efficiency of an m2 Linux MacBook Pro though...

We support open source software (and hardware), and partner with developers and maintainers across the ecosystem. We deliberately create a big tent, because we want open source software to win. We don’t partner based on individuals’ or organizations’ beliefs, values, or political stances outside of their alignment with us on increasing the adoption of open source software. We’ve sent out large quantities of hardware to folks at Fedora, Bluefin, Bazzite, NixOS, Arch Linux, Linux Mint, Omarchy,...
@IslandUsurper People were making noise on the Fediverse because some of the open-source projects Framework sponsored had a conservative or far-right maintainer. One of them had discriminatorily moderated against someone in the LGBT (and had apologized, when I looked into it), and another one had written some questionable articles which many found racist. Framework supported their projects, but denounced the acts of the maintainers.
It is time for a new #Linux laptop. My Librem 13 served me well for eight and a half years. Yesterday it was in my lap when a bouncy 60 pound dog bounced into my lap, and it now has problems I can't fix. Unfortunately #purism doesn't have the Librem 14 in stock.
Any recommendations? I am looking at #System76 models. I was interested in #FrameworkComputer but heard problematic things about the company's sponsorship choices.
Repairability is a priority!
VERKAUF: Framework Laptop 16 Mainboard
https://friendica.rollenspiel.monster/display/b2e8d1f0-1769-84b7-5e51-a0e545984361
@oscherler Seems like it, right? But that's not the case for me (on a #FrameworkComputer 13).
Also see this issue: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5020