• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle

  • My whole infrastructure is designed so that my homeserver is expendable.

    Therefore my most important tool is Syncthing. It is decentral, which is awesome for uptime and reducing dependance on a single point of failure. My server is configured as the “introducer” node for convenience.

    I try to find file-based applications, such as KeePassXC or Obsidian, whenever I can so that I can sync as much as possible with Syncthing.

    Therefore there is (luckily) not much left to host and all of it is less critical:

    • Nextcloud AIO: calendar, contacts, RSS, Syncthing files via external storage
    • Webserver: Firefox search plugins (Why is this necessary, Mozilla?!), custom uBlock Origin filter list, personal website

    So the worst thing that can happen when my server fails is: I need to import my OPML to a cloud provider and I loose syncing for some less important stuff and my homepage is not accessible.

    Since I just rebuilt my server, I can confirm that I managed a whole week without it just fine. Thank you very much, Syncthing!


  • I was in a similar situation not too long ago.

    My criteria for another scripting language included that it should be preinstalled on all target systems (i. e. Debian and Fedora), it should be an interpreted language and it needs to have type safety.

    Afterall I settled with Python due to its popularity, its syntax and features (type safety since v3.6, etc.) and the fact that it is preinstalled on many Linux distributions. System components often use Python as well, which means that libraries to interact with the system tend to be included by default.




  • They would also need to take responsibility for any security issues related to the chipset. It is also not possible to upgrade proprietary firmware (e. g. for the modem) at all without support from the chipset manufacturer.

    Fairphone doesn’t seem to care much about security (they use public keys for signing their OS afterall!), so they may be fine with those compromises.

    Qualcomm is interested in selling new SoCs, so even if they actually offer support extensions, their fees are most likely very high to make it unprofitable for manufacturers to go this route.


  • They won’t do that, because older Pixel phones used Qualcomm SoCs and Qualcomm didn’t support these SoCs for more than three Android versions.

    They might technically be able to extend support for the Pixel 6 and up (Tensor SoC), depending on the contract and who, Google or Samsung, is responsible for providing the chipset drivers. But even if it is technically possible to extend support, it is probably also unlikely to happen due to the additional expenses it requires.

    Overall it’ll be interesting to see how many phones actually live long enough to see their final update after seven years. Considering I already had to replace the battery on my three year old Pixel 5 once (which initially came with Android 10 and got updated to Android 14). USB connectors and broken screens are also common failure points for aging phones.