<patientplatypus>
but wait hold on - so this is opening a websocket on localhost BUT
<patientplatypus>
BUT
<AphelionZ>
mm?
<patientplatypus>
what if i am distributing this frontend application to many clients
<patientplatypus>
?
<patientplatypus>
then localhost will no longer work - you see?
<patientplatypus>
this is a problemo
<AphelionZ>
well yeah you'll need it on a server eventually
<patientplatypus>
or am i totally wrong on this?
<patientplatypus>
so how would i change this if i put it on a server - would i ipfs init on the server and then change /ip4/0.0.0.0/tcp/4001/ws to /ip4/<SERVERADDRESS>/tcp/4001/ws ?
<patientplatypus>
does that sound right? im just guessing honestly?
<AphelionZ>
no, 0.0.0.0 is fine
<AphelionZ>
that publicly exposes that port
<AphelionZ>
as opposed to 127.0.0.1 which will be localhost-only
<AphelionZ>
keep 0.0.0.0, and add the line I said
<patientplatypus>
hmmm ok
<AphelionZ>
don't overthink this, yet
<AphelionZ>
let's just get it working first and then you can break it
<patientplatypus>
ok doke lines added
<patientplatypus>
thanks for your patience ive been going crazy trying to get this to work
<AphelionZ>
ok so restart the daemon and check the logs and make sure it swarms on /ws
stoopkid has quit [Quit: Connection closed for inactivity]
<patientplatypus>
is that in the swarm specification?
<AphelionZ>
bootstrap
<AphelionZ>
yours wouldnt be wss though, it would be ws
<AphelionZ>
and it would be an ipv4 multihash, not a dns4
<patientplatypus>
ok sorry now im totally lost
<AphelionZ>
here I'll PM it hang on
<patientplatypus>
thank you very much (i wont steal ur thingz i just want to noze)
<patientplatypus>
hehe
<patientplatypus>
hi
<AphelionZ>
so bootstrap are (as i see them) foundational peers that you connect to first and always to set up your initial peering, I sww swarm peers as more like "user" nodes
<AphelionZ>
does the latter encapsulate the former or are they fundamentally different
<lidel>
patientplatypus, ipfs id
<patientplatypus>
@lidel go-ipfs... i dont think i have js-ipfs installed. however i thought that was just what it was compiled in and it didnt matter what version you had.
<AphelionZ>
patientplatypus: if you are using IPFS in the browser it's js-ipfs
tribrid has joined #ipfs
<patientplatypus>
so do i need to delete and reinstall ipfs but use js-ipfs this time?
<lidel>
patientplatypus, honestly I have trouble to understand twhat is your goal
<patientplatypus>
chat application using pubsub in the frontend
<patientplatypus>
pretty straightforward
malaclyps has quit [Ping timeout: 246 seconds]
<lidel>
patientplatypus, you dont need go-ipfs for that, you need to enable pubsub in js-ipfs's constructor and then maybe websocket signaling via websocket-star
<lidel>
should be enough to start coding
<patientplatypus>
@lidel so, the command line daemon is written in go, but im installing the js-ipfs through npm in my frontside application. See here: https://github.com/ipfs/js-ipfs and here: https://dist.ipfs.io/#go-ipfs (notice there is no js-ipfs daemon tool).
<lidel>
patientplatypus, how are you running it? bundling via webpack?
<lidel>
or running in node?
<patientplatypus>
in vue.js with webpack but i dont think that should matter
malaclyps has joined #ipfs
<lidel>
patientplatypus, i know there were issues with default minifier in webpack and js-ipfs, but before we go that road, what actually does not work?
<lidel>
if we removed the need for go-ipfs, whats left to fix? :)
<patientplatypus>
im not sure i follow - i have to have go-ipfs as its the daemon
<patientplatypus>
confused
<lidel>
why?
<lidel>
js-ipfs is a regular node
<lidel>
for chat its all you need
<lidel>
:)
<lidel>
in production you may want to run own signaling server and/or relay, but for now i would not think about that and focus on the app itself
Guest43893 has joined #ipfs
<lidel>
patientplatypus, question: how did you check if connection to your local go-ipfs node failed? was there an error or was it just not present in output of js call ipfs.swarm.peers(..)?
teej has joined #ipfs
Fuseteam has quit [Read error: Connection reset by peer]
simbergm has quit [Remote host closed the connection]
mkg20001 has quit [Read error: Connection reset by peer]
betz[m] has quit [Remote host closed the connection]
swedneck[m] has quit [Read error: Connection reset by peer]
lordpipe has quit [Remote host closed the connection]
mitfree[m] has quit [Remote host closed the connection]
turt2live has quit [Read error: Connection reset by peer]
mindhog[m] has quit [Read error: Connection reset by peer]
stebalien has quit [Read error: Connection reset by peer]
peddie1 has quit [Read error: Connection reset by peer]
dcallagh has quit [Read error: Connection reset by peer]
jcgruenhage has quit [Read error: Connection reset by peer]
k0mpjut0r has quit [Write error: Connection reset by peer]
<lidel>
cool :) patientplatypus:by default there are 8 bootstrap servers, error you see means one of them is probably down, its ok to ignore it as long other ones work
<patientplatypus>
ahhhhh i see
<patientplatypus>
wellll.....my other problems still stand can't get it to work yet unfortunately
<patientplatypus>
boooo
<lidel>
patientplatypus, i wonder why two tabs can't see each other, maybe because you use the same repo (and peerid?) in both of them?
<lidel>
try testing using two different browsers (eg. firefox and chrome)