Old thread >>51467711 >What is IPFS? It's bas

Heres a site dedicated to hosting various animu links. An anon from last thread made it. Pretty chill.

/ipns/QmUqBf56JeGUvuf2SiJN
JahAqaVhFSHS6r9gYk5FbS4TAn

>>51477984
Index of sites and various files:
ipfs.io/ipns/QmaGks9KKzu2WykHQjJFJkcUAN4ZoF7ok9h2hXj1WQn47U/

Anime tracker:
ipfs.io/ipns/QmUqBf56JeGUvuf2SiJNJahAqaVhFSHS6r9gYk5FbS4TAn

Pomf clone on top of ipfs: glop.me
Image sharing on top of ipfs: ipfs.pics

Sharing is caring.

Question: can/how would streaming (f.e. Internet radio) be done with IPFS? I get stuff like twitter or 4chan, and but streaming seems a bit "impossible"... Or am I just not understanding it?

>>51477984
>Daily reminder to pin files that you care about.
So this is a giant echo chamber?

>>51478053
Im the one who made this site. Its still very early in development. Looking for any feedback or suggestions people have still! Thanks m8s

>>51478066
Its a copypasta. So pretty much yeah.

>>51478058
Like many other things, this is planned.
Interresting post here
https://github.com/ipfs/ipfs/issues/103
As well as in a few other places in the issues trackers on github.

>>51478058
When you download from ipfs, you receive chunks on-demand. You can already stream videos over ipfs without too many issues, so downloading works.

As for uploading, it seems multipart formats are supported. Not sure how well exactly, but you should definitely look into it. In theory, it can also be implemented with ipns when ipns' support for arbitrary signing key is implemented (i.e. with forward-references).

>>51477984
Equivalent of torrenting files on IPFS?

>>51478366
Downloading files.

>>51478366
Not sure what you are asking.

>>51478121
By this time next year, ipfs will be the GOATest. I haven't been this hype for new tech in over a decade, holy shit!

>>51478404
>>51478407
Sorry, I didn't look into it all that well before asking. How does one go about getting new content? Sorry if this sounds too retarded to answer.

>>51478519
Find URL and download. You can get results from google by searching through an ipfs gateway, such as by using site:gateway.ipfs.io/ipfs (or ipns), or via our site: ipfs.io/ipns/QmaGks9KKzu2WykHQjJFJkcUAN4ZoF7ok9h2hXj1WQn47U/
which links to content we know about.

>>51478519
There isn't a ton of content on ipfs yet. There have been a few sites posted that have a bit of content setup. But as of now, there really isn't much up there. If you are looking for files and such, it's best to stick with normal torrents for now.

Is the meme dying down now?

>>51477984
QmTQ7FbRJBcZcbyKWy4xiajvdAqQTjrEPZ1LhrFHcrUxrL

Put together Diebuster for you guys

>>51479099
Nice. What quality is this in?

>>51479150
720p h264 for bandwidth. I've got BD rip if anyone wants.

>>51479183
Thanks man. Im good with 720p. Saves space and still looks good.

>Go to sleep for 5 hours
>Wake up and Start to add Movies directory for you guys
>Threads die out
Thanks guys. Another dead project.

>>51479292
SHUT UP
IF YOU BUILD IT, THEY WILL COME

Is there a "guide for dummies" to upload files? ive got 4TBs of movies/shows/anime in 1080P which id like to add

>>51479292
>thread way over the bump limit systematically
>ded
kek

>>51479327
Literally in the OP
>>51479307
Right...

Isn't there already something like this?
I can't remember the name but I used it a long time ago during raids.

Alright faggots, you and IPFS were both made for one thing: pin this.
QmVbCbGE39kSpgwX33j3s5XiidgFaY8SdE23VBqtbf8rgc
It's your destiny.

>>51479363
I think you may be thinking of Freenet

>>51479347
Well clearly threads will eventually die out. I am talking about the users. Its just same fagging with 10 people now.

>>51479327
You can go to localhost:5001/webui and drag'n'drop the files. From the command line, you'd do ipfs add -r "the folder" and note the hash next to the folder (should be the last displayed hash). Note that this operation will copy every file to a local directory even if it's on disk, and allowing inplace sharing is a planned feature but not yet available.

>>51479379
No, Way different.
Some anons hosted forums on it.
It was almost exactly like this.
It wasn't i2p either.

>>51479327
Be careful about uploading that much stuff. Currently IPFS copies all the files you want to send. So it doubles your disk usage. Might wanna pick and choose what you want to upload.

To upload directories, like entire shows, use

ipfs add -p -r <dir>

To upload single files, use

ipfs add -p <file>

It will calculate the hash for you and print it out. Thats what you want to share.

>>51479390
>30 posts in
kek

>>51479366
Need an ipns name on dat shiet so you can give us more updated versions eventually.

>>51479406
Tor? GNUnet? Im interested now.

>>51479366
Oh shit m8. Is this a bunch of anime reaction pics. Pinned.

>>51479392
>>51479413

>You can go to localhost:5001/webui and drag'n'drop the files.
That easy? cool
Thanks for the warning, ill add a few things just to test and maybe make a backup

>>51479432
Nope. Not even.
It's really bugging me now.
All I remember is that it all of the files were de-centralized, I think p2p like this program.
And it came with it's own web browser.

>>51479429
You should rather wait for someone more organized than me to do that
>tfw spent an hour selecting smug anime faces from my 4chan folder

>>51479486
Perfect dark?

>>51479486
limewire (gnutella)?

>>51479486
Ares? lol

>>51479498
>Perfect dark?
No, Not that either. I've used that before.
You wouldn't believe how much japanese CP is on there.

>>51479366
Is it just me, or is this downloading super slow?

Werks for me.

>>51479514
>>51479518
GTFO, not even close

>>51479525
Its ok for me, i think its just you

>>51479525
That's normal, my connection is super shitty and for some reason it looks like ipfs uses 80% of it for things that aren't file transfers.

>>51479547
Hm. Weird. Downloaded Diebuster super fast. This is hardly moving though. Wonder whats up.

>>51479535
no u

>>51479556
Well alright. Once I get it downloaded, Ill pin it and help you out there.

>>51479563
You might be very far from any seed.

>>51479579
It looks like 7 people have accessed it so far so it should be super fast if they all pinned it (doubt it) and once the initial seed is done.
It should take approximately an hour at current speeds if what

ipfs stats bw

is accurate.

Anyone know how to tell what files you are seeding?

