-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status #35
Comments
I would like something like this. I updated IPFS to the latest master (0.4.0-Dev) and now I cannot load any images using my local server (Via IPFS redirect plug-in). Even though I am connected to over 25 peers. I am assuming there is some compatibility issue between the version ipfs.pics nodes run and the latest? |
We are running 3.8 right now (connected to 122 peers). We are planning to update when 4.0 is not a dev version anymore. And yes there is a compatibility issue between 4.0 nodes and 3.x nodes unfortunately, I recommend running the latest stable version. Just out of curiosity, are you running an ipfs.pics instance or are you using raw ipfs? |
I use the ipfs.pics main site then have the redirect plug-in the causes all urls matching */ipfs/ to be redirected to 127.0.0.1:8080/ipfs/. I do this to help cache the images for the network. I do not host an instance of the site myself. Just use my local ipfs daemon to load the images instead of your gateway. I assume that is what you mean lol. |
The version of ipfs we use in production is now displayed on the homepage, until we have a proper stats page. |
ipfs.pics should have a status page at https://ipfs.pics/status which contains:
The text was updated successfully, but these errors were encountered: