<physes>
I get "Path Resolve error: Could not resolve name."
zorglub27 has joined #ipfs
dignifiedquire has quit [Quit: Connection closed for inactivity]
mgue has quit [Ping timeout: 260 seconds]
<deltab>
physes: the entry expired; you'll need to publish it daily
PseudoNoob has joined #ipfs
mgue has joined #ipfs
chriscool has joined #ipfs
<Kubuxu>
or have the daemon that published it running
<ne1>
is everything public on ipfs at this point?
<ne1>
no authentication mechanism or anything like that?
r0kk3rz has quit [Quit: WeeChat 1.4]
<Kubuxu>
it will republish it, but only if it is one that published it initially
<Kubuxu>
ne1: no, if you want something private you have to encrypt it before adding
<ne1>
ok
cemerick has joined #ipfs
ianopolous_ has quit [Remote host closed the connection]
r0kk3rz has joined #ipfs
Encrypt has joined #ipfs
physes has quit [Ping timeout: 260 seconds]
kobigurk has joined #ipfs
wuch has joined #ipfs
ygrek_ has quit [Ping timeout: 244 seconds]
cyberwolf has joined #ipfs
cyberwolf has quit [Client Quit]
ianopolous_ has joined #ipfs
ralphtheninja has quit [Ping timeout: 248 seconds]
ralphtheninja has joined #ipfs
zorglub27 has quit [Ping timeout: 260 seconds]
physes has joined #ipfs
<physes>
I thought once you published something it was permenent
<physes>
is there any way of adding it to ipfs so that it will serve without having to leave the daemon running?
<physes>
is that what bitswap/filecoin is for?
ralphtheninja has quit [Ping timeout: 260 seconds]
ralphtheninja has joined #ipfs
slothbag has joined #ipfs
<r0kk3rz>
physes: ultimately someone has to serve it, so yeah thats basically what filecoin is for
<physes>
hmm. could the storage incentivization be done on Ethereum via a smart contract?
<r0kk3rz>
afaik filecoin will be built as an ethereum token, so i guess so
<physes>
As an ethereum developer I've been thinking about how to emulate the incentivization aspects of swarm for ipfs. Would be better to use ethereum than attempting to run a completely sepearate chain
<physes>
ah
<r0kk3rz>
physes: im sure we will learn more about the plans once the devcon2 videos as up
<physes>
For the Nebulis dns system I'm building there will be a token called "Dust", which is a kind of metering token. Any chance this could be adapted to help the incentivization project? Would like to contribute to IPFS if possible, although it seems like a closed-box
bsm117532 has quit [Ping timeout: 240 seconds]
<r0kk3rz>
closed box?
<r0kk3rz>
if you want to build a storage network on ipfs, go right ahead
zorglub27 has joined #ipfs
<physes>
ok
johnytiago has joined #ipfs
<pawal>
physes: the ipfs:// URI is already kind of used in IPFS
<pawal>
it also sounds like that you are creating domain names that will potentially clash with the current DNS system, which is a really bad idea
<pawal>
rather than have name queries go through a URI, you should probably use a reserved TLD name for it (IETF dnsop discusses .alt for alternative naming schemes)
Encrypt has quit [Quit: Quit]
johnytia_ has joined #ipfs
johnytiago has quit [Read error: Connection reset by peer]
G-Ray has joined #ipfs
johnytia_ has quit []
<physes>
thanks for your suggestions @pawel. There won't be clashes as it uses a different URI. Although it might be a good idea to be able to flag obvious overlaps to prevent phishing
<pawal>
physes: ipfs:// defines sofar ipfs://ipfs/Qm... and ipfs://ipns/Qm... so it would be possible to add other naming schemes to ipfs:://whatever/...
<physes>
That's good
<pawal>
the problem with other namespaces that looks like DNS it that it will definitely leak to DNS
<physes>
Well, in the browser, the best practice would be to have a drop-down that allows people to go between ipfs and http to make that clear
<physes>
The records map the url, aka ipfs://<pre>.<mid>.<tld> to /ipfs/ or /ipns/. Whether it's an ipfs or ipns record is specified as a boolean, so the only necessary information is the ipfs hash and the bool, not necessarily that it maps ipfs's native uri schemes
physes has quit [Quit: Page closed]
G-Ray has quit [Quit: Konversation terminated!]
cemerick has quit [Ping timeout: 260 seconds]
zorglub27 has quit [Quit: zorglub27]
zorglub27 has joined #ipfs
<pawal>
Not all applications are based on a web browser...
bsm117532 has joined #ipfs
bsm117532 has quit [Remote host closed the connection]
physes has joined #ipfs
<physes>
Then how would it clash with the dns system?
<r0kk3rz>
physes: you would have two authorities claiming the name foo.bar
physes has quit [Ping timeout: 260 seconds]
G-Ray has joined #ipfs
ianopolous_ has quit [Remote host closed the connection]
PseudoNoob has quit [Remote host closed the connection]
ianopolous_ has joined #ipfs
herzmeister has quit [Quit: Leaving]
herzmeister has joined #ipfs
ylp has quit [Ping timeout: 260 seconds]
ylp has joined #ipfs
G-Ray has quit [Quit: Konversation terminated!]
zorglub27 has quit [Quit: zorglub27]
Encrypt has joined #ipfs
slothbag has quit [Quit: Leaving.]
Guest77192 is now known as cypher
cypher has joined #ipfs
cypher has quit [Changing host]
Foxcool has quit [Ping timeout: 258 seconds]
arpu has quit [Ping timeout: 248 seconds]
arpu has joined #ipfs
physes has joined #ipfs
anewuser has joined #ipfs
<physes>
Not if it's a separate namespace and is clearly delineated as such. you can have two different foo.bar's in different contexts, just like people can create the same username on different platforms. If there is no problem with overlapping user-namespaces then I don't see the issue here
Foxcool has joined #ipfs
pfrazee has joined #ipfs
anewuser has quit [Read error: Connection reset by peer]
anewuser has joined #ipfs
G-Ray has joined #ipfs
physes has quit [Quit: Page closed]
rgrinberg has joined #ipfs
PseudoNoob has joined #ipfs
zorglub27 has joined #ipfs
physes has joined #ipfs
physes has quit [Quit: Page closed]
VegBerg has quit [Ping timeout: 244 seconds]
G-Ray has quit [Ping timeout: 260 seconds]
wuch has quit [Quit: WeeChat 1.5]
VegBerg has joined #ipfs
<kumavis>
daviddias: alo/
<kumavis>
reviewing last weeks ipfs-wide sync call
<kumavis>
id like to start run webrtc libp2p experiments in metamask
taaem has joined #ipfs
<kumavis>
dont need to do anything eth related just yet, but would like to see if we can keep a mesh up and running, and how the health changes over time
<kumavis>
not sure how many concurrent users but 2.8k installs and people tend to leave their browsers running
<kumavis>
are there any utilities for measuring mesh health?
<kumavis>
could also help test flood-sub perf+behavior
Pierette has joined #ipfs
herzmeister has quit [Quit: Leaving]
herzmeister has joined #ipfs
anonymuse has joined #ipfs
zorglub27 has quit [Ping timeout: 260 seconds]
wrouesnel1 has joined #ipfs
ANTI-torture has joined #ipfs
<ANTI-torture>
Fuck all mosad members. Fuck u family,u wife,u daughters!!!!!!!!!!!!!!!!!!!
<ANTI-torture>
Fuck all mosad members. Fuck u family,u wife,u daughters!!!!!!!!!!!!!!!!!!!
<ANTI-torture>
Fuck all mosad members. Fuck u family,u wife,u daughters!!!!!!!!!!!!!!!!!!!
taaem has quit [Remote host closed the connection]
<achin>
ping someone with ops daviddias jbenet Kubuxu lgierth whyrusleeping
<ANTI-torture>
Fuck
<ANTI-torture>
All Jewish
<ANTI-torture>
From fake Israel
ANTI-torture has left #ipfs [#ipfs]
ylp has quit [Ping timeout: 260 seconds]
<wrouesnel1>
does this make sense as a pattern for ipfs: daemon running (as a docker container) on my home fileserver, exposing the API port internally so I can manage it? How would I configure the local ipfs client on my desktop to use this daemon's API by default (and can I secure that, i.e. wrap it with SSL/basic auth?)
ylp has joined #ipfs
chris613 has joined #ipfs
<r0kk3rz>
wrouesnel1: what is your aim?
<r0kk3rz>
sounds like you want to use your fileserver as a gateway
<wrouesnel1>
that's the idea. gateway + local cache (since it has like, 20TB of storage)
<r0kk3rz>
im not sure ipfs is really set up for that pattern yet, unless you set up a http proxy and used it that way
<wrouesnel1>
so that's what I have going at the moment: nginx on the webserver handling the port 5001 ui
<r0kk3rz>
maybe the routing=client option can be used in future for this
<achin>
i wonder if changing the Addressses.API parameter on both your fileserver and your desktop would get you most of the way there
<wrouesnel1>
is there a concise reference for config options? the examples page is a bit sparse...
ulrichard has joined #ipfs
<achin>
not that i know of i'm afraid
anonymuse has quit [Remote host closed the connection]
Oatmeal has quit [Ping timeout: 260 seconds]
JesseW has joined #ipfs
herzmeister has quit [Quit: Leaving]
herzmeister has joined #ipfs
kulelu88 has joined #ipfs
pfrazee has quit [Remote host closed the connection]
physes has joined #ipfs
<kumavis>
daviddias:
cketti has quit [Quit: Leaving]
pfrazee has joined #ipfs
<kumavis>
daviddias: i guess another thing is what is something meshy we can do
<kumavis>
pubsub would be great but im assuming thats not readily available
Oatmeal has joined #ipfs
anonymuse has joined #ipfs
anonymuse has quit [Remote host closed the connection]
anonymuse has joined #ipfs
anonymuse has quit [Remote host closed the connection]
ohmygouda has joined #ipfs
matoro has quit [Ping timeout: 268 seconds]
soloojos has quit [Ping timeout: 245 seconds]
soloojos has joined #ipfs
<Mateon1>
This is frustrating, after a day of fighting with dependency after dependency cause I had the wrong version of Node, I find out that I can't install Orbit on anything. - "Ubuntu On Windows"/WSL: No syscalls for pthreads, trololo; Windows host: "throw new Error('no binary available for os:' + goenv.GOOS)" from go-ipfs-dep@0.4.4-floodsub2
<whyrusleeping>
Mateon1: thats no good :( hey haad any ideas there?
<whyrusleeping>
Kubuxu: the list of hashes you sent me wasnt very well formatted, i hadnt gotten around to backing them up yet
wrouesnel1 has quit [Quit: Leaving.]
SuperPhly has joined #ipfs
palkeo has joined #ipfs
ohmygouda has quit [Ping timeout: 260 seconds]
Encrypt has quit [Quit: Quit]
Tugger has quit [Ping timeout: 260 seconds]
Tugger has joined #ipfs
taaem has joined #ipfs
cemerick has joined #ipfs
Tugger has quit [Ping timeout: 260 seconds]
Gehenna has joined #ipfs
ReactorScram has quit [Remote host closed the connection]
chriscool has quit [Ping timeout: 260 seconds]
matoro has joined #ipfs
Tugger has joined #ipfs
physes has quit [Quit: Page closed]
Encrypt has joined #ipfs
rgrinberg has quit [Ping timeout: 260 seconds]
SuperPhly has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Gehenna has quit [K-Lined]
ygrek_ has joined #ipfs
Encrypt has quit [Quit: Quit]
Tugger has quit [Ping timeout: 268 seconds]
Tugger has joined #ipfs
<whyrusleeping>
Kubuxu: also, on your stress script, you should make it so that gateway requests have to pull from a different node
ygrek_ has quit [Ping timeout: 260 seconds]
barnacs has quit [Ping timeout: 244 seconds]
barnacs has joined #ipfs
JesseW has quit [Ping timeout: 268 seconds]
kevina has quit [Remote host closed the connection]