- 4 points
- 1 point
- 2 points
- 4 points
- 1 point
- > I understand why they dropped [Photon] in favor of Qt and later Web technologies
The arrows of time branch and spiral, so it's possible that "later" could require some properties of "earlier".
If Photon could not be open-sourced, it could be licensed to a third party for custodian maintenance. If QNX is abandoning Photon forever, would Blackberry object to Photon being cloned for Linux or FreeBSD? That could preserve a future option for QNX to use it again, like XFCE.
Enthusiasts still use Blackberry keyboards on handheld devices in 2025, which sell out in minutes. In a parallel universe, Blackberry.com offers embedded SBC developers self-service purchase and global delivery of the legendary Blackberry keyboard, with Bluetooth for convenience or USB-c for security.
- $100M+ last quarter, split between QNX and endpoint device software, https://www.panabee.com/news/blackberry-earnings-q3-2025
275M cars with QNX, https://roboticsandautomationnews.com/2025/12/19/blackberry-...
AI/robotics, https://qnx.software/en/industries/robotics
- 276 points
- 2 points
- 2 points
- Still present in Debian stable 12 (trixie), detected by outbound network firewall OpenSnitch.
Related 2012 report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675710
- 10 points
- 1 point
- 28 points
- 3 points
- 2 points
- 4 points
- What do you think of https://bughunters.google.com/open-source-security/patch-rew...?
- 4 points
- 1 point
- 1 point
- 1 point
- For ~100K authors with content on Github Pages, Liquid conformance avoids learning new template syntax or a programming language.
For a greenfield site where Jekyll/Liquid compatibility is not beneficial, Zola may be an option, https://github.com/getzola/zola
This has potential to replace Github Pages ruby-based Jekyll+Liquid, which is unusably slow on iOS without JIT.Conformant: Incompatibilities with strict shopify/liquid are bugs to be fixed. Flexible: Liquid embraces variants for different domains and we want to follow in that spirit. Performant: Do the best we can within what is conformant.Compiled cobalt with liquid-rust on iSH is fast enough for static blog publishing and browser-based offline site preview on iOS/iPadOS, https://www.hackerneue.com/item?id=46220227
- Cobalt + Liquid-Rust + iSH enables offline writing with iPad portability, lockdown mode security and battery life, retaining interoperability with Linux static publishing toolchains. No jailbreaks or sideloading required.
Due to lack of JIT on iOS, Jekyll is too slow to run on iSH. Liquid-Rust (https://github.com/cobalt-org/liquid-rust) templates, even with partial compatibility for the Ruby-based Liquid template engine, reduce the cost of migrating from the Jekyll Ruby static site generator used by Github Pages.
On Debian x86, build a cobalt static binary for use on iSH (Alpine Linux /w musl libc) on iPadOS:
Copy cobalt static binary to iSH filesystem via iOS Files app, execute and view http://localhost:NNNN with a web browser:sudo apt install rustup build-essential rustup target add i586-unknown-linux-musl git clone https://github.com/cobalt-org/cobalt.rs cd cobalt.rs cargo build --release --target i586-unknown-linux-musl cp target/i586-unknown-linux-musl/release/cobalt /mnt/usb./cobalt --no-watch --host 0.0.0.0 --port NNNN - 1 point
Is this independent of the Linux Security Modules policy, e.g. RHEL default policy for SE Linux?