>>51479594
That would make sense.

>>51479643
I don't think you can yet.

>>51479626
It looks like Im actually seeding some other file out at pretty high speeds. So thats probably taking all my bandwidth.

How could you tell 7 people have accessed it?

>>51479659
Drat. Thanks anyways man.

File: goo gl-aQi6Xh.png (63KB, 884x884px) Image search: [Google]

63KB, 884x884px

>>51479514
>gnutella
I started looking though the different versions of this, I think it actually might be one of them.
This is the only thing I recognize.

>>51479695
You can query the DHT to get a list of node IDs able to serve a certain block

ipfs dht findprovs <hash>

File: illegal-spying.jpg (233KB, 1024x786px) Image search: [Google]

233KB, 1024x786px

if we're gonna do this, rather than having a bunch stupid generals, we should have a single one concerning:
i2p
freenet
ipfs
gnunet
and tangentially, tor, retroshare and the like, etc

>>51479773
Not a good idea

>>51479816
general threads never are
that's why I'd rather see one than four+

>>51479743
Oh nice. This however, is giving me a bunch of errors. Im assuming the peer ID hashes are people that are seeding it, but what does it mean when it says

unrecognized event type: 6

or when it says

error: dial attempt failed: failed to dial <peer.ID aS15tE>

Is it fine to just ignore those errors and count the peers listed?

>>51477984
Do I need a linux box, or can I do this on windows? The command line does not frighten me.

>>51479850
>Is it fine to just ignore those errors and count the peers listed?
Yes, that's what I'm doing.
I don't know what unrecognized events are but I think the unable to dial peer means that someone in the DHT routed you to a peer that is disconnected. This is just a guess though.

>>51479643
ipfs pin ls

>>51479915
You can do it on Windows

>>51479924
I meant currently seeding. Like being able to tell which file is taking all the upload data. Thanks for this though. I appreciate it.

>>51479915
There are windows binaries on here for the GO based version: gobuilder.me/github.com/ipfs/go-ipfs/cmd/ipfs?branch=v0.3.9

>>51479956
>>51479925
Thank you

File: 1428745649170.gif (3MB, 555x312px) Image search: [Google]

3MB, 555x312px

>https://github.com/ipfs/apps/issues/6#issuecomment-158700659

PHP works with this right?

>>51480006
What does this mean? Im not very good at reading through source.

>>51480026
We might be able to address code that executes

>>51480086
Oh sweet. Thats great.

Is it possible to run two ipns hashes from one location?

>>51480136
Not yet

>>51480145
Drat. Alright. Thanks friend.

File: 1447706457649.png (147KB, 336x437px) Image search: [Google]

147KB, 336x437px

Are you guys still pinning my smug collection? How's the progress so far?

File: 1445985308719.jpg (115KB, 513x653px) Image search: [Google]

115KB, 513x653px

I'm still downloading and waiting for pin to finish.

>>51480294
I literally just finished downloading. 1h12m12s it took. What a life.

File: 4.jpg (271KB, 1200x1740px) Image search: [Google]

271KB, 1200x1740px

>>51480350
It finished just when I posted that

File: 1436294105493.png (254KB, 381x403px) Image search: [Google]

254KB, 381x403px

>>51480294

QmVV9Hteg6JcRwv9LjZZHrQCrKJYPZLvVb2264MfE4vso2

QmRa2z3zTL2XHtheA
jYnsuSDiyDn4sKktWrywg31KdnMmX
170MB of pepes

This is alpha software, not gonna run it until it's stable at least.

File: 1439784455484.jpg (136KB, 732x485px) Image search: [Google]

136KB, 732x485px

>>51480508
>>51480392
>>51480362
N o i c e
QmYYf5gfwCjppWPWXHLn8Xi5k3XsCpHg2Exx7M1G7tin5v/cheeeeeeeen/

>>51477984
Go to install url, get 404, am i missing something?

>>51480854
It goes to the right page for me, which is https://ipfs.io/docs/install/
Maybe your ISP is fucking with you.

any porn or hitman hiring sites to attract the plebs?

>>51480887
May be because im browsing from smartphone?
Anyway this got me worried

>>51480904
Sime 8ch anon has a hash that's supposedly CP.
>notclickingthatshit.webm

>>51480960
[spoiler]Its a rick roll.[/spoiler]

>>51480960
this
QmV9NkLXi9w7a7pXTqksAVfHNmBrJypDzrk6zCJWYbmxeP

File: 1389857923922.gif (998KB, 500x383px) Image search: [Google]

998KB, 500x383px

>>51480989
>[spoiler]

Does anyone else have a problem with the daemon stalling or getting insanely slow upload and download speeds when it's been running for a while?

>>51481665
I have, think it's just a general issue

File: calculated risk.gif (172KB, 554x390px) Image search: [Google]

172KB, 554x390px

Real quick, are these ipfs hashes in base64? base64 for URL?

>>51482187
no

File: magic.jpg (50KB, 640x661px) Image search: [Google]

50KB, 640x661px

>>51482212
Alright, thanks. There seemed to be too few special characters. Can you tell me how they are encoded, and why?

>>51482187
It's a SHA256 multihash.

Base64 isn't a hash either, by the way.

>>51482265
>why?
It's content-addressed, so when your client asks for a file, you need a way to have a way to address the content itself (and not the location where it happens to be stored). The address thus has to uniquely identify your file, but obviously be shorter than the file itself. Of course, you can't have both, but using cryptographic hash function hits the sweet spot where you get a short address length and can be more or less convinced that you'll never run into collisions, with two files sharing the same address. Since it's cryptographically secure, you protect yourself both from accidental collisions, and ones forged by an adversary.

File: stevie wonder eats breakfast.jpg (28KB, 652x640px) Image search: [Google]

28KB, 652x640px

>>51482268
>>51482324

Heh. My mistake for being unclear; I meant to ask how the hash is encoded. Googling around, I get the impression that it's Base58, which seems stupid and I'm not sure why they've chosen that.

>>51482361
Oh, okay, now I understand you. Base58 seems to be the standard encoding for other Merkle DAG based protocols, e.g. Bitcoin. Here is their reasoning: https://en.bitcoin.it/wiki/Base58Check_encoding

// Why base-58 instead of standard base-64 encoding?
// - Don't want 0OIl characters that look the same in some fonts and
//      could be used to create visually identical looking account numbers.
// - A string with non-alphanumeric characters is not as easily accepted as an account number.
// - E-mail usually won't line-break if there's no punctuation to break at.
// - Doubleclicking selects the whole number as one word if it's all alphanumeric.

