Petr Kracík
Petr Kracík
That GPIO was probably from some example, it's already half year ago and those days there was nothing like I2S used HDMI if I remember. Also it was just suggestion....
Based on LNDHub documentation, it does not support API call v1/transactions I think problem is because LNDHub backend extends class LND which contain that API Call.. Even there is .catch...
Now I discovered another behavior on new phone: swipe up to see transactions: there is animation seems like "loading"... and it waits like 30sec after those 30sec I can see...
Thanks, I somehow missed this and still creating and uploading my packages to Pypi. Compiled version from mpi seems to be better way, I have to study how to migrate...
How looks this issue? IPv6 is almost everywhere and here it missing global addresses. I just extended wifi sta with global getter, so I can get global IP already
Let me check, for orientation it would be enough. Later I can check also support. But for now I need it as proof-of-concept that board will work and can be...
Github replaces some : with emojisc next time i'll use code block And that ffff is right, it's ipv4 noted in ipv6 format, i suppose haproxy and nginx have it...
+1 for NIP for this. Since there are like 10 different relays and new users/admins can not decide at early testing, it would lead to split/missing data when different relays...
> `nostril-query | nostcat --stream | jq '[.[0], .[2]] | nostcat ` This seems only takes actual (and future) events, not historical. So it could be used to sync two...