stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.19 and js-ipfs 0.34 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of
rcat has quit [Remote host closed the connection]
cwahlers_ has quit [Ping timeout: 258 seconds]
Xenguy has quit [Ping timeout: 246 seconds]
pcre has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
boredmanicrobot has joined #ipfs
clemo has quit [Ping timeout: 245 seconds]
Xenguy has joined #ipfs
cwahlers has joined #ipfs
renich has joined #ipfs
pecastro has quit [Ping timeout: 250 seconds]
renich_ has quit [Ping timeout: 250 seconds]
spinza has joined #ipfs
Xenguy has quit [Ping timeout: 246 seconds]
Xenguy has joined #ipfs
Fessus has joined #ipfs
jesse22 has quit [Ping timeout: 252 seconds]
placer14 has quit [Quit: placer14]
hurikhan77 has joined #ipfs
ctOS has quit [Quit: Connection closed for inactivity]
placer14 has joined #ipfs
kakra has quit [Ping timeout: 255 seconds]
placer14 has quit [Quit: placer14]
srkk has left #ipfs ["WeeChat 1.6"]
renich_ has joined #ipfs
renich has quit [Ping timeout: 272 seconds]
boredmanicrobot has quit [Quit: boredmanicrobot]
shizy has quit [Quit: WeeChat 2.4]
muravey has joined #ipfs
ctOS has joined #ipfs
nighty- has joined #ipfs
jamiew has quit [Ping timeout: 240 seconds]
mowcat has quit [Remote host closed the connection]
jamiew has joined #ipfs
mischat has quit [Remote host closed the connection]
Belkaar has quit [Ping timeout: 245 seconds]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
_whitelogger has joined #ipfs
boredmanicrobot has joined #ipfs
boredmanicrobot has quit [Remote host closed the connection]
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
muravey has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zeden has joined #ipfs
muravey has joined #ipfs
abhinavmehta has joined #ipfs
muravey has quit [Read error: Connection reset by peer]
}ls{ has quit [Ping timeout: 255 seconds]
mischat has joined #ipfs
}ls{ has joined #ipfs
ellyacht has joined #ipfs
ellyacht has left #ipfs [#ipfs]
abhinavmehta has quit [Ping timeout: 246 seconds]
aerth has quit [Ping timeout: 256 seconds]
tombusby has quit [Ping timeout: 256 seconds]
joocain2 has quit [Ping timeout: 256 seconds]
tombusby has joined #ipfs
joocain2 has joined #ipfs
aerth has joined #ipfs
abhinavmehta has joined #ipfs
abhinavmehta has quit [Ping timeout: 246 seconds]
zeden has quit [Quit: WeeChat 2.4]
Mateon3 has joined #ipfs
Mateon1 has quit [Ping timeout: 246 seconds]
Mateon3 is now known as Mateon1
cyberwolf has joined #ipfs
mischat has quit [Ping timeout: 252 seconds]
parqua has joined #ipfs
mischat has joined #ipfs
Jesin has quit [Quit: Leaving]
MrSparkle has quit [Quit: Crono dies]
Jesin has joined #ipfs
lord| is now known as PuzzlePopsicle
PuzzlePopsicle is now known as lord|
parqua has quit [Ping timeout: 272 seconds]
mischat has quit [Ping timeout: 252 seconds]
Boss314 has joined #ipfs
konubinix_ has quit [Quit: ZNC 1.7.1+deb2+b3 - https://znc.in]
mischat has joined #ipfs
ctOS has quit [Quit: Connection closed for inactivity]
mischat has quit [Remote host closed the connection]
mischat has joined #ipfs
mischat has quit [Client Quit]
joocain2 has quit [Ping timeout: 256 seconds]
joocain2 has joined #ipfs
polman has quit [Ping timeout: 246 seconds]
HeavyMetal[m] is now known as Tubez[m]
Tubez[m] is now known as HeavyMetal[m]
renich has joined #ipfs
renich_ has quit [Ping timeout: 272 seconds]
renich has quit [Ping timeout: 250 seconds]
renich_ has joined #ipfs
renich_ is now known as renich
Xenguy has quit [Ping timeout: 244 seconds]
Xenguy has joined #ipfs
airwind has joined #ipfs
ylp has joined #ipfs
vyzo has quit [Quit: Leaving.]
vyzo has joined #ipfs
ctOS has joined #ipfs
renich has quit [Ping timeout: 246 seconds]
<Voker57>
hmm wtf
<Voker57>
Error: write /home/ipfs/.ipfs/datastore/029221.log: no space left on device
<alanshaw[m]>
wow, `ipfs-http-client` is significantly smaller now, about 33% smaller than when we started working on bundle size at v28.1.0
pcre has quit [Remote host closed the connection]
spinza has joined #ipfs
clemo has joined #ipfs
abhinavm_ has joined #ipfs
abhinavmehta has quit [Read error: Connection reset by peer]
manray has quit [Ping timeout: 272 seconds]
Steverman has joined #ipfs
leliamesteban[m] has joined #ipfs
<Steverman>
So.... my professor made a programming language for concurrent and distributed programming with dynamic information control flow (information theory). It transpiles into nodejs that uses libp2p as the p2p backend :D. All done through LLVM IR
<seba->
sounds bloaty
obensour1 has quit [Ping timeout: 246 seconds]
<jon1012>
is there a standard way to tackle the spam issue on ipfs pubsub ? (gossipsub)
<Steverman>
seba-: It's just to teach information control flow
obensour1 has joined #ipfs
vroom has quit [Quit: Something went wrong!]
vroom has joined #ipfs
vroom has joined #ipfs
vroom has quit [Changing host]
abhinavm_ has quit [Ping timeout: 250 seconds]
abhinavmehta has joined #ipfs
manray has joined #ipfs
malaclyps has quit [Read error: Connection reset by peer]
llll has joined #ipfs
malaclyps has joined #ipfs
abhinavmehta has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
yal_ has joined #ipfs
llll has left #ipfs [#ipfs]
abhinavmehta has joined #ipfs
abhinavmehta has quit [Client Quit]
abhinavmehta has joined #ipfs
leeola has joined #ipfs
fazo has joined #ipfs
polman has joined #ipfs
<lordcirth__>
jon1012, you mean flooding (performance) or spam (messages being mistaken for real ones)?
Ai9zO5AP has joined #ipfs
<jon1012>
both
<jon1012>
I am making a network on top of ipfs pubsub, and there might be a big risk of attack, spam and ddos being one of them
<lordcirth__>
spam is solvable with some kind of signature system, possibly with PoW to register new keys to make bans mean something. Flooding pretty much has to be solved at the pubsub implementation.
<jon1012>
PoW?
<lordcirth__>
Proof of Work
<lordcirth__>
For example, Bitmessage, since it floods all messages to everyone, requires proof of work per message. But since pubsub doesn't, you could have PoW per new ID so that you can ban spammers, perhaps.
<jon1012>
oh I understand
<lordcirth__>
It's not an easy problem to solve in practice, though.
<jon1012>
yeah...
<lordcirth__>
If it takes 10 minutes to generate a new key, that doesn't really affect a legit user too much. But it means banning actually slows down a spammer
<jon1012>
my issue is that users of the services will need 10 minutes before starting to use the service
<lordcirth__>
However, a spammer could get a lot more computing power than a legit user, especially with botnets
<jon1012>
imagine having to wait 10 minute before having your facebook account active
<jon1012>
you lose your users
abhinavmehta has quit [Read error: Connection reset by peer]
<lordcirth__>
So, you may need to give up on preventing flooding. But there are other ways to tackle spam, like web of trust. Freenode does that.
<jon1012>
steem resolved that issue with having to either pay or wait a few weeks to get your account... but same, user retention is very bad
<jon1012>
steemit resolved that issue with having to either pay or wait a few weeks to get your account... but same, user retention is very bad
<jon1012>
yeah you are right...
<lordcirth__>
Ultimately it's a very hard problem in an uncensorable distributed network :P
<lordcirth__>
You may want to study how Freenode's WoT handles spam.
<jon1012>
I'll look at it, thanks!
<lordcirth__>
np. let me know if you have something we can test
matth has joined #ipfs
matt-h has quit [Ping timeout: 246 seconds]
dandevelo has joined #ipfs
dandevelo has quit [Remote host closed the connection]
airwind has quit [Quit: airwind]
dandevelo has joined #ipfs
dandevelo has left #ipfs [#ipfs]
<cmkat[m]>
how good is ipfs with meshed networks?
Unknown has joined #ipfs
Unknown has quit [Client Quit]
appa_ has joined #ipfs
alphazb has joined #ipfs
alphazb has quit [Client Quit]
alphazb has joined #ipfs
zeden has joined #ipfs
abhinavmehta has joined #ipfs
placer14 has joined #ipfs
Tiez has joined #ipfs
alphazb has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
abhinavmehta has quit [Read error: Connection reset by peer]
abhinavm_ has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
matt_ has joined #ipfs
matt_ is now known as Guest26163
alphazb has joined #ipfs
abhinavm_ has quit [Ping timeout: 246 seconds]
matth has quit [Ping timeout: 272 seconds]
lordcirth has joined #ipfs
<lordcirth>
This tool does chunking in clever ways: https://github.com/systemd/casync "The chunking algorithm is supposed to create variable, but similarly sized chunks from the data stream, and do so in a way that the same data results in the same chunks even if placed at varying offsets."
<lordcirth>
This sort of thing seems very useful for ipfs; anyone know if someone's done something like this for ipfs?
<lgierth>
Steverman: that sounds super interesting, any links you can share?
<lgierth>
lordcirth: interesting, i wonder what their exact chunking algorithm is. by default ipfs naively chunks at fixed byte intervals, but it also offers rabin fingerprinting chunking (see ipfs add --help)
<lordcirth>
lgierth, oh, I'll look into that, thanks
<lgierth>
always interested in benchmarks too
kptz has left #ipfs [#ipfs]
matth has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
Guest26163 has quit [Ping timeout: 272 seconds]
ctOS has quit [Quit: Connection closed for inactivity]
bart6 has joined #ipfs
Tiez has quit [Ping timeout: 268 seconds]
bart6 has quit [Client Quit]
renich has joined #ipfs
renich_ has joined #ipfs
renich has quit [Ping timeout: 245 seconds]
reit has joined #ipfs
reit has quit [Ping timeout: 246 seconds]
robmisio has joined #ipfs
<robmisio>
I'm tinkering with ipfs-js, but not sure how to retrieve content via ipns.
<robmisio>
I publish a file and it has the hash "QmWRcfMHeGHFHwboVky45cmd55XeQ4WpJZ7iGMefK1Wyg3". Then I do node.name.publish("/ipfs/<hash>"), which returns a "name" of "QmP9kz6uhYjfVzBU8GcKnDJNqtFXsWAxFqBFE7V8xGMKnh". I'm trying to reach the content via the gateway at https://ipfs.io/ipns/QmP9kz6uhYjfVzBU8GcKnDJNqtFXsWAxFqBFE7V8xGMKnh, but it never comes back. Is that the right way to retrieve it? Also is there a way to retrieve it from the api
MrSparkle has joined #ipfs
manray has quit [Ping timeout: 244 seconds]
mowcat has joined #ipfs
renich_ has quit [Ping timeout: 272 seconds]
renich has joined #ipfs
renich has quit [Ping timeout: 245 seconds]
renich has joined #ipfs
robmisio has quit [Ping timeout: 256 seconds]
<lordcirth>
robmisio, that is how one fetches ipns links, yes. However, I can't fetch your ipfs object from here.
Fessus has quit [Remote host closed the connection]
Fessus has joined #ipfs
reit has joined #ipfs
<matshenricson[m]>
It is often hit or miss when it comes to getting content from ipfs.io, sometimes it works, many times it doesn't, and I have no idea why
<lordcirth>
Probably load / timeouts
<matshenricson[m]>
It makes it hard to build stuff upon it
<lordcirth>
You shouldn't be building stuff on a volunteer public gateway
<lordcirth>
Use IPFS or run your own gateway for your app
fazo has quit [Remote host closed the connection]
manray has joined #ipfs
reit has quit [Ping timeout: 246 seconds]
<matshenricson[m]>
I do, but that requires everyone to run their own gateway, and then you're down to the same problem, again
<matshenricson[m]>
All example code shows examples where you get to fetch objects from ipfs.io, but it often doesn't work. I've tried it many times, and I've seen other demo with the same problem, and none of us knows why
NamesKelly[m] has joined #ipfs
<lordcirth>
matshenricson[m], probably because everyone is using ipfs.io when they shouldn't and it's overloaded
<lordcirth>
matshenricson[m], so, why can't your program require a localhost go-ipfs daemon?
<matshenricson[m]>
If I run my own gateway at 1.2.3.4 and my peer runs on 5.6.7.8, how can my peer know if my data has arrived?
ylp has quit [Quit: Leaving.]
<lordcirth>
matshenricson[m], could you please clarify what you are doing?
nighty- has quit [Quit: Disappears in a puff of smoke]
<matshenricson[m]>
Lets assume two smartphone apps. I publish a picture on my phone, how will that image arrive to my peer who uses an app on her phone?
<matshenricson[m]>
Lets assume we both have local IPFS daemons
<lordcirth>
matshenricson[m], Phone A does 'ipfs add'. Then pushes the hash to a pubsub channel that they are both subscribed to. (preferably with some signing involved. The peer receives the hash and does an 'ipfs get'
<matshenricson[m]>
If ipfs.io is bogged down all the time, is there another server somewhere else that I can use instead while I experiment, or demo the coolness of IPFS?
NamesKelly[m] is now known as DeineMomheitKell
<matshenricson[m]>
I can send the CID by email just as well, right?
<lordcirth>
matshenricson[m], you could, yes, if you don't mind requiring email.
<lordcirth>
The IPFS-only way would be to use pubsub, plus occasionally summarizing the past under an IPNS name so that clients who missed a pubsub message can catch up.
<matshenricson[m]>
Cool, I will try that list
<matshenricson[m]>
Perhaps ipfs.io could return quickly if it is bogged down? Right now it just hangs...