File: you are my rock.png (96KB, 193x252px) Image search: [Google]

96KB, 193x252px

>>51482415
Thanks. I guess I just don't value those reasons as much as I value powers of 2, so I'm unlikely to convince them to change anything.

So what's the history of this IPFS thing?
Who is in charge?
Surely not /g/.

>>51482745
Stanford graduate.

Anyone know how I could setup a functional website using php? Not very many people have php installed on their computer.

Or perhaps there is another type of script I could use? I'm pretty new to web development.

>>51483409
Dynamic content isn't feasible outright. Either use plain http for that (i.e. every resource is on ipfs but the frontend is an http site, like with neocities and ipfs.pics), or consider building the site with smart contracts (eris or ethereum among several options) if you're interested in having a fully distributed and decentralized site.

>>51483618
Ah that makes sense.
What exactly are smart contracts? Ive heard the term before, but couldnt find much on it aside from bitcoin stuff.

File: 1430365905774.png (31KB, 325x262px) Image search: [Google]

31KB, 325x262px

I guess I should start uploading all the rare files I've been archiving over the years. Here are some:

This one disappeared with Megaupload:
/ipfs/QmV7shD3Vnff4kCSyur
QKtRDaA9NDMpMqp15wHD91fJjMP

Special TLC made for /f/, original was only uploaded to Pomf:
/ipfs/Qmd4JP4dWhCfnh2cct47H
ndgCcfRECrkSV6Z3NordgPTQ3

Dilbert 1-3. Creator removed the originals, and all that is left are shitty Youtube reuploads. I had to hunt around for a long while to find versions with as little generation loss as possible:
/ipfs/QmaB7eziMHqhuWGiZFMQic
1cxEu2SPHVvSZ6qnQWGdYcaJ

Bonus:
/ipfs/QmVUoY96TQbFjxHaXKr8E4
pqCVXfqnTayGdH56dMFstcJL

>>51483640
A cryptographically-ensured form of distributed computing. Basically instead of the server performing and verifying transactions, users are allowed to do so because cryptography ensures that the operations must be correct and no tempering can happen. Check the sites of the respective technologies to learn more.

>>51483719
Sorry if these questions are stupid, but how would this help my website? Examples of how it could prehaps?

>>51483665
>/ipfs/QmVUoY96TQbFjxHaXKr8E4
>pqCVXfqnTayGdH56dMFstcJL
Wat

>>51483792
Because everything from the data to the code is distributed and decentralized, there is no single point of failure.

>>51483807
Thats the same thing without the contract, no? All the website files are distributed and decentralized. any data that is probably included in ipfs links is also distributed and decentralized. Whats the difference?

>>51483665
Pinned :^)
... on a gigabit vps

>>51483857
That's true only with static sites. If you serve dynamic content, then you can't rebuild the site without a direct connection to your server to get the feedback necessary to perform the rebuild. With smart contracts, any user can initiate a rebuild because smart contracts ensure that the input is legitimate and that he output is correct, basically.

is there any way to open up the ipfs http interface to hosts outside the local? I want to be able to run ipfs on one machine in my network and just pull assets from that.

>>51483892
one of the advantages of ipfs is its ability to find peers close to you

if you run ipfs on multiple machines in your lan, they will communicate with each other

>>51483892
Edit your config file and change where the gateway value is

/ip4/127.0.0.1/tcp/8080

change it to

/ip4/0.0.0.0/tcp/8080

>>51483892
You don't want the http interface for that, you want the 8080 interface. Check out ipfs config --help and you should find a way to specify more places to listen on, but you shouldn't have a problem, over lan, in connecting to another machine on 8080. hostname.domain:8080, as per usual.

>>51483885
Ahhh. I think I see now. So users submitting content to a site would not work though. Because then it would have to send that content out to everyone. Correct?

Also, does a user have to have the contract software installed to use it?

>>51483917
Not him, but I have one always-on server and a couple of desktops and laptops, and would prefer to pin files on the server, so that the files are always accessible. Doing that through the webui would be better than having to SSH into the machine constantly.

>>51483966
you can change the bind address in the config file for this (>>51483933)
the webui is on 5001, so change that line instead/as well
don't port forward 5001/8080 externally though, only 4001 (even that appears to be optional, i've had ipfs.io get content from my machine even through a nat, shit's magic)

>>51483966
Do what I said in my reply here >>51483933 But also change the API line to have the 0.0.0.0 part. That just specifies what address its listening for. 0.0.0.0 is everything. Also make sure your ports are good through your firewall.

>>51483933
do you have to restart the daemon after changing this through the ipfs config interface?

>>51484013
Yeah you do.

File: 1444470357553.png (214KB, 487x286px) Image search: [Google]

214KB, 487x286px

>>51483665
>QmVUoY96TQbFjxHaXKr8E4
>pqCVXfqnTayGdH56dMFstcJL

>>51484021
fuck. goodbye you 200 bastards

>>51484032
Cant handle the restart?

How is this different from other forms of decentralized file-sharing? How would this be obfuscated? Would it be tor-levels of obfuscation?

>>51483997
i just did this, it looks like the webui will only poll a local ipfs installation. sorry.

>>51484032
you could try sending a SIGHUP to the daemon
some daemon's can reload their config with a signal

>>51484049
unlike some other decentralized filesharing we talk about, this one has no focus on anonymity (deliberately)

you can run it atop tor though

>>51484049
It's not obfuscated, and not strictly for file sharing.

Out of interest, is there a feasible way to use this as a local distributed filesystem, like you would Ceph or GlusterFS?

>>51484082
Suppose I want to share <popular movie> over it? Would it be be able to be traced back to me in that case?

>>51484103
No one can see who originally published it, but everyone can see who is seeding it. You will be listed among that.

A domain/share naming system is planned, correct?

>>51484103
the one anonymizing function ipfs has is that by design there are no 'origin' servers

when something is added, you seed that thing as a node, if someone else downloads it (or adds the same file themselves), they also seed it as a node, and there is no way to tell who put the file on the network initially

>>51484120
just curious, gnunet claims to be able to get around this problem. how does it do that?

>>51484137
IPNS, it's functional but not complete yet
plain DNS is also usable

