●● IRC: #techbytes @ Techrights IRC Network: Wednesday, December 21, 2022 ●● ● Dec 21 [01:34] *u-amarsh04 has quit (Quit: Konversation terminated!) [01:35] *u-amarsh04 (~amarsh04@uvxvchtayzkvk.irc) has joined #techbytes ● Dec 21 [03:08] schestowitz > No Microshit policy Thanks! Happy holidays to you and your wife and [03:08] schestowitz > thank you so much for all your support over the years! [03:08] schestowitz > [03:08] schestowitz > Cheers, [03:10] schestowitz >>>> http://techrights.org/wiki/Sirius_Open_Source [03:10] -TechBytesBot/#techbytes-techrights.org | Sirius Open Source - Techrights [03:10] schestowitz >>>> [03:10] schestowitz >>> Let me know if there are any keywords to search for in my databases [03:10] schestowitz >>> [03:10] schestowitz >>> I hope your next role will work out better. [03:10] schestowitz > [03:10] schestowitz > [03:10] schestowitz > I had already searched for the obvious keywords (Sirius, Mark Taylor) [03:10] schestowitz > before asking the question [03:10] schestowitz > [03:10] schestowitz > Are there any less obvious names or keywords that are worth searching for? [03:10] schestowitz I try never to name clients or colleagues. It would darken the series somewhat. ● Dec 21 [04:18] *u-amarsh04 has quit (Quit: Konversation terminated!) [04:19] *u-amarsh04 (~amarsh04@uvxvchtayzkvk.irc) has joined #techbytes ● Dec 21 [05:06] *XFaCE_ (~XFaCE@uzfeivw9fp6ba.irc) has joined #techbytes [05:06] *XFaCE has quit (connection closed) ● Dec 21 [09:02] schestowitz
[09:02] schestowitz[09:02] schestowitzThats the suggestion put forward for community discussion by a prominent Ubuntu developer. The reasoning is that since Nautilus lets us create/extract commonly-compressed formats (including the ubiquitous .zip and tarballs) shipping a separate app that does the same thing (albeit with more formats) is unnecessary.
[09:02] schestowitz
[09:04] -TechBytesBot/#techbytes-www.bunniestudios.com | Towards a More Open Secure Element Chip bunnie's blog [09:04] schestowitz[09:04] schestowitzSecure Element (SE) chips have traditionally taken a very closed-source, NDA-heavy approach. Thus, it piqued my interest when an early-stage SE chip startup, Cramium (still in stealth mode), approached me to advise on open source strategy. This blog post explains my reasoning for agreeing to advise Cramium, and what I hope to accomplish in the future.
[09:04] schestowitzAs an open source hardware activist, I have been very pleased at the progress made by the eFabless/Google partnership at creating an open-to-the-transistors physical design kit (PDK) for chips. This would be about as open as you can get from the design standpoint. However, the partnership currently supports only lower-complexity designs in the 90nm to 180nm technology nodes. Meanwhile, Cramium is planning [09:04] schestowitz to tape out their security chip in the 22nm node. A 22nm chip would be much more capable and cost-effective than one fabricated in 90nm (for reference, the RP2040 is fabricated in 40nm, while the Raspberry Pi 4s CPU is fabricated in 28nm), but it would not be open-to-the-transistors.
[09:04] schestowitz
[09:12] schestowitz[09:12] schestowitzI have reviewed, updated and revised my short book about the Rust programming language, Rust for the Polyglot Programmer.
[09:12] schestowitzIt now covers some language improvements from the past year (noting which versions of Rust theyre available in), and has been updated for changes in the Rust library ecosystem.
With (further) assistance from Mark Wooding, there is also a new table of recommendations for numerical conversion.
[09:12] schestowitz
[09:22] schestowitz[09:22] schestowitzMandiant is reporting on a trojaned Windows installer that targets Ukrainian users. The installer was left on various torrent sites, presumably ensnaring people downloading pirated copies of the operating system: [...]
[09:22] schestowitz