I used to rely on keybase to pass around docs among devices. I don't believe keybase has been maintained for some time now and the file transfer seems to have stopped working. In comes #Syncthing, which I've used for various things over the years. I now have multiple devices syncing through an encrypted and self-hosted server and passing docs around works really well. One thing I don't like to rely on are the shared Syncthing discovery servers, so I configured Syncthing to run without using them. Also, the docs weren't quite clear on how to config encryption so all docs are stored encrypted on the central server, while being decrypted by the remote devices. I finally figured it out. While not intuitive it is quite easy to do now that I understand how to do it. Would anyone be interested in me further documenting this use case? #foss #opensource

Who can tell me how to install Aurora Store on a @daylightco without logging into the Google Play store?

Received my first zap from @Patches, many thanks!

What are some effective ways to bootstrap liquidity for a #lightning channel? For example, when setting up @ZEUS for the first time, it's recommended to buy a 0-conf channel. Ideally I could do this w/sats generated by a #bitaxe connected to @OCEAN, however it appears one needs some liquidity to receive payouts, which brings us full circle. I can see providing value and receiving zaps via Nostr as one option, so would be curious to hear what someone w/a devops background could do for people in exchange for some zaps.

I've kept one #Bitaxe pointed at Public Pool for the big bang 💥 and reconfigured another to point @OCEAN to unleash a trickle of sats 🌊

Just when I was about to add my first bookmark, then hesitated thinking the list had to be public, I discovered Private Bookmarks Nostr + the @Amethyst UI for the win 🦾

Turns out connecting a #Ledger to a #qubesos qube is easier than I thought it would be. - plug the Ledger into the laptop - attach Ledger to qube - add Ledger udev rules using this script

GitHub

udev-rules/add_udev_rules.sh at master · LedgerHQ/udev-rules

udev rules to support Ledger devices on Linux. Contribute to LedgerHQ/udev-rules development by creating an account on GitHub.

And that's about it.

When I had my #bitaxe connected to public pool I saw many shares submitted regularly. Now that I switched to @OCEAN I barely see any shares submitted. Is this to be expected and if so, why?