osmaczko

I'm happy to learn. Maybe I'll have time to pick it up next week. I'll ask for explanations then. Thanks!

@jakubgs unfortunately, I don't think I will have time for this task anytime soon, as I am already full of higher-priority, protocol-level tasks. 15k+ lines of changes on almost each...

> That's fine @osmaczko, understandable. Thank you. > Unless developers agree that updating the vendor SHA is less annoying than dealing with that massive vendor folder. @jakubgs correct me if...

> * Using a mobile device as a full node when the mobile device is in my home. If the UI catches up with features like community administration, it would...

> > > I've added this [task](https://github.com/status-im/status-desktop/issues/11902) to change the default visibility to false when the state is Accept/Reject pending. When the backend will be available, we can set the...

Hey @ilmotta, the 2.33.2 mobile app version points to [this commit](https://github.com/status-im/status-go/commit/030cbea7312191dc3d66b4a6d66cf68c0460fa0c), which doesn't include the [memory leak fix](https://github.com/status-im/status-go/pull/6449). I've just [cherry-picked it](https://github.com/status-im/status-go/pull/6510) into the `release/10.7.x` branch, which seems to be...

> What I have done before this log: > > * create a new profile > * set profile log level to debug > * leave Status to background >...

Hey mobile team, I did some investigation from the status-go side and have a few findings. Please take a look: - https://github.com/status-im/status-go/pull/6517 - https://github.com/status-im/status-go/pull/6519 (and the comments, especially [this](https://github.com/status-im/status-go/pull/6519#issuecomment-2797752454) one)...