01:08:09 <sgp_> I don't know if this is the right place to report this, but I was trying to broadcast a transaction from my daesom today and I believe it didn't work since it couldn't find i2p nodes to broadcast to
01:08:28 <sgp_> removing the monerod i2p options allowed it to work just fine
01:08:54 <sgp_> the relay_tx command returned a message that the transaction was successfully relayed when I was using i2p, but it wasn't
01:14:16 <sgp_> Better UX includes the following:
01:14:23 <sgp_> 1. Saying the broadcast failed
01:14:53 <sgp_> 2. Saying that there are no nodes to connect to in i2p/Tor if that's the issue
01:15:28 <sgp_> 3. Possibly passing the option back to the user in the daemon or wallet to broadcast over clearnet if desired
01:37:25 <objectorange> I thought TOR and I2P support wasn't integrated yet.
01:38:24 <objectorange> the UX surely should let the end user know that if true
02:39:05 <gingeropolous> id bet 1 montero that we won't see fullon i2p/tor until we make it the default
03:19:50 <objectorange> I don't believe it's even possible to use them yet right?
03:20:20 <objectorange> Aren't they awaiting review prior to merging them into main?
03:20:53 <objectorange> I would think we should run them through a testnet for at least a year first no?
03:21:21 <objectorange> Or six months...between releases.
03:21:32 <objectorange> Then six months on limited nodes.
03:21:52 <gingeropolous> afaik, it just hooks into existing software more or less and then relays using existing networks... ?
03:21:52 <objectorange> Like a special release only for a select few to limit any issues.
03:22:21 <objectorange> So the code is available and just requires the person setting it up to configure it?
03:22:25 <gingeropolous> i mean, you have to manually set up the tor / i2p nodes... well i dunno actually. i'll stop talking
03:22:35 <objectorange> yeah I don't know either
03:22:45 <objectorange> I saw the configuration settings for adding them as proxies
03:23:21 <objectorange> And I thought moneromooo said that it was awaiting review, but that might be on sekreta only
03:23:41 <objectorange> I don't have the whole picture yet on kovri and sekreta
03:23:52 <objectorange> I thought kovri was just I2P too
03:24:13 <objectorange> I had no idea you guys were supporting TOR too
03:24:25 <objectorange> I don't think that's been out in the general news
03:24:38 <gingeropolous> well the cryptonews is so good
03:25:26 <objectorange> great seeing monero support both TOR and I2P
03:29:25 <objectorange> now...is it really? :)
03:44:08 <vtnerd> i2p/tor support is already included
03:44:20 <vtnerd> but finding nodes via seeding is not yet integrated
03:45:49 <vtnerd> we were hoping to use the ipv4/6 seed nodes to spread hidden service information, but there seems to be a few privacy issues with that
03:46:18 <vtnerd> i2p/tor was actually in the last release
03:46:37 <vtnerd> the cli wallet also supports connecting to a daemon of i2p/tor too
03:46:42 <vtnerd> *over i2p/tor
05:20:20 <objectorange> awesome
05:20:38 <objectorange> so nodes must be specified manually?
07:49:53 <omartijn> hyc: You're right, read txns are are also using mdb_txn_safe as well, so that only leaves the issue of multiple threads calling the unsafe env_set_mapsize
07:50:38 <omartijn> It's an unlikely scenario indeed, since you need to be modifying the database from outside monero, but it's still a possible problem
11:29:19 <ErCiccione[m]> Would be a good idea to autoban an IP address:port when it keeps spamming a wrong version number? Doing it manually doesn't make any sense in the case there are multiple nodes using a wrong version.
11:33:00 <moneromooo> I think so.
12:31:04 <ErCiccione[m]> Ok, i will open an issue about it
13:15:12 <sgp_> vtnerd: did you see my comments above?
13:24:19 <vtnerd> ah, yes about i2p, was that for the cli or the gui
13:24:39 <vtnerd> the cli needs to print out info too really
13:26:55 <vtnerd> yeah I need to some logs for 2 specific cases
14:33:41 <selsta> I wonder if Github is having problems
14:34:36 <omartijn> It seems to be slow in updating the web interface and calling webhooks atm
14:35:01 <selsta> I force-pushed 3 minutes ago and the PR is not updating. Guess I’ll wait.
15:14:31 <sarang> https://www.githubstatus.com/
15:24:51 <selsta> yep I looked underneath the graph and missed the status message on top lol