What about Traccar? I see a section in there for "drives", although I just leave mine on all the time
I just use what is called a "GPS Case" off of Amazon. I got the one branded "MoKo" and cut out the two elastic straps which allows me to put in both my halves of my split- I'm not sure if this will fit yours, but maybe it will give you ideas.
You change how frequently checks are performed. Traccar runs a simple every X seconds pattern. Default is 5 minutes. On 5 minute pings I see a 15-20% drain over the course of 24 hours, which seems reasonable, given that I'm on GrapheneOS and not leveraging Google's location tracking simplifications. If you're not on GrapheneOS your battery usage for location tracking will probably be better. Just not private.
I should note that my scenario was exactly the same. I wanted to share location with family. Additionally, Traccar supports temporary location share links for friends if you'd like. You'll need to self-host it- I personally set up the Traccar server inside kubernetes and used Traefik for reverse proxy and SSL, but this is not necessary.
I started out with Owntracks. I found it to be unreasonably complex. I swapped to Traccar. It was much easier to get functional.
I'll believe it when I see it- Spotify lossless was announced years ago. I don't believe them.
I like AirVPN, my main issue is server stability. iVPN and Mullvad at least were able to maintain a connection continuously for weeks on end across various networks, but this is not the case for AirVPN. It's to the point where I'm considering alternatives because I'll start using my device only to find out the VPN tunnel has died and I have to manually reconnect it.
It is indeed the Beekeeb case, maybe the part list of the build kit on the website lists the size?
I noticed that movement combined with a balanced team really helped make higher hazard levels tolerable. For example, you can solo things a bit more on lower levels, but on higher levels having a good combination of crowd control (Driller excels in this) and single-point high DPS (such as the secondary with Engineer) makes it really balanced. We'd set up strats like Driller creating sticky flame traps all over to dump DPS downrange and soften targets while gunner can finish them off, or freeze targets allowing stuff like sentry guns to shatter them. It's really the team cohesion that makes hazard levels easier. When we paired our overclocks together in unique ways it made for easier play through (e.g. intentionally keep to flame or freezing, or, intentionally use both to leverage the temperature shock strat)
NixOS docs themselves are a tad lax, but it will get better.
Learning nix itself is also important:
Just this morning I was having issues with a wacky dual-boot install with NixOS and Windows sharing an EFI partition, and quite interestingly ChatGPT and I were able to troubleshoot the process and get it resolved in under half and hour. I was really impressed by the specific configurations it was giving me for my /etc/nixos/configuration.nix , so that is also another resource you may consider leaning on when you run into walls in other documentation sources.
Unsatisfying resolution, wiped windows disk, cleared partitions, and let windows do an automatic install. Interestingly it decided to install a windows boot manager alongside the Linux one.
I've probably parsed dozens of pages now, including the "Dual boot NixOS and Windows" page on nixos.wiki, and not really sure what the best steps are since most seem to leverage the fact that everything is on a single partition. My windows lives on a physically separate drive than NixOS, so osprober does not detect the windows partition at all. I tried to go down the route of grub-mkconfig but that doesn't seem to be a nix package and I couldn't mount my Windows bootloader as it is NTFS. Is this even possible with this configuration?
My next step was going to be to physically disconnect each of my disks/NVME, nuke everything bit by bit, then only connect the disks I want and install each OS with it's specific disk connected.
Oh, one funny downside to this board is that because it's so absurdly energy efficient, I've found a few battery chargers (e.g. Anker) don't detect it as enough current draw to charge them lmao. Not a deal breaker, just amusing.
They're really fun. I like them especially for things like:
- battery life
- charging status
- is my Bluetooth connection working
- are the halves talking to each other
- what Miryoku mode I'm in (fun, not really functionally helpful)
- what Bluetooth slot I currently have active, and if other slots are cleared or paired to a device. Miryoku tracks 4 slots.
Sourced from Beekeeb, using vanilla Miryoku for keymap, totally wireless with ZMK + MIP displays. Using MBK blanks and Choc Robins, with Netdot Gen 10 magnetic connectors for charging.
Compared to the Piantor, the innermost thumb buttons are a bit more offset but all thumbs seem to be closer which I prefer. Solid layout, may be my favorite.
I can't give too much specifics due to IP and company infosec but was having issues with network drives
Posting this here for sake of search engines and if others are losing their mind trying to troubleshoot.
Problem: I have a USB-C Piantor, connected through a USB/thunderbolt port on a Dell XPS 13. My OS is Arch Linux, and it when plugging the keyboard in, the Piantor would show up on lsusb but not do anything. dmesg shows the following error:
device descriptor read/64, error -71.
Solution: Disable USB suspend in a root terminal:
# echo -1 >/sys/module/usbcore/parameters/autosuspend