No worries.
I don’t think people show as online until after they have successfully added each other anyway.
UPDATE: Looks like it’s worked this time. We got connection!
I’m off now too, looking forward to the next update @riddim ![]()
No worries.
I don’t think people show as online until after they have successfully added each other anyway.
UPDATE: Looks like it’s worked this time. We got connection!
I’m off now too, looking forward to the next update @riddim ![]()
If fees are above 0.2 GWEI, the default max-fee, then uploads may fail due to ant detecting that and preventing uploading. A safety feature so people do not lose all their ETH if they do not set the max-fee option themselves
dweb doesn’t use the same limit as ant (and the limit can be adapted on startup)
--max-fee-per-gas <MAX_FEE_PER_GAS>
Max fee per gas / gas price bid.
Options:
- `low`: Use the average max gas price bid.
- `market`: Use the current max gas price bid, with a max of 4 * the average gas price bid. (default)
- `auto`: Use the current max gas price bid. WARNING: Can result in high gas fees! (default: when using custom EVM network)
- `limited-auto:<WEI AMOUNT>`: Use the current max gas price bid, with a specified upper limit.
- `unlimited`: Do not use a limit for the gas price bid. WARNING: Can result in high gas fees!
- `<WEI AMOUNT>`: Set a custom max gas price bid.
I think the doc string is wrong - for me it always shows
Max fee per gas set to: LimitedAuto(60000000)
so 0.06 gwei
which is the limit I’ve seen every time I recognized it on startup
thanks for pointing this out @neo I somehow missed that this error message by me is not right either
I probably should just drop any assumptions about particular levels
Originally I used the same limits but may not have tracked their change at some point. Probably in the options.
I don’t know if it’s only me but some of previous messages seems to disappear.
Yes I’m seeing the same… A bug in the message Persisting it seems - haven’t had a chance to dig into it…
My suspicion is that it’s somehow connected to my timeout falling and the current state of the Scratchpad not being read correctly… (I’ve added a 10s read timeout to my operations because at some point it seemed to me a pretty sane assumption that the Scratchpad doesn’t exist if the value doesn’t get returned within that timespan… I’ve seen that limit being hit repeatedly within the last weeks though…
any update? network propagating messages quickly enough or are things just crooked?
Network is fine - riddim not so much
And there’s evil stuff lurking so I might not be able to do too much in the near future - just because of family stuff and not because of the network ![]()
I hope things turn around for the better soon, for your sake but also that we need you.
Just popped back to celebrate
a new Friends/Dweb user (a self described non techie) via Mastodon…
Oh… I guess I need to release a version without timeouts… The network is a bit slower lately and the timeout being hit and Scratchpads being interpreted as non-existing does cause trouble within the app logics…