robotdna

joined 1 year ago
MODERATOR OF
[–] [email protected] 4 points 6 months ago (3 children)

Do we prefer Ansible over Terraform?

[–] [email protected] 3 points 6 months ago (1 children)

What about Traccar? I see a section in there for "drives", although I just leave mine on all the time

[–] [email protected] 1 points 7 months ago

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.

[–] [email protected] 2 points 7 months ago

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.

[–] [email protected] 13 points 7 months ago (2 children)

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.

[–] [email protected] 30 points 7 months ago (9 children)

I started out with Owntracks. I found it to be unreasonably complex. I swapped to Traccar. It was much easier to get functional.

[–] [email protected] 6 points 7 months ago

I'll believe it when I see it- Spotify lossless was announced years ago. I don't believe them.

[–] [email protected] 3 points 7 months ago (2 children)

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.

[–] [email protected] 8 points 7 months ago (7 children)

They no longer offer this, right?

[–] [email protected] 1 points 8 months ago

I'm not sure, although if it's truly a clone, why wouldn't it work?

[–] [email protected] 1 points 8 months ago (1 children)

It is indeed the Beekeeb case, maybe the part list of the build kit on the website lists the size?

 

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.

48
Wireless Chocofi (toast.ooo)
submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]
 

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.

 

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

 

Credit FlorkofCows

 

Credit FlorkofCows

 

Credit FlorkofCows

 

Credit FlorkofCows

 

Credit FlorkofCows

 

Credit FlorkofCows

65
cpa (toast.ooo)
 

Credit FlorkofCows

 

Credit FlorkofCows

112
pain (toast.ooo)
 

Credit FlorkofCows

view more: next ›