WTF! #HamasisIsis terrorists just released a girl who was kidnapped 52 days ago, WITH HER DOG! 😨

I'm an Israeli, living in Tel Aviv. I don't feel safe and can't work on my day job nor on hobby projects like this one. No jew feels safe nowadays, anywhere. I might feel safer If my enemy shows a shred of humanity and release the civilian women and children. It's your incentive that I feel safe.

X (formerly Twitter)

Ella Kenan (@EllaTravelsLove) on X

Hamas has released 2 Israelis that were kidnapped on October 7th as a "humanitarian gesture". These 2 elderly women are on their way to Israel, y...

Some users asked me about using Permission Groups in WoofBot - I guess it's less intuitive than I thought. Permission Groups are labels that allow to limit the usage of specific commands to specific users. Why? Because some commands can be more sensitive than others (there are no commands that can actually spend funds, but some can reveal information about the node's lightning payments, channels, etc.). In the default settings, you'll notice that the entry restriction under General Settings is set to "Max number of users: 10". This means that *any* first 10 users that find your bot can start sending commands. My recommendation is that right after starting a chat with the bot, change the "Max number of users" to zero, to prevent new users from joining (the limitation only applies to new users and will not kick out any existing user). Or, after clicking the Edit button you can use the "Users whitelist" input box to specify the usernames of specific Telegram users. Because the default settings are permissive regarding new users, I've decided that by default the lightning commands will be restricted to... nobody! Here's what you'll see when you scroll to down in the main page: nostr.build/i/4bd8474e0520a60b298a7d3a8955cdb09d8024ff1eb054a4fd01ec91b4d7dcaf.jpg You can see that the "/watch mempool-clear" command is marked as: "Any signed-in user can run this command", but "/watch lightning-channels-opened", "/watch lightning-channels-closed", "/watch lightning-forwards", "/watch lightning-invoices-created" and "/watch lightning-invoices-paid" are all marked as "Only users that belong to the following permission-groups can run this command" - and the list of permission-groups is empty, meaning nobody can run them! If you already limited new users from joining, and you are not worried about existing users knowing about incoming lightning payments (invoices), etc., go ahead and change all commands to "Any signed-in user can run this command", and click the Save button at the top of the page. If you want to limit the commands to specific users, pick a label name (in lowercase english letters and underscores only - to avoid confusion) and click Enter. For example I picked "vip_users": Don't forget to click the Save button! (You may need to scroll up for that). Then go to the Users page and click on the id of some user, enter the permission-group name, click Enter and then click the Save button: Repeat to every user that you want to add to "vip_users", and they will be able to call the "vip_users" commands. I hope this helps. If you have any question, please let me know in the comments.

🥳 New Version v0.9.7 🥳 - Fixed the /about command: note129vx635uauu7gy2vqejmtnejtpnlrsjrzwccmknnaxquuhwfujnqcz6gnl

There is a minor problem with the /about command and the latest LND v0.16.3-beta - the reply message is: "LND version: unknown". Working on a fix:

GitHub

About command does not return lnd version · Issue #67 · woofbotapp/woofbotapp

Contribute to woofbotapp/woofbotapp development by creating an account on GitHub.

Did you find other problems? Please let me know!

🥳 New Version v0.9.6 🥳 - Important improvement to the logic that looks for outgoing payments from watched addresses. If you watched addresses on a Raspberry-Pi and got many alerts like "your node was not synced for some time" - they happened because the logic was so inefficient that it couldn't keep up with the rate that new blocks were coming. - Important improvement to the logic that watches whether the mempool is "clear" (all the transactions can fit in a single block). The old logic calculated the exact weight of the mempool every minute. Pulling the entire mempool is very slow when the mempool is nearly full (can take even 20-30 seconds). Instead, we now first call a simpler api `getmempoolinfo` which gives the mempool's "size without witness-data", from which we calculate a lower bound to the mempool "weight" (the difference between "size" and "weight" is explained here:

Weight units - Bitcoin Wiki

). If the lower bound is too high (over 4M wu), we know that the mempool is not empty and don't need to calculate its exact weight. If the lower bound is low, calculating the exact weight of the mempool is easy and fast. No new features this time, but if you're running a node on a Raspberry-Pi you'll feel a big difference. Many thanks to The Bitcoin Lizards for stress-testing the Bitcoin mempool.

@Umbrel ☂️ WoofBot v0.9.6 is waiting for review for over a week...

GitHub

Update WoofBot to 0.9.6 by woofbotapp · Pull Request #551 · getumbrel/umbrel-apps

Tested on my Raspberry Pi. This version does not have new features, but contains important performance improvements.

Daily Fail 🤦‍♂️ Apparently it is not a good idea to fetch and iterate over all of the mempool transactions every minute and calculate their total weight in order to check if they can fit in a single block... getmempoolinfo doesn't give the entire weight (doesn't include witness data), but when it's too large anyways we don't care about the exact mempool weight - it won't fit anyways! A fix will come soon.

🥳 New Version v0.9.1 🥳 - Fixing a bug in the integration with LND v0.16.2. Thanks Alex Bosworth for maintaining the Node.JS lightning package (Couldn't find his Nostr to tag him).

😬 The LND integration might be broken with the latest version. Will debug this over the weekend…

X (formerly Twitter)

Umbrel ☂️ (@umbrel) on X

The new Lightning Node app update is now live on the Umbrel App Store with LND 0.16.2 and the ability to view keysend payments in your Lightning wa...

#[0] Verifying My Public Key: "woofbotapp"

🥳 New Version v0.9.0 🥳 - Removed webpage-preview in link to Twitter. Added link to Nostr. - New command: /about - get information about the app version, Bitcoin node version, and LND version. - Adding partner-node name when mentioning channels in notifications - when channels are opened/close, or when payments are forwarded.

#[0] Verifying My Public Key: woofbotapp

@nostrdirectory Verifying My Public Key: woofbotapp

Poll:

X (formerly Twitter)

WoofBot 🐶 (@woofbotapp) on X

If there was a paid WoofBot Telegram bot as a service (i.e 丰10 sats per notification), would you use it? 1. Yes. 2. Not me, but people who don't ...