feat: upgrade protocol handlers to use new protocol.handle() API

[akhileshthite]

Our current protocol handlers use the deprecated protocol.registerStreamProtocol() API. We need to migrate to the modern protocol.handle() API which uses fetch-style request/response patterns.

### Current approach (deprecated):

protocol.registerStreamProtocol('ipfs', (request, callback) => {
  // Stream-based handler
  callback({ statusCode: 200, data: stream });
});

New approach (protocol.handle):

protocol.handle('ipfs', async (request) => {
  // Fetch-style handler - return Response object
  return new Response(body, {
    status: 200,
    headers: { 'content-type': 'text/html' }
  });
});

Main registration:

• src/main.js - Change protocol.registerStreamProtocol() to protocol.handle()
  Protocol handlers (all need fetch-style conversion):
• src/protocols/ipfs-handler.js
• src/protocols/hyper-handler.js
• src/protocols/web3-handler.js
• src/protocols/file-handler.js
• src/protocols/hs-handler.js
• src/protocols/bittorrent-handler.js
• src/protocols/peersky-protocol.js
• src/protocols/theme-handler.js

After migration, test all protocols:

Accessing (read operations):

• ipfs:// - Load CID content
• hyper:// - Load Hypercore data
• file:// - Directory listings and file access
• hs:// - peersky://p2p/p2pmd app
• bittorrent:// / bt:// - Torrent content
• web3:// - Web3 resources
• peersky:// - Internal browser pages

Publishing (write operations):

• IPFS upload via peersky://upload or other p2p apps.
• Hyper publishing same as above

Note: Visit these after this is addressed #15 #16

[Sameem-baba]

Hey there! Can I work on this?

[Omiii-215]

@akhileshthite

Hi! I’d like to take this up.

I’ve gone through the issue details and understand that we need to migrate all deprecated protocol.registerStreamProtocol() usages to the modern protocol.handle() fetch-style API across all custom protocols (ipfs, hyper, web3, hs, bittorrent, peersky, theme, file).

My plan is to:

• First refactor src/main.js to use protocol.handle() consistently.
• Then convert each protocol handler to return proper Response objects while preserving streaming behavior (especially for large IPFS/Hyper content).
• Carefully test both read (ipfs://, hyper://, file://, peersky://, etc.) and write flows (IPFS/Hyper publishing) to ensure no regressions.
• Keep an eye on related issues perf: HypercoreError: BAD_ARGUMENT when uploading large files exceeding block size limit #15 and perf: large video files only play audio when using HTML sniffing in file retrieval #16 to avoid introducing streaming or upload regressions.

If that sounds good, I’d be happy to work on this and open a structured PR with proper testing notes.

Please let me know if I can be assigned :)

[akhileshthite]

@Sameem-baba Assigned!

[HarshalAtre]

@akhileshthite , i want to work on it , please assign

[akhileshthite]

Assigned.