I had one of the LeapMotion input devices back around when they launched, and really did try to use it in earnest - using a whole bunch of shortcuts and AutoHotkey hacks to navigate the OS with it. There were even experimental programs people wrote to input text with it, using something similar to chorded keyboards.
It didn't really work out though. Long story short: my arms got tired. Turns out that it's a kinda fundamental problem with how they had designed the interface - hovering your hands above something for extended periods of time is simply just tiring and uncomfortable.
That seemed pretty obvious the first time I saw it, but I figured maybe I was over-estimating the issue. I mean, here's this darling company with a product everyone's excited about. Surely they must have thought about that!
The Leap Motion still does hand tracking better than MediaPipe, and it's still the best hand tracker I know of (besides larger devices like the Oculus Quest).
We've got an open source library for mobile hand-object input [https://portalble.cs.brown.edu/], and the version with Leap Motion is really nice, but doesn't directly work with a phone (we had to pipe data through a compute stick to make it work).
I'd love to see MediaPipe Hands match LeapMotion precision some day, but I'm not even sure if it's possible. A real depth sensor goes a long way.
Syncthing. Been using this combination for a few months now and seems to work fine between an Android phone and a few Windows + Linux machines.
I had previously been hosting TiddlyWiki from my phone, but offline editing + opportunistic syncing when on WiFi seems to fit a personal wiki better for me.
Highly specific to Dell XPS laptops, but I used to have a similar issue to this. Eventually realised that the display wasn't actually turning off sometimes when I closed the lid. After much mucking around, it eventually turned out that in some of these laptops the magnet in the lid that triggers the "lid closed" action can become physically unstuck, and move around in the display housing (on my XPS 9350 this is in the bottom right corner of the display). Using an external magnet to jiggle it around both allowed testing to trigger the sensor and confirm the issue, and also to move it back to its proper location. Seems to work properly again now.
This sounds like a great idea, and I'm sure there's people that would be willing to help (me included). Is there somewhere organized already for people to discuss the development, or where to contribute (Gitter, Discord, IRC, etc.)? I couldn't find anything mentioned in the GitHub pages.
I've been using SyncThing for years with my KeePassXC database without issues (including Android for use with Keepass2Android).
On the odd occasion it's been modified on two devices without a sync and SyncThing produces a sync-conflict file, a simple "Merge from database..." within KeePassXC happily pulls in the newer data from both databases to merge them again.
I use the Staggered File Versioning feature on at least one device + a separate backup mechanism to satisfy my paranoia about losing the database.
Are there any plans to support different versions of Raspbian (ie. Jessie Light)? Setting up headless pis with only a WiFi dongle (for other people to then use) is something I've often had to do, and setting up that initial connection with a PSK and SSID can be a pain - this would be great for that, though I suspect you'd need some sort of compatibility information added to the block json files.
Having support for Raspbian Lite is possibly the most requested feature right now (along with a block for static IP), and I'm working on that right now. Follow @PiBakery on twitter to get notified of when that update is released!
It didn't really work out though. Long story short: my arms got tired. Turns out that it's a kinda fundamental problem with how they had designed the interface - hovering your hands above something for extended periods of time is simply just tiring and uncomfortable.