Working a bit on libti*/gfm/tilp once in a while, I need to spend more time on the matter, but at the moment, I'm dealing with a set of 1990s or early 2000s PCs. I've had these motherboards lying around for nearly a decade, ever since I picked them up while cleaning up my previous job's work place and brought them home several months later.
I knew most of these motherboards were broken, indeed they are, but I've found 6 computers in working state so far. There could probably have been at least 7 if I had taken care of the leaking RTC batteries in 2010-2011: in the summer of 2010, one of the computers used to work.

The entire content at https://symbolibre.org/ , be it the about summary https://symbolibre.org/en/the-project/ or the news items, has now been translated to English

Over the past few days, the word has started spreading about a ~university project of a team of 25 French students working part-time for several months, which yielded the Symbolibre graphing calculator effort, based on modern, cheap hardware components and
open source / libre software
I'm not involved in that project, I'm just relaying news. To date, most information about the Symbolibre remains written in French, AFAICT.

It's based on a $5 RPi Zero module without networking capabilities (not a "W" model), which brings hardware characteristics previously unheard of on a graphing calculator: 1 GHz ARM CPU, 512 MB of RAM + e.g. 8 GB of Flash (well, whatever one puts inside the internal SD card slot). Only the Prime G2 isn't completely dwarfed by this. The screen is 320x240, like all other graphing calculators with ""high-resolution"" screens.
On the software front, unsurprisingly, it's running Linux, and therefore, it enjoys the widest collection of user-space programs, including giac/xcas, a full-blown Python implementation with a full-featured IDE, etc. There's a screenshot taken on a computer, so it looks like there's a computer version of the software.
They used 3D printing for the case and also keyboard buttons, though their pictures don't show the keyboard buttons.

The best aspect, and it's not surprising, is that the Bill of Materials, detailed in at least one of the topics linked below, amounts to around 80€ in the current setup, and can be decreased by using other power circuits... yes, 80€ is just about the (commercial) price tag of a TI-83 Premium CE or a NumWorks calculator, both of which have immensely weaker hardware characteristics.
Technically, the Symbolibre has much more raw power than needed to run the cores of CEmu, the NumWorks simulator, TilEm and TIEmu, though the input (keyboard...) and UI might be less obvious. Firebird should work, but I'm not sure about full speed emulation of a CX, let alone a CX II in the future.

In France, there's (fortunately) no official list of calculators allowed for the main standardized tests, and as long as the SD card slot is not user-accessible during an exam without opening the case (it isn't), such a calculator probably wouldn't run afoul of stupid standardized testing constraints, especially if a blinking LED is added. This requirement of an exam mode with blinking LED was supposed to be enacted last year, after a 3-year notification period, but it wasn't, because unsurprisingly, many pupils still only had working, but older, models without exam mode.

One of the students is an administrator at Planète Casio; two of the TI-Planet admins (critor and Bisam) met the team and saw the calculators for themselves on April 3rd and 4th. The project was publicly showcased at the ~university on April 4th.
The students' plan is to keep developing the project as time permits, of course. And judging by the interest the project is generating, they might receive external contributors, like NumWorks

Official site: https://symbolibre.org/
Forum topics in other calculator communities: https://www.planet-casio.com/Fr/forums/lecture_sujet.php?id=15667 , https://ti-pla.net/t22470 , http://www.hpmuseum.org/forum/thread-12726.html .

Nope, installing Ndless is clearly not known to void the warranty
And yes, it's hard to conceive that such misbehaviour can be produced purely by software.

Switching Android from Linux to Fuchsia is apparently far from trivial, according to Kees Cook this summer (2018/07/28) on ##linux-hardened. I'm not aware of a no-logs policy on that chan, so straight from my logs:

