It may make more sense for you to use the gateway.ipfs.io URL for IPFS-available content, because then people who are using a local ipfs node and a browser-url-rewriting-extension to auto-rewrite gateway.ipfs.io to appropriate localhost HTTP requests (to actually use the p2p net to fetch instead of HTTP) will be fetching the content natively.
Either that, or get ipfs.busy.org listed in the popular IPFS url-rewriter extensions, so that it rewrites those URLs too.
Right! Good catch, we will take a look about that.
Your a Smart MOFO. Has anyone ever told you that? Just watched the d.tube videos you @pkattera and @ned. Sounds like you guys have a fun job. Sort of wish I had something to bring to the table aside from conceptually. Totally regret not learning coding. Totally sucks having ideas without the means to put them into tangible/utilizable ideas.