IPFS+FUSE+Lagrange

I'm trying to see if I can view IPFS files in Lagrange. I'm trying to combine `ipfs daemon --mount` with the file:// URI scheme, but it isn't working. `cat /ipfs/QmPNcpFxMZuntK37LtUJkB7uEfHHWV4cH7j6bd4Fi9WsFU/declaration_independence_cyberspace.gmi` works fine, but when I try to open <file:///ipfs/QmPNcpFxMZuntK37LtUJkB7uEfHHWV4cH7j6bd4Fi9WsFU/declaration_independence_cyberspace.gmi> in Lagrange, it gives the error "Failed to Open File โ€“ The requested file does not exist or is inaccessible. Please check the file path."

When I `ln -s /ipfs/QmPNcpFxMZuntK37LtUJkB7uEfHHWV4cH7j6bd4Fi9WsFU/declaration_independence_cyberspace.gmi ~/`, I still get the same error at <file:///home/lersputa/declaration_independence_cyberspace.gmi>. If I instead `cp` the file to my home directory, then it does work, so it's not just an interaction between Lagrange and file:// โ€“ it's something involving IPFS and/or FUSE.

Likewise, when I `ln -s /ipfs ~/ipfs`, then <file:///home/lersputa/ipfs/Qm[...]WsFU/declaration_independence_cyberspace.gmi> still gives me the same error again.

In Firefox, <file:///ipfs/Qm[...]WsFU/declaration_independence_cyberspace.gmi> opens fine, and <file:///home/lersputa/declaration_independence_cyberspace.gmi> redirects to the file:///ipfs/[...] (and displays successfully). Firefox doesn't redirect <file:///home/lersputa/ipfs/Qm[...]WsFU/declaration_independence_cyberspace.gmi>, but shows the file anyway.

This suggests to me that it's not purely an IPFS/FUSE issue, but that there's something involving Gemini, Gemtext, and/or Lagrange as well.

Posted in: s/IPFS

๐Ÿฆ‹ lersputa

2023-08-22 ยท 3 years ago

3 Comments โ†“

๐ŸŒ† skyjake [...] ยท 2023-08-22 at 18:33:

Which build of Lagrange are you using? (e.g., manually built from source, AppImage, Flatpak)

๐Ÿฆ‹ lersputa [OP] ยท 2023-08-26 at 04:10:

Flatpak, 1.16.7.

๐ŸŒ† skyjake [...] ยท 2023-08-26 at 04:47:

Maybe give the AppImage a try? Flatpak apps are sandboxed and the Lagrange app has been configured to only allow access to your home directory. (A symlink is not enough to circumvent this.)