{"type":"rich","version":"1.0","title":"Christopher Allen [ARCHIVE] wrote","author_name":"Christopher Allen [ARCHIVE] (npub19g…ct5d0)","author_url":"https://njump.me/npub19g47w5ewcqlpd7n07wpkp5cvcu2gjwrse0vl47l0avwl9hu933xsqct5d0","provider_name":"njump","provider_url":"https://njump.me","html":"📅 Original date posted:2020-05-17\n📝 Original message:On Thu, May 14, 2020 at 8:30 AM Keagan McClelland via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e \u003e It should be therefore a top priority to make the UX of connecting my\n\u003e mobile LN client to my home full node extremely easy, so that centralised\n\u003e services can't improve much on that step. Especially if I already run a\n\u003e full node.\n\u003e\n\nThere already is an emerging approach for this, called QuickConnect\nhttps://github.com/BlockchainCommons/Bitcoin-Standup/blob/master/Docs/Quick-Connect-API.md\n\nIt is currently offered by BitcoinStandup (both Mac and Linux),\nBTCPayServer, Nodl, MyNode, RaspiBlitz full node tools and hardware, and is\nused currently by FullyNoded, FullyNoded2, and a couple of other\nexperimental apps to allow secure connection via Tor v3 from a remote to\nyour own personal full node.\n\nWe know that QuickConnect needs another major iteration and welcome\ncontributions to requirements and/or proposals for the next version.\n\nWe invite you to share your thoughts here.\nhttps://github.com/BlockchainCommons/Bitcoin-Standup/issues/66\n\n— Christopher Allen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20200517/f483ba8b/attachment.html\u003e"}