stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.18 and js-ipfs 0.33 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://botbot.me/freenode/ipfs/ | Forums: https://discuss.ipfs.io | Code of Conduct: https://git.io/vVBS0
pecastro has quit [Read error: Connection reset by peer]
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
Steverman has quit [Ping timeout: 252 seconds]
joseminao has joined #ipfs
joseminao has quit [Read error: Connection reset by peer]
dethos_ has quit [Ping timeout: 268 seconds]
spinza has quit [Quit: Coyote finally caught up with me...]
spinza has joined #ipfs
hannahhoward has joined #ipfs
ddahl has joined #ipfs
hannahhoward has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ddahl has quit [Ping timeout: 245 seconds]
mudpuppy has joined #ipfs
mudpuppy has quit [Remote host closed the connection]
unrife has quit [Remote host closed the connection]
joocain2 has quit [Ping timeout: 256 seconds]
joocain2 has joined #ipfs
bomb-on has quit [Quit: SO LONG, SUCKERS!]
hurikhan77 has quit [Remote host closed the connection]
hurikhan77 has joined #ipfs
djdv has quit [Quit: brb]
Welcome has joined #ipfs
Welcome has quit [Remote host closed the connection]
lidel` has joined #ipfs
lidel has quit [Ping timeout: 252 seconds]
lidel` is now known as lidel
plexigras has quit [Quit: WeeChat 2.3]
dethos_ has joined #ipfs
bomb-on has joined #ipfs
beerhall[m] has joined #ipfs
Encrypt has quit [Quit: Quit]
reit has joined #ipfs
beerhall[m] is now known as Onoketa[m]
ddahl has quit [Ping timeout: 245 seconds]
klot has joined #ipfs
klot has quit [Remote host closed the connection]
klot has joined #ipfs
klot has quit [Remote host closed the connection]
klot has joined #ipfs
klot has quit [Remote host closed the connection]
klot has joined #ipfs
BeerHall1 has joined #ipfs
BeerHall has quit [Ping timeout: 240 seconds]
hannahhoward has joined #ipfs
papazeus has joined #ipfs
papazeus has quit [Ping timeout: 250 seconds]
BeerHall1 has quit [Remote host closed the connection]
BeerHall has joined #ipfs
BeerHall has quit [Client Quit]
Caterpillar2 has joined #ipfs
Fessus_ is now known as Fessus
<fiatjaf>
I'm working on a centralized index of stuff stored on IPFS you want to share with others
<fiatjaf>
like a github but for any kind of data or files you have
<fiatjaf>
and also we don't store the data, you do
<fiatjaf>
it's basically just a simple, very simple, centralized, very centralized, ipns
<fiatjaf>
do you have any suggestions or commentary about it?
<fiatjaf>
I'm thinking about calling it IPCI, intraplanetary centralized index, but name suggestions are very welcome
ygrek__ has quit [Ping timeout: 245 seconds]
Steverman has quit [Ping timeout: 252 seconds]
irdr has quit [Ping timeout: 244 seconds]
irdr has joined #ipfs
irdr has quit [Remote host closed the connection]
<Kolonka[m]>
It's Git on IPFS?
<Kolonka[m]>
Isn't the object model already essentially that?
irdr has joined #ipfs
joseminao has joined #ipfs
joseminao has left #ipfs [#ipfs]
hannahhoward has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bomb-on has quit [Quit: SO LONG, SUCKERS!]
hannahhoward has joined #ipfs
Caterpillar2 has quit [Ping timeout: 250 seconds]
Caterpillar2 has joined #ipfs
Caterpillar2 has quit [Client Quit]
The_8472 has quit [Ping timeout: 260 seconds]
ygrek__ has joined #ipfs
djdv has joined #ipfs
The_8472 has joined #ipfs
Steverman has joined #ipfs
hannahhoward has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<voker57>
i don't see how git is related
<voker57>
and to get a meaningful link to git repo you need ipns too
hannahhoward has joined #ipfs
<r0kk3rz>
fiatjaf: so its like a user submitted indexer?
<r0kk3rz>
sounds useful
<fiatjaf>
yes, pretty much that
<fiatjaf>
Kolonka[m], not git at all.
<fiatjaf>
I said github just because github serves much as a social hub of any stuff as a hosted git repo service.
}ls{ has joined #ipfs
grumble has quit [Quit: Need to reconnect so here's a random tip: The command "xrandr --output HDMI1 --set 'Broadcast RGB' Full" (you might need to replace HDMI1 with your monitor output name) might significantly improve contrast on external monitors. s/Full/Automatic/ to reset]
grumble has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
The_8472 has joined #ipfs
joocain2 has quit [Ping timeout: 256 seconds]
joocain2 has joined #ipfs
thomasan_ has joined #ipfs
thomasan_ has quit [Client Quit]
pubswap_ has joined #ipfs
<pubswap_>
I’ve noticed a bit of a lag in the browser when using js-ipfs and catReadableStream. I can see the peer websockets in the dev console streaming frames immediately but it can take upwards of 10+ seconds before the first ‘data’ on the stream is fired. I have looked at the source a bit but unsure of what could be causing this. It does not seem to be network lag time finding the hashes as those seem to come instantly in the Frames view
<pubswap>
I have my own gateway if I wanted to stream over HTTP.
<fiatjaf>
oh
<fiatjaf>
sorry
<fiatjaf>
I didn't mean to say you were incapable of running your own gateway
<pubswap>
I do not. I am interested in connecting the browsers as nodes themselves. I understand that with the websocket/bootstrap config now each ws host is essentially a gateway as well but that will not always be the case.
kaminishi has joined #ipfs
<pubswap>
No worries, I didn’t think you were, just not sure of what you are asing or how that pertains to the lag on the read stream.
<pubswap>
Maybe I should say…. 1. I don’t wish to centralize the decentralized nature of IPFS by forcing all traffic through a single point of failure like the gateway and… 2. I don’t wish to burden a public gateway with what could be a significant amount of load.
fractex has quit [Remote host closed the connection]
obensource has quit [Ping timeout: 244 seconds]
<pubswap>
Even with using ipfs.io as ws peers, I have noticed some spotty performance which has impacted my service prompting me to host my own ws peer node as well as api/gateway/etc.
fractex has joined #ipfs
clemo has quit [Ping timeout: 268 seconds]
spinza has joined #ipfs
<pubswap>
Which brings me back to my issue, when using js-ipfs in the broweser to execute ‘catReadableStream’, the blocks from the IPFS netowkr (or the websocket peer) start coming in instantly but the ‘data’ event on the stream object is not triggered until sometimes 10+ seconds later.
<pubswap>
Anyone know why this is?
<pubswap>
Ideally, I’d like to access those blocks from the stream as soon as they are downloaded and available.
The_8472 has quit [Ping timeout: 260 seconds]
obensource has joined #ipfs
The_8472 has joined #ipfs
emerson has quit [Remote host closed the connection]
Mateon3 has joined #ipfs
klot has quit [Read error: Connection reset by peer]
Mateon1 has quit [Ping timeout: 272 seconds]
Mateon3 is now known as Mateon1
bomb-on has joined #ipfs
adin has quit [Ping timeout: 250 seconds]
adin has joined #ipfs
FimFx has joined #ipfs
plexigras has joined #ipfs
evilem has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
ygrek__ has quit [Ping timeout: 252 seconds]
<AphelionZ>
fiatjaf: and lidel they are protobuf files arent they?
The_8472 has joined #ipfs
<AphelionZ>
the keys
<fiatjaf>
AphelionZ, yes they are. I've linked to a repo where somebody put out the bare minimal protobug stuff to decode them.
<AphelionZ>
gotcha
<fiatjaf>
pubswap: let me make my point again: use window.ipfs. if the visitor has a running node + IPFS Companion he'll fetch and rehost content from his own node.
<fiatjaf>
(that node may be js-ipfs running inside IPFS Companion or it can be go-ipfs running as a daemon in the background)
<pubswap>
fiatjaf: I have integrations with the local node if one exists, yes. This is the main method of uploading or publishing.
<fiatjaf>
that will be much better and faster for people running a daemon (I believe js-ipfs is still struggling against browser connectivity stuff)
<fiatjaf>
pubswap, if the visitor doesn't have IPFS at all, he should still be able to browse content
<fiatjaf>
gateways exist for that
<fiatjaf>
cloudflare-ipfs.com should be capable of handling a lot of traffic (isn't cloudflare alone powering a huge percentage of the entire web today through its caches and so on?)
<pubswap>
Indeed but the browser client has the node so all visitors should have a node.
<fiatjaf>
no
<fiatjaf>
stop embedding js-ipfs
<fiatjaf>
that's too resource-intensive
<fiatjaf>
use window.ipfs when available
<fiatjaf>
otherwise fallback to the gateway
<fiatjaf>
(this is just a cheap suggestion)
<pubswap>
resource intensive on what side?
<fiatjaf>
the client
<fiatjaf>
a casual visitor
<pubswap>
Right but server goes crazy
<fiatjaf>
who doesn't know what is ipfs, just wants to watch a video his friend has sent
<fiatjaf>
what server?
<fiatjaf>
cloudflare-ipfs.com?
<pubswap>
the one hosting the gateway
<fiatjaf>
it is certainly better prepared than a poor machine
<pubswap>
seems you are suggesting to reduce resource utlization in the client by pushing it to the server.
<fiatjaf>
yes
<fiatjaf>
I'm suggesting that you let people opt in to use ipfs on their machines or don't
<fiatjaf>
they do that by installing ipfs companion
<fiatjaf>
otherwise it means they don't want their entire CPU being used to run a js library on some rogue page they just clicked
<pubswap>
My entire reason for designing and developing this service on IPFS was to utlize the benefits of IPFS. If I wanted to just stream video from an HTTP server, I would not use IPFS at all.
<pubswap>
but I do have fallback logic as it seems you are eluding to.
<pubswap>
the problem there is I have to then double or triple the storage requirements to store different formats of the same video.
<pubswap>
Not ideal.
<pubswap>
so I have disabled that logic for now
<pubswap>
The only issue with all of this is as I have stated a couple times now…. Te delay between the js-ipfs browser receicing the blocks from th websocket and when it fires the data event on the stream.
<pubswap>
Furthermore, the fallback logic I have was only used by those whose browsers cannot utlize the MediaSourceExtension. But I am not sure I even care about that at this point.
<pubswap>
It also seems somewhat odd to come to an IPFS IRC channel for a question about IPFS to be told not to use IFS. ¯\_(ツ)_/¯
rendar has quit []
<voker57>
js-ipfs != ipfs
<voker57>
it does not implement all go-ipfs features either
<pubswap>
heh, dont’t tell them that. :-)
<pubswap>
as a client, it works fine. I don't use it as a server so cannot comment.
<pubswap>
so back to readable streams…….?
<pubswap>
maybe js-ipfs has their own channel that is not advertised?
<r0kk3rz>
no this is the js-ipfs channel
qtfy has joined #ipfs
qtfy has quit [Client Quit]
irdr has quit [Ping timeout: 252 seconds]
<pubswap>
Looks to be some anomosity between the two projects. If that continues you may want to consider different channels.
<fiatjaf>
I'm not saying you shouldn't use ipfs
joocain2 has quit [Ping timeout: 256 seconds]
irdr has joined #ipfs
joocain2 has joined #ipfs
<fiatjaf>
read everything I said again and you'll get it
<pubswap>
I have but do you have anythign to say about the question I have asked?
<fiatjaf>
but again, I'm just a lone user here, you should probably ignore me
<pubswap>
Everything you has said so far is of no use to me.
<fiatjaf>
I wasn't trying to answer your question.
hannahhoward has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ygrek__ has joined #ipfs
<pubswap>
Thank you?
joocain2 has quit [Ping timeout: 256 seconds]
joocain2 has joined #ipfs
hexfive has joined #ipfs
<pubswap>
BTW, been messing with go-ipfs release 0.4.18 today. The resource utlization difference is considerable and easily noticed. Well done!
<pubswap>
0.4.17 used to regularly spike over 200% CPU with, at times, 20% memory usage (on a 32GB system). I have not seen 0.4.18 spike over 60% utlization and hovers around 2% memory usage.
hurikhan77 has quit [Remote host closed the connection]
<voker57>
that's because they added "connection manager" who cuts down connection to that single node which has your data while you're downloading it
<voker57>
and forbids resuming it for like half an hour
hurikhan77 has joined #ipfs
<voker57>
connections consume a ton of memory because some very lazy coding so they added this as a band-aid
<pubswap>
yeah the release notes are suprisingly detailed.
dimitarvp has quit [Quit: Bye]
FimFx has quit [Ping timeout: 252 seconds]
trqx has quit [Remote host closed the connection]
trqx has joined #ipfs
<fiatjaf>
Swedneck, means it's a domain that has to be resolved, not an ip
<Swedneck>
Wut
<Swedneck>
but you want to resolve the IP from the domain, no?
<Swedneck>
i.e. an A or AAAA record
random_yanek has quit [Ping timeout: 245 seconds]
joocain2 has quit [Ping timeout: 256 seconds]
hexfive has quit [Quit: WeeChat 2.2]
rain2 has quit [Quit: WeeChat 2.2]
joocain2 has joined #ipfs
random_yanek has joined #ipfs
aerth has quit [Ping timeout: 256 seconds]
aerth has joined #ipfs
<Swedneck>
can you even use dns4 as a bootstrap address?
spinza has quit [Quit: Coyote finally caught up with me...]
<fiatjaf>
dns4?
<fiatjaf>
yes, you want to resolve, but I guess you can pass the domain and ipfs will resolve that for you
<fiatjaf>
otherwise if it's a dynamic ip you would have to resolve it manually every 30 minutes and update your bootstrap list
hurikhan77 has quit [Remote host closed the connection]
ygrek__ has quit [Ping timeout: 264 seconds]
hurikhan77 has joined #ipfs
spinza has joined #ipfs
<Swedneck>
ah, well yeah i do want to add a ddns address
<Swedneck>
more like every week at least, in this case
jamesaxl has quit [Quit: WeeChat 2.2]
flerovite has quit [Ping timeout: 268 seconds]
flerovite has joined #ipfs
newnick has joined #ipfs
newnick has quit [Remote host closed the connection]
kaminishi has quit [Remote host closed the connection]