Ethereum

Ever wondered how vitalik.eth.limo works?

- .limo is just a regular server, but it acts as an intermediary for IPFS pages

- Vitalik uploaded his blog to IPFS and set its content hash on his ENS name

- When you visit vitalik.eth.limo, the .limo server looks up the content hash on Ethereum using his ENS, fetches the blog from IPFS, and serves it back to your browser as a regular webpage

Did I get that right @greg?

Follow up -> Brave and Opera natively support IPFS and Ethereum node queries

No need for .limo - just type vitalik.eth in the address bar to load his blog directly from IPFS

How it works:
- The browser queries Ethereum to resolve vitalik.eth via ENS and get the IPFS content hash
- It fetches the blog directly from IPFS using the content hash
- The content loads into your browser with the address bar showing the IPFS content hash (http://ipfs.io/ipfs/bafy...)

Nice! 

BTW Phantom seems to be overreacting

/ethereum foundation | control the memes control the minds paragraph.xyz/@chaskin

Building @kiwi 
Writing @ https://kanfa.macbudkowski.com/

Probably not over-reacting. There is a severe amount of phishing content ran through public IPFS gateways. We've had to build a lot of internal tools to handle it at Pinata to ensure that phishing isn't happening through our public and dedicated gateways.

Everyone is from somewhere. Cofounder and CEO of Pinata. https://www.pinata.cloud/

Ipfs.io is the url that is being blocked, not IPFS. I would imagine my personal IPFS gateway https://kyletut.com/ipfs/bafybeifvusbh4iunpvwjlowu47sxnt4hjlebx46kxi4yz5zdsoecfpkkei/ is not blocked by Phantom

Understand the concern but then why "warning-gate" the whole IPFS? If Vitalik's own site can't be trusted than what can?