feat: add `peersky://archive` to list all published P2P content (IPFS, Hyper, ENS) for discoverability

[akhileshthite]

Problem:

Currently, there is no way to access or discover previously published p2p data in PeerSky. This issue proposes adding an archive section to improve content discoverability.

TODOs:

• Add archive section in settings.html in pages/
  (Copy the settings sidebar UI to list everything, including IPFS, Hyper, and ENS cached data.)

• For Hyper:
  In each app, all data is stored in a Hyperdrive (e.g., 'drag-and-drop').

  • You can check each P2P app to find its Hyperdrive name in pages/p2p/.

For the chat app specifically, the Hyperdrive name is defined in protocols/hyper-handler.js.

• For IPFS:

  • Although data is stored in the local ipfs directory, there is no built-in index of stored CIDs.
  • Update each P2P app (pages/p2p/) so that whenever a file is uploaded to IPFS, the returned CID (or URL) is also appended to a central JSON file (e.g., ipfsCache.json).
  • This JSON file will act as an index, similar to how Hyperdrive names are tracked.

• For ENS:
  The names and hashes are stored in ensCache.json.

[Ayush-Vish]

@akhileshthite I am interested in this feature.

[akhileshthite]

@akhileshthite I am interested in this feature.

Cool!
Assigned.

[ADARSH-IIIT]

I am also interested, should I also try to add this feature?

[parth-1372]

Hi @akhileshthite , I’m interested in working on this issue and wanted to share my planned approach before starting.

I’ve outlined a high-level flow for how the Archive section would integrate with the existing renderer → IPC → main → storage pipeline, and how IPFS, ENS, and Hyper data would be surfaced in a single place for discoverability.

The diagram above reflects this approach and keeps changes scoped to existing patterns (settings UI, IPC handlers, and lightweight JSON indexing).

If this direction looks good, could you please assign this issue to me?
Happy to adjust the approach based on feedback.