/tech/ - Technology★

>Thread #3

Fuck you faggot OP

Newfags shouldn't create threads.

>>983928

t. actual retard until your third line

>>983929

Fork when?

I'll delete this thread if negative pressure ramps up in this thread. >>>/ipfs/

>>983930

>I'll delete this thread

Ooops I'm unable to delete the whole thread

Again:

>>>/ipfs/

>>983932

Fuck off, Either you stick with IPFS, or we will turn this car around for Beaker/Dat

https://beakerbrowser.com/ https://datproject.org

>>983973

>implying both of them do not have CoCks

What about making your own alternative?

>>983932

>>983930

IPFS threads are fine. I was calling you out for being a filthy newfag because you continued the gay numbering of threads started by the last faggot cuckchan OP. We've had perpetual IPFS threads for over 4 years. We don't number threads.

>>984128

Why the hell is your old ass windows install not airgapped?

>>984179

Nobody will listen to 8chan... unless it is QAnon, in that case fake and gay

I would rather hope that we can fork all the source code and integrate it into our stuff

>>984194

Numbering threads is a tradition (see Gamergate and /pol/ threads about Happenings)

>>984194

>newfag

NOT AN ARGUMENT

>the last faggot cuckchan OP

Then invite him back here for and tell him why

>We don't number threads.

The next threads will no longer be numbered, hopefully.

>>984232

See >>984228

>>985209

<reading comprehension

Just ignore the autistic shitposting this thread started with.

>>984222

I'm a poor fag with limited hardware. My rig is so old even just browsing the chans can result in freezing. It even has problems on threads with >600 posts or >300 files, to speak nothing of anything more resource intense like even vidya from the 90s, often the results in full blown overheating in <30 mins.

>>987060

Why don't you use GNU/Linux or BSD on such a weak system?

>>987341

You could just install gentoo with a ntfs drive and then run the program in wine.

>>987348

For what ever reason it's not within the wine db.

>>987351

That doesn't stop you from doing it though. Just run it in wine with a ntfs drive and then see if it works. Considering how simple, and old, it is you should be able to run it just fine.

>>987341

man locate

it's called IPFS because even FTP over moon-bounce amateur radio outperforms it

Bump because the (((distributed web))) is getting BTFO

>>987731

Holy shit, fucking savage!

>>987887

>>987731

> Trusting (((the cloud)))

Are you scared of P2P, Moshe? What, Torrents destroyed your business plan?

To all the bluepilled autists who still foolishly have hope in decentralization, read this thread

>>988725

Seems to be a lot of shilling in this thread. Let's clean it up with some good news!

https://www.youtube.com/watch?v=xzYEjHER6x4

The increasing pushback only tells me that this thing is becoming more and more sane as an alternative to paying Shlomo Shecklestein to host your data for you.

>No goy stop hosting things for free! My cousin Marty Rothenberg will only charge you $20 per GB, that's only as much as half a cup of coffee for *100% guaranteed uptime!

*up to 100%, terms and conditions may apply, we reserve the right to remove content at any time. Content hosted in our BaseMentTech™ datacenters are only allowed to be accessed in select geographical regions

WikiLeaks is experimenting with hosting via IPFS

https://mobile.twitter.com/wikileaks/status/1050445287322505226

Google intends to add dweb, ipfs, and other protocols to Chrome

https://groups.google.com/a/chromium.org/forum/m/?_escaped_fragment_=msg%2Fblink-dev%2F29sFh4tTdcs%2FK4XroilVBAAJ

>>988809

Guess we'll just do nothing then.

>>988809

Hi FBI

>>989448

Hi Mossad

>>988994

Whitepill

>>989350

glow in the darkpill

>>989985

Hi KGB

>>989986

FUCKING THIS

(((IPFS))) BTFO. We're literally stuck with Jewgle forever.

>>990026

Daily reminder that IPFS users never stop winning.

https://twitter.com/VictorBjelkholm/status/1038050005637050368

IPFS Weekly #15

https://blog.ipfs.io/49-ipfs-weekly-15/

>>990134

It is time for us to glow

To destroy (((that fucking show)))

https://www.youtube.com/watch?v=dX3k_QDnzHE

https://www.youtube.com/watch?v=DJQQrjVmQG0

IPFS Simply explained

https://achainofblocks.com/2018/10/05/ipfs-interplanetary-file-system-simply-explained/

Is anyone building an IPFS Nyaa?

>>983973

Dat looks good, too.

Is this real or another sketchy CIA trap like that stream alternative shilled by 4chan's /g/ a couple months ago?

>>987341

Have you tried https://duckduckgo.com/?q="Everything+Search"+linux

>>993682

> sketchy CIA trap like that stream alternative

never heard of this. give link?

either way this is a real open source project, many companies are starting to adopt it as well

IPFS v0.4.18 Is Out

This is a really big update.

>experimental support for the QUIC protocol. QUIC is a new UDP-based network transport that solves many of the long standing issues with TCP

>now supports the gossipsub routing algorithm (significantly more efficient than the current floodsub routing algorithm) and message signing

>the new `ipfs cid` command allows users to both inspect CIDs and convert them between various formats and versions

>the refactored `ipfs p2p` command allows forwarding TCP streams through two IPFS nodes from one host to another. It's ssh -L but for IPFS

>there is now a new flag for `ipfs name resolve` - `--stream`. When the command is invoked with the flag set, it will start returning results as soon as they are discovered in the DHT and other routing mechanisms

>Finally, in the previous release, we added support for extracting blocks inlined into CIDs. In this release, we've added support for creating these CIDs. You can now run ipfs add with the --inline flag to inline blocks less than or equal to 32 bytes in length into a CID, instead of writing an actual block

>you can now publish and resolve paths with namespaces other than /ipns and /ipfs through IPNS. Critically, IPNS can now be used with IPLD paths (paths starting with /ipld)

>this release includes the shiny updated webui

>this release includes some significant performance improvements, both in terms of resource utilization and speed

>In this release, we've (a) fixed a slow memory leak in libp2p and (b) significantly reduced the allocation load. Together, these should improve both memory and CPU usage

>we now store CIDs encode as strings, instead of decoded in structs (behind pointers). In addition to being more compact, our Cid type is now a valid map key so we no longer have to encode CIDs every time we want to use them in a map/set

>bitswap will now pack multiple small blocks into a single message

>this release saw yet another commands-library refactor, work towards the CoreAPI, and the first step towards reliable base32 CID support

>CoreAPI is a new way to interact with IPFS from Go. While it's still not final, most things you can do via the CLI or HTTP interfaces, can now be done through the new API

>from now on paths prefixed with /ipld/ will always use IPLD link traversal and /ipfs/ will use unixfs path resolver, which takes things like sharding into account

>we intend to switch IPFS gateway links https://ipfs.io/ipfs/CID to to https://CID.ipfs.dweb.link

>this way, the CID will be a part of the "origin" so each IPFS website will get a separate security origin

https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md

>>993848

Steemit/Bitchute is not CIA, just shekel grubbing.

Neither is GitGud.tv, just GaymerGayte

>>993887

>QUIC

>ipfs p2p

>ipfs name resolve --stream

>performance patches

>all this browser standards stuff

I like it.

Does /g/ even use this? How safe is it? Are files encrypted and anonymous?

>>998746

>/g/

I dunno, why don't you ask them?

>anonymous

If they add I2P support, sure. In the meantime tracking peers is as easy as bittorrent.

>>983922 (OP)

