alanshaw changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.22 and js-ipfs 0.40 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
Trieste has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
zhangyafei[m] has joined #ipfs
<zhangyafei[m]>
有没有在青岛的
mowcat has quit [Remote host closed the connection]
digitalnomad91 has quit [Read error: Connection reset by peer]
cxl000__ has quit [Read error: Connection reset by peer]
cxl000__ has joined #ipfs
Jybz has joined #ipfs
is_null has joined #ipfs
rendar has joined #ipfs
Mateon1 has quit [Ping timeout: 246 seconds]
Mateon3 has joined #ipfs
Mateon3 is now known as Mateon1
Acacia has quit [Read error: Connection reset by peer]
Ai9zO5AP has quit [Read error: Connection reset by peer]
Ai9zO5AP has joined #ipfs
nehh^ has quit []
The_8472 has quit [Ping timeout: 252 seconds]
teleton has joined #ipfs
The_8472 has joined #ipfs
se7en- has left #ipfs [#ipfs]
se7en has joined #ipfs
is_null has quit [Ping timeout: 260 seconds]
is_null has joined #ipfs
is_null has quit [Ping timeout: 260 seconds]
Jybz has quit [Quit: Konversation terminated!]
is_null has joined #ipfs
Jybz has joined #ipfs
tsrt^ has joined #ipfs
Jybz has quit [Client Quit]
ygrek has joined #ipfs
Jybz has joined #ipfs
is_null has quit [Ping timeout: 268 seconds]
teleton has quit [Quit: Leaving]
aLeSD has joined #ipfs
jokoon has joined #ipfs
woss has joined #ipfs
notkoos has quit [Quit: WeeChat 2.2]
awk1314 has joined #ipfs
ygrek has quit [Ping timeout: 268 seconds]
mowcat has joined #ipfs
RamRanRa has joined #ipfs
mauz555 has joined #ipfs
woss has quit [Remote host closed the connection]
zarr[m] has joined #ipfs
<zarr[m]>
Hello
mauz555 has quit []
_whitelogger has joined #ipfs
jokoon has quit [Quit: jokoon]
_whitelogger has joined #ipfs
ygrek has joined #ipfs
awk1314 has quit [Remote host closed the connection]
Mateon3 has joined #ipfs
Mateon1 has quit [Ping timeout: 265 seconds]
Mateon3 is now known as Mateon1
mauz555 has joined #ipfs
_jrjsmrtn has joined #ipfs
__jrjsmrtn__ has quit [Ping timeout: 260 seconds]
ygrek has quit [Remote host closed the connection]
ygrek has joined #ipfs
pruebisima[m] has joined #ipfs
pruebisima[m] has left #ipfs [#ipfs]
markg85 has joined #ipfs
ygrek has quit [Ping timeout: 240 seconds]
mauz555 has quit []
caskd has quit [Quit: Freeman you fool!!]
caskd-dev has joined #ipfs
caskd-dev has quit [Client Quit]
caskd has joined #ipfs
caskd has quit [Client Quit]
caskd has joined #ipfs
bbtbear[m] has joined #ipfs
Elfo_ has quit [Quit: WeeChat 1.9.1]
ygrek has joined #ipfs
mr_Arthur has joined #ipfs
uniquerockrz has joined #ipfs
Clarth has joined #ipfs
todo has joined #ipfs
appa has quit [Quit: WeeChat 1.9.1]
gimzmoe has joined #ipfs
todo has quit [Client Quit]
Clarth has quit [Quit: Leaving]
ipfs-stackbot has quit [Remote host closed the connection]
ipfs-stackbot1 has joined #ipfs
mr_Arthur has quit [Quit: Leaving]
<eleitlDiscord[m]>
Will IPNS be using Base32 encoding in future? I can't find anything definitive online so far.
<ShadowJonathanDi>
you can just use base32
<ShadowJonathanDi>
get the CID, and then encode it in base32
<ShadowJonathanDi>
it should make no difference
<ShadowJonathanDi>
the only thing you'll have to keep an eye out for is that you dont change the codec identifier, and the multihash
<ShadowJonathanDi>
:conniehmm:
<ShadowJonathanDi>
or maybe you can change the codec
<ShadowJonathanDi>
idk
<eleitlDiscord[m]>
Are there CLI options for that, or does one have to do it manually?
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
<markg85>
eleitlDiscord[m]: ah right, sorry didn't catch your comment to move the discussion here
<markg85>
here now :)
<markg85>
So, again, isn't IPFS internally doing a publish to 20 nodes too?
<markg85>
How would it suddenly become centralized if i do that manually?
<eleitlDiscord[m]>
Thank you. I don't know how IPNS publishing is done internally. All I know is that with the tweaks suggested to me here yesterday the nodes can now at least resolve my IPNS I just published, while previously they could not.
<markg85>
hmm, i didn't have that problem :P
<markg85>
Question (as i try to do the manual publish), do you happen to know how i can get the peer id of a gateway node?
<eleitlDiscord[m]>
You could try reverse DNS for ipfs swarm addrs output perhaps, and see whether any of these also run public gateways? Or just probe for /ipns/ on these, which is probably not a polite thing to do.
aldente has joined #ipfs
jcea has joined #ipfs
MrAureliusR has joined #ipfs
Trieste has quit [Ping timeout: 260 seconds]
<markg85>
hmm, that trick doesn't seem to be working
<markg85>
Error: no key by the given name or PeerID was found
Trieste has joined #ipfs
DavidPH has quit [Quit: Leaving]
elfatherbrown has joined #ipfs
markg85 has quit [Quit: Konversation terminated!]
aldente has quit [Quit: aldente]
xcm has quit [Ping timeout: 260 seconds]
<eleitlDiscord[m]>
No idea, then.
<millysoose[m]>
Could someone explain why ipfs chunks files to generate those ipld objects? I understand what it's doing, but not why
jacobhenner[m] has joined #ipfs
jokoon has joined #ipfs
jcea has quit [Ping timeout: 245 seconds]
xcm has joined #ipfs
<JorropoDiscord[m>
it allow to download the file from multiple source, the first link refer to the root ipld object of the file, listing other list of file shard or listing file shard, so you can download lets say shard 1-5 from Qmfoo and 6-10 from Qmbar securly (because without you if Qmbar lied on the content of the file you will be only able to know it once the file is fully downloaded (and you can't know where is the error and from
<JorropoDiscord[m>
wich peer is it))
rendar has quit []
jokoon has quit [Quit: Leaving]
elfatherbrown has quit [Ping timeout: 245 seconds]
UndefinedIsNotAF has joined #ipfs
karol[m] has joined #ipfs
<eleitlDiscord[m]>
Is there node reputation tracking implemented in the current codebase?
<ShadowJonathanDi>
reputation of what kind?
<eleitlDiscord[m]>
Whether the node has been serving you bogus content.
<ShadowJonathanDi>
...there *is* no "bogus content"
<ShadowJonathanDi>
i'm not sure where you pulled that assumption that out from, but the job of a node in the network is to *be* the network
<ShadowJonathanDi>
which includes serving with no prejudice
<ShadowJonathanDi>
the only "reputation" that any other node can have in relation to you is a bitswap ledger
<ShadowJonathanDi>
which tracks how many blocks have been exchanged between the two nodes, and who is in "debt" and who has "credit"
<eleitlDiscord[m]>
If I continue to serve you chunks which don't hash to what I've requested, am I being a good node?
<ShadowJonathanDi>
if another node has "debt" (received more than sent), the chances of the current block being sent becomes smaller
<eleitlDiscord[m]>
* If I continue to serve you chunks which don't hash to what you've requested, am I being a good node?
<ShadowJonathanDi>
im pretty sure that's a tad impossible
<ShadowJonathanDi>
since you can only serve blocks to other nodes if they're in the other nodes' `iwant` list, and in *your* `ihave` list
<ShadowJonathanDi>
if you're talking about discrepancies between block hash and block content
<ShadowJonathanDi>
i cant say anything about that
<eleitlDiscord[m]>
Why can't the node lie about ihave, and serve you crap?
<ShadowJonathanDi>
but those should be rejected and errored out from exchange
<ShadowJonathanDi>
nope
<ShadowJonathanDi>
the other node would probably need `iwant`
<ShadowJonathanDi>
* the other node would probably need it in `iwant`
<ShadowJonathanDi>
if you can botch the protocol to start serving bullshit to the other node though... idk
<ShadowJonathanDi>
* if you can hack your node's protocol to start serving bullshit to the other node though... idk
<ShadowJonathanDi>
* if you can hack your node's protocol to start serving random blocks to the other node though... idk
<eleitlDiscord[m]>
Of course I'm talking about creative misues for the protocol. You can't assume the IPFS network will continue to be operated by good actors only.
<eleitlDiscord[m]>
* Of course I'm talking about creative misuses of the protocol. You can't assume the IPFS network will continue to be operated by good actors only.
<ShadowJonathanDi>
yeah i know that, though one serious aspect (integrity) is already solved in a widespread way
<ShadowJonathanDi>
what you're talking about is DoS-ing nodes, which idk anything currently about
<ShadowJonathanDi>
yes on the bad actors coming prevalent tho
<ShadowJonathanDi>
though currently i dont know how that's solved on a node-to-node basis
<eleitlDiscord[m]>
You could have a badnode list in the DHT, though of course implementing consensus is going to become complicated.
<ShadowJonathanDi>
it is already solved on a network basis
<ShadowJonathanDi>
even with DHT, multiple patches to the original Kademlia implementation makes sure that nodes that have been up longer are preferred
<ShadowJonathanDi>
in a natural way
<ShadowJonathanDi>
yeah i cant answer that question
<eleitlDiscord[m]>
Ok, so there is some basic reputation tracking already. Good.
<ShadowJonathanDi>
yeah thats mostly to prevent obvious leeching
<ShadowJonathanDi>
and to promote caching and serving blocks
<ShadowJonathanDi>
because if you keep hoarding blocks, eventually you'll start to build credit with immediate nodes if they constantly want blocks that you have, right?
<ShadowJonathanDi>
that way you're serving them blocks, build credit for yourself, and eventually be able to *immidiately* pull blocks from them when you request it
<ShadowJonathanDi>
because if you're in debt, that chance starts to lessen
<eleitlDiscord[m]>
Thanks, interesting.
patrice[m] has joined #ipfs
aLeSD has quit [Ping timeout: 260 seconds]
aLeSD_ has joined #ipfs
eldritch2 has joined #ipfs
fleeky has quit [Quit: Ex-Chat]
eldritch2 has quit [Remote host closed the connection]
ygrek has quit [Ping timeout: 268 seconds]
<bonedaddyDiscord>
So you can resolve IPNS from the command line and API pretty quickly if you use streaming results
<bonedaddyDiscord>
Part of the issue is when you go to resolve a record it waits for something like 16 nodes to respond before reaching a quorum
<bonedaddyDiscord>
You can reduce the required quorum and enable streaming results
<bonedaddyDiscord>
Or just enable streaming results
<eleitlDiscord[m]>
Is ipns:// canonical syntax for IPNS hyperlinks?
<bonedaddyDiscord>
idk what an IPNS hyperlink is, but `ipns://` and `ipfs://` are the "protocols" so if you want to update an ENS record you could list `ipns://` or `ipfs://`. iirc its a goal for browsers to support using `ipns://` and `ipfs://` as if it were `http://` but unless you use a plugin like ipfs companion, `ipns://` won't be recognized
<eleitlDiscord[m]>
Yes, I'm running the IPFS companion right now. Can be a bit annoying, if it attempts to second-guess what kind of IPFS gateway I'm trying to use, and switches to the one I've configured.
<eleitlDiscord[m]>
IPNS name resolution seems to work now, probably due to the tweaks you suggested to me yesterday.
is_null has joined #ipfs
lord| is now known as lor|d
lor|d is now known as lord|
ipfs-stackbot1 has quit [Remote host closed the connection]
ipfs-stackbot2 has joined #ipfs
luizirber has quit [Ping timeout: 246 seconds]
luizirber has joined #ipfs
sheepDiscord[m] has left #ipfs ["User left"]
hqdruxn08_ has joined #ipfs
hqdruxn08 has quit [Read error: Connection reset by peer]
Newami has joined #ipfs
Newami has quit [Client Quit]
Jybz has quit [Quit: Konversation terminated!]
mowcat has quit [Remote host closed the connection]