05:27:08 Howdy fellas 🤠 > Hi 16:50:15 I wonder if the monero: URI schema can be registered with IANA 16:59:12 that only makes sense for Windows 17:05:15 gan: What about GANA payto registry? 17:11:32 This isn't about Windows btw lol. This has to do with a new standard about requiring payment in XMPP 17:12:57 Initially the standard would maintain its own registry for payment types, but due to concerns (mostly just people wanting their shitcoin to appear on it), the registry was offloaded to the IANA and GNUnet registry 17:14:39 Similar for RFC8905, handling of them depends on a system-provided URI handler and potentially its dispatcher 17:14:40 None of that requires registration per se, for example, I believe obsidian (https://obsidian.md/help/uri) is unregistered, while steam https://www.iana.org/assignments/uri-schemes/prov/steam is 17:14:41 That's even less relevant because that should be up to the client, XMPP as a protocol shouldn't be concerned about that, unless they have a specific XEP which recommends a set 17:14:42 Cindy_: GNUNet as a project is against cryptocurrencies as a whole, good luck with that 17:14:43 Interesting that the RFC doesn't really target GNU Taler 17:19:57 I mean yeah, the ProtoXEP has switched to a generic URI (and not a payment type with all the details in it) 17:23:20 But the standardization is important for parsing details off the URI 17:27:46 gan: Also GNUnet registry interestingly has ETH in it 17:28:02 https://gana.gnunet.org/payto-payment-target-types/payto_payment_target_types.html 17:28:14 I see no use in it largerly, magnet existed for ages before receiving any assignment from IANA 17:28:15 to not mention that majority of XMPP clients determine clickability of a link based off author's vibe and shattered dreams 17:29:00 https://git.gnunet.org/gnunet/gana/file/payto-payment-target-types/eth.txt.html 17:30:11 Huh, interesting, perhaps I shat myself informationally-speaking 17:30:12 Maybe after LynX moved on, Grothoff became more open to it 17:32:34 To be quite honest, I'm just curious if you could get away with publishing a payto:// schema standard for Monero to GANA 17:32:43 :P 17:34:06 Looks like they don't exactly require a formal proposal with the big players? 17:34:08 at least, judging from https://gana.gnunet.org/about.html#history 17:34:10 So, indeed, maybe they should be email about incorporating Monero then 17:38:34 Also this is how the ProtoXEP looks like, just so you know (and I know it looks AI sloppish, blame the author): https://xmpp.org/extensions/inbox/payment-required.html#usecase-muc 17:38:51 You're given an error with options that have a link URI inside them 17:39:02 (and a label about what they're supposed to be) 17:39:49 Ideally clients should be able to parse them to show the actual amount if they could 17:40:34 Instead of having the user click and wait to be able to see the actual amount from their wallet app 17:41:54 So yeah, it would be nice if the URIs were standardized 17:42:22 Perhaps so 17:47:12 Also the author, for some reason, REALLY likes Lightning 17:47:28 I don't really know why 17:48:16 Eh, probably because it at least makes bitcoin usable, I guess? 17:48:32 You can always ask the Nostr crowd 🧌 17:48:38 Lol 17:49:21 If having to keep like 5-6 different open channel is required to make bitcorn usable... 17:49:40 send a LN payment, thing try 75 different routes until it find one that work! 17:50:09 https://git.gnunet.org/gnunet/gana/file/payto-payment-target-types/POLICY.html 17:50:25 "Adding records is possible after expert review" 17:50:28 Expert review? 17:50:47 Do they mean GNUnet/Taler experts? or Monero experts 17:53:31 Good question with no answers 17:53:31 Probably somebody need to shoot up an email to seek clarification on that