>>51484141
the way things like tor and maybe gnunet (haven't really looked into gnunet) work is that they do 'onion routing', or they route traffic over various randomly chosen nodes so it's impossible to tell who is accessing what

ipfs doesn't do this by default because it's slow, wasteful, and makes it impossible to source data from close peers, basically, it defeats a couple advantages
the inventor of ipfs realizes that ipfs will only be adopted widely if it's faster than what we have, he's being practical

most people don't need to have their static traffic anonymized, those who want to can by layering it over a network like tor, that's what they were made for

>>51484139
You could imply from this, that sharing <popular movie> is similarly risky to using BitTorrent, because content protectors send fines and C&Ds to seeders and downloaders in general rather than the original uploader.

>>51484198
thanks bud

>>51484211
yes, it's about as 'exposing' as being a regular bittorrent peer

>>51484054
This. The interface loads, but it can't find the Node ID or anything else.

>>51484198
I think there should be an "Anonymity" layer in the OSI model.

>>51484054
>>51484241
couldn't you do an ssh port forward to make it appear local?

$ ssh server -L5001:localhost:5001

-- then visit "localhost:5001"

>>51484254
speaking of the webui, does it flat out stop working after a bit for anyone else?

does ipfs do any kind of deduplication? if I and someone else publishes the same file, would it just generate the same hash and thus not require any kind of redownload?

>>51484289
yep, everything is deduplicated, the same content will always have the same hash

>>51477984
So as a Windows user... I don't get in on this fun?

How would one individually add a layer of anonymity to it using tor?

>>51484312
https://gobuilder.me/github.com/ipfs/go-ipfs/cmd/ipfs

>>51484312
There are windows binaries available.

>>51484312
This runs on everything from Windows to Plan 9.

>>51484254
Clever. Yeah, that works. I had to forward 8080 too, since some of the links in the webui point to http://localhost:8080.

>>51477984
So does the OP mean you can be non-traceable with your torrents?

>>51484153
So there will never be a time where you can simply navigate to ipfs://niggers?

>>51484427
i think the dev is after "/ipfs/niggers"
to coincide with unix paths ("/ipfs/niggers" can be a valid local path as well)

People keep mentioning using smart contracts with web development. Can anyone explain how that would actually help a website? It seems that you have to install the smart contract stuff to use the contract. No one wants to install software just to browse a site.

>>51484398
You aren't traceable as the uploader. But everyone can see that you are sharing the files. So you aren't completely untraceable.

Is it possible to access the webui over the internet remotely? I have this running on a gigabit dedi.

>>51484468
How is that actually a link. There's no domain or anything that it's directing to

>>51484484
ssh

Is this the kind of stuff that would make the web not such a bloated shit?

>>51484484
See >>51484254 >>51484373. That's the only way we've got working.

>>51484490
>being this new

>>51484484
Yeah. There were some anons talking about it a while ago in the thread. Just look back 10 or so posts. Only thing you'd have to do different is port forward external ports as well.

Beware though, the webui has no authentication. If anyone finds your webui, they can upload whatever they'd like through your connection.

>>51484510
doing an ssh port forward is completely safe, as the port is only forwarded through a secure ssh tunnel

>>51484509
Just popped out of the womb yesterday. How does it work?

>>51484531
>How does it work?
Are you talking about why it's highlighted as a link in your browser or something? Because that's not a link that would work on the normal Internet (it's probably for some other Freenet-like web that I don't know about).

>>51484643
It's a link that routes right to google. I copied and pasted it in my browser as well as clicked it. Same place every time. Am on clear net right now.

>>51484678
Its using the decimal equivalent of an ip for the 332... number then the %73%65 etc is text converted to ascii in hexadecimal.

>>51484678
Oh, right. IP addresses can be given in decimal notation instead of dot-separated decimal. Kinda forgot about that. Example (you have to add a HTTPS exception): https://1347911747/

>>51484743
>>51484751
Ohhhh. Thanks for the responses. That was really confusing me.

>>51484303
>>51484289
That's not deduplication at all.
In fact, that's the opposite of deduplication.
What you're really doing is mirroring the files across servers.
Deduplication is an effort to reduce duplicate files on a local server using things like symlinks to save disk space.

How do I define a file name for an added file?

I added something via: ipfs add filename
And can reach it via ipfs.io/ipfs/<hash>
But the filename is just the hash?

Why is it that the web interface lets me view directories super quickly but "ipfs ls *dirhash*" never fucking works

>>51485631
well, it depends how you look at it

lets say we both have .. an episode of a tv show, the exact same file
lets say we both make a torrent including the file and share it
in this case you'll end up with two seperate swarms sharing effectively the same data but in such a way that they are incompatible (you don't automatically benefit from the peers of both torrents, only the ones connected to the torrent you chose)

with ipfs, if we both add that episode to ipfs, it will get the same hash, regardless of if we named the file differently or if we add it with other files (say i added the episode by itself, and you added it along with the rest of the seasons' episodes)
people who go to get that episode will automatically be able to get it from either of us, and anyone else who has that file (even ones who already had it)

you can think of it as deduplicated /effort/
the cache is natually deduplicated locally as well, since you don't store the same block more than once

you do want several people with the same blocks, since that adds redundancy and performance

>>51485631
It's on the block level, not file level, so if two files owned by you coincide on some block, only one copy of it will be stored.

>reduce duplicate files
That's the same thing that the anon you're responding to is saying, so I'm not sure what your point is. Or do you think it's not deduplication if you're using something other than symlinking or something?

If I had for example a directory shared with two files in it, and later added a third one, would ipfs add -r <directory> notice the already added files and only update the directory listing by uploading the third one?

>>51486027
Yes.

>>51485634
Files themselves do not have a human readable name outside of directories, so you'd have to wrap it inside a directory. One way to do this after you've already added the file is to

ipfs get

it, give it a filename of your choice and then

ipfs add -w

it. This wraps it inside a directory, so that the filename is preserved. The file itself does not need to be added again, since it hasn't changed, so this will complete almost instantly. All this does is add a new object with an entry associating the human readable name and the hash of the file. After you're done, you can delete the file you downloaded with "get".

>>51486027
>>51486124
>Yes
I should mention that you'll get a new hash for the directory, though, so you'd have to update that wherever applicable (web links, IPNS publications, DNS records).

>>51479363
MORPHiS
The dev went silent, no?

add files in-place when?

can't find the issue page on it

>>51485765
The first responder got the idea.

All this talk about hashes is somewhat confusing.
Am I right in assuming that the SHA-256 hash is in fact the SHA-256 checksum derived from the file?

>>51486387
hash and checksum are the same thing senpai.

>>51486428
I guess.

>>51486387
yea, an ipfs hash consists of the hash type, hash length and the hash itself, which is sha256 by default

>>51486124
I found a new way to add a filename:

1. Create a new directory object using:

$ ipfs object new unixfs-dir
QmUNLLsPACCz1vLxQVkXqqL X5R1X345qqfHbsf67hvA3Nn

2. Add your hash to the newly created object:

$ ipfs object patch QmUNLLsPACCz1vLxQVkX qqLX5R1X345qqfHbsf67hvA3Nn add-link "New filename" QmdSSEukuh311rvY7bVXK B7pt83EUmbG9wvnsa5MxTAww1
QmP9BYqgQceZpHct2tPKZo HboTUUpbatWxdyM5Ck61E4z3

Now the hash QmP9BYqgQceZpHct2tPK ZoHboTUUpbatWxdyM5Ck61E4z3 will point to a directory where QmdSSEukuh311rvY7bVXKB 7pt83EUmbG9wvnsa5MxTAww1 is named "New filename".

>>51486387
That's what "hash" means, yeah. Hash and checksum are used interchangeably. Technically, were talking about the labels of nodes in the Merkle graph, so they are not always hashes of the files or blocks themselves, but sometimes of the hashes of the children's hashes, and so on. One file can be divided into several blocks, each of which is hashed to get an address for the block itself, and then the address of the file would be something like the hash of the concatenation of all these hashes.

QmZp1WkkSG9w9f
xDnrxJojpD89i32Dh
9LKxujGkmNEtdib

>>51486924
Pinned.

File: 1437023296364.png (9KB, 616x28px) Image search: [Google]

9KB, 616x28px

>>51486924
:^)

>>51483665
>/ipfs/QmVUoY96TQbFjxHaXKr8E4
>pqCVXfqnTayGdH56dMFstcJL
QmXw2NG29RVFrtgPqca2JUiTB11xfssQiEvf8dGoyk7TZH

Sonata Green blog
/ipns/sonatagreen.com/

Homestar runner mirror?
/ipfs/QmVJ5LiYPQzZ
3DGgLs5fAXFX7
E8v4mZPmrBwfVo56Dvt7S

QmWvBeB1LbxNTY6ciQfKxvXDiXAcHViRwPhbo9dCELaifP
More platinum disco

IPFS seems to be really, really slow for me, is that normal?
On Fedora and with a local install by the way.

>>51487535
I've noticed you need to give the daemon some time to do things and it gets faster after a while.

>>51487535
You need to give the swarm some time to populate.

But IPNS lookups are always slow-ish because of an open bug.

File: 1434513245721.png (73KB, 586x589px) Image search: [Google]

73KB, 586x589px

>That one guy away from everyone else
Stay strong

>>51487535
leave it running for a while so it can discover more DHT nodes

>>51483956
Yes and yes.

>>51487563
>>51487579
>>51487631
Got it, will IPNS suffer the same problem you have with things like Bitcoin where as the network keeps growing over time the amount of info you need in every node becomes really high?
Is this by design?

>>51486484
That's way convoluted mang, -w or just adding a directory is much better.

>>51487648
I think a IPNS record is just a normal file saying "This IPNS name points to this IPFS path", but signed with your node's private key. The file is requested and transferred like any other file (and garbage collected by other nodes when needed). It's not distributed to every node at all.

>>51487648
i'm pretty sure ipfs has no ever-increasing component to it like bitcoin

ipfs has a fair amount of stuff "on" it already, all things considered, and my .ipfs folder is 138K (minus the block cache, which is only a cache of blocks i have requested myself)

>>51487648
No, because you find paths by probing nearby nodes. You don't cache a full blockchain, so per-node data requirements are O(1) wrt network size.

>>51487654
Can you do that to an IPFS path? How would you declare the file name? add -w works when you are adding a "real" file, but in order to rename it afterwards you either have to get it or do some object mangling, from what I can tell.

>>51487685
>you either have to get it
"get" it as in running "get". Damn moot swallowing my code tags.

>>51486484
Oh, and this doesn't pin the new directory, so you'd have to do it manually.

>>51487685
Name doesn't matter because it's all hashes in the end. You can download the file, rename it locally, and rerun add -w to get it a new name if it bothers you that much.

>>51486212
It's in a github issue, planned for the current sprint if I'm not mistaken.

>>51487746
i found it since
https://github.com/ipfs/go-ipfs/issues/875

they have it as a low prio enhancement, but this is what i'm looking forward to the most right now

imagine the explosion of content once people can add shit without worrying about making a second copy of everything?

>>51487725
Dude, just read the comment chain. I already gave that answer before I found the alternative way.

>>51487769
Not sure if retarded or just pretending.

>>51487797
Back at you, anon. Sounds like you don't understand the problem at all.

>>51487809
Retarded it is, then. Oh well.

>>51487822
What a coincidence. Looks like we reached the same conclusion.

>>51487766
>https://github.com/ipfs/go-ipfs/issues/875
I like the git-annex like symlinking idea, but I'm guessing that won't work with segmented files.

>>51488170
This is with regard to files on disk and has nothing to do with blocks.

>>51488245
They are stored as blocks in the ipfs cache, from what I can tell, so there is no file that you could symlink to.

>>51488262
The blocks are generated from the file on disk.

>>51488276
Yes. Now try going in the reverse direction with symlinks.

>>51488293
No problem there.

>>51488351
What do you mean? Symlinks are 1-1. You'd need a way to map each segment of the original file to a separate file in the cache. That's not possible on traditional filesystems without shared extents.

>>51488382
You could google it instead of making a fool out of yourself.

>>51488431
Google what? Concatenating symlinks?

>>51478084
Do you remember an intern from UT Austin who worked with you this summer?

>>51478066
That is what most distributed file systems are.

Look at Freenet, files die on there when they don't get accessed over time and the whole network runs out of space to store it.
It is a pretty natural way of pruning old content if you start to run out of space.

>>51488564
Except in the case of freenet, you can't upgrade the network capacity even if all the capacity of the network can be used to archive popular content. Hence, it's trash.

>>51488170
i just want something along the lines of a sqlite database containing file paths, and their hashes (whole file, plus each block)
then update it like however rsync/mlocate does theirs

as for outdated entries (file has been moved/renamed/modified since), just detect them on read (failure to open the path, checksum mismatch), and either update the db to match, if possible, otherwise ignore/remove from the db

>>51488644
Top kek.

>>51488644
So you'd store the files in their original location and generate the IPFS data blocks on demand? That could work, but it looks like the devs are worried about performance, since you constantly have to rehash files and segments to check for inconsistencies.

>>51488644
Another option might be to flat out refuse to add any files without 'chattr +i', setting up an inotify thing to monitor for when this changes and issue a recheck when it does. Maybe it should consider the file broken until it has been reenabled and the file rechecked.

>>51488749
well bittorrent pulls it off

what i described is not terribly different to bittorrent, its metadata the ".torrent" files are a file/folder listing along with their block hashes

just do what they do, send what you think is right, and have the receiver verify what was sent (come to think of it, they have to do this anyway), perhaps also do a checksum while sending the data, so you're aware by the end if you need to remove/update the entry

>>51489019
Apex kek.

>>51489074
you know something i don't, boy?

>>51489019
Well, with IPFS you would need to recompute more than the block hashes, because of the Merkle DAG database. Every file containing a block identical to the one that changed will have a different hash, and every directory containing a changed file will have to change, and so on. Not saying it is impossible, but it's potentially a lot more work.

>>51489102
Ignore him. It's the same guy as in >>51488431 and >>51487797.

>not encrypted or anonymous

remind me why we are using this over GNUnet/FreeNet/i2p?

>>51489162
because we gotta go fast and you don't need nsa-proof anonymity for sharing chinese cartoons and sad frog drawings

>>51489105
yea, that's true

though even just adding individual files like this would be fine for me

from what i've seen, updating a directory hash seems rather lightweight
i understand a partial file change would unavoidably require a whole-file re-hash, but for many kinds of files this doesn't happen (basically any media)

>>51489162
different use-cases, this doesn't intend to replace those

>>51489182
you need encryption/anonymity for piracy tho bud

>>51489220
then run ipfs over tor/i2p

ipfs pin add -r /ipfs/QmTmMhRv2nh889JfYBWXdxSvNS6zWnh4QFo4Q2knV7Ei2B/
Error: pin: merkledag: not found

What am I doing wrong? That opens as the Gentoomen Library in browser.

>>51489247
daemon isn't running

>>51489162
It's fully encrypted and is designed to be compatible with anonymizing solutions like i2p or tor. i2p cannot host decentralized content and belongs in the trash for that purpose.

>>51489162
It is encrypted.
It's also designed to be able to run on any (anonymous) network, but this is WIP.

>>51489220
This is at least as anonymous as regular torrents. Freenet is so ridiculously slow for large downloads it's not even funny.

>>51489236
why would i run ipfs over tor/i2p instead of just using tor or i2p?

what is the usecase for ipfs? i watched their video on their website and i still have no idea what it's for.

>>51489259
>>51489267
encryption is to stop people spying on what you're doing. when they can literally just connect to u and see every file ur seeding ur fucked.

>>51477984
So is this exactly like freenet? I mean, except freenet is for websites while this is for file sharing. But it seems to be the same concept.

What am I missing here?

>>51489304
>>>/reddit/

>>51489312
Thats exactly what I thought.
DOA with a few weirdos populating stuff.

>>51489328
https://www.reddit.com/r/ipfs
is this the place?

>>51480989
>using spoiler tags incorrectly on a board that does not discuss fictional or narrative media

>>51489312
Freenet has a hardcap on hosting capacity, ipfs does not. The connectivity model of freenet and ipfs are widely different. Freenet is meant to be a completely different, isolated construct whereas ipfs is a thin layer that is meant to be compatible with existing and future technology.

>>51489304
IPFS is for persistance and resilience against websites dying or changing without leaving a trace of the previous versions. It's a global, distributed bookmarking system, with the added bonus that uploading files is extremely easy compared to running a web server or creating a torrent.

How to.. setup in windows?

>>51482782
Is that why he talks like the late, great Aaron Swartz?
>all that lip smacking
>talking way too fast because 2 smart 4 plebs
>same cadence

>>51489312
https://github.com/ipfs/faq/issues/18

>>51489374
so once you upload a file, it's there forever?

>>51489408
It depends. Once you upload a file and someone views it, they automatically become a server of their own. Normally, they garbage collect the file and stop seeding after some time, but they can opt out of this. The "bookmarking" in the metaphor is what people call "pinning", which means that a node chooses to seed a file indefinitely.

So it's permanent as long as someone has the file pinned, which will not always happen.

>>51489408
As long as other people access it or pin it.
There's a project to offer compensation (like buttcoins) to people that voluntarily share their HDD space and bandwidth to others to guarantee their files will always be accessible. But this is still far away in the future since ipfs itself is still in alpha and will stay in development for quite a while.

>>51489342
>virulent shitposter shitposting virulently
Shocking.

>>51489304
You don't see any use cases for a fast and fully distributed filesystem?

>>51489442
>>51489487
so it's permanent as long as it exists?

aka it's not permanent and it's just like any other content on the web.

>>51489509
The normal web can't detect when someone has downloaded and archived it.

>>51489497
the web is already a fast fully distributed file system

>>51489509
>I'm retarded please look at me!
(you)

>>51489509
It's Relatively Permanent or Effectively Permanent.

>>51489497
Not shitposting, they are re-inventing the wheel, darknet software has been around for ages and there are no compelling reasons to use this.

>>51489525
The web is decentralized, not distributed.

>>51489522
the person hosting the content can.

>>51489529
no it's not

>>51489525
I laughed.

This is the biggest meme since tox, torrents are way better in every way.

>>51489543
>the person hosting the content can.
Nope.

>>51489525
No, HTTP is a centalised model and the web is not a unified hierarchy.

>>51489541
Which darknet protocols are built around merkle hash graphs (like torrents)?

>>51489566
>Which darknet protocols are built around merkle hash graphs (like torrents)?
Like I said, no compelling reasons. I understand you are excited but nobody will know what the fuck that even means.

>>51489552
>not content-addressed
>no mutable links
>not inherently compatible with other technology
>no caching
>isolated networks
>requires centralized trackers
The only meme here is you desu senpai.

>>51489509
That's relative to how many people are using it. If it becomes as widespread as the web I can guarantee you that broken links will become extremely rare compared to what's going on now. Nothing is permanent. Daily reminder that you will die one day.

That's not its only advantage anyway. Things like "offline" connectivity, proximity fetching and a lot of other stuff is also very important.

>>51489565
yep

>>51489552
Think of it as an augmented torrent protocol.

>>51489543
There is no "person hosting the content".

