ndeet's avatar
ndeet
ndeet@btcpayserver.org
npub1qm72...74md
Let's change the world with #bitcoin. Working on BTCPay Server integrations for e-commerce solutions. Mostly PHP and JS.
ndeet's avatar
ndeet 2 weeks ago
Land of the free? Only if you didn't make uncle Donald angry, no congress approval or change of law needed? Even here in EUdssR they at least do some democratic theater and push through laws when countries get sanctioned. View quoted note →
ndeet's avatar
ndeet 3 weeks ago
Huge opportunity for Bitcoin / LN, we have everything setup already. It's easy for agents to get an LN wallet working without KYC. You as agent operator (or your agent) should reach out to merchants and ask them to support Bitcoin payments. There are plenty of solutions like @BTCPay Server and other self-custodial and custodial solutions out there that are easy to setup for merchants - without them having to do a masterclass in LN channel management. This is a great trend and opportunity we should use to push for Bitcoin adoption. Let's go! View quoted note →
ndeet's avatar
ndeet 1 month ago
#openclaw lessons: crash during update, all broken, `openclaw` commands do not work anymore ##What happened: When running `openclaw update` there were some warnings but the usual screen that asks you for restarting the service did not appear, it just stopped. **Error on console you see when that happens during `openclaw update` (or not if you let openclaw update itself 💀 ** `Update Result: ERROR Root: /home/ndeet/.npm-global/lib/node_modules/openclaw Reason: global update Before: 2026.2.15` When trying to run `openclaw status` there was an error that the binary was not found anymore: `$ openclaw -bash: /home/ndeet/.npm-global/bin/openclaw: File or directory not found` ##What happened (in my case): System ran out of memory and I did not have a swapfile configured. I run openclaw on a local server using proxmox kvm VM and it has 4GB of ram. **to check if your server also ran out of memory: ** `journalctl -b | grep -i "out of memory\|oom\|killed process"` if it shows some crashes of openclaw.service or npm then you likely have the same issue as me In my case the old install was moved to temporary directory but new version not installed yet due to error ``` $ ls -lah ~/.npm-global/bin/ total 8,0K drwxrwxr-x 2 ndeet ndeet 4,0K 18. Feb 11:29 . drwxrwxr-x 4 ndeet ndeet 4,0K 30. Jän 17:35 .. lrwxrwxrwx 1 ndeet ndeet 44 30. Jän 18:06 clawdhub -> ../lib/node_modules/clawdhub/bin/clawdhub.js lrwxrwxrwx 1 ndeet ndeet 40 30. Jän 18:06 mcporter -> ../lib/node_modules/mcporter/dist/cli.js lrwxrwxrwx 1 ndeet ndeet 41 16. Feb 11:54 .openclaw-8sOzPP85 -> ../lib/node_modules/openclaw/openclaw.mjs ``` note that there is no symbolic link pointing to openclaw.mjs but only the temporarily moved one of `openclaw-8sOzPP85` Solution: move symlink so openclaw works again `mv ~/.npm-global/bin/.openclaw-8sOzPP85 ~/.npm-global/bin/openclaw` Now openclaw should work again (try by running `openclaw status`) but doing update would likely crash again. The best solution would be to allocate more RAM but it could also be that you did not have any swap configured that can be used for ram spikes like this (check with `free -h | grep Swap`). So if you don't have any swap you can create a swapfile. ##Create a swapfile: ``` # Create the file sudo fallocate -l 4G /swapfile # Secure it (only root should read it) sudo chmod 600 /swapfile # Format as swap sudo mkswap /swapfile # Enable it sudo swapon /swapfile # Verify free -h ``` Make it permanent across reboots: `echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab` Optionally, tune swappiness (default is 60, lower = RAM preferred over swap): `echo 'vm.swappiness=10' | sudo tee -a /etc/sysctl.conf` `sudo sysctl vm.swappiness=10` **You can now try the update again and it should work. 🥳 **
ndeet's avatar
ndeet 1 month ago
Don't use #openclaw wrapper services that make it easier to run. It's already easy and the creator of openclaw discourages it himself. He constantly works to make it easy as possible to do it yourself. Most wrapper services will be gone when the hype dies off. When you use wrapper service you expose data to: - wrapper service - hosting provider (maybe subcontractor of datacenter) - model provider When you host at VPS provider: - hosting provider (maybe subcontractor of datacenter) - model provider When you host at home *: - model provider ** * you don't need a mac mini, completely overblown, you can run on e.g proxmox server (2-4gb ram plenty enough), start9, or old laptop, you don't even need it run 24/7 ** you can use Maple AI which anonymizes data, not sure about ppq.ai. Best would be local models but not economically possible with big models atm. No matter what as long as local models not possible, you will always send sensitive data to model providers to complete tasks. Better avoid other 3rd parties that can also read your data. If you can't do it yourself ask someone you trust to set it up on your home server or on a VPS rented by you. Avoid convenient wrappers.
ndeet's avatar
ndeet 1 month ago
Very good perspectives. Especially about finding out about minority fork, makes me still a bit uneasy thinking about that 😄 Seems Walker also came around from unconditionally following Core opinion. Biggest take: there is often nuance and seldomly just black and white. View quoted note →