>(though it's not recommended unless the file has a lot of seeds)

So same as torrents then? popcorn time for ipfs when?

>Is it a meme?

What are some use-case scenarios besides replacing torrents? hosting websites? storage? can compete against datacenters in terms of cost?

>>999838

I don't think it is fit for any useful storage except archiving, as (as far as I know) there exists no deletion or edit function, and the system tries to bloat itself forever.

I'd rather rent anonymous decentralised storage for money, with the bonus that I have a guarantee that the files will not just be lost, and that I can edit / remove my files. Also, there is litterally no incentive for nodes to participate in IPFS, so you can expect most nodes to actually come from the NSA for surveillance purposes.

>>1000049

This is not to shill any cryptocurrencies that rent storage, because they are mostly shit, from a technological point of view.

>>983922 (OP)

I just installed IPFS. I have not downloaded anything and it has used 700 megabytes in less than 25 minutes. This is retarded.

>>1000049

>>1000065

>edit function

Use IPNS, faggot

>deletion

If you upload files to a distributed storage system and expect some way to magically delete the file from all the seeders' computers and prevent them from reuploading the file with the same hash, congratulations: you're retarded.

>>1000218

Filecoin vs Stroj vs Sia vs Maidsafe

>>1000218

>Are you talking about 700 megabytes of bandwidth?

Yes. And it is still going all these hours later. Not as much but still a lot. High idle bandwidth usage has been listed as an issue for years now and it is still shit.

>>1000460

>Until it's fixed you could try

Well anon knowing IPFS it will be a decade until it is ready.

Don't bother. IPFS has been considered useless to those who truly know what is actually going to happen.

Read >>997341 for example. More and more people here are taking the blackpill and accepting that nothing we do will make us able to escape the eternal kikery.

Don't bother fighting back anymore. You will either take it up the ass like the rest of us, or take your own life. We lost. We're done forever.

>>1004430

With some normalfag-friendly application or web UI, you could boil it down to "log in with your key, then write a post/attach files and upload." Popular content would load faster as more people view and reblog it, and you wouldn't be limited to a centralized, proprietary platform's whims.

The big disadvantage to this over Tumblr and other blogging platforms is the lack of a search function or asks. This does mean pedophiles couldn't flood service-wide tags or search terms with CP, but it would make finding blogs outside word of mouth or a future IPFS search engine harder. It would also eat up precious data for phoneniggers and other burgers stuck with data caps.

>>1004430

>ipfs displaces torrents as an easy means of redistributing content.

Why?

>I changed a letter in one of my filenames so now there's two separate swarms of seeders" retardation needs to stop

And how is IPFS going to fix this?

On bittorrent I just update my RSS feed and let my followers update. The RSS article is OStatus compliant, so it's self-contained, containing multiple checksums and signature.

*Nix, do simple things well.

>>1004446

You just described Scuttlebutt.

>>1004465

>And how is IPFS going to fix this?

Read the OP, faggot. IPFS really, really hates file duplication and changing filenames doesn't change file hashes.

>Scuttlebutt

I'll look into this.

>>1004476

I read IPFS Golang, and JavaShit. It's kike software.

They have no solutions, only begging implementations.

I'm not sure how ANSI C code in libtorrent can beat Google Spysoft.

>>1004529

/thread

>>1004465

>and let my followers update

Swarm deduplication should be automated in the standard by default, not left up to clients to implement (or not), like in the case of Bittorrent.

Going through the trouble to automate 90% of the work seems like a waste of time when you can just have it 100% automated in the majority of the network rather than the minority.

There's no circumstance where it makes sense not to do this. If you're trying to get a hash, why care where it comes from as long as it's valid?

If you're publishing data, the intent is already to share the data with random peers.

>>984128

>a gui

https://github.com/ipfs/go-ipfs/issues/5003

Like this or do you mean something else?

>>1004529

Why not separate the specifications from the implementations?

There's multiple implementations on github that are written in C. You could probably re-use a lot of existing libraries because of how they separate systems >>1000218

This is like people claiming i2p is somehow bad because the reference implementation is in Java. Despite a functioning C++ varient also existing.

You'd better spend your time writing the implementations you want, rather than complaining about the ones you dislike. The specifications are there. The designs are already done and you have multiple reference implementations.

You're not a nodev are you?

>>1004446

>With some normalfag-friendly application or web UI, you could boil it down to "log in with your key, then write a post/attach files and upload."

This looks like it might be that

https://github.com/Peergos/Peergos

>>1004430

>All the different chunking options give me pause though, as they have the same effect.

Thankfully the default is a fixed size and not "auto" like in most torrent clients, so it shouldn't be an issue unless people intentionally change the chunking method when adding files.

>>1004529

>>1004647

https://github.com/Agorise/c-ipfs

https://github.com/chronaeon/c-ipfs

https://github.com/bitshares-munich/c-ipfs

Pick your poison

This TBH https://github.com/ipfs/py-ipfs

>>1004647

>should be automated

Ah, you have no respect for security or privacy.

>you can just have it 100% automated in the majority of the network

Seems you've never installed your own tracker.

>This is like people claiming

I don't sell projector screens.

>You're not a nodev

What's your github account? I don't use Social Networks, esp. Microsoft ones.

>>1004673

I'm fine https://www.libtorrent.org/projects.html

>>1004680

Sell me IPFS when we're making history:

https://en.wikipedia.org/wiki/Named_data_networking

>>1004807

I get the impression you're being insincere for the sake of attention and are not actually interested in discussing this. Maybe you should use social media instead of trying to do that here. Or try /g/.

>>1004872

Renaming a file*

>>1004872

Full automation: misleading bit, download the whole repo.

You want semi automation, the more you can control the better, even if it runs mostly by itself.

>>1004913

>Security is completely irrelevant

Yeah, I concluded from you as much.

>except automated.

A windmill is also automated. Does it work like a windmill?

Does it not need my intervention if I made the typo?

>trackers even have to do with [Automation]

A lot. It's what you are claiming trackers don't have: a way to publish updates, even for typos.

>actual implementations for a lot of these concepts

We have prototypes, empirical evidence, and scientists working on this. Not hobbyists that wrote a thesis paper.

http://named-data.net

http://www.named-function.net

>IPFS developers would need to do

Nodev, got it.

>some research project that hasn't yielded anything

It's ok to ignore the 10 years worth of work in CCN, and working implementations.

Reminds me ZeroCoin.

>1 program handle all my hashes/magnets

Be sure to run it in ring 0, so you can't expect any breaches.

This is the systemd of statements.

>What's so great about NDN and why should I wait more decades for it when this exists today?

The same question Linux have in Desktop adoption, and display server support: lack of support.

Bittorrent works here and now, and a proven solid track record, while IPFS still begs to complete it's not so sound ideals.

It's snake oil, and you don't even see it.

>>1004924

IPFS already has the openBazaar fork with TOR/I2P but it has not been mainlined as the development is slow as shit.

>>1004807

> Libtorrent has no de-dup function

> Shilling NDN, which is in a worse state than IPFS and Dat Protocol

>>1004925

>Shilling

Yeah, that's what I thought of IPFS when it was announced, and thanks to you, even more refined.

Anything IPFS says it wants to do, Bittorrent software already provides, and more.

But we're done with conversation Nodev.

In the next ten years, we'll see Bittorrents on post quantum crypto, making it impossible to spy and tamper, unneeding TOR & I2P.

>>1004934

> we'll see Bittorrents on post quantum crypto, making it impossible to spy and tamper, unneeding TOR & I2P.

Well you are now the nodev.

>#3

you're missing a couple of zeros

>>983922 (OP)

>integration with TOR

Doesn't tor get slow when people torrent over it? How would this even be implemented?

So this currently isn't released yet, but look at what they have planned for v0.34 js-ipfs. The ">" indicates a check, while the "<" indicates no check.

https://github.com/ipfs/js-ipfs/issues/1721

>Refactor files API

>Upgrade to latest ipld-dag-pb

>Refactor Object API

<--cid-base option

<CID version agnostic get and #1757

<DHT

>IPNS over pubsub

>IPNS over DHT

<addFromURL, addFromStream, addFromFs

>Support for HAMT directories in MFS

The DHT isn't completed yet, but if you check on this thread [https://github.com/ipfs/js-ipfs/pull/856] there's only two things left to do.

>>1007342

So when the DHT Implementation is complete, does that mean JS-IPFS and Go-IPFS can finally pull data from each other?

>>1007342

you forgot the nocopy bug

IPFS is bloat, just use DHT+bittorrent

>>1007413

Fuck off, IPFS' main draw is its per-file deduplication autism and bittorrent doesn't have that. You might as well call bittorrent bloat and tell everyone to use FTP.

>>1007465

>per-file deduplication

solved by dht

>You might as well call bittorrent bloat

bittorrent solves a problem, ipfs does not

>>1007497

>the entirety of ipfs could be duplicated using bittorrent and symlinks

Nice work guys

>>1007413

SHA1 is broken though

>>1007499

So just track each file separately and have the client bundle together related files? Bittorrent can do it

>>1007501

It's much easier to have bittorrent clients optionally upgrade to sha256 than it is to try and create a whole new network

>>1007504

Those are extraordinarily trivial problems which could be solved in a bittorrent client, you don't need a new fucking network for that

>>1007507

Also, the

>you don't need a new fucking network for that

excuse is like shitters insisting on using HTTP for fucking everything even if it doesn't fit their use case. To make the existing bittorrent network work like IPFS would create an ungodly mess which takes away bittorrent's existing perks so it can ape another protocol.

>>1007508

>a torrent of torrents

>one text file in the top-level torrent lays out the folder heirarchy and location for all the other torrents included in the bundle

There we go, took me 30 seconds and I just implemented IPFS in bittorrent+DHT

>>1007510

And how would you replicate IPNS, oh wise perverter of bittorrent?

>>1007498

>symlinks

What if you torrent some music, and you want to change tags? Now the whole file is different and you can't seed it anymore.

>>1007510

The multitorrent clusterfuck still breaks if someone renames a file or changes music tags as >>1007512 suggested.

>>1007511

I've got no idea what that is

>>1007512

>>1007513

IPFS is file-addressed, that breaks IPFS too

>>1007515

You can't seed to a swarm if you've modified your files, that's literally impossible. If you're talking about something to do with IPNS, maybe that's revolutionary technology, but as for IPFS itself there's nothing in it that can't be done with bittorrent

>>1007502

> It's much easier to have bittorrent clients optionally upgrade to sha256 than it is to try and create a whole new network

This will never happen. I had this conversation back when shattered happened and nothing has changed since.

The only way to unfuck bittorrent is by abandonding it and creating something better.

>>1007539

I'm not even going to read that, your proposition that you can seed into the same swarm with different files is absurd

>>1007543

How is it? If there's a document originator, he just announces that there was a change and others download the changes.

>>1007543

>he thinks metadata == file contents

Nigger, with a decent hashing system the file's hash doesn't change if you tweak the filename, timestamp, or other metadata. It's the same fucking file with different metadata so even if some other asshole changed his file's name, you can still peer with him because the hash and file contents are the same.

>>1007546

>>1007547

This whole discussion is pedantic as fuck and worthless but this entire thread started >>1007512 with some downloader changing id3 tags in his music. That changes the hash, and creates a new swarm. Regardless, from the link provided, do versioned files even work yet? The issue linked to from the medium post https://github.com/ipfs/notes/issues/23 is over three years old and still open. The only interesting part of this whole project seems to be IPNS. I will read into it some, but from what I've seen of IPFS, I find it hard to believe that IPNS is not some silicon valley-tier rebranding of a preexisting technology

>>1007558

Anon's id3 tags example is silly and likely wouldn't work, but changing filenames, timestamps, and similar metadata does not change the hash in IPFS or create a new swarm. Combine that with the ability to peer with those seeding a different folder with some shared files, and you have some interesting significant advantages over bittorrent when it comes to actually keeping torrents alive.

>>1007558

>>1007562

>versioned files

I don't remember that going anywhere.

>>1007407

I think so. They say this in the dht section

>It allows your IPFS node to find peers and content way more easily and it has full interop with Go IPFS nodes so y'all have the full IPFS network at your fingertips

I think before, you'd have to have an ipfs-go node set up a websocket connection in order to interact with one using js-ipfs. And since there wasn't a dht you couldn't really download content without knowing a peer that contained the content (could be wrong).

>>1007409

Not sure what that is. Don't see anything recent related to it for js-ipfs.

>>1007577

nocopy is a ipfs-go bug, search it in the issues page.

>>1007507

>I see what you're saying, and I agree it could be done. I also recognize that this is not standard for BT. However, I still don't see the need for someone to make a protocol where this desirable feature is standard, when we could just stick with the existing protocol and make unofficial extensions that will only ever have azureus users connected because people insist on using minimal and or outdated clients with a subset of modern features

why nigga

How isn't moving to a format and network that has these things considered in the standard, a better solution?

There isn't even a migration path. You literally just add the directories that have your seeding content in it, and you're done. Migration complete, and if everyone did this all the swarms would merge.

Now think of how bad it is moving from 1 bittorrent client to another.

>oh man macroTurret just came out and it has this feature I want but my client doesn't have, I'll just migrate from 1 non-standard to another easily!

It's ASS.

>>1007514

>IPFS is file-addressed

IPFS is content addressed, that's the entire advantage. Any named content you see is metadata that's part of the node.

Notice that "Hash:" value is different to the object I'm requesting. The one I'm requesting contains the metadata and a reference to the actual data. Like a real networked filesystem, it seperates metadata from data, but guess what, metadata is also just data and you can content address it too.

Bittorrent can't compete with this, the transfers may as well be fire and forget. Unless you absolutely never modify the content, or meticulously manage it yourself. Why would anyone want to bother with this when it can just be automated and built in.

The absurd amount of dead torrent files that are basically duplicates with an additional text file, needs to stop.

>>1007543

>your proposition that you can seed into the same swarm with different files is absurd

Do you not understand how chunking works?

If you add a file, you chunk it and save the chunks, if you modify it and add it again, there's going to be duplicate blocks for the majority of the file or tree. The only thing you have to store to have 100% availability for both copies, is the difference between them. The duplicate blocks take up the same space, and the delta takes another space.

Read this

https://en.wikipedia.org/wiki/Data_deduplication

it's not a new concept, and everyone goes apeshit about ZFS for having it.

What if you could have that, but for network transfers too?

Why not use a tool that's more efficient with storage and bandwidth, for data transfers?

HTTP and BT need to be deprecated.

>>1007562

>Anon's id3 tags example is silly and likely wouldn't work

You could implement the MP3 format in the same way files are implemented.

Since ID3 is just metadata, you could literally just extend regular files to have fields like Artist, CoverArt, etc. and the Data field point to an audio stream or another container.

If that was done the blocks would be separated and the data stream would always have the same hash/swarm. Since metadata is so small compared to an entire extra copy, it's likely people would seed the original anyway since it would be the difference of a few bytes, not a few MB.

You could setup something to like output this ipfs mp3-object in whatever format like json and that would be really easy to support.

`ipfs object get hash ----encoding=json,` would give you the metadata with a link to the data.

Which seems really easy to add support for compared to other shit media players support. Like RTMP, DASH, etc.

>>1007895

I'm not 100% sure but I think that's how this works.

https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#directory-sharding--hamt

>>1007900

>instead of just extending bittorrent to do what I want, I'll implement my own standard from scratch

The absolute state of /tech/, lapping up this silicon valley shitware

>>1007751

It breaks the file folder and file hashes on the macro scale, but not the data chunk hashes or hashes of the other files in the micro scale.

>>1007955

The original hashes don't break. The new hash is different but the old hash will continue to work.

When you change the metadata you're only adding those changes, so the original will still work as long as the metadata and data blocks are available.

It's only a few bytes so there's no reason not to just keep the original pinned as well as your modified copy if you're worried about permenance.

Look here >>1007901

you basically are just changing this struct for directories that changed and these are tiny, even when you include upwards recursion on parent directories.

Anyone that lists the index is mirroring the metadata themselves until their next gc too, so even if you delete the original metadata, people can still retrieve the index from someone who has it, while retrieving the main data blocks from you.

You don't store 2 full copies of a file, to provide 2 full copies. You only need to know which blocks are in common and which are not.

But in any case changing something never breaks the original.

Just like how if you make a new magnet link the old one still works as long as people still have the data, but the issue here is that magnets will only download from peers of the same swarm which is only the people with the exact same metadata/torrent file. IPFS simply doesn't have this restriction, you can get any data from any peer, and in theory over any network they add support for, which will include bittorrent itself at some point.

If this happens you could not only swarm merge in the same network, but across networks too. So you could download X% from ipfs peers and Y% from bittorent peers for the same content.

You'd have to know the hashes for both networks, but this is how in-network swarm merging already works.

And the magnet link format already allows you to specify hashes for bittorrent, gnutella, ed2k, and probably more so you could just post shit like this.

magnet:ipfs-hash;bt-hash;http-backup-location

and feed it to a single client and let it sort it out.

As it should be imo. Let the download manager manage the downloads and figure out where the data is and how to get it. I shouldn't have to know ANY of this bullshit but I do because it's all terrible.

>>1008063

>You don't store 2 full copies of a file, to provide 2 full copies.

This is important. I only know of 1 BitTorrent client that does swarm merging and it forces you to make duplicate files on disk.

https://github.com/BiglySoftware/BiglyBT/wiki/Swarm-Merging

I must have hundreds of gigabytes of duplicate data in different temeporary directories (to avoid name conflicts) from the manual merging process of multiple seedless torrents.

My options are to

- manually find and delete duplicates, removing myself as a seeder which is bad for the network

- symlink the files myself by hand, still leaving me the problem of storing them in a unique directory and spending time on it

- waste disk space keeping the duplicates. Which is not efficient.

I'd rather the filesystem take care of this for me, and IPFS does.

>You act like just because something already exists that we can't replace it with something better.

>That's not how this has ever worked.

>Did you forget how we got here in the first place? Should I send you the rest of this post via an ed2k link?

Well.. you are right something always replace the old shit.

However! You have it all backwards. ED2K is better than Bittorrent and Bittorrent is better than IPFS. Bittorrent still haven't caught up with the capabilities of ED2K/Kad. It was fun to watch the development.

Bittorrent now has PEX!

err.. come on granpa.. been having that shit forever.

Bittorrent now has DHT!

phew.. cool so that's what you call your Kad implementation.

Bittorrent has.. well still does not have distributed file search..

Ha! Move along fucker. The donkey has been stale for a decade and you still can't keep up.

IPFS.. hmm.. you have TOOLS to mount it and an HTTP proxy. Also some sort of revision system? Wow. Tell me more. Oh, no wait I think even bittorent built git over torrent. Hell the donkey even pioneered using your fucking DAG for error correction.

Tech is dead. Showmanship isn't.

Donkey is king.

>>1008554

I'm too young to remember edonkey, but why did it die? If you were to build a new filesharing application today would you use ed2k?

>>1008554

I'm not sure how old are you but if you're past your 30s you shouldn't even need to think why encompassing solutions are always preferred in the long run. Nobody likes to deal with abstraction layers.

Who did this?

https://vitriol.co

>>1009028

you did, faggot

>>Is it a meme?

>You be the judge.

<go

<JS

<thinks they are the only content addressable storage

i have judged

>>983922 (OP)

N00b question.

I've installed ipfs. I can launch it via command line / terminal on different operating systems, etc.

So, how the fuck do I find anything worthwhile on it?

It's not like I can go to a search engine and type in something_cool.zip and it take me to it on IPFS.

I can load my own shit up in it, and see the hash, etc, but I want to access other people's cool shit, not just shit I've created.

https://vulpine.club/users/DJWalnut/statuses/101253610548868742

>>1010220

>The Vulpine Club is a friendly and welcoming community of foxes and their associates, friends, and fans! =^^=

What point are you trying to make by linking a random conversation on furry twitter? Is this spam?

https://mastodon.ar.al/users/aral/statuses/101247284978291769

>>1010493

> my unpopular program is much better because they get money a different way and are licensed differently

if dat's so good, why didn't it get as popular or as wide-spread as IPFS?

> inb4 muh VCs influence

fuck off. you should know that dat is BSD licenced, compared to IPFS's MIT license, something free software respecting

>>1010493

>random masodong namefag

Fuck off.

>>1010556

>if dat's so good, why didn't it get as popular or as wide-spread as IPFS?

Dat is closer to a bittorrent replacement with a built-in VCS for updating your torrent. It lacks IPFS' deduplication autism, aka the reason most people are interested in IPFS in the first place, so many of IPFS' more interesting implications and uses flat out wouldn't work on Dat.

>>1010493

>Exactly, but it changes the fact that if we use it and collaborate on its ecosystem we make easier for them to continue with their business model.

If there are other alternatives, it's better to focus on them instead of in VC funded software.

>IPFS is always going to be able to copy what we do, but they will need to put some effort on that, instead of using us as free labor.

I'm really surprised to see someone post something like this openly from a mastadon person.

Is this not just intentionally being spiteful to a software project solely because you don't like the people who make it. And you don't like those people because they have funds and are partnering with other funded software projects who also release free software and services?

How is this going to help mastadon users or anyone for that matter?

Not adopting a platform that you admit is likely to become dominant, because the developers get paid.

Nobody complains about this for any other open source software project that I know of.

The main argument BSD users like to throw around is that FreeBSD developers get full time salary from Apple and Sony. They treat it as a good thing and I don't see how it could be anything else.

Literally what's the fear? I'd much much much rather use software from someone who is getting paid than from someone who has to be supported some other way. Probably though ads or selling user data.

If protocol labs wants to trick /biz/ out of their money with cryptomemes why should I even care if I get distributed anime pictures as a result?

Who loses?

Would people use an IPFS tracker that functions like a Bittorrent tracker? It would periodically keep track of how many online people have pinned specific file hashes. To simplify things it would recursively keep track of items in subdirectories of a given hash directory. It wouldn't keep track of directories directly. Users could recursively query directories so a client could easily summarize the seeders count for each subdirectory and each individual file.

I try to upload and then it says

Error: read tcp 127.0.0.1:50383->127.0.0.1:5001: use of closed network connection

What does this mean?

>>1011728

>an IPFS tracker that functions like a Bittorrent tracker

Something like https://github.com/DistributedMemetics/DM/issues/2 ?

>>1011735

No not an indexer I already talked to him/you I mean like a bittorrent tracker in how it keeps track of available peers and seeders for a specific torrent. It would let people know the minimum amount of online seeders available for files on IPFS.

>>1011745

What would this provide over the DHT? If you're just wanting to find how many people have a file, you can already do that with `ipfs dht findprovs <hash>`.

Note that there is no way to know if someone has pinned a file or just has it in their cache.

>>1011757

Wow the DTH got a lot faster. I got results in 3 minutes compared to over 10 minutes last time I tried that last year. As you said, it would be a more conservative but reliable number since it would only include people who have actually pinned the file in question. I figured instead of people waiting for DHT results they could query the tracker database instead. And no, I wouldn't want to cache the DHT results since it includes files in people's file cache which is unreliable.

https://github.com/libp2p/js-libp2p-websockets/issues/74

Just in case any JShitters like me are having trouble connecting web peers check above.

>>1018673

I don't mind it not having Tor support, but I2P would be nice.

>manbaby

Maternal insults are lame.

>>1018587

https://github.com/RTradeLtd/Temporal already made it

>>1018679

>Maternal insults are lame.

Does "immature" fall under this? "arrogant" seems appropriate. I stand by what I said though, it's childish behavior.

>I don't mind it not having Tor support, but I2P would be nice.

Sorry, I got off topic.

It just makes me mad that Tor users are already seen as criminals and pedophiles, and then we have people like this trying to push the project on top of that. It doesn't seem helpful. Although my complaints aren't either.

I would like to see these integrated but I'm not in any rush for it either. To me it doesn't matter if they support it if they can't guarantee anonymity yet. But I don't see what that dev is complaining about since if you don't have this opinion, you can still use it today. And apparently multiple projects and people do.

>>1018738

Neat.

>>1018851

>It just makes me mad that Tor users are already seen as criminals and pedophiles

Because the TOR devs are a bunch of fags who deserve no sympathy https://twitter.com/torproject/status/898256109789687808

more evidence for IPFS+I2P, not BitTorrent+TOR

>>1021117

>Because the TOR devs are a bunch of fags who deserve no sympathy

Their work in favor of privacy is unmatched and that alone deserves sympathy.

A dumb opinion doesn't undo it all, especially as they don't act on it.

>>1021392

Loads fine for me. Maybe you are being too conservative for your security settings.

>>1021394

Could someone be trying man-in-the-middle me?

>>1021396

You may have wrong date settings. Check out whether the date on your computer is accurate.

Somebody tell me if this shit will do anything resembling a normal file system, or is everything just an object because some developer was weaned off his moms tit on Java and Soy.

And yes, yes, I have read the fucking docs. They were written by someone who wears a pussyhat.

>>1021728

based

>>1021728

>on Java

Object doesn't have to refer to objects from OOP.

>>998765

ipfs is not meant to be anonymous, it uses DHT essentially and nodes are essentially broadcast. What it /is/ useful for is to make it hard to censor the content since that would require taking down all the bootstrap servers (which you can patch with your own) and the clients that host the content.

To anonymize it you simply need to tunnel the traffic over a network interface (actual or virtual) that is secured.

>>1021822

Lets not also mention that he doesn't know what a merkledag data structure is. Doesn't know that its also used to de-duplicate content and optimize for speed.

>>1021960

>it is meant to be insecure

Ok. Into the garbage it goes.

>>983929

>We are committed to providing a friendly, safe and welcoming environment for all, regardless of gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics.

>see the hangout mettings between the devs

>literally nothing but white guys, no wimminz, kangz, nothing

>all this shit to appease faggots who dont even contribute to this

WEW

>>1018673

Ever since tor started with muhnatzees I been suspicious that they might have been compromised

>>1022536

Software project constantly get into trouble for not having a so-called code of conduct in their repositories, so adding one could be merely a preventative measure. At worst, it's virtue signaling. You probably shouldn't let it bother you, although, if IPFS gets really big and starts being used at a massive scale the above-mentioned cock will likely be used by yids to purge bad goyim from the development team and install their own actors, similar to what's happening with Linux recently.

>>1022549

What happened to just telling annoying faggots to fuck off?

>>1021962

This is the laziest argument I've ever heard on tech, this is worse than "install gentoo" or "delete system32", seriously, get off the motherfucking soy you fucking faggot.

>>1022647

>getting mad because you're stupid

lmao

>>1022588

Defamation, blackmail, and rape allegations happened.

This thread has devolved into bickering about nonsense. I suggest we make an IPFS board. When was the last time any of you even shared something over it? I was trying but the file size of my file I was trying to upload crashed my net.

Keep linking shit and stop arguing over nonsense. Its not meant to be anymous, dumbasses. The CoC is pointless toosince the only people using it and programming it are whites.

>>1022892

There's already >>>/ipfs/ . We used to have more sharing before /tech/ went to shit through cuckchan newfags and the mods not giving a shit.

>>1022536

>>1022892

Delete this before the bright hairs find out.

>>1022896

We don't need a whole board for this. /v/ has a constant "share thread" where it's not bound by the protocol or distribution method. The post ipfs hashes, magnet links, mega urls, vola rooms, and other things.

Someone could start one here if the board owner would allow it. But I'm not sure what kind of stuff /tech/ would even (want to) share.

>>>/v/15953491

>>1023813

IPFS+I2P through the Temporal project

Is there any distributed imageboard being currently worked on? What's your take on proof of human work blockchain? Captcha puzzles are generated collaboratively between recent miners and none of them know the solution

https://eprint.iacr.org/2018/722.pdf

https://eprint.iacr.org/2011/535.pdf

The first paper suggests rewarding betrayal to prevent collusion between capatcha generators, thus involving currency. This is also an incentive to mine to prevent attackers from taking over. There must be a way, it could be fun to watch anime directly on anon post.

>>1025320

Distributed =/= decentralized in terms of software development/engineering.

Polite sage.

>>1025657

>I want to see a digital world where only the people who generate hentai@home credit can post on my website

How would you implement this using IPFS and Ethereum/Tron/Neo/Cardano/Eos/Stellar/Iota/etc... (smart contracts)? Asking for >>>/hydrus/ (to create a social network seeding/tagging layer on top of it)

>>1025723

For reference https://bitcoinexchangeguide.com/neo-vs-eos-vs-trx-tron-vs-xlm-stellar-vs-ada-cardano-altcoin-battle/

Some ideas:

1. Those who seeds more have more rights in downloading materials they like, similar to private trackers and Sia/Storj/Filecoin/Maidsafe/etc. storage tokens

2. Those who tags more may or may not be genuine (e.g. tag trolls, tag bots), with or without incentives, thus we need an overseer to make sure the tags are good

3. Tying #1 and #2 together may not be a good idea, as seeders could also be a tag abuser, or worse use tag bots to rig the system and gain dominance

4. To fix #2, those who engage in the community with tagging should have the most power, but we must create a consensus system for a Steem-esque "proof of collaboration"

>>1025764

Some ideas regarding voting https://en.wikipedia.org/wiki/Penrose_square_root_law https://en.wikipedia.org/wiki/Jagiellonian_compromise

The power of a person's vote should be the square-root of the person's contributions.

Some problems regarding quantification of file contributions:

1. If we assume every file is created equal, does that mean a high-resolution image is the same as an emote/flag?

2. If we assume that file is ranked by its file size, people would cheat by converting low-res jpeg into png, mp3 into flac, and epub to pdf.

3. Even if we can quantify the files, how does that stop things like Waifu2x 2x upscale and SVP 60fps from slipping through the cracks?

4. If we actually use file popularity to rank file weight, then it becomes a shilling and spamming operation, how do you tag and manage them?

>>1009928

Anyone have a plain english guide on setting up "geocities pages that updated over IPNS." Because, for the personal "I'm soooo random!" website, IPNS looks tempting.

>>1025320

There are no captcha puzzles that can't be solved by AI. Human pow has no future.

>>1025893

What about faptcha?

>>1025849

You don't need a guide.

ipfs add -Q -r my_website_root | ipfs name publish

When it says "published to Qm..." this is your IPNS reference. "/ipns/Qm.../"

The apis you want to read about are

ipfs key --help
ipfs key gen --help
ipfs key list --help
ipfs name --help
ipfs name publish --help

>>1025723

I think the answer is simply "yes, smart contracts could help" at this level. The things mentioned here

>>1025764

>>1025845

should be ironed out ahead of time by the hydrus community (and/or developer).

In principle, smart contracts and blockchains allow you to emphatically claim history and truth at a global/network scale. But that's not really interesting to talk about until you know what you need to prove and how the data is generated. What "value" is, has to be defined before we can speculate how to implement it.

Then you can discuss potential exploits and how to defeat them.

I think you should start a thread there if one doesn't already exist, either way link to it here.

When it comes to auto image analysis we have lots of options today. This thread has some and there's A LOT more >>>/hydrus/1553

When the results are unsure, we can always fallback to human intervention. How those people are elected, what power they have, etc. again has to be defined in human language first.

For reputation, I guess I would look into older p2p networks that tried to have reputation systems, like ed2k/kademelia.

And I'm sure things like sybil mitigation are good to know.

https://ieeexplore.ieee.org/document/6363920

https://www.sciencedirect.com/science/article/abs/pii/S1389128615004168

If you can figure out how DHT networks work without spam killing them, you might have a basis for distributing votes, once a vote's weight and impact are defined.

Somewhat related to A3 - (bots to rig the system and gain dominance)

I wonder when the IPFS people are going to release filecoin research. If they're going to have a credit system based around hosting data, they likely have to solve a lot of these same problems. But IPFS isn't even out of alpha yet and it's been years so it might not make sense to wait for that. Then again if it's taking them years maybe it's not worth trying to solve on your own if they're going to do it for you.

At the very least they'd have to have some way to prove you're hosting and that the data you're hosting is cryptographically legit.

Helping A1 - (Those who seeds more have more rights in downloading)

Without relying on peers or trackers to be trusted.

We need to have a thread where we can dump knowledge. I'm not really strong on consesus or trust tech since I feel like it's constantly been evolving for years. But I'm wondering how other people handle this, specifically blockchains, p2p networks and even centralized systems. Like if there are boorus with points/credit systems, how they handle it, etc. How do federated platforms deal with it too, things like NNTP based services, or even modern things like Mastodon. Things like OpenBazaar might be worth investigating too.

There's also the idea of using libp2p directly to implement your own system that is decentralized in most parts but (semi-)centralized in authority.

Like distributing files via IPFS while forcing vote data to be sent to specific peerID(s) who processes it and then updates the single source of truth.

This way you don't really have to maintain your own blockchain if you don't feel like you need all the things that offers you. Like I doubt most people actually need an entire history of events versus just operating on the latest copies of something in a traditional database kind of fashion.

i.e.

>Peers a,b,c tagged files X with

This is everything the auth server needs to know and distribute, probably best on demand

versuses

>tag X was tagged y by peer a on $date -> tag count was incremented by peer b -> 3million entries...

This is not central and everyone has to have a copy of it(or its head), and they traverse it themselves to find the truth about something.

Depends on what you want and need.

If I remember correctly the former is more or less how the hydrus tag repos work already

>>1025915

Can't you just do automated image recognition?

>>>/hydrus/1553

https://trace.moe/

>>1026364

>list at least 3 options

>bias against blockchain specifically in favor of simpler approach

>this is somehow DUDE BLOCKCHAIN LMAO

Can you just not.

>>1026380

All of said options are stuffed with convoluted bullshit just so you can set up a crappier and less convenient version of something people already have. For imageboards we're better off with a hybrid solution where images and videos are served over IPFS to save server bandwidth.

>>1026394

Hydrus isn't an imageboard, it's a booru.

>a hybrid solution where images and videos are served over IPFS to save server bandwidth.

>>1026335

>Like distributing files via IPFS while forcing vote data to be sent to specific peerID(s) who processes it and then updates the single source of truth.

>>1026432

>>1026380

We need to consider WHEN simpler approaches break and WHEN blockchain breaks. To put simply, simpler approaches can't scale with user count.

No matter it is a private tracker on libp2p and IPFS, or using storage coins like Sia/Storj, or NNTP-esque solutions, we need a solution once we expand out.

>>1026385

But you can use Bitcoin SV (Satoj's Vishnu) to store data files, as big as 128 mb, forever and ever in the blockchain, for a minimal fee. Miners will be forced to keep your file around forever.

>>1027339

Absolutely.

wget the site with relatives and just ipfs add -r the files.

>>1027345

It worked. You need to add -w also.

Since its still in heavy development I'm worried about getting hit by some zero day if I were to install IPFS directly on my computer so I was thinking about ways to isolate it from the rest of my system. Using a VM should probably be enough but obviously I don't have resources to launch a VM for every other program so my next best option is probably a sandbox.

So how did you set up IPFS? Should I just install it directly on my system and live on the edge?

>>1028815

Use firejail or some unix user fuckery to sandbox it.

>>1028894

>How are you defining profit?

Gain of any kind that prolongs the service. Be it monetary or some other kind of token for distributed computation, storage, etc.

"Profit" may not be the most appropriate word here though.

>The way I solved it is...

Interesting approach.

>You just contradicted yourself

You left "but" out of the quote.

Despite the 2 being similar they are not the same, given that 1 is inherently generic (cash) while the other isn't intended to be (post token). Likewise with the other tokens. Specific vs generic.

As already mentioned, the issue that would need to be solved is some way to prevent exchange for monetary value. Potentially you could maintain a blacklist of tokens going through known fiat exchanges, but that's just cat and mouse and doesn't prevent individual private trade. As far as I can tell there's no way to handle this.

>How would the 8ch tokens be used and produced?

This was just an example, tokens could be used instead of a captcha challenge, generated through whatever hashing scheme you wish.

>a public privately permissioned blockchain solved that problem

If you can have access to an account, you can sell the access to that account. This happens a lot in video games for non-transferable items.

It only prevents the tokens from leaving the system, not people buying into the system with (preexisting) credit.

>Eventually nodes will become partitioned with some discussions only happening on a particular node

Wouldn't CRDTs resolve this?

https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type

I believe this is how people are building chat and document editing programs on top of IPFS now.

They will still diverge in the event of a large outage, but can become joined again.

Clients could have bias on this too, when a conflict was resolved, in the data it should still be in the correct order, but you could render it as if it's a post at the bottom of the thread with out of order timestamps.

I think meguca does this. Assume 2 postsers A and B

A reserves a post slot, B reserves a post slot, B submits post, A submits post. I think it renders AB until you refresh, then it would be BA. Or it might render AB with out of order timestamps. I forget. Not that the rendering of the data is worth considering before the data itself. But it seems like divergence and then (re)unification shouldn't be cause a technical or visual disaster. But I'm not very familiar with all that, so something could be problematic with what I'm saying.

>Matrix DAG

Neat. I didn't know about this. Seems like a good base if it's designed for chat in the first place.

>>1025657

>I want to see a digital world where only the people who generate hentai@home credit can post on my website.

>decide to duckduckgo hentai@home

>first result is FBI's recruit website

hmm

>>1028703

>>1028894

>>1028900

>>1028930

Just fucking work on the Grid protocol

https://github.com/thegridprotocol

>>1028994

>2011+8

>not knowing what hentai@home is

>>1029039

I wasted my time reading the docs. Looks like he's just writing his own implementation of Matrix but without domain names required and with decentralized image storage and real documentation. He said he wants Grid to be federated with Matrix. The PoW he's describing is literal proof of work. Only well thought out and well backed ideas will be considered when coding things.

I'm talking about creating something brand new. Take Matrix's DAG idea (every new message references all previous tip messages), add a configurable hashcash PoW to each message, and use a gossip protocol like in Bitcoin to create decentralized full nodes. Full nodes will determine consensus rules, just like in Bitcoin. The advantage of not having to enforce a global universal state is that each node could determine the appropriate level of PoW required to be added to their DAG. They will still propagate all messages that conform to the global consensus rules. Thus nodes that choose to enforce higher PoWs than required will be subsets of the larger global graph. Light clients connect to full nodes to view and post messages. Higher level things like client level message blacklists created by full node operators could optionally be used for further reducing spam or optionally enforcing administrative policies at a given PoW level.

>>1029249

>to achieve some sort of "soft" consensus

Each node having their own view of the network is too much of a trade off when dealing with serious monetary systems. We'll see what happens when they turn off their central coordinator.

>giving attackers the possibility to forge subtangles and manipulate the weight of older entries

In a message oriented system long subbranches aren't an issue because no message takes priority over others and relative ordering doesn't matter. A message branch is "confirmed" (added to the graph) if and when the trailing message refers to a previously known message. There is no waiting. It either is or is not valid. See my image and explanation >>1028930 for offline merging and >>1029088 for my whole idea.

>We might even set a target number of posts / seconds (preferably low, e.g. one every 10 minutes)

I also think we should have a hard cap of incoming messages per second. Not quite that low though. 8chan experiences less then 1 post per second and 4chan experiences 9-10 posts per second on average. I think matching 8chan levels is a good starting point.

>which would be automatically be adjusted according to the global hashrate

I'm not advocating for a PoW arms race like how cryptocurrencies use it. See my previous posts. I would also argue against dynamically adjusting the acceptable PoW level on the node level because as you said, attackers can always raise the difficulty high enough that no honest users can reasonably post anymore.

>Do you mind sharing more details?

Basically anonymous coins using DPoS but publicly revealing your votes doesn't compromise your or anyone else's privacy.

I WOULD upload a buch of big awesome directories, but this error keeps appearing. Asked help chat for help, only person was confused. Seems to be an error in GoLang itself. (They provided link)

https://github.com/golang/go/issues/11745

>>1029656

Independent uploads (Very inconvienent)

I physically stole these things and made copies before destroying the source. All wrapped with -w, so you should be able to see the directory names (right?)

ipfs://QmagA7ixdDe88cdyxCbZGtHfMcttrZ2sWWypgL855jCRsa

ipfs://QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn

ipfs://QmQLaJUKQ5gLJZdzrQ6faJmVsdFVH4GBBtpaoGtDeX6q4p

God damn, can't even upload small packages rn. wtf did they do?

Gonna keep trying here..

ipfs://QmUAsJPMWurh2XecDizt4ec7FETm4WJJHkACDyuRk1HPWo

ipfs://QmYU8naXg15E5nnFaogfC9a2ahnTegUe28g1gFUpVM5e8q

ipfs://QmYz7rwABzp1wKDeyGJCWs1FHgkbNcQzzrhszUTkvjMBEn

There are several directories I STILL can not upload due to this error. This annoyes me greatly. Enjoy what I did upload.

>>1029656

>Note: This is actually just a bug in error reporting. That is, go reports one error when it should be reporting another. In this case, you likely don't have read permissions on one of the files you're trying to add to ipfs.

Does it error out on the same file every time?

Fixing the issue in Go won't help, it will just make the error message what it's supposed to be. You'd still have to fix whatever is wrong with the local file. Since you can add some files but not others it's probably permissions.

You should try running

cd /where/it/is
find . -type d -exec chmod 755 {} ";"
find . -type f -exec chmod 644 {} ";"

on the directory you want to add and see if it shows any errors. If not, try adding it to IPFS again.

>>1029763

>>1029656

I forgot

chmod -R +rX directory

>>1029763

Well slap my ass and call me Judy, it worked. When I physically stole these CDs I had full intention of pirating them for free on IPFS and the like, and it's been a long while since I could attempt to.

ipfs://QmV16dyLSoBnb7JMfpy7wgHh8SLKvfSGuA9opjCeifaDY5

ipfs://QmQK4fznj8im3mxNx3bMi4eyrjka8581EHs8uy7Dedsp3w

Also, IPFS Companion for Firefox no longer exists, so I downloaded the beta channel and it doesn't work. Wat do?

>>1029833

Some misc now, also taken from physical media

ipfs://QmWQ3U5uqLTgxgt1TKJYiHesZjfKa248DsCm4qQGzUeSHw

ipfs://QmYfvxWyE81kArais9TVPe7e6bxzLaXYLEZmKi5fmud8FE

ipfs://QmR8XeoJnkAe2P1Kq5tNppHUf6Wz9GiwAvz7YNX22EQGGR

Bunch of movies I have saved to my machine

ipfs://QmXpgQDp8iDav42M5VN4wF5c354xrLiSgegYMDgboR8cxP

ipfs://QmY4UJMxkqaB4jLYGXghsQQHnYnSpcy1yfmsFFu1qYhAph

ipfs://QmeybnTMwFUsirCP6jebtGvLikJk56zTD9kyUvx8gbE7wH

ipfs://QmZfU3ybfYG8MQhNPqNYWj179EPMjoK3jR4NJacioPZHjd

ipfs://QmPRVdYh5qECazXBsqth7SbL33Wb7B9oK1jyWPakSoxEZm

ipfs://QmR6wuCjADqMQBkpLLevLAxehxPkigKDFLPf9doVDfgj61

ipfs://QmVxR78VHAZFWgU7EStGGrh2a1AkHwENjTRTRDaAHwN4SA

ipfs://Qmcp6FobaVBgNKAf88dgdL1UPEQZDnW8Um9kqA2gj4gC7m

ipfs://Qme6NYm7ny28eNLzMHJhcJvCsdgeFTCNPw2QM3DvW7UZuy

ipfs://QmVQGuymt5BLHYFgER2amm9mApdQoaiV3wDysv5vCbRbbK

ipfs://QmXtsoszmvijiRpsjHCJ1jxhaAqhQ8sXxTKdYqmgbj2WaY

ipfs://QmViWvJKsRRkT8D4ZAXpM8mvDoYGo9YmnpKFxpTbTyyo5W

ipfs://QmebWELSxDkAwyL5d19rSDZZrngWtkQzB7NAQJS6Guzk5s

ipfs://Qmd4HZJF1kaAUAeHZtpRwePM1SD2Y335fHFPGhHUTHx48F

ipfs://QmSbCFVQ6gy9gd9MmstSNnM49hRXDTUxvhhjXzJeDwCjww

This is it for now. Please mirror, enjoy, etc.

>>1029833

>IPFS Companion for Firefox no longer exists

It looks like Mozilla only removed it temporarily because the builds failed.

https://github.com/ipfs-shipyard/ipfs-companion/commit/bf9a69ed9dbc36d56e165c2dfaa83e833cd462ec

I don't know how their process works so maybe it's waiting on review from Mozilla, or maybe it has to be built by them.

I can't believe they delete the whole page though.

I have 2.7 stable if you want to try it

ipfs://Qmb1dT9M2jEMLkB9HgidcQpwUkQ74wHVf4J3meFejpiZB9

But the Beta branch works fine for me. What's it doing wrong for you?

>>1029842

It simply does nothing, the beta branch. I click it to see if there are options I can configure and the pop-up is a blank white window. No links are modified to clickable. I'll download your 2.7 version.

After uploading all those gigabytes to IPFS, my net as a whole is not working very well. Any tips to rectify this?

>>1029845

Restart everything like your computer, modem and anything else in between. Works %99 of the time and but if it doesn't, just reinstall your operating system.

>>1029846

>if it doesn't, just reinstall your operating system

Lol, ok. I'm not that stupid

>>1029845

IPFS is P2P, when you add something to IPFS you're not uploading it, you're just making it available for download from that machine (while the daemon is running).

Your daemon also has to tell the DHT about it so people know you're providing it. IIRC someone in a previous thread (or this one) said that this is really inefficient right now, but is being worked on so maybe it will be different soon.

This only has to happen if the network doesn't already know about something (if a DHT record isn't expired). At least I think that's how it works for KAD-DHT, I don't know how theirs works specifically.

If it's even remotely sane this should only happen when you add something new or if you've been offline for a long time and come back online. You need to tell some peers that you have the content and where you can be reached which takes some bandwidth and opens a lot of P2P connections temporarily. Some ISPs probably throttle you when this happens.

>>1029851

I used "Upload" for want of a better word. My ISP is Cox Communications and I don't know if I am being throttled or not. However, I am only running this for 30 minutes now. It probably just needs more time. After that, my connection should normalize, right? According to the WebUI I am currently peered with 69 peers, but when I checked earlier it was at over 280. As I was typing that it jumpped to 183. IDK then...

>>1029854

>After that, my connection should normalize, right?

It should, after the DHT records are propagated.

For multiple GBs at once that's a lot of records to provide. Since each hash is made up of smaller hashes that also need to be provided.

For example check this out >>1029842

>ipfs ls Qmb1dT9M2jEMLkB9HgidcQpwUkQ74wHVf4J3meFejpiZB9
QmVXMmiViNa3LtwJDHhkNrqYY16XHgYLusEsAAPn7F4H5c 6831852 ipfs-firefox-addon@lidel.org.xpi

Shows the file but even the file itself is made up of smaller blocks (in BT these are called pieces/chunks)

You can see the individual blocks with the same command

ipfs ls QmVXMmiViNa3LtwJDHhkNrqYY16XHgYLusEsAAPn7F4H5c

So that 1 6MB file with a directory turns into 28 hashes that I need to tell the network I provide.

If the number of peers I need is 5 (I don't know the actual number) that's 140 DHT STORE requests that have to succeed. If we count just the hash as 46 bytes that's 6.44KiB of total DHT traffic to provide the folder to the network, and real requests have overhead and other shit.

Take into account you have a lot more records than that coming from GBs of files and they're all probably fighting for the same bandwidth.

If a STORE times out, you try another peer until it succeeds.

So forwarding the port might help you not waste bandwidth since you'll just connect to whoever is fastest and know the connection won't fail.

My knowledge of DHT comes from using ed2k, bittorrent, and Wikipedia though, not IPFS specifically. So it might work differently, or I could be flatout wrong.

They might only provide the root hash or something more optimal.

> I am only running this for 30 minutes now.

It depends on your upload bandwidth and other DHT nodes/peers.

>over 280

Right now I have around 900 but I leave my daemon up all the time (except when playing games). I also have my ports open, a fast connection, and am in the US so there are likely a lot of nodes wanting to connect to me that are also physically closer.

>>1029867

If I could, I'd have it running 24/7 on a dedicated archive/seedbox machine but I have no money and this is running on a laptop. My options are limited atm

>>1029874

is it some fuckhuge collection of memes and books again? let that shit die already if it is

>>1029883

No, they're electronic textbooks and video games I stole, and various films/videos

>>1029883

Do not disparage the meme posters.

>>1029874

If you keep your connection up long enough for me to mirror it. I will host them until my next repo garbage collection. So far though I only managed to grab 2 blocks. So it might be working but it's getting out there slowly. Maybe your connection is dropping in and out.

Hopefully your personal situation improves regardless.

>>1029900

I've kept it up for hours, what's your status?

>>1029281

>Each node having their own view of the network is too much of a trade off when dealing with serious monetary systems

The computational power required to assemble the main tangle have to be large enough to eclipse small sub graph made by isolated or malicious nodes. Though I agree that unlike bitcoin, consensus is never 100% achieved. Only the probability a transaction to be valid is known from the cumulative weight of all confirmations.

>I also think we should have a hard cap of incoming messages per second.

I have been thinking about how to implement it on a dag and to proves historical records, but I'm not sure. I might be missing something stupid. We could make nodes not validating posts which were witnessed being created too fast or with too title PoW/PoS, but the problem is that can the spammer confirm his own posts and then merge into the main branch? We could let nodes vote against posts ([-1, 1] weight with each dag link) but we open an easy way to censorship (although always publicly available). It isn't even fair for high latency nodes. Only the hard consensus of a blockchain provides a straightforward solution. Else users have to decide individually or it should be coordinated by moderators.

>I'm not advocating for a PoW arms race like how cryptocurrencies use it.

Neither do I. I think I'll just wait for a better solution than PoW.

>attackers can always raise the difficulty high enough that no honest users can reasonably post anymore.

The main way to defend against it is to have the right amount of centralization through opt-in signed moderation. Nodes must agree that blacklisted posts don't count toward the speed limit so moderators are able to negate such attack without cpu work. Some moderators could even handle by neural networks.

>Basically anonymous coins using DPoS but publicly revealing your votes doesn't compromise your or anyone else's privacy.

Having untradable tokens to do anonymous staking would be nice but how would they be distributed? If they are automatically rewarded through time, how to protect against Sybil shills creating many fake identities?

We need to set rules in a way we don't even have to compete against corporate shills or spammers. We could trust the ability of people to process information comprehensively. For exemple, this vague idea: a board where an identity is required, but posting is anonymous through a zero-knowledge proof for user validity (ring signature). Misbehaving would get the identity tainted, then doing so repeatedly will increase the probability of being blacklisted. This could work as an anonymous Twitter too (only the public messages from followed users get displayed but it's impossible to tell identities apart, adding and removing follows would be random but statistically optimal after enough votes for one user).

>>1029953

ipfs get QmV16dyLSoBnb7JMfpy7wgHh8SLKvfSGuA9opjCeifaDY5
Saving file(s) to QmV16dyLSoBnb7JMfpy7wgHh8SLKvfSGuA9opjCeifaDY5
 7.99 MiB / 1.33 GiB [>---------------------------------------------------------------------------]   0.59% 37d5h12m28s

I tried connecting to you directly (via peerid of the only provider for that hash) but it kept timing out so there must be some connection problem going on. You're only reachable rarely. This shows some kind of network problem because regardless of the DHT I should be able to connect to you.

>>1029965

What do then?

>>1029956

>I have been thinking about how to implement it on a dag and to proves historical records, but I'm not sure

Easily, the node software has a queue for incoming messages and only relays them at a fixed rate, say 2 messages per second. Honest nodes won't send or relay messages over twice per second and will block nodes that submit messages more than twice per second. This weeds out spam nodes that try to submit messages at much higher rates. It becomes a consensus rule.

>We could make nodes not validating posts which were witnessed being created too fast or with too title PoW/PoS, but the problem is that can the spammer confirm his own posts and then merge into the main branch?

Messages can only be broadcasted at a fixed rate. If I'm connected to 8 nodes, the overall incoming message rate will be 16 messages per second if each node is limited to 2 messages per second. Individual nodes can connect to any amount they want but a minimum of 8 would be recommended.

>The main way to defend against it is to have the right amount of centralization through opt-in signed moderation

I agree but on the node or client level, not the overall network level.

>Nodes must agree that blacklisted posts don't count toward the speed limit so moderators are able to negate such attack without cpu work

Blacklists shouldn't be network wide. They should be applied on the node or client level. Multiple nodes can contribute to shared message blacklists. One of the great qualities about PoW is that it can be very hard to produce but very cheap to verify. To verify all you have to do (simplified) is hash the message and check it against the PoW hash. It takes milliseconds to verify a message with an arbitrary PoW difficulty.

>but how would they be distributed?

>If they are automatically rewarded through time, how to protect against Sybil shills creating many fake identities?

I'm talking about a regular cryptocurrency not anything special. DPoS works with 1 coin being 1 vote. Votes are cast by locking up coins for a small period of time and signaling your vote for specific nodes to be allowed to produce blocks. Once the voting round is over (it happens periodically) the top 30 or so voted nodes get to "mine" blocks at a fixed rate and in a fixed order. Free market competition drives the limited amount of block producers ("miners") that are voted for to give away a large portion of their block reward to their voters. They're basically buying votes. This is a good thing because it distributes coins most to those who secure it, the voters. Most nodes will give away between 70% to 90%. If the miner node violates consensus rules their block will be rejected and both they and their voters won't get paid. This will lead voters to vote for another node who follows the rules because they directly profit from it. It's a pretty good self regulating system with no power wasted on heavy calculations. The only weakness I see is that attackers could take advantage of low voter turnout to get 51% of the votes to vote themselves as "miners". They would profit the most but the system itself would still continue to be secure if checkpoints are included. The worst they could do to maximize their profit would be raising transaction fees. That's the same outcome as PoW but with way less capital needed to sustain the system.

>a board where an identity is required, but posting is anonymous

I suppose that could work if you wanted a whitelisted board. Ring signatures can be used.

>posting is anonymous through a zero-knowledge proof for user validity (ring signature)

Looks like you don't understand zero-knowledge proofs. They can only prove an unknown variable is within a range of possible values. In the case of Monero, they prove all inputs to a transaction are equal to the ouputs. This means the transaction's net value cancels out to zero. This proves someone can't create coins from nowhere and some unknown valid amount is being transferred. Only the sender and receiver know how much was transferred.

>Misbehaving would get the identity tainted, then doing so repeatedly will increase the probability of being blacklisted

If you use ring signatures you can confirm all the given signatures for a message are whitelisted. That means any one of the whitelisted users who's signature was used could have posted the message. It's impossible to determine which in the group of signatures was the actual message sender. That's the whole point. If you were to profile undesired posts you would be forced to correlate message content with multiple posts that share a common signature and deduce the bad actor relatively easily. If you did that, it defeats the whole purpose of the ring signature in the first place. You can't have your cake and eat it too.

Looks like Filecoin is more or less public, but at the moment it's only good for research and devs, I guess.

https://filecoin.io/blog/opening-filecoin-project-repos/

https://github.com/filecoin-project/specs

https://github.com/filecoin-project/go-filecoin

>Please note: Filecoin is in heavy development. Code is changing drastically day to day. At this stage, the repos, devnets, and other resources are for development. This release is aimed for developers, researchers, and community members who want to help make Filecoin. Miners and users who seek to use Filecoin will want to wait for a future release (likely, the testnet milestone).

>>1029970

>>1029965

My connection is significantly better now and I am at 610 peers and growing. Please continue to try, or retry if you stopped.

IPFS 0.4.19 is preparing its first release candidate

https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md#0419-2018-02-14-unreleased

>>1036812

> I hope it's on by default in the next release.

AutoNAT is already enabled by default, not sure about AutoRelay though. They elaborate that it uses other IPFS peers (described as relays) to get around a NAT.

>>1036812

>Things seem to load much faster than they used to. Even when I add something and try to get it through the gateway, it shows up pretty quick.

I agree, using this hash here >>1035793, directories load much quicker. Looks like IPFS is actually becoming viable! The only problem is that files aren't loading, but that may because peers aren't available or my router is blocking some stuff.

I ask for your help, /tech/. After adding a bunch of files to IPFS is there anything else I need to do in order for the network to be able to access them?

I can access the file by going to my own hosted node (http://localhost:32148/ipfs/QmUwsKgJxpxtEgqWrwjuYFbudDgm3JchPvy9TcK3LPuUFT) but if I want to use an external node I just can't access the files. It time outs or just throws an error. I tried both with ipfs.io and ipfs.infura.io

How long does it take for ~100 GB of files to reach the network?

I'm using version 0.4.19

>>1038483

>~100 GB of files

I'm guessing you probably have these in a fuck-huge directory with hundreds of files, while at the same time having a slow internet connection.

Maybe try organizing these into more manageable sub-directories?

Alternatively, it might just be that your hosted node is having trouble connecting to the network?

>>1038492

Yup. More than one thousand files.

I typed "ipfs swarm peers" and I see a bunch of IP addresses and stuff. Is that sufficient evidence my node is properly connected to the network?

But yeah, there's close to no traffic according to the WebUI so maybe that's the problem.

>>1038495

How did you add your files? Because it's possible your node didn't announce that you're a provide for the hashes in question, in which case there aren't any nodes that know you have those files in the first place.

Try to run:

ipfs dht provide <cid>

>>1038483

this may be a dumb question, but are your ports open? open port 4001, tcp only. you could also alternatively use UPnP, but that isn't as safe.

>>1038536

It is a dumb question but since I'm retarded it was the appropriate one. I guess that's what I deserve for using DHCP. Now the port is open and traffic is flowing.

>>1038517

It seems this is also a needed step. Is there a way to batch provide all the CIDs or should I just create a script?

But yeah, now a test video I added is working.

THANK YOU!

>>1038552

They should be provided by default when adding, and I think they're provided at an interval regardless of how you added them (while offline or not).

You don't have to do manually provide them, but they were probably not available after forwarding the port because the provide didn't happen automatically yet.

If this is wrong, someone please correct me.

>>1038797

I'm >>1038495

It doesn't matter because now I have a different problem altogether. Ever since opening port 4001 (i.e.: getting real traffic) my shit-tier Technicolor cablemodem router DPC3848VE craps itself after about 10 minutes of running ipfs daemon.

I'm thinking about getting a new router and using that piece of crap in bridged mode but at the same time I really don't feel like buying a new router just for IPFS, especially since I live in a third world country and everything is expensive as fuck.

Disabling MDNS help mildly but not decently enough.

>>1038874

Start your daemon with the flag "--routing=dhtclient". That should help stop your router from shitting itself.

>>1038897

Didn't help, crapped itself after less than 5 minutes. Thanks for your suggestion.

>>1038874

dht is just really heavy. no consumer nat router can handle it well. they are designed for normie web browsing not having thousands active connections at the same time and thats what dht does.

>>1039037

Why is it done at the router level? How much router RAM is needed in order to use it without problems?

>>984228

>Numbering threads is a tradition

Not when it an eterna-bread newfaggot.

>>1038874

23 days later I am here to tell you that you can get a netgear R7800 from china for $70.

I have a asus ac68u and my node hovers around 600-800 peers. I also run H@H. No issue so far. The R7800 is an even better router.

>>1047335

Well, I didn't want to turn this into my personal blog but I ended up buying a router and my cablemodem still craps itself, even in bridged mode. Maybe it's the sheer amount of connections or something. I don't even know how to diagnose it.

>>1047364

What is "bridged" mode? How many peers do you get?

I'm running on a home connection that also relies on a ISP modem. I have it in bridge mode and it works fine. Router says 1500 connections.

>>1047373

"Bridged mode" is the cablemodem's term for not acting like a router.

More than 900 peers last time I tried.

>>1047336

Is that actual memory usage or just allocated/reserved memory usage?

>>1047569

Pretty sure it's actual usage.

It's up to 528MB now

>>1047677

My ipfs running in the background is using 6MB you gianormous faggot I have many connections. Did you compile it from source? Did you set how many peers are allowed to a more sane value then 2000 in the config i.e "HighWater" and "LowWater" being max and minimum connections? If no then you are a faggot who needs to go back.

I've never looked at IPFS thing, convince me to try this.

>>1047731

IPFS is just bittorrent but without the bloat and duplication of files via multiple torrents. Do you have a file you want p2p'd and don't want jewgle to take it down? i.e piracy Are you a reporter that's not a fag and will get censored by the cabal? Are you a giant media organization trying to save costs by making all your clients act as CDN's thereby saving you electricity, bandwidth, time, and keeping your files up even after your organization ends or changes all without you having to worry about it after publishing? Then IPFS is for you.

>>1047722

Who gives a shit I just download it and run, I'm not autistic enough for your bullshit.

And it only has ~900 peers at most.

542MB now

>>1047740

Ok then, you still can adjust the config file under ~/.ipfs/config to change the highwater and lowater values. You also could update to the latest version instead of whatever you are using. Where are you downloading ipfs from?

install gentoo faggot