>>51489580
You are such a daft cock.

>>51489566
If !BE/4wes0mE shits on it, you know it's absolutely god-tier.

>>51489583
magnet uri bro
You don't need trackers, dht works great.

thread screenshots are deprecated
https://ipfs.io/ipfs/QmQUTjk7VG8qGg66rZWhDSBREgaMFdyW8zVFJWfWnTLsxh/

>>51489596
>There is no "person hosting the content".
but there is

>>51489593
Not even a tiny bit. If you're this ignorant you might as well kill yourself now you waste of oxygen.

>>51489593
I may or may not have saved this thread. Do you think Satoshi Nagasaki knows which is the case? And how would you access my archive when the thread 404's?

>>51489601
>magnet uri
>You don't need trackers
Filtered.

>>51489597
That's a good point. He is, after all, the person who devotes his time to choosing software to bait people in desktop threads.

So can I use this as a replacement to torrents and not get raped for copyright.

Also can I leave my multiple TB hdds serving on ipfs this and expect to be safe? Or is it obvious what im doing, and can peers be malicious?

>>51489633
As far as I know there is no such thing as an illegal blockhash.

>>51489622
he knows you downloaded the thread. anything you do with your copy is subject to uncertainty. you could delete it or keep it.

>>51489633
>So can I use this as a replacement to torrents
Yes
>and not get raped for copyright.[sic]
If you use it over i2p, yes. It is not anonymizing even though it's encrypted. It is also safer than torrent because you can't tell if you're downloading from someone who's hosting the content explicitly or if the content is merely cached, so more evidence must be obtained.

>>51489644
Exactly.

>>51489640
https://en.wikipedia.org/wiki/Illegal_number

>>51489640
but isn't my actual computer external facing when I'm serving content? My IP is used to connect to me and get my files. Isn't it then trivial for a copyright enforcement agency to connect to me, log my IP, and send a notice?

>>51489673
Yes. This is not for file sharing. At least, not any more than Bittorrent should be.

>>51489658
that's the same as ipfs though, just like was said earlier. the files are automatically pruned after a date, and users can delete them manually too. it's no different except your internet cache lasts a lot longer by default.

>>51489673
Yes because it's just like torrents in that regard. Obviously if you wanted anonymity you'd run this through a Tor or i2p proxy.

>>51489608
That's pretty cool. How long until 4chan archives start using it?

File: hurr.gif (344KB, 1920x1080px) Image search: [Google]

344KB, 1920x1080px

>>51489625
You are a fucking retard.
I strip all trackers all magnet uri and they work fine.

>>51489720
Why are you still in this thread? You've dropped your turd and you can go.

>>51489706
It's different because if ANYONE has a copy you can find and access it.

>>51489706
>the files are automatically pruned after a date,
False.
> it's no different except your internet cache lasts a lot longer by default.
You're so retarded it hurts.

>>51489696
So why are we using it?

inb4 >we

"we're" all using it to send anime that's pretty obvious. I understand the benefits of the system for keeping files alive, but it seems without an immediate use if it can't be used to share files care free.

maybe it just needs like proxy servers that know what IP belongs to what hash or something. well I don't know, I'm not good at cryptography or networking.

>>51489756
You scared the anime police are going to come after you?

>maybe it just needs like proxy servers
As said above you can just use an anonymity layer. You can still join a swarm all the same.

>>51489755
it's literally no different though. all that's required to emulate this behaviour is to make your downloads and temporary internet folder never autodelete and to run a web facing server serving the content.

literally all ipfs is.

>>51489756
You should make a site that hosts lists of links to the hashes and call it something catchy like a magnet uri.

Oh wait.

>>51489706
Your browser cahce is not accessible by anyone browsing the web. The point is that you immediately act like a server and help keep the content alive. When you "save" something you are discoverable by others who want to browse the site and hence become indistinguishable from the original host.

It doesn't matter if not all files are shared by everyone indefinitely. The web can't do anything remotely similar. The best you'll get is someone hosting a mirror, on another address that you'll have to discover via e.g. Google. Discovering mirrors is not part of HTTP.

>>51489747
that's literally because they are using the software to run an http service serving the content.

this software is a nice all in 1 package but it's nothing new.

>>51489792
what the fuck are you on about

why are we being flooded with shitposting?

>>51489807
>that's literally because they are using the software to run an http service serving the content.
WHAT

>>51489792
How would you have your web server serve your cache at the same address as the original page?

>>51489798
My browser cache isn't accessible because I don't run a http service to serve the data back. I could just start apache and do it and voila, ipfs.

File: 1428307095793.jpg (131KB, 565x575px) Image search: [Google]

131KB, 565x575px

>>51489807
bitswap doesn't use HTTP. Nice comment though, you know what you're talking about.
QmVbCbGE39kSpgwX33j3s5XiidgFaY8SdE23VBqtbf8rgc/1436392015169.webm

>>51489847
>>51489843

>>51489811
>why are we being flooded with shitposting?
316 / 20 / 44 / 2
>316
>44

>>51489807
There is no HTTP involved.

>>51489811
I think it's shills. Maybe fed-senpai finally noticed us. Doshiou~ :3c

>>51489811
IRC

>>51489719
dunno

https://github.com/VictorBjelkholm/ipfscrape

>>51489843
>>51489860
So if I go to
/123.133.some.guy/ipfs/hash#JHJHujh2jh2hjkhvvc/coolvideo.webm

and he has removed it, will someone else who has that file serve it to me on that url(or behind the scenes with the software searching for the has)? if so you might have convinced me of the benefits over conventional http and webserver models.

>>51489924
Do you know what torrents are?

>>51489924
You never connect to someone else's ipfs service you fucking inbred. Holy fucking shit 10/10 if troll, -10000000/10 if retarded.

>>51489924
Yes. It's content-addressed and not location-addressed.

>>51489924
you don't remotely understand the concept behind ipfs

>>51489939
then how do I get the file?

I watched the ipfs video on their website, all 18 minutes. and he was running a external facing webserver that served his content from his IP.

>>51489962
RRRRRRRRRRRRREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

>>51489939
>>51489951
>>51489955
>>51489933
mixed signals here guys.

if this is to spread to dumb people like me it needs to be explainable

>>51489962
You get the file from peers in a swarm.

Fucking hell.

>>51489981
>if this is to spread to dumb people like me it needs to be explainable
It doesn't need to just yet.

>Path Resolve error: multihash length inconsistent: &{124 132 [104]}
;_;

