00:18:11 <plowsof[m]> Hinyo released this interesting pgp script, it appends monero's block hash / date to a message , then encrypts it with your pgp key (to prove it was a recent message) CyberPunk++ mode (how-to is in the repo also) https://github.com/hinto-janaiyo/monero-gpg/blob/main/monero-gpg
00:19:32 <plowsof[m]> Like standing next to a newspaper 😁
00:30:04 <elizabeth[m]> hey all, is there someone else I should message regarding completed CCS milestones? tried messaging luigi1111w a while back but I don't think they got it 
00:30:44 <plowsof[m]> @luigi1111 elizabeth
00:31:06 <elizabeth[m]> thanks! username always changing lol
00:32:29 <nioc> elizabeth[m]: he only uses 4 variations of luigi  
00:34:04 <elizabeth[m]> good to know, I messaged the wrong 2/4 then 😩
00:37:35 <plowsof[m]> also congrats on another completed milestone im guessing! 🥳
00:43:23 <luigi1111> Just message all the luigis
00:43:35 <luigi1111> But yeah sorry if I missed you, happens sometimes
00:47:24 <plowsof[m]> We don't even know if luigi is one person 
00:48:23 <plowsof[m]> the one with 4 1's seems nice, the one with the w im not too sure about yet 
01:59:10 <plowsof[m]> https://www.reddit.com/r/Monero/comments/ux6lzk/ethxmr_atomic_swap_development_update_live_on/
02:47:19 <elizabeth[m]> <plowsof[m]> "also congrats on another..." <- thank you!! been working to share this update for a while, excited to finally get there
12:15:05 <jwinterm> Rucknium[m]: https://twitter.com/W0wn3r0/status/1529435068288180225 :P
13:38:31 <plowsof[m]> There will be a Community meeting this Sunday https://github.com/monero-project/meta/issues/707 👀
14:18:00 <sgp_> I'm going to host a Monero upgrade Q&A again today at noon CT from @monero on Twitter. Will tweet about that shortly. Can anyone join me?
15:12:13 <nikg83[m]> <sgp_> "I'm going to host a Monero..." <- Can you use that Twitter account to help exchange wallets ? 
15:23:40 <sgp_[m]> <nikg83[m]> "Can you use that Twitter account..." <- ?
15:23:41 <sgp_[m]> https://twitter.com/monero/status/1529482668097916929
16:08:53 <msvb-web> Great news plowsof[m], cool to hear about another community meeting.
19:08:08 <chesterfield[m]> plowsof ... so hot right now
22:20:42 <nikg83[m]> <sgp_[m]> "?" <- https://twitter.com/polosupport/status/1522573011408330753
22:21:17 <nikg83[m]> Maybe offer them help if they genuinely have wallet problem
22:42:13 <cryptogrampy[m]> HELLO ALL
22:42:59 <plowsof[m]> Hello Gramps!
22:43:58 <cryptogrampy[m]> I JUST WANTED TO SHARE THAT I ADDED USD/EUR AS DEFAULT CURRENCIES IN HOTSHOP, SO YOU'LL BE ABLE TO TYPE IN '$0.23' WHICH IS THE PRICE I PAID FOR GAS WHEN I WAS YOUR AGE AND IT WILL CALCULATE THE XMR EXCHANGE AMOUNT AND DISPLAY IT IN THE QR FORMAT ON THE RECEIVE SCREEN.  PLEASE FEEL FREE TO TEST IT OUT, AND ONLY USE TINY AMOUNTS AND TEST/PLAY WALLETS: https://sunny-malabi-a3b5ff.netlify.app/
22:44:33 <cryptogrampy[m]> (alternatively, you can turn off the exchange stuff or keep Monero as the primary currency in the settings tab in the top right)
22:45:47 <cryptogrampy[m]> multiple confirmations should also be fairly functional as well.  
22:47:02 <dsc_> awesome
22:47:17 <cryptogrampy[m]> I'M HEADING DOWNSTAIRS FOR ROOT BEER FLOAT AND MOVIE NIGHT, BUT PLEASE LET ME KNOW IF THIS IS WORKING FOR YOU.  IF YOU USE ALL OF THE DEFAULTS AND JUST WANT TO TEST IT OUT, THE AMOUNTS PAID TO THE DEFAULT QR/ADDRESS IN THERE MAY OR MAY NOT GO TO MY WALLET.  YOU HAVE BEEN WARNED.
22:49:11 <plowsof[m]> Awesome indeed, thank you for the updates!
23:13:52 <BusyBoredom[m]> This is awesome cryptogrampy, super user friendly!
23:13:52 <BusyBoredom[m]> Why does it require nodes to be HTTPS, and do you have a plan to use subaddresses instead of integrated addresses? 
23:43:23 <cryptogrampy[m]> > <@busyboredom:monero.social> This is awesome cryptogrampy, super user friendly!
23:43:23 <cryptogrampy[m]> > 
23:43:23 <cryptogrampy[m]> > Why does it require nodes to be HTTPS, and do you have a plan to use subaddresses instead of integrated addresses?
23:43:23 <cryptogrampy[m]> most browsers upgrade the http request to https automatically and it will cause errors.  Http is fine with .onion nodes.
23:43:35 <cryptogrampy[m]> also thanks :) 
23:44:18 <cryptogrampy[m]> And I used integrated addresses because they can be generated with zero knowledge of the spend key wallet's address usage.  With subaddresses, you need to know the spend key wallet's subaddress index to be able to generate new ones.
23:45:02 <cryptogrampy[m]> You always know you're getting a fresh/random integrated address, but you don't know if you're reusing a subaddress, and you don't know if the spend key wallet will even detect the spend in a high index subaddress 
23:46:41 <cryptogrampy[m]> you could send a link to your custom HotShop to a dozen of the waiters at your restaurant and they would be able to collect payments all at the same time and have no address collisions
23:51:08 <plowsof[m]> in the situation of multiple workers , they could each have their own custom shop , each with a specific sub address - however - the 'boss' would still need to maintain a database of who is assigned what sub address, this would work, but payment id's are 'simpler' 
23:54:38 <BusyBoredom[m]> You can generate subaddresses using only view key and primary address, because the primary address contains the public spend key (credit to plowsof for pointing that out to me a while ago). 
23:54:38 <BusyBoredom[m]> Your other point makes perfect sense though, subaddresses would require some central DB to prevent collisions 🤔
23:54:48 <cryptogrampy[m]> plowsof[m]: Still wouldn't work.  HotShop begins syncing at the latest blockheight for speed reasons.  In the subaddress case, you would still need each server to do a full sync to prevent address reuse
23:55:39 <cryptogrampy[m]> > <@busyboredom:monero.social> You can generate subaddresses using only view key and primary address, because the primary address contains the public spend key (credit to plowsof for pointing that out to me a while ago). 
23:55:39 <cryptogrampy[m]> > 
23:55:39 <cryptogrampy[m]> > Your other point makes perfect sense though, subaddresses would require some central DB to prevent collisions 🤔
23:55:39 <cryptogrampy[m]> Yeah generation random subaddresses isn't a problem, it's generating subaddresses that haven't been used that's the problem, but apparently this will be solved soon(tm)
23:55:50 <cryptogrampy[m]> err
23:56:07 <cryptogrampy[m]> generating subaddreses that haven't been used, but also are at the correct index to be detected by a wallet
23:56:31 <plowsof[m]> is address re-use an issue? if its a point of sale / wait for payment
23:58:22 <cryptogrampy[m]> hmmm i'd say it's very not ideal
23:59:07 <cryptogrampy[m]> integrated addresses are much sexier
23:59:36 <plowsof[m]> HotShop works perfectly as is with payment id's , other methods are possible which require extra logic ~ some caveats ~ the boss has to link sub addresses to each employee ( think.. swiping an nfc badge on a PoS system etc )