Please don’t flood Lemmy with clickbait titles. The commentary on top of the fox clip adds precisely nothing.

Of course! I’ve loved mine. The community and integration with Gadgetbridge are both awesome. You’re in for a treat if you go this route.

On the watch front I opted for the Bangle.JS 2. The abstraction to everything being JavaScript can be annoying, but takes away some foot guns for tinkerers who don’t want to optimize lower level code.

wherever you get your PCBs and associated components ;)

https://mikrophone.net/build.html

Cool video and channel. Thanks for posting!

TLDW:

[It was a cool attempt that may have spurred mobile Linux devs in an important way. Removable battery + hardware switches for communication subsystems were genuinely innovative and in tune with community interests. Also it was bad. 8 year old CPU, software that was trying to do everything everywhere all at once, cameras that didn’t work then technically did. Pine64 still exists and the Pinephone Pro is a thing (that the presenter hadn’t tested).]

Presenter was generous when describing the end product. It seems to me like they want to like it but came to the same conclusion as most did – it’s definitely not a daily driver. That said, it doesn’t have to be to remain a cool product.

Do give them a watch though if you have a chance. This is from a <1k subscriber channel and was well put together.

It’s mostly Mastodon. (Shoutout to @RmDebArc_5@sh.itjust.works for posting the link to FediDB)

I prefer Syncthing-fork for some more straightforward configuration. Mainly the three button options equating to “follow the run conditions, damnit”, “run damnit”, and “stop damnit”

Amazing work! I’m very excited to see mobile Linux reach a usable state for every day processing. Thank your for your time and energy. It is valuable and going to good use.

Why the Pixel 3a? Is there anything special about it (or not special, which might mean my old 3XL is good for more than gathering dust?)

How can I get involved? I know my way around C and would love to pitch in.

“Chuff” in the context of rock climbing = bad, made an effort but didn’t get very far / fell a lot

Even faster – tailscale. For a cheeky way to play with your friends make a burner account with a shared login to get on the same tailnet for free. On the endpoints, turn off tailscale-ssh and any of their other “features” you don’t need.

I’m a big fan of buying power tools twice. I happen to go Ryobi for the first round but Harbor Freight / Northern Tool are probably similar.

If you can stand the fuss, buy corded tools and skip the brand loyalty that comes with batteries.

The biggest killer of cheaper power tools is generally heat. There are plastic components in the drive train. They hold up great to short jobs, but heat is their kryptonite. If you let a Ryobi tool cool down whenever you notice it getting warm to the touch it’ll last a long time. If you need to run a tool for hours at a time then skip the fuss and go straight to a more brand with a good reputation like DeWalt, Makita, Bosch, or Milwaukee.

Red boxes fit all brands my friend :)

Green tools the first time (I can bike to home depot) Yellow tools the second time

assuming you mean *can’t

if cordless: batteries

else: brand cuckery

Second this ^

I have one and it’s fine, but not directly supported by OpenWRT. Looks like Beryl and Slate are though

Excellent notes. If I could add anything it would be on number 4 – just. add. imagery. For the love of your chosen deity, learn the shortcut for a screenshot on your OS. Use it like it’s astro glide and you’re trying to get a Cadillac into a dog house.

The little red circles or arrows you add in your chosen editing software will do more to convey a point than writing a paragraph on how to get to the right menu.

Is there a reason you’re not considering running this in a VM?

I could see a case where you go for a native install on a virtual machine, attach a virtual disk to isolate your library from the rest of the filesystem, and then move that around (or just straight up mount that directory in the container) as needed.

That way you can back up your library separately from your JF server implementation and go hog wild.

Syntax-wise, it’s meant to be identical. I got on board when they were the only ones that enabled rootless (without admin privileges) mode. That’s no longer the case since rootless docker has been out for a while.

I’m personally a fan of the red hat docs and how-to’s on podman over the mixed bag of tech bro medium articles I associate with docker.

At the end of the day this is a bit of a Pokemon starter question. If your top priority is to get a reasonably common and straightforward job done just pick one and see where it takes you! :)

Syncthing is my answer though I appreciate it doesn’t get to the root of your question.

There are local backups that include your system settings, text messages, contacts, call history and (optionally) apps. The one thing I want is the ability to pick a directory for the local backup so I can make it work with syncthing without jumping through hoops.

It’s also compatible with Nextcloud and WebDAV if those are options for you.

I miss my pixel 5 :(

Avoid AMD? Why do you say that?