• 0 Posts
  • 25 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


  • eOS+Fairphone is fairly different proposition. Not equivalent to GrapheneOS in my view. It’s a good option in terms of product ownership. GrapheneOS remains the undisputed best proposition in terms of security.

    Why hasn’t GrapheneOS started supporting Fairphones ? Because they don’t meet their security requirements on hardware level. Why hasn’t Fairphone seek partnership with GrapheneOS? Maybe they did and we don’t know about that because it didn’t lead anywhere, probably because the 2 organizations have very different goals.

    You are probably thinking the demographic that value privacy and security overlaps with people valuing product ownership, repairability and fair manufacturing. You would be totally correct. I would be delighted to have an all inclusive option at a reasonable price. Today it’s a trade-off decision. Repairability as top value: Fairphone+eOS. Security as top value: Pixel+GrapheneOS.



  • Completely wrong target for GrapheneOS. The GrapheneOS demographics, which I belong to, isn’t interested in high-end phones. They want a no nonsense simple phone with lots of storage and security first design.

    • fancy AMOLED screen: don’t care
    • 5 fancy cameras: don’t care
    • super powerful CPU and GPU: don’t care
    • storage space: yes please, I have photos and music to store locally!

    This will be harmful to GrapheneOS project. It will go like this: no one buys the phone because it’s too damn expensive and full of features the privacy nerds like me don’t care about. Even fewer buy the phone with GrapheneOS pre-installed and it’s a total flop. Motorola stops the partnership saying “we did it and no one wanted it”. No other OEM wants to partner with GrapheneOS after that.






  • Got my printer back in 2018, at the time the Prusa i3 MK3 was amongst the best printer you could get for the money, best in class performance and reliability, while having totally Open-source mechanical, electronics and firmware. I also got the material changer MMU2.

    People keep buying Prusa because they are committed to keep Open-source and community contributions alive. Very model gets upgrades down the line, coming in parts from community feedback and contributions.

    When the MK3S upgrade came out, they shipped it to me at a minimal cost. When the MMU2S upgrade came, they did too. Just this month, I have upgraded to MK3S+ and MMU3, printing the parts and sourcing the Hardware by myself. Prusa maintains very good documentation and assembly guides, to make the process as easy as possible.

    8 years ago I paid for a good printer. Today it’s still relevant and has been super reliable the whole time (MMU2, not so much, I am still testing the MMU3).



  • They are talking about the firmware that runs on the device. The user front-end to easily configure it is another story. Hopefully it’s going to quickly get support for Linux as they are starting from well established Open-source projects for keyboard firmware (QMK and ZMK). If it works like for keyboards, you will be able to configure your mouse with something like VIA that runs on Chrome/Chromium (and maybe one day Firefox ?) using the WebUSB API.

    I have 2 keychon keyboards, an old one and a newer one with QMK firmware. Both have worked perfectly well for Linux. The QMK one is easy to configure with VIA once the device permissions are sorted out.