>>51489985
wait so then what's different between this and torrents?

>>51489962
Not sure what video you're talking about, but there are several ways to do it. One is to run ipfs directly and either write the content to a file or cating it. Another is to use a web gateway on localhost which runs the IPFS protocol on the backend, like you said.

>>51489981
I said "yes" as in "you're almost correct". What the other's are raging about is that the address doesn't contain an IP or anything similar in the first place. The peer serving the file is completely secondary and transparent. What matters is the content.

>>51489962
the web server it ships with is just a front end, a 'bridge', to allow ipfs access with a web browser (since current browsers yet support ipfs directly)

try it yourself, download ipfs, run the daemon, then open this;
http://localhost:8080/ipfs/QmVbCbGE39kSpgw
X33j3s5XiidgFaY8
SdE23VBqtbf8rgc/1436392015169.webm

the video will be located and downloaded over ipfs, addressed/identified by the hash you used, and served to your browser over http (ONLY between the ipfs daemon you're running and your browser, http is NOT used over the internet here)

>>51490020
Make sure there's no space when you copy the link.

>>51490027
Torrent-like transfer is a part of IPFS. The key word is part, and the data structures are not the same anyway.

Is it just me or is there not a single progress indicator on CLI pinning?

>>51490027
Caching, content-addressing, everything is basically a single massive torrent (in gaymen's terms), always encrypted end-to-end (optional with bittorrent), mutable links, can be used naturally with other technologies, etc.

>>51490027
You can have six different torrents with six different swarms even if the file in the torrent is exactly the same. It's extremely inefficient.
Also mutability, signing, dag trees and a lot of other `ABSTRACT BULLSHITE THAT YOU WILL NEVER COMPREHEND

>>51490061
Not just you. The webui isn't very polished because the software is still in alpha and has more important issues to deal with for the time being. At least it doesn't segfault like gnunet's :^)

>>51490027
IPFS has block-level deduplication, versioning, mutable links and one single, global swarm.

>>51490061
There doesn't seem to be any. I think they were discussing this quite recently.

>>51490061
Someone mentioned a workaround: wget the file through the http://localhost:8080, wait until it is done, and ipfs add it. Adding will be instant, since the file downloaded via IPFS behind the scenes.

>>51490046
Ok, thanks.
That was stupid.
:3

>>51490039
oh i see thanks for clearing that up.

>>51490081
>>51490074
ok thanks i'll read the wikipedia pages on some of these terms.

for the hashes of files, this works great for indentical files yes? but torrent websites for instance may have a thousand torrents for a single movie, all different type/size etc. will there be a way to like determine similar files(not sure if hashes can be used this way)? or will indexing websites solve that issue?

>>51490085
Can you give me a brief overview on how the versioning works? it sounds quite cool.

>>51490145
>will there be a way to like determine similar files
Large files are split into small blocks, each with its own hash. If two files have the same block, they'll both seed the same content even if it doesn't come from the same file. However, for non-text content, it's very rare for it to happen. Obviously if you're downloading a 4K BD-rip you don't want to receive a 480p camrip block instead so you will always have different set of blocks for different such files. But if you encode the same file with the same settings, assuming the process is deterministic, then the file will be the same anyway.

>>51490145
Short answer is content-addressability (again): Since addresses are uniquely determined by the file contents, making an edit to the file changes the address. The content on the old address is still accessible (barring garbage collection and not enough people pinning it). The block level dedup also helps a bit, since the whole file won't have to be redownloaded and repinned, only the block that changed.

>>51490145
>for the hashes of files, this works great for indentical files yes?
yes, identical files can be downloaded from anyone who has it, regardless of filename

>will there be a way to like determine similar files
not by the hash, there is no indication as to how "similar" a file is except by comparing how many block hashes are the same between two files (large files are chunked into multiple smaller blocks, for various reasons, both the whole file and each block have their own hashes)

>Can you give me a brief overview on how the versioning works? it sounds quite cool.
a hash 'defines' a unique file, so if the file is updated, it naturally gets a new hash, so now you have two hashes, one that links to the old version of the file, and another for the new version

How to pin while running Daemon?

GAIS GAIS GAIS I DID EED
https://ipfs.io/ipns/gindex.dynu.com/
Should give access to my site index. Works on my end, anyway, with ipfs.io

>>51490253
how would you see the version history. and what decides whether it's a modification or a new file?

is the original uploader the only one who can create new versions?

i know they said gitlike, so is the original uploader like the maintainer of his file? and can accept changes or something but ultimately decides versions?

>>51490306
ipfs pin add <some hash>
with -r if it's a directory.
If you add a file, it's automatically pinned. If you pin a file you haven't downloaded yet, it will be downloaded.

File: emag eht.png (24KB, 677x343px) Image search: [Google]

24KB, 677x343px

>>51490365
uhh...

File: nise.jpg (108KB, 1280x720px) Image search: [Google]

108KB, 1280x720px

>>51487522
/ipfs/QmUR7dx8bg3H7GRHY
jRn3UmAGyuNs2ChJRswzFeGGz3cLC

>>51490354
No matter how you look at it, an update and a new file are the same thing. With IPNS names, the original creator provides a permanent name to access a resource. To update where that permanent link points, one uses ipfs name publish <hash to publish> <key to publish to>. For now, <key to publish to> isn't supported and will be your node's key by default, though.
Whether a file is replaced or "updated", the entire hash changes because that's how hashes work.

It's gitlike in that sense, since only the original uploader can decide what's the canonical next version. However, any version can be pinned by anyone. If someday someone decides the new version of the content is shit, they don't need to pin the new version of the content on behalf of the uploader, they can also assign a new dynamic name to the version they prefer as if it were a git fork.

>>51490404
Open a new terminal window.

>>51490429
tricky shit. thanks for that insight.

>>51490354
>how would you see the version history
You can't at the moment, but I remember reading something about plans to add such a feature a while ago.

>is the original uploader the only one who can create new versions?
>is the original uploader like the maintainer of his file
To add to what >>51490429 said: Anyone can release new versions or update it however they want. But all users can create a signature for any file, but the signature is unique to your node. You would then give out this signed address to anyone who would be interested in your newest version of the file. They can then be certain that the file originated with you (or that you vouch for it in some way, at least). These signature files also happen to me mutable, so you could update them to point to another file (e.g. a later version) and your peers would see your new version instantly.

>>51490625
You can see the version history in the sense that you can keep a record of versions accessed through an ipns name, for instance.