stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.18 and js-ipfs 0.33 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of Con
<postables[m]>
fiatjaf: why? That would be such a waste of developer time the IPFS team is doing a great job
<postables[m]>
If one really wanted to, the specifications and building blocks are already out there so realistically it probably wouldn't be a crazy amount of work, but it would still be a huge endeavor. One that would be better spent contributing to the already existing IPFS ecosystem and improving it
<aschmahmann[m]>
fiatjaf: If you're interested and feel strongly enough about it I'd look into creating a rust-ipfs. There are some people at https://github.com/ipfs/ipfs/issues/5 who have expressed interest
<voker57>
there's already rust-ipfs in some stage of development
<aschmahmann[m]>
voker57: didn't realize it was already underway, thanks for the link
mauz555 has joined #ipfs
<voker57>
ipfs team might be doing a great job... but generall not on things ipfs users want
arthuredelstein has quit [Ping timeout: 245 seconds]
cwahlers_ has joined #ipfs
cwahlers has quit [Ping timeout: 244 seconds]
valor0101001 has quit [Ping timeout: 246 seconds]
arthuredelstein has joined #ipfs
arthuredelstein has quit [Ping timeout: 250 seconds]
arthuredelstein has joined #ipfs
reit has quit [Ping timeout: 268 seconds]
sammacbeth has quit [Ping timeout: 246 seconds]
sammacbeth has joined #ipfs
arthuredelstein has quit [Ping timeout: 246 seconds]
dimitarvp has quit [Quit: Bye]
valor0101001 has joined #ipfs
<postables[m]>
voker57: sure, but a stable and we'll built protocol is a good thing. IMO it's much better to work with the IPFS developers helping everyone to reach a stable v1.0.0 faster, then heading off and building out your own clients, with additional functionality.
<postables[m]>
The last thing the IPFS ecosystem needs is a bunch of people working on diverging clients, creating a fractured and non-interoperable community (for example, js-ipfs is an example of an IPFS client which has interoperability issues with the bulk of the nodes providing a solid IPFS ecosystem running go-ipfs).
<postables[m]>
Also the specs could change completely before a v1.0.0 is reached, which could invalidate a lot of work people would do by creating their own clients from scratch
<refpga>
Fns[m]: okay, so would that move the entire ~/.ipfs folder to IPFS_PATH?
<Fns[m]>
refpga: No, it will only look for it in location defined by this variable. If it does not exist, it will initialize it from scratch.
<Fns[m]>
If you wish to move it, you'll need to manually move it to desired location.
<refpga>
Fns[m]: Thanks.
vyzo has quit [Quit: Leaving.]
vyzo has joined #ipfs
_whitelogger has joined #ipfs
fleeky has quit [Ping timeout: 246 seconds]
fleeky has joined #ipfs
<refpga>
Hi, what is the Qm... ID I am asked to cat to in the first step after init (Where all the help files reside)? something like `ipfs cat /ipfs/Qm.../readme`
<refpga>
That ID is different than the one in the output of ipfs id -f="<id>"
<Fns[m]>
refpga: It marks the hashing algorithm used, if I'm not mistaken. Hold on…
groxx has quit [Quit: Connection closed for inactivity]
<refpga>
Thanks. I am presented with the hash of directory with help files in the beginning. How can I access that hash again?
jamesaxl is now known as Eiquoh
<refpga>
Just after init, it says `ipfs cat /ipfs/Qmthehash/quick-start
<refpga>
Fns[m]: ^^
<refpga>
How does one manage all these hashes?
}ls{ has joined #ipfs
<Fns[m]>
I have a number of pinned things, gimme a moment
<Fns[m]>
QmS4ustL54uo8FzR9455qaxZwuMiUhyvMcX9Ba8nUH4uVv I think
<refpga>
Yeah
<refpga>
How does one manage these hashes?
rendar has joined #ipfs
<Fns[m]>
Depends on what you mean by 'manage'. I'm afraid I wount be able to explain things in detail, though.
<Fns[m]>
In short, all files and folders you add are stored by their hashes. If you add a folder with files, it will give you hash of the folder pointing to hashes of files inside, those files can be seen by their name inside the folder
refpga has quit [Ping timeout: 246 seconds]
refpga has joined #ipfs
<refpga>
Fns[m]: I want to keep these hashes for easy retrieval to cat these files. Is there any 'library of bookmarks' kind of thing to retrieve these hashes in order to access those files again?
<refpga>
I think the webUI can be used to use a browser's bookmark functionality to save them. But on the commandline, we need to enter hashes each time we want to access a file.
hurikhan77 has quit [Ping timeout: 252 seconds]
<Fns[m]>
refpga: Not sure, but there is pinning of hashes.
<Fns[m]>
IPFS will retrieve and store locally all files you request (by hashes), and will share those files with others who request them. It is supposed to delete them from your local store after a while if you don't use them any more (if garbage collection is enabled with --enable-gc flag), in order to avoid that and store files permanently, you can pin them with ipfs pin add <hash>. Pinned files are not removed. Can be unpinned with
<Fns[m]>
ipfs pin rm <hash>.
<Fns[m]>
As for bookarking, I'm not sure there is a convinient way. There was a search engine for ipfs somewhere
<refpga>
okay, thanks.
refpga has quit [Quit: WeeChat 1.6]
cwahlers_ has joined #ipfs
cwahlers has quit [Ping timeout: 246 seconds]
spinza has quit [Quit: Coyote finally caught up with me...]
plexigras has joined #ipfs
reit has quit [Quit: Leaving]
spinza has joined #ipfs
refpga has joined #ipfs
kapil____ has quit [Quit: Connection closed for inactivity]
q6AA4FD has quit [Ping timeout: 246 seconds]
aarshkshah1992 has joined #ipfs
jpf137 has joined #ipfs
jpf137 has left #ipfs [#ipfs]
jpf137 has joined #ipfs
kapil____ has joined #ipfs
dolphy has quit [Read error: Connection reset by peer]
clemo has joined #ipfs
clemo has quit [Client Quit]
dolphy has joined #ipfs
mischat has joined #ipfs
mischat has quit [Read error: No route to host]
aarshkshah1992 has quit [Remote host closed the connection]
aarshkshah1992 has joined #ipfs
thomasanderson has joined #ipfs
cwahlers has joined #ipfs
thomasanderson has quit [Ping timeout: 245 seconds]
cwahlers_ has quit [Ping timeout: 250 seconds]
aarshkshah1992 has quit [Remote host closed the connection]
hurikhan77 has joined #ipfs
clemo has joined #ipfs
aarshkshah1992 has joined #ipfs
hurikhan77 has quit [Ping timeout: 252 seconds]
malaclyps has quit [Read error: Connection reset by peer]
malaclyps has joined #ipfs
Steverman has joined #ipfs
hurikhan77 has joined #ipfs
chiui has joined #ipfs
dimitarvp has joined #ipfs
dolphy has quit [Read error: Connection reset by peer]
movaex_ has joined #ipfs
chiui has quit [Ping timeout: 250 seconds]
test has joined #ipfs
test has left #ipfs [#ipfs]
refpga has quit [Ping timeout: 268 seconds]
aarshkshah1992 has quit [Remote host closed the connection]
cwahlers has quit [Read error: Connection reset by peer]
cwahlers has joined #ipfs
xcm has quit [Read error: Connection reset by peer]
xcm has joined #ipfs
xcm has quit [Read error: Connection reset by peer]
aarshkshah1992 has joined #ipfs
Steverman has quit [Ping timeout: 250 seconds]
xcm has joined #ipfs
lidel` has joined #ipfs
lidel has quit [Ping timeout: 250 seconds]
lidel` is now known as lidel
aarshkshah1992 has quit [Quit: Leaving...]
jesse22 has quit [Ping timeout: 240 seconds]
pmatteo1998 has joined #ipfs
nonono has quit [Ping timeout: 246 seconds]
<jamiew>
Fns[m]: refpga: search engine is http://ipfs-search.com (and #ipfssearch on IRC)
mischat has quit [Remote host closed the connection]
brianhoffman has joined #ipfs
erratic has joined #ipfs
rendar has quit []
spinza has quit [Quit: Coyote finally caught up with me...]
thomasanderson has joined #ipfs
spinza has joined #ipfs
NukeManDan[m] has joined #ipfs
cwahlers has quit [Ping timeout: 246 seconds]
cwahlers_ has joined #ipfs
Steverman has quit [Ping timeout: 240 seconds]
discopatrick has joined #ipfs
user_51 has quit [Ping timeout: 244 seconds]
user_51 has joined #ipfs
vivus has joined #ipfs
redxzilg[m] has joined #ipfs
jesse22 has joined #ipfs
fredthomsen has joined #ipfs
alex[m]9 has joined #ipfs
Steverman has joined #ipfs
jesse22 has quit [Ping timeout: 268 seconds]
mischat has joined #ipfs
GonZo2K[m] has joined #ipfs
mischat_ has joined #ipfs
mischat has quit [Ping timeout: 252 seconds]
fredthomsen has quit [Quit: Leaving.]
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
VitalyLipatov[m] has joined #ipfs
<postables[m]>
refpga: for managing hashes you'll want to keep a "cache" in a database
<postables[m]>
if your hash list grows large, it will take VERY long to list all your hashes
<postables[m]>
*edit:* ~~if your hash list grows large, it will take VERY long to list all your hashes~~ -> if your hash list grows large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs list ls`
<postables[m]>
*edit:* ~~if your hash list grows large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs list ls`~~ -> if your hash list grows large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs list ls`, even on
<postables[m]>
an SSD it's not even that much faster, maybe 2-3s at most.
<postables[m]>
*edit:* ~~if your hash list grows large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs list ls`, even on an SSD it's not even that much faster, maybe 2-3s at most.~~ -> if your hash list grows large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes
<postables[m]>
and it takes 2 minutes to list them through `ipfs list ls`, even on an SSD it's not even that much faster, maybe 2-3s at most. In turn I keep the parent hash (ie, for all recursive pins, simply list the top-most hash)
<postables[m]>
*edit:* ~~if your hash list grows large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs list ls`, even on an SSD it's not even that much faster, maybe 2-3s at most. In turn I keep the parent hash (ie, for all recursive pins, simply list the top-most hash)~~ -> if your hash list grows large, it will take VERY
<postables[m]>
long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs list ls`, even on an SSD it's not even that much faster, maybe 2-3s at most. In turn I keep the parent hash (ie, for all recursive pins, simply list the top-most hash) in a postgresql database
<postables[m]>
*edit:* ~~refpga: for managing hashes you'll want to keep a "cache" in a database~~ -> @refpga: for managing hashes you'll want to keep a "cache" in a database
<postables[m]>
*edit:* ~~if your hash list grows large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs list ls`, even on an SSD it's not even that much faster, maybe 2-3s at most. In turn I keep the parent hash (ie, for all recursive pins, simply list the top-most hash) in a postgresql database~~ -> if your hash list grows
<postables[m]>
large, it will take VERY long to list all your hashes, for example I think I have something like 18K pins on my nodes and it takes 2 minutes to list them through `ipfs pin ls`, even on an SSD it's not even that much faster, maybe 2-3s at most. In turn I keep the parent hash (ie, for all recursive pins, simply list the top-most hash) in a postgresql database
vyzo has quit [Quit: Leaving.]
vyzo has joined #ipfs
postables[m] is now known as postables2813[m]
postables2813[m] is now known as postables[m]
cwahlers has joined #ipfs
cwahlers_ has quit [Ping timeout: 252 seconds]
postables[m] is now known as postables1337[m]
cafx is now known as raindrop
postables1337[m] is now known as postables[m]
mischat_ has quit [Remote host closed the connection]
mischat has joined #ipfs
mischat has quit [Remote host closed the connection]
mischat has joined #ipfs
discopatrick has quit [Quit: Connection closed for inactivity]
fredthomsen has joined #ipfs
mischat has quit [Remote host closed the connection]
fredthomsen has quit [Quit: Leaving.]
mischat has joined #ipfs
mischat has quit [Ping timeout: 252 seconds]
spinza has quit [Quit: Coyote finally caught up with me...]
pmatteo1998 has quit [Remote host closed the connection]
spinza has joined #ipfs
chiui has quit [Remote host closed the connection]
mischat has joined #ipfs
kn0rki has quit [Remote host closed the connection]