node-fetch VS ipfs

2023/07/18 12:39:52 [error] 5224#5224: *2630494 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.19.0.1, server: www.mywebsite.com, request: "GET /index.php?route=tool%2Finfo HTTP/1.1", upstream: "http://10.11.63.81:9000/index.php?route=tool%2Finfo", host: "www.mywebsite.com" 172.18.0.1 - - [18/Jul/2023:12:39:52 +0000] "GET /index.php?route=tool%2Finfo HTTP/1.1" 502 150 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" 257 0.057 [website-namespace-website-svc-80] [] 10.11.63.81:9000 : 10.11.63.81:9000 0 : 0 0.057 : 0.000 200 : 502 1c7796af3b6c7b43f709f4c708ecb026 svc website-svc ClusterIP 10.11.63.81 80/TCP,9000/TCP,443/TCP ingress configmap server-snippet: location @location { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_pass http://website-svc.website-namespace.svc.cluster.local:9000; proxy_set_header X-Forwarded-Port 9000; } the ingress resource annotations: nginx.ingress.kubernetes.io/backend-protocol: "FCGI" nginx.ingress.kubernetes.io/fastcgi-index: "gateway.php" nginx.ingress.kubernetes.io/from-to-www-redirect: "true" spec: tls: XXX rules: - host: "www.mywebsite.com" http: paths: - path: / pathType: Prefix backend: service: name: website-svc port: number: 80 ingress website-api-ingress nginx www.mywebsite.com localhost 80, 443 41d

node-fetch - window.fetch for Node.js.

User-Agent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch)

I don't mind pinning, but back in the day I was having issues using IPFS to transfer small files between devices. I admit I haven't investigated to see if the problems were ever resolved.

I've been watching https://github.com/ipfs/helia which is going to replace https://github.com/ipfs/js-ipfs and hoping they can get an IPFS node working in the browser.

I haven't tried https://js.ipfs.tech/ (js-ipfs) in a while, what is the state of it?

On the topic of IPFS, but also slightly tangential -- how has nobody written an Activity Pub client/server in Javascript and distributed it as a Browser Addon?

If IPFS can be literally hosted via a Firefox Extension[1], how has nobody done the same for an arguably easier protocol like Activity Pub?

1: https://github.com/ipfs/js-ipfs

If you can load them up in js-ipfs that might be better?

Store the content in ipfs and just put the hash in the URL? I haven't used https://github.com/ipfs/js-ipfs in this capacity but I'm under the impression that that's what it's supposed to do.

js.ipfs.tech

You need an import statement instead of require since Node has upgraded to the new module system. Use import * as IPFS from 'ipfs-core'. Read more here: https://github.com/ipfs/js-ipfs

Please take a look at https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md for more understanding

You could include js-ipfs[0] and fetch all your resources from IPFS without going through a gateway. However, this approach would make the site fully dependent on JavaScript.

A PWA with a Service Worker could perhaps implement its own client-side "gateway", translating public gateway URLs into direct IPFS access. Without the Service Worker (or without JS) it would fall back to using the gateway.

[0] https://js.ipfs.io/

Of course,You can try it out. You can create some Hash to IPFS from this link Adding data to IPFS https://js.ipfs.io/ and then browse the hash in https://ipfs-gateway.cloud/ It is directly connected to IPFS Node.