Once 1P API work (Issue 875989) has been in stable for a while and has been proven to work well, we should consider deprecating sending of resource loading hints and probably NoScript hints via component updater.

This would need to be done via Finch experiment to ensure there is no regression in any metrics (e.g., hints availability/coverage rate).

The benefit of deprecating the component updater path is that the Chrome would need to maintain only one copy of hints on the disk. Secondly, it might simplify both the server and client code.

Note that the privacy constraints for 1P API may dictate that 1P API can only be enabled for a subset of users (depending on the user opt-ins). In that case, deprecating resource loading hints via component updater may result in reduced coverage for users that are outside of the opt-in coverage.