At the very beginning, @Purism could communicate regularly on the project.
The deadline is very near, and they are now working hard to deliver the phone on time. Public communication is a bit scarce lately, but the development is still going steady.
Although formalized news posts take time to write, a lot happens in the community development channel (https://developer.puri.sm/Volunteering/HowTo.html)
Lurking in the channel can be time-consuming though. I'll try to give regular TL;DR of #Librem5Dev
Hey, what's up? We can proudly announce to you that pmOS is now up on mastodon!
I'm still amazed by the state of that industry. Why paying for an eBook for nearly the same price as a printed book gives you a file you don't own and you can't use, while piracy gives you a file you can use like an actual book?
When buying a book, I can read it where I want, in as many places I want, on as many couches I want, and I can even lend it to a friend. And that's legal.
Wasn't technology supposed to make the future better?
I have a bunch of friends from Twitter joining Mastodon tonight so I made a quick guide to how the site works. Making it public so anyone can see/boost it if it's helpful. If you have any questions feel free to ask!
Travel related threat-models are considered seriously for the Librem 5.
The Librem 5 developer kit will have 3 slots:
- one for a smartcard (containing the GPG keys)
- one for a SIM card (linked to the user's identity)
- one for a SD card (containing personal data).
While there is no commitment to it, it is envisioned that those will be removable on the actual phone, which would lower the risk when traveling.
Early images of @Purism Librem 5's prototype OS are based on Debian testing. This means phones supported by mainline Linux can run it.
It is to be noted that Purism will focus on FSF-endorsed PureOS and RYF-certified hardware, and does not support non-free hardware. This is not the intended used of those dev images.
The i.MX.8M board used for the Librem 5 sports a hardware decoding and encoding device. Whether it requires non-free firmware or driver is being studied. If it required a proprietary driver, the device would not be used, as it would prevent the RYF certification.