autopilot word brings shivers to every noderunners spine

Reply to this note

Please Login to reply.

Discussion

Could you explain what you wrote for everyone (an us) to understand? Should we wait for the new functionality adoption or can we do something about it?

Its more of a technical thing that should improve over time, it’s something clients need to do

Right, the Rabbit client has limited UI context so I just saw Will's note, but else's; still it seems it answers to everyone in the conversation. Autopilot is usually a word associated by bitcoin lightning operators (aka node runners) as the easy solution to channel management that ended wrong because the code opened and closed several channels per shorts periods of time, thus the shivers. ¡Saludos!

Yes nostr autopilot is completely different. Instead of managing channels (i don’t trust ai with my money) it manages relay connections. where it pulls data from based on peoples read/write relay lists.

To implement this safely you need to harden your client against relays that might try to do nasty things to your client, which is why its a bit more work than just connecting to a trusted relay pool

from where it pulls data that sounds great! from where it writes to, i think that could be reckless...

still the fashion of choosing a relay very well could be similar as to choosing a newspaper brand, that could meaning, a very personal decision

Yes autopilot is more for what you’re reading from. You configure your own write relays, except for a few situations: writing to specific people and replying to threads. You need to write to the relays that user reads from or else they may not get the message.

mhmhmh the probing tools of lightning could be of use?

Alex's 'The Boss' Bosworth (Balance of Satoshis) code had some great features to rout payments...

I don’t think you can stretch the analogy that far in this case. Probing is something very specific to lightning