This brings us back to my original point. Even with trusted IPNS namespaces, IPFS needs to protect its users. If nothing else IPFS should have some kind of content policy engine that warns or blocks the user from unintentionally leaving safe namespaces and/or retrieving random hashes.
P.S. 555.555.555.555 isn't really a great example IP :)
Moving towards IPNS namespaces would probably be a great start.
Example content sites like the below one (found in another comment) are a disaster just waiting to happen:
https://ipfs.io/ipfs/QmU5XsVwvJfTcCwqkK1SmTqDmXWSQWaTa7ZcVLY...
This brings us back to my original point. Even with trusted IPNS namespaces, IPFS needs to protect its users. If nothing else IPFS should have some kind of content policy engine that warns or blocks the user from unintentionally leaving safe namespaces and/or retrieving random hashes.
P.S. 555.555.555.555 isn't really a great example IP :)