This reminded me of that swatch internet time project, dividing the day into 1000 beats.

Swatch Internet Time

Swatch Internet Time

Current time in .beats, epoch, etc.

View quoted note →

Built my first n8n dashboard for #cln Cool cool

Managed finally to get my lightning node rebalanced via sling i guess i can call myself now a real node operator Gotta keep playing around with the fees though but very satisfying for a small node indeed Still looking for a new watchtower candidate

LightningNetwork+

LN Login • LightningNetwork+

Bitcoin Lightning Network Liquidity Swap Organizer

#cln @Start9 #sling

https://bip110.orange.surf/live.html We are now 300 blocks ahead is it over or they just take a break ? Are we now the good guys or like the Roman Empire who brings peace and slavery ? So many questions !

Personal relay test!

Snowflake docker proxy NAT restricted vs unrestricted makes a difference ❄️ Snowflake proxy (last 24h) Connections: 812 Traffic relayed: ↓ 8,37 GB / ↑ 0,80 GB Finally got around to configure this on all levels correct! #tor #snowflake

Good reading! I think I understand the direction and you have started strong regarding knots and its challenges but then you just went on about core and bip110 and suddenly you said knots it is for me. 2 questions A/ do you imply that arbitrary data on core and consequently bip110 is a bigger change/problem for you where as knots than seems to be the smaller “evil” ? B/ did you dig further into the knots dev structure especially the single point of failure you have mentioned? I am a node operator since some time and have updated mine to core v30 but with a limited op_return threshold, assuming this way I may navigate through this, but also lacking the time to really understand the issue at hand, however your article has helped, thanks

Does anyone have got also a challenge with restricted NAT usage on a snowflake docker setup since a few days my connection seem to be 0 #asknostr #tor #snowflake

Close call 🇩🇪 but its a result driven sport