This is a thread for random discussions that gets posted everyday at 5am central.
Tell us what you're doing today, ask questions, or vent about your life. Whatever you want, let it rip!
pull down to refresh
1 sat \ 1 reply \ @nout 18 Jan 2022
What's keeping me busy
- One person from the team I manage resigned today (for family reasons) :(
- Two new people are starting next week
- Some weird CSS issue that seems to be a Chrome bug...
reply
0 sats \ 0 replies \ @k00b 18 Jan 2022
I'm sorry about your teammate! Happy to hear your team is still growing though.
reply
1 sat \ 0 replies \ @relc 18 Jan 2022
checking stacker news since long time
reply
7 sats \ 0 replies \ @k00b 18 Jan 2022
Going to ship the WoT ranking algo shortly. It'll won't be live on the main feed yet but I'll write a little about the model we're using.
Then I'll probably spend the rest of the week doing some of the smaller items from the github issue backlog.
reply
4 sats \ 4 replies \ @jb55 18 Jan 2022 freebie
yesterday I released lnsocket, a C library for sending messages on the lightning network. It can currently connect to lightning nodes and send/receive lightning network messages (TLVs).
This weekend I am planning on getting the build working on iOS so that I can make a proof of concept for controlling a clightning node directly over lightning.
Right now it's a bit difficult to connect to your lightning node's wallet: you have to run other software next to your lightning node that connects to it's RPC to send/receive wallet information, channels, etc. It would be nice if your lightning node could give you this information directly over the lightning network, since your lightning network port is already publically exposed on tor or the internet.
All you would need to do is whitelist client pubkeys and you would be good to go!
Maybe one day we could have a blip that specs out a standard RPC mechanism so this could work for all nodes instead of just via a clightning plugin.