• 0 Posts
  • 943 Comments
Joined 10 months ago
cake
Cake day: January 2nd, 2025

help-circle
  • Exactly, keeping components separated, especially the router.

    Hardware routers “cost money because they save money” (Sorry, couldn’t resist that movie quote). A purpose-built router will just run and run. I have 20 year old consumer routers that still “just work”. Granted, they don’t have much in the way of capability, but they do provide a stable gateway.

    I then use two separate mesh network tools, on multiple systems. The likelihood of both of those failing simultaneously is low. But I still have a single failure point in the router, which I accept - I’ve only had a couple outright fail over 25 years, so I figure it’s a low risk.


  • Separate devices provide reliability and supportability.

    If your all-in-one device has issues, you can’t remote in to maintain it.

    Take a look at what enterprises do: redundant external interfaces, redundant services internally. You don’t necessarily need all this, but it’s worth considering "how do I ensure uptime and enable supportability and reliability? ".

    Also, we always ask “what happens if the lone SME (Subject Matter Expert) is hit by a bus?” (You are that Lone SME).














  • If you stop using original roms this isn’t an issue as it’s part of Play Services.

    Not using Play Services is the key.

    Lineage and Graphene don’t have Play Services by default.

    That’s the tough part, and why FDroid is pushing hard on this too - basically all phones have Play Services.

    Damn few of us flash Lineage or Graphene and run without Play, and damn few phones allow flashing anymore.

    Fortunately Graphene is working on their own hardware. Looks like it’s time for me to stock up on every kind of flashable phone I can find.

    The lack of backwards compatibility is a major issue too. Many of my apps are fine - I don’t need updated versions despite everyone screaming “you’ll get hacked using old software”. I have some stuff on my phone from 2010, and far older on my PC. This “hack” is just repeating the party line for orgs like Google to keep pushing us to newer devices.



  • Give us an example of what you want as the end result - what devices you have, are you sharing calendars with someone else, etc.

    My best answer is to run a calendar server on some machine and let your calendar sync to that whenever the devices are online on the same wifi simultaneously. (E.G. Run Owncloud in a docker on your laptop).

    Alternatively you could run Tailscale on the devices which would provide a secure mesh network, eliminating the need to be on the same wifi - so long as they’re online they can sync via Tailscale.

    Tailscale even has a feature (Funnel) that will route specific internet traffic into your Tailscale net - this would eliminate the need to have Tailscale on every device. You could host a calendar on a laptop (say Nextcloud in Docker with Tailscale), enable Funnel only for the calendar port, and apply security in Tailscale so only you have access.