kubo v0.14.0 added support (opens new window) for the Reframe protocol (opens new window), which enables users to configure how their kubo node discovers content, peers, and handles IPNS records by just adding an HTTP endpoint to their config file. This means if you have a new content routing system you’d like to try out next to, or instead of, the IPFS Public DHT it’s now simple to do so. Similarly, Reframe starts enabling applications like public IPFS HTTP Gateways to decouple their DHT nodes from their content serving nodes so that they can be scaled and load-balanced independently.
This is a companion discussion topic for the original entry at https://blog.ipfs.tech/2022-09-02-introducing-reframe/