I was curious about the IPFS archiving and it appears that it just inlines everything. This is a bit of a shame because with IPFS's content-addressing and deduplication it would be really cool if the assets were out-of-line so that they could be duplicated between webpages.
That being said there are problems with inlining IPFS URLs currently. Because few people support ipfs: URLs you essentially need to pick a gateway and embed that into the archived document which is unfortunate. That being said most people who run their own gateway intercept ipfs.io automatically so it is a sort of defacto IPFS scheme.
You could probably post-process this yourself if you wanted to to "pop out" the inline blobs.
Example of my blog. You can see that the images, CSS and JS are inlined: https://ipfs.io/ipfs/QmcEKGbtFsYrUoDLFMLv45yrZ1hP7ZyyX79x9Ts...
That being said there are problems with inlining IPFS URLs currently. Because few people support ipfs: URLs you essentially need to pick a gateway and embed that into the archived document which is unfortunate. That being said most people who run their own gateway intercept ipfs.io automatically so it is a sort of defacto IPFS scheme.
You could probably post-process this yourself if you wanted to to "pop out" the inline blobs.