Marcin Rataj

I think this is greatly outdated, most of things got resolved, and remaining ones changed priority. We did not maintain list in this issue since March. Let's close this to...

@SgtPooki thanks for flagging, for issues that exist in other repos: - https://github.com/ipfs/helia/issues/665 - https://github.com/ipfs/helia-verified-fetch/issues/52 - https://github.com/ipfs/helia-verified-fetch/issues/160 we should have dedicated tickets here that can be closed once a dependency...

When it comes to UI, would be good to make something that looks good on mobile, so we have less work when we are ready to ship PWA (https://github.com/ipfs-shipyard/helia-service-worker-gateway/issues/21)

Mostly done in https://github.com/ipfs/service-worker-gateway/pull/310, remaining work here here is to add protocol handlers to manifest: - https://developer.mozilla.org/en-US/docs/Web/Manifest/protocol_handlers It should use the same handler as one described in - https://github.com/ipfs/service-worker-gateway/issues/214#issuecomment-2102963620

Yes, existence of BASE_URL means hostname needs to be hardcoded at build time, which means we can't have single trusted build which can then be deployed/cached on multiple gateways, people...

In my experience, the needs are: - Ability to **move Issues** between repositories within the same org - Example https://github.com/ipfs/ipfs-desktop/issues/1954 → https://github.com/ipfs/ipfs-webui/issues/1900 - Ability to **move Repositories** between Orgs -...

The `swarm.key`-based [private network (aka PNET) is experimental in Kubo](https://github.com/ipfs/kubo/blob/master/docs/experimental-features.md#private-networks), but stable and as long users are okay with double-encryption and being limited to TCP-only, it could be supported. It...

Ok, there are things which are time-consuming to implement, and some which we can cheese a little by reusing existing abstractions, such as the fact everything in Kubo (swarm keys,...

The MVP hard limitation of 'only one swarm at a time' is what makes its implementation with preexisting Kubo feasible, but yes, in the future we could explore multi-swarm use...

@heEXDe thank you for filling this. Mind providing bit more context, so we can route this to the right repository? 1. is the memory usage coming mostly from `kubo` daemon...