stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.5.1 and js-ipfs 0.43.1 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of Conduct: https://git.io/vVBS0
lawr3nce has quit [Remote host closed the connection]
main has quit [Quit: im out]
main has joined #ipfs
endvra has joined #ipfs
<odisseus[m]>
What is the format of the request body expected by the endpoint `/api/v0/object/put`?
Ecran has quit [Quit: Going offline, see ya! (www.adiirc.com)]
luis[m] is now known as lqdev
}ls{ has joined #ipfs
lqdev has quit [Quit: authenticating]
lqdev has joined #ipfs
endvra has joined #ipfs
endvra has quit [Ping timeout: 265 seconds]
apiarian has joined #ipfs
<alecbcs[m]>
Hi all, I'm using the go-ipfs CoreAPI and so far I've been able to set up a node and pin files locally. However, it doesn't seem that those pins are then being shared back with the IPFS network for when I stop the IPFS daemon on my laptop with only the go code I've written running the files no longer are accessable from any end point. Even ones I'm directly boot strapping on to. Any help would be hugely appreciated.
Pie-jacker875 has quit [Remote host closed the connection]
Pie-jacker875 has joined #ipfs
<odisseus[m]>
Are your files accessible from other nodes (e. g. public HTTP gateways) while your node is running?
<alecbcs[m]>
When the daemon is running on my laptop yes but after I turn that off and try a file that should be pinned to the running go instance that isn't cached on the public gateways then I don't believe so as it hangs searching for the file.
<alecbcs[m]>
Here's a link to the code that is setting up the IPFS node. Am I missing something?
FennecCode has quit [Ping timeout: 260 seconds]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
Belkaar has quit [Changing host]
FennecCode has joined #ipfs
andi- has quit [Ping timeout: 260 seconds]
}ls{ has quit [Ping timeout: 260 seconds]
<odisseus[m]>
From what i understand, you're trying to launch and manage an IPFS node, and that your managed node cannot connect to the outside world where a standard IPFS daemon can
<odisseus[m]>
* From what i understand, you're trying to launch and manage an IPFS node, and your managed node cannot connect to the outside world where a standard IPFS daemon can
<odisseus[m]>
* From what I understand, you're trying to launch and manage an IPFS node, and your managed node cannot connect to the outside world where a standard IPFS daemon can
<alecbcs[m]>
Not exactly, as it currently stands the node can reach out and pin blocks. However, those pins are later not accessable to other ipfs nodes. In short it can call out and grab data from the network but the network cannot seemingly reach in and ask for data back from the node.
<odisseus[m]>
Make sure your mamaged node and the daemon are configured to use different network ports
}ls{ has joined #ipfs
<odisseus[m]>
* Make sure your managed node and the daemon are configured to use different network ports
<alecbcs[m]>
How do you configure which port the node should use through the go API?
MDude has quit [Quit: Going offline, see ya! (www.adiirc.com)]
jrt has quit [Killed (orwell.freenode.net (Nickname regained by services))]
jrt has joined #ipfs
reit has joined #ipfs
reit has quit [Max SendQ exceeded]
chachasmooth has quit [Ping timeout: 246 seconds]
chachasmooth has joined #ipfs
}ls{ has quit [Quit: real life interrupt]
ipfs-stackbot has quit [Remote host closed the connection]
ipfs-stackbot has joined #ipfs
jadedctrl has quit [Ping timeout: 265 seconds]
stripedpajamas has joined #ipfs
Newami has joined #ipfs
Newami has quit [Quit: Leaving]
IGNBoniekDiscord has joined #ipfs
ldlework has joined #ipfs
<ldlework>
Hello. I'm looking for some kind of private-social media tooling for a smaller community to curate and share data such as public-domain books, datasets and archived web-content such as articles. Does anyone have any recommendations I can start looking into?
Wikipedia[m] has joined #ipfs
lolinternets[m] has joined #ipfs
<JCaesar>
Hm, wasn't there some nextcloud alternative that can use ipfs?
<JCaesar>
ldlework: anyway, if you're looking for an ipfs solution... ipfs-cluster, plus some conventions on a folder structure wouldn't do the trick?
<ldlework>
JCaesar: I do not want to replicate all available resources on all participating nodes.
<ldlework>
I want nodes to be able to search the network for data of interest to them, download it from peers in the network, and seed any data they've gotten back to the network.
kaotisk-irc has joined #ipfs
<ldlework>
JCaesar: know what I mean?
cacca has joined #ipfs
xxx has joined #ipfs
kaotisk-irc has quit [Quit: Leaving]
cacca has left #ipfs [#ipfs]
xxx has quit [Remote host closed the connection]
Adbray has quit [Remote host closed the connection]
Adbray has joined #ipfs
Adbray has quit [Excess Flood]
Adbray_ has joined #ipfs
hsn has joined #ipfs
Sajesajama has quit [Quit: Leaving]
<JCaesar>
sounds like.. ipfs?
<JCaesar>
But yeah, I guess you lack the nice tools to organize the metadata...
stripedpajamas has quit [Quit: sleeping...]
<ldlework>
Yeah that answer wasn't very helpful :)
frhs has quit [Ping timeout: 258 seconds]
redfish has quit [Ping timeout: 246 seconds]
drathir_tor has quit [Ping timeout: 240 seconds]
redfish has joined #ipfs
joocain2_ has joined #ipfs
krueg has quit [Ping timeout: 246 seconds]
joocain2 has quit [Ping timeout: 240 seconds]
endvra has joined #ipfs
noresult has quit [Ping timeout: 240 seconds]
<odisseus[m]>
Check out https://diasporafoundation.org, it might be what you need for the social interaction. You might also want to set up an IPFS private cluster for common storage.
}ls{ has joined #ipfs
<odisseus[m]>
* Check out https://diasporafoundation.org, it might be what you need for the social interaction. You might also want to set up an IPFS private network for common storage.
noresult has joined #ipfs
ylp has joined #ipfs
<JCaesar>
Does diaspora interact with ipfs in any way?
Trieste has quit [Ping timeout: 265 seconds]
Trieste has joined #ipfs
<ldlework>
odisseus[m]: also does a cluster force each node to carry the whole data library?
bengates has joined #ipfs
cxl000 has quit [Ping timeout: 256 seconds]
cxl000 has joined #ipfs
fazo96 has joined #ipfs
cxl000__ has joined #ipfs
patagonicus has joined #ipfs
cxl000 has quit [Ping timeout: 256 seconds]
<JCaesar>
I think there's a replication factor to control that.
<odisseus[m]>
<ldlework "odisseus: also does a cluster fo"> What I actually had in mind is a private _network_, not a cluster.
<odisseus[m]>
I have never used Diaspora and I know very little about it, but it seems to fit the requirement of a "private-social media tooling for a smaller community'.
<odisseus[m]>
* I have never used Diaspora and I know very little about it, but it seems to fit the requirement of a "private-social media tooling for a smaller community".
<swedneck1>
honestly i don't think the IPNS publish times are too bad, just think of it like building your hugo site :P
<swedneck1>
i'd probably recommend friendica over diaspora
fling has joined #ipfs
dethos has quit [Ping timeout: 264 seconds]
<ShokuninDiscord7>
What's the difference between them?
<ShokuninDiscord7>
I assumed they'd both be activitypub by now
Nact has joined #ipfs
choward6 has joined #ipfs
choward has quit [Ping timeout: 240 seconds]
choward6 is now known as choward
fabianhjr has joined #ipfs
<swedneck1>
pretty sure diaspora still uses its own thing
<aschmahmann[m]>
kravietz: IPNS publish/resolve times using the DHT are unfortunately still slower than they could/should be since there's a bunch of the network still running pre 0.5 nodes that are behind NATs and are advertising themselves to the rest of the network. As more people upgrade to go-ipfs >=0.5 network performance should increase, however there's also interest in figuring out a good way to upgrade the network for new nodes
<aschmahmann[m]>
without waiting for users to upgrade their nodes.
<aschmahmann[m]>
Note: If you use IPNS over PubSub and the publishers and subscribers are running go-ipfs >=0.5 then an IPNS resolve should be about as fast as an IPFS resolve.
<kravietz[m]>
aschmahmann: Thanks, that's very detailed answer! Just to clarify, I'm using absolutely dumb setup where by website (krvtz.net) is hosted on IPFS but then exposed to the traditional web - simply `HTTP -> Nginx -> go-ipfs(gateway)`.
<kravietz[m]>
Now the key decision was what to put in Nginx config...
Pie-jacker875 has quit [Remote host closed the connection]
<kravietz[m]>
When I added direct `/ipfs/` link it all worked very fast but obviously each new version of website required change of the CID in Nginx config which is overkill.
<kravietz[m]>
Adding `/ipns/` had an unpleasant effect of the name being resolved for quite a long time, which triggered Nginx timeout and 500 internal server error response to clients.
Pie-jacker875 has joined #ipfs
<kravietz[m]>
Now, I'm not sure how this exactly works but if the IPFS node pulled the IPNS and IPFS CIDs once, shouldn't they reside there like forever? Because the slow IPNS resolution seemed to happen periodically even for the same content...
<kravietz[m]>
Disclaimer: at some point I had `--enable-gc --routing=dhtclient` in the `ipfs.service` in systemd (now removed)
Portugueses has quit [Ping timeout: 256 seconds]
Pie-jacker875 has quit [Read error: Connection reset by peer]
<aschmahmann[m]>
>shouldn't they reside there like forever
<aschmahmann[m]>
What node were you publishing the IPNS records from, was it generally online? Also, as I mentioned you may want to try using IPNS over PubSub (i.e. passing the `--enable-namesys-pubsub` flag to both daemons) to see how it goes.
<aschmahmann[m]>
great question. That's the great thing about immutable data, as with IPFS. However, IPNS is mutable so even though you've requested the data once before it might have changed in the meanwhile. While you can tweak cache durations, it ends up being the same problem as the traditional web you need to do a refresh.
maxzor has quit [Remote host closed the connection]
Pie-jacker875 has joined #ipfs
<kravietz[m]>
Nope, I publish from my laptop but then the server where Nginx and IPFS node resides is 24x7 so my idea was like "push once, stay there forever". I figured out you can do `ipfs pin` which is I guess precisely what I need but it seems like you can't pin a IPNS - I mean, you can but it will effectively only pin the CID behind it.
<kravietz[m]>
Ok I've just enabled the PubSub on the node, let's see how it goes...
dethos has joined #ipfs
Pie-jacker875 has quit [Read error: Connection reset by peer]
Pie-jacker875 has joined #ipfs
Hong has joined #ipfs
mischat has quit [Remote host closed the connection]
Pie-jacker875 has quit [Remote host closed the connection]