git ssb

1+

arj / ssb-browser-turtle



Issues getting it to work

%C6sDHFgBUUaHcd6yGglvmeZlylQdzPn5lgr0Mk35f34=.sha256
Closedcel opened this issue on 1/28/2020, 10:06:42 PM

Issues getting it to work

@arj

Moving discussion from %OBjNeQk... so that it is out of the way of casual Patchwork users. (Is this a good idea?)

Progress since %u0P/3fx....

Got an error alert Unable to download application message. Added a console.error(err) to inspect the error and found it was about a missing getThread RPC method. Found the ssb-get-thread module and installed it as an ssb-server plugin. Changed it to not allow anonymous and then made the browser key a master key in my ssb config so that it could call getThread, because I'm not sure I want to expose that method to peers. Should the app fall back to using sbot.backlinks or sbot.links if the call to getThread fails? Also I get an error in the log about missing tunnel.ping method but it doesn't seem to break anything. Now the app info loads. But pressing "Load App" triggers an error, navigator.serviceWorker.controller is null: 2020-01-28-165611_1920x1080_scrot.png
Earlier misc. errors: 2020-01-28-165646_1003x772_scrot.png

%5tGFhTil5GS365IDxpq6xB6+PcrW1z2Y+KfeAn8LXFA=.sha256 arj · 1/29/2020, 2:39:16 PM

@cel Try the latest version and run npm run build and serve from dist/ instead that should give you the service worker file.

%CSKLCaCPQWFo76WauRsbnLb2zEbBy/djMfp5BRkvKH4=.sha256 arj · 1/29/2020, 2:59:25 PM

As for the ssb-get-thread and ssb-tunnel requirements, I used get-thread because that is used in ssb-browser-demo but the tunnel one should probably be changed to something else.

%vabZ9ve3cb5/K5tl55COscley5S15HFmNUTpTxfCc6g=.sha256 cel closed this issue · 1/29/2020, 4:14:48 PM

@arj Cool, it works!

Built with git-ssb-web