I believe my zapper is now back in service after upgrading to
new hardware multiple times.
1st hardware upgrade attempt MeerKat from system76
USB would loose power after 24 hours of run-time.
Only discovered after completing a full migration.
Return the hardware after retreating to old hardware.
2nd hardware upgrade attempt desktop from Velocity Micro
Issue with graphic card.
returned next day after receiving
Current hardware upgrade desktop from system76
Did a one week burn-in before doing any migrations.
no issues so far.
Now three months or so later, I've updated the local instance
of albyhub and opened a new LSP channel with Olympus by Zeus.
Here is the ablyhub upgrade process that worked for me.
Download current release and manifest files
Navigate to 
Download albyhub-Server-Linux-x86_64.tar.bz2
manifest.txt
manifext.txt.asc
-------------------------------------------------------------
Copy the downloaded files to $HOME
mv $HOME/Downloads/albyhub-Server-Linux-x86_64.tar.bz2 $HOME
mv $HOME/Downloads/manifest.txt $HOME
mv $HOME/Downloads/manifest.txt.asc $HOME
---------------------------------------------------------------
Verify manifest signature & Checksum
Only need to import once
curl https://raw.githubusercontent.com/getalby/hub/master/scripts/keys/rolznz.asc | gpg --import
gpg --verify manifest.txt.asc manifest.txt
shasum -a 256 albyhub-Server-Linux-x86_64.tar.bz2
The above checksum should be referenced in the file, manifest.txt.
cat manifest.txt
----------------------------------------------------------------
Stop AlbyHub & Backup existing data
systemctl stop albyhub
cp -r $HOME/.local/share/albyhub /media/veracrypt1/albyhub
cp $HOME/bin/albyhub $HOME/bin/albyhub114
cp -r $HOME/lib $HOME/lib114
----------------------------------------------------------
Extract new release Binaries & Start AlbyHub
tar -xvjf albyhub-Server-Linux-x86_64.tar.bz2
./
./lib/
./lib/libldk_node.so
./bin/
./bin/albyhub
systemctl start albyhub
----------------------------------------------------------------
Login and open new private channel
Navigate to http://localhost:9090
GitHub
Releases · getAlby/hub
Alby Hub - Your own Bitcoin Lightning node: easy, connectable, feature-rich ✨ Run anywhere. Become self-sovereign. - getAlby/hub
When we launched Keybase over 11 years ago, we read a lot of good, well-informed feedback. We folded some but not all of these suggestions into Keybase. Most important, you convinced us that passwords are not a good long-term strategy for protecting secret key material. As a result, we spent months ripping up the app and pivoting to per-device keys, which were clearly the right way to go. WhatsApp eventually caught up in 2023!
Among the best ideas that we lacked the bandwith to tackle were: federation, open-source backend, YubiKey support and SSO support. No longer affiliated with Keybase or Zoom (Keybase’s new owner), I’ve been thinking about how to resurrect these very good ideas. Today, I’m happy to announce FOKS, the Federated Open Key Service. The gist is “Keybase, but with federation, SSO and YubiKey support, and fully open-source”. FOKS is not a fork, but rather built from scratch in pure Go. FOKS inherits the general goal of Keybase: give teams of users, each with multiple devices, shared secret keys so they can share data securely across the internet. It inherits Keybase’s core cryptographic techniques: append-only data structures that allow clients to catch dishonest server behavior; and cascading key rotations on device revokes and team member removals. The key difference is federation.