07:20:25 <m-relay> <m​onerobull:matrix.org> hello
07:20:44 <m-relay> <m​onerobull:matrix.org> why doesnt the new gui connect to my node
07:22:23 <m-relay> <1​23bob123:matrix.org> https://github.com/monero-project/monero/issues/9235#issuecomment-1987596301 ?
07:22:59 <m-relay> <m​onerobull:matrix.org> lol of course
07:23:15 <m-relay> <m​onerobull:matrix.org> i set a rpc password and the very next release breaks it
07:23:29 <m-relay> <1​23bob123:matrix.org> rip
07:24:37 <m-relay> <m​onerobull:matrix.org> and whats wrong with the other nodes?
07:24:56 <m-relay> <m​onerobull:matrix.org> without password
07:57:21 <plowsof> DE node @ node3.monerodevs.org:18089 with spare bandwidth 
07:58:08 <plowsof> Monerobull can you connect to nodes without password fine in the gui? Surely 
07:58:31 <m-relay> <m​onerobull:matrix.org> No
07:59:00 <m-relay> <m​onerobull:matrix.org> Tried xmrvsbeast and tux.pizza
08:00:24 <plowsof> Cant test until the afternoon selsta 
10:10:58 <m-relay> <1​23bob123:matrix.org> 50 lashes for jeffro?
11:31:06 <selsta> plowsof: i think you can connect when switching from local node to remote node with it already selected
11:36:10 <selsta> basically select -> it fails to connect -> click on local node -> switch back to remote node and it should connect
11:36:45 <selsta> what i'm most annoyed is that i saw this before release but i thought it's a GUI bug because i usually don't use rpc-login
12:47:23 <sech1> selsta https://www.getmonero.org/2024/03/09/monero-GUI-0.18.3.2-released.html "Update p2pool to v3.8" it's v3.10
12:47:50 <selsta> will update the release notes
13:07:26 <ofrnxmr> "i set a rpc password and the very next release breaks it" << its been on master for 5mths. I feel partially at fault for not noticing 
13:08:08 <ofrnxmr> Havent run master in a long time, and i use these features 
13:14:30 <m-relay> <p​lowsof:matrix.org> ofrnxmr matrix account unbanned in #monero-gui:monero.social by plowsof
17:46:13 <m-relay> <1​23bob123:matrix.org> Thank fck
17:48:41 <m-relay> <1​23bob123:matrix.org> What about naptha ?
17:48:42 <m-relay> <k​inghat:matrix.org> BigmenPixel: whats left to get the flatpak verified on flathub and then it can be added to the website as a suggested install?
17:51:27 <m-relay> <k​inghat:matrix.org> oh looks like: https://github.com/flathub/flathub/issues/3905#issuecomment-1872557613
18:12:51 <m-relay> <1​23bob123:matrix.org> How come it was relying on one person?
19:24:34 <m-relay> <o​frnxmr:monero.social> Bigmen has been maintaining for a long time
19:25:07 <m-relay> <o​frnxmr:monero.social> The problem is that we wanted it to be more "official", but the roadblock is that flathub is anything but official
19:26:39 <m-relay> <o​frnxmr:monero.social> Tobtoht's featherwallet flatpak is shipped in the most ideal way, imho. Not sure how difficult it would be ship like that
19:28:18 <selsta> i don't want any extra work regarding flatpak, if it's something we have someone else has to maintain it
19:28:24 <m-relay> <t​obtoht:monero.social> ofrnxmr: easy to upstream once #8929 is merged
19:28:55 <m-relay> <o​frnxmr:monero.social> That's amazing news
19:30:46 <m-relay> <o​frnxmr:monero.social> And +1, selsta
20:08:01 <m-relay> <p​lowsof:matrix.org> for bigmenpixel, i think reaching out to community to approve payout for his entire CCS (1 year of maintenance will be over this month, and from affar he has been performing duties / more work than the debian/whonix maintainer did for certain). then coming back to the table seeking opinions on this flatHUB / flatpak situation. afaict the "work" (the workflow for packaging / pushin<clipped message>
20:08:01 <m-relay> <p​lowsof:matrix.org> g binaries to a flatpak server) has been done
20:08:54 <m-relay> <p​lowsof:matrix.org> one look at the install/update stats for flathub shows how valuable (or... dangerous) flathub is and im uneducated on how to proceed
20:09:27 <m-relay> <p​lowsof:matrix.org> https://klausenbusk.github.io/flathub-stats/#ref=org.getmonero.Monero&interval=infinity&downloadType=installs%2Bupdates
20:10:40 <m-relay> <p​lowsof:matrix.org> i can offer an opinion and say yeah, ofcourse get the verified checkmark, why not? hashes can be confirmed for the github workflow (thats done on monero-core repo) and the client but im sitting here with a hardware wallet