Opened 5 years ago
Closed 4 years ago
#15992 closed enhancement (fixed)
ipfs links to Haiku releases
Reported by: | kallisti5 | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Website/www.haiku-os.org | Version: | R1/Development |
Keywords: | ipfs | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
Haiku R1Beta1 has been uploaded to ipfs.
/ # ipfs add -w /export/haiku-r1beta1-x86_64-anyboot.zip added QmWAHucGiatLTWY6LNxexpjSzVeosLZaT8G396RLYzp74r haiku-r1beta1-x86_64-anyboot.zip added QmRYyJA1S3EiCS5NG5FGRCXwGLzu8VCADREAJmZbL5j4qs / # ipfs add -w /export/haiku-r1beta1-x86_gcc2_hybrid-anyboot.zip added Qmejz9ahT1agELvqBn4oM35ACaDaWFksjo4nf4AEcoUZdy haiku-r1beta1-x86_gcc2_hybrid-anyboot.zip added QmUyJJhfhevw5M93AvLYysh7kQRkrHGcmUVCN9L11RDYSs
These can be linked to directly via:
- Haiku R1Beta1 x86_64
- ipfs://QmRYyJA1S3EiCS5NG5FGRCXwGLzu8VCADREAJmZbL5j4qs
- Haiku R1/Beta1 x86_gcc2_hybrid:
- ipfs://QmUyJJhfhevw5M93AvLYysh7kQRkrHGcmUVCN9L11RDYSs
They can also be linked to via public gateways (https://ipfs.github.io/public-gateway-checker/) such as:
- Haiku R1Beta1 x86_64
- Haiku R1/Beta1 x86_gcc2_hybrid:
Change History (7)
comment:1 by , 5 years ago
Component: | - General → Website/www.haiku-os.org |
---|---|
Description: | modified (diff) |
Owner: | changed from | to
comment:2 by , 5 years ago
Description: | modified (diff) |
---|---|
Keywords: | ipfs added |
comment:3 by , 5 years ago
Ok, so IPFS suffers the same issue as bittorrent without seeders. Linking to public gateways would direct everyone to my nas.
so, linking to ipfs:// ... would be better because it would encourage people to run the IPFS client, and cache a copy locally to "seed"
comment:4 by , 5 years ago
I'm not sure I understand why this would be simpler than bittorrent. Can't hurt us to share the links, I guess. May create problems for your NAS if no one else is seeding, however.
comment:5 by , 5 years ago
True. I mention easier than bittorrent because it comes with a bunch of options for running local ipfs nodes which would seed haiku once downloaded.
- Browser Extensions:
- https://addons.mozilla.org/en-US/firefox/addon/ipfs-companion
- https://chrome.google.com/webstore/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch
- brave://settings/extensions in Brave
There's also ipns which means we could link to artifacts via TXT dns records: https://docs.ipfs.io/guides/concepts/ipns/
There's also a huge API behind it where people deploy websites like wikipedia and can navigate it p2p.
https://cloudflare-ipfs.com/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/
I'm still trying to figure out if it's "the most innovative thing ever" or "way over complicated" :-)
comment:6 by , 4 years ago
I should mention here that I setup https://ipfs.haiku-os.org which is a direct link to Haiku R1B2 hosted on IPFS going through the free cloudflare ipfs gateway.
I pinned the relevant hashes at pinata.cloud so there is some CDN backing to them. Seems to be working fine, so closing this one.
I have the Haikuports repos mirrored on IPFS as well, but not willing to pin 65GiB at pinata.cloud given the cost and some limitations I ran into.
Closing this one with the above info.
We *might* be able to host haiku-os.org on IPFS and get away from netlify (it's just a static site)... but waddlesplash hates that idea so leaving it alone for now :-)
comment:7 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This is less of a "todo" and more of a discuss. These ipfs links are p2p, and slightly easier to use than things like bittorrent.
I'm running an ipfs server on my NAS I uploaded these from... really hope all the bandwidth doesn't come from only my NAS though :-| Needs more investigation.