Search

2 results for “postmarketos”

1. 

   ROllerozxa @rollerozxa

   2026-10-22

   A (likely not exhaustive list) of Principia's current platform support:

   - Windows has always been supported, but the open source builds have generally only supported Windows 7+. However I made a custom toolchain building everything from the ground up to create separate builds that runs on Windows XP again.
   - Android has always been supported, but the FOSS builds haven't supported anything <4.0. A FOSS build that runs on at least Gingerbread would be cool but I'm generally burnt out on Android stuff.
   - Linux support was one of the first things I worked on when the source code released, the original devs were all Linux users but I worked on getting that into a more usable state for end-users (like not depending on Valgrind to run & such...). Builds with GCC or Clang, runs on glibc or musl, have gotten it running on a Raspberry Pi as well as on Nura/postmarketOS with configurable touch support from the Android version.
   - I ported Principia to Haiku OS, but haven't been able to get Haiku on real hardware yet
   - I ported Principia to macOS with a VM, also set up CI to build it too but I don't have any real Apple hardware to test with
   - I ported Principia to the web browser and integrated it into the site so you can conveniently create levels in the sandbox or play levels from the community site in your web browser
   - I ported Principia to the Nintendo Switch with devkitPro, but their SDL3 is a bit unfinished and I haven't gotten further along with that. I also don't have a homebrewed Switch either.
   - I recently got Principia to compile for iOS again in a VM but doesn't render in iOS sim yet. There's also a iOS slopfork from someone else that's further along but we don't talk about that one.

   Principia is extremely portable with little dependencies, I replaced the old build system with a unified CMake build system to make it easier to build for different platforms, and I have managed to get rid of stuff like GTK3 and replacing them with Dear Imgui-based dialogs, but the main limiting factor at this point tends to be OpenGL 2.1 / ES 2.0 and SDL3.

   Big endian support feels like the only low-hanging fruit left, as I believe there are parts of the codebase that are currently not endian safe and warn about it in our porting doc.

2. 

   bill, Anxiety As A Service @[email protected]

   2026-10-21

   Posting here because I need the character space...

   If your #Android device is running #Google apps, your #Signal chats are generally not private. I just had a conversation topic that only came up once in a specific Signal chat show up in targeted advertising on #Youtube. The chat happened on another system, so it wasn't the phone's keyboard (which was swapped out from stock anyways). But the signal chat info showed up in a targeted advert just minutes after starting the Youtube phone app, which I rarely use.

   Virtual keyboard had been swapped out already, so it wasn't likely a keyboard cache attack.

   This behavior did not show up when using after-market Android operating systems like Graphene (or Calyx or Postmarket, etc). That is also because I usually run multiple segregated profiles, and Google apps have their own tiny little box there. This was my spare phone because my regular Graphene phone was inoperable at the time.

   This isn't to throw shade on the excellent work Signal does, but to make very clear to people that the best way to keep things like this from happening is to use separate user profiles for app that aren't trustworthy. This isn't really possible for me with a $BigVendor phone that pre-installs a bunch of apps that you can't get rid of easily. Which is why the next couple of night will be spent installing CalyxOS on yet another pixel refurb.

   #android #google #signal #youtube