Quote[18:48:21 CEST] <xtrWrithe>   hello, im using this kernel, it comes with grsec? or i will need to patch it manually?
[20:04:37 CEST] <Lionel_Debroux>   linux-hardened does not come with PaX/grsecurity.
[20:05:24 CEST] <Lionel_Debroux>   There used to be minipli's unofficial forward port of grsecurity to newer Linux 4.9 stable versions, but that stopped when KPTI was integrated to mainline: mixing the broad KPTI changes with MEMORY_UDEREF and KERNEXEC was too much, too hard work, IIUC.
[20:22:57 CEST] <xtrWrithe>   Lionel_Debroux: ty for reply, yes i saw that the other port is dapper's one, but as you say KPTI made it very hard to keep working and the 4.13 versiom doesnt work yet
[20:23:38 CEST] <xtrWrithe>   what should i focus on to prevent kernel exploits or at least mitiagte them a bit?
[20:37:45 CEST] <Lionel_Debroux>   smeso reimplemented something like MPROTECT, and several other protections, in the SARA LSM... but LSMs still aren't stackable, and on the anti-exploitation front, nothing comes remotely close to grsecurity.
[20:37:59 CEST] <Lionel_Debroux>   Individuals are out of luck, they can't buy grsecurity subscriptions on their own.
[20:39:55 CEST] <Lionel_Debroux>   If you're part of a small company, and can convince those who decide (or are one of the deciders and it doesn't cost too much), maybe you can become a customer of Open Source Security, Inc.
[20:41:54 CEST] <Lionel_Debroux>   If you're part of a large company... you're probably out of luck as well, as the subscription probably won't be very cheap, and making those who have the power to decide on such bills - and are usually of the dumb financial type - understand the value of grsecurity, no matter how huge it is, is usually a hopeless task.
[20:51:01 CEST] <Lionel_Debroux>   In the longer term... IIUC, Android's going to switch to a completely different kernel implementation with a Linux compatibility layer. Microsoft used the same approach for Win10's WSL.
[21:49:16 CEST] <kees>   Lionel_Debroux: Android leaving Linux is somewhere between "never" and "in decades maybe"
[21:49:44 CEST] <kees>   xtrWrithe: I recommend the latest upstream kernel, and the recommended settings linked from the /topic
[21:49:51 CEST] <kees>   (if you can't find a way to use grsecurity)
[21:53:26 CEST] <Lionel_Debroux>   You know the topic better than I do, but... that far in the future, really ? Why ?
[21:53:54 CEST] <kees>   Lionel_Debroux: because changing a kernel is hard.
[21:54:03 CEST] <Lionel_Debroux>   AFAIK, many Android apps, especially those written in higher-level languages, do not have strong dependencies on Linux.
[21:54:32 CEST] <kees>   Lionel_Debroux: true, but the system integrity is tightly bound to Linux (e.g. SELinux)
[21:55:05 CEST] <kees>   Lionel_Debroux: now, what I'd expect is for that kind of thing to happen in VERY small devices where memory and CPU resources are the tight spot
[21:55:29 CEST] <kees>   but on phones... multi-core CPUs, gigs of RAM, I really think it'll stay Linux for a long long time
[21:57:56 CEST] <Lionel_Debroux>   Yeah, Linux on very small devices is a lost cause. The tinification efforts weren't deemed useful enough (by the powers that be) to offset the (sometimes small, IIUC) maintenance increase.
[21:58:32 CEST] <Lionel_Debroux>   Higher performance and better compatibility are deemed more important than smaller footprint... or better security.
[22:00:29 CEST] <Lionel_Debroux>   It's the first time I'm reading "the system integrity is tightly bound to Linux (e.g. SELinux)" argument, which is indeed a good technical reason why moving away from the Linux kernel for some usages can be hard.

And agreed, Fuchsia should be able to manage to be part of our world for a while.

TI-Planet, Cemetech and ticalc.org also use the automated Let's Encrypt CA to obtain certificates trusted by clients. And we all configure our Web servers to listen for TLS connections on TCP port 443, presenting the server certificate obtained from Let's Encrypt to clients.

QuoteAny sane person dealing with sensitive, closed-source code would host their code themselves.

Right, but so many directors, financial people and managers aren't sane and competent that it isn't funny

Migrating a company's documents and e-mails to Office 365 - or the Google version thereof - shouldn't ever be an option to be considered seriously because of the privacy / confidentiality implications, let alone a decision imposed on users. My company's going through that **** at the moment, it's criminal.

The biggest issue is probably the private repos, used by companies for their internal source code, falling into the hands of one of the Internet giants (whichever it is - it would largely be the same for Google, Apple or Amazon; Facebook's not really into coding in the first place). Even larger potential for industrial spying than with an independent Github, and an unfair advantage against competitors wrt. Azure integration (well, they'd better provide GCE and AWS integration at the same time if they want to avoid that pitfall) + LinkedIn integration (no alternative with remotely similar popularity).
Companies moving to their private Gitlab / Gerrit / similar instances would just be doing what they should have done much earlier.

Also, some people think that this move makes MS (even) more vulnerable to censorship, especially China's censorship: https://twitter.com/i/web/status/1003397774908559360

My main TI community projects are in the process of being imported to Gitlab, though I'll probably continue updating both sides for a while.

For a while, I used Choqok, which is far more convenient than the standard browser-based client (I don't have a smartphone) because it makes it possible to store large - and even insanely large - amounts of contents for later reading. I gave up on most of Twitter altogether, because I was drowning in content, but I miss some aspects of the Choqok experience.
It's sad to see that they're attacking third-party clients again...

Ads aren't an issue with uBlock Origin. In general, ad blocking, besides removing often uninteresting and always distracting content, is also a must for security, as ads were shown multiple times to be an attack vector.

In dictatorships such as China and Russia - but let's face it, also in so-called democracies - some state workers sometimes have the right to break even their countries' rules, in a more or less controlled way, to misinform, mislead and perform mischief on people from other countries and in other countries. Maybe that's what we're seeing here.

Interesting work
The shield is quite thick, so it's not stealthy... but that's probably not a design goal ^^

There's quite a bit of code duplication between the nspire-communication/nspire-client/uart_*/*.cpp files; you may want to factor uart_getsn_mdf() and friends to a common file. Also, you may want to use a thin layer to abstract the UART protocol communication details, making it possible to add support for other transmitters

Amusing

Do you plan on making a special version of Oiram CE, which could feature a subset of your sprite mods, the peace sign or things like that ?

It had been a while since I read this topic. That's fantastic work, as usual

The number of Linux distros supporting secure boot is growing.

FWIW, I never had problems dual-booting Windows on my or work computers, since the summer of 2005.
I recently destroyed the Windows copy on this computer to gain some breathing space on the HDD, and I seldom boot Windows on the other computers, the latest one of which was preinstalled with Win 10, but still