stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.23 and js-ipfs 0.41 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
doubtingben has joined #ipfs
Mx8v has joined #ipfs
<RubenKelevra>
<it-xp[m] "hi there. If I submit too comple"> Maybe that's more suited question for thethe developer channel? #ipfs-dev:matrix.org
<RubenKelevra>
> <@it-xp:matrix.org> hi there. If I submit too complex RFP 0, should I split it into multiple RFPs, which solve problems, close to some listed request? or in that case much adequate publish one big book about all covered directions?
<RubenKelevra>
* Maybe that's more suited question for the developer channel? #ipfs-dev:matrix.org
<RubenKelevra>
But generally I think one large RFP in ipfs/notes would be a good option, for discussion and you can work out a solutions and single steps in a team effort. 🤔
<RubenKelevra>
On the other side, if you have concrete implementation ideas, it might be wise to implement them one by one.
<RubenKelevra>
But that's just a personal opinion.
cipres has quit [Ping timeout: 260 seconds]
evanmn has joined #ipfs
scalar has joined #ipfs
}ls{ has quit [Ping timeout: 256 seconds]
}ls{ has joined #ipfs
<RubenKelevra>
<it-xp[m] "That is a problem - I have a few"> Okay, that's WAY bigger than expected. I would maybe break it down into topics: Some seems to be protocol related, some cryptographical related, some more philosophical and some are UIX.
<RubenKelevra>
But some topics sound REALLY cool! Thanks for sharing your thoughts and the work you put into it!
dqx_ has quit [Ping timeout: 265 seconds]
doubtingben has quit [Ping timeout: 265 seconds]
scalar has quit [Ping timeout: 240 seconds]
fleeky has quit [Ping timeout: 256 seconds]
llorllale has quit [Quit: WeeChat 1.9.1]
Belkaar has quit [Ping timeout: 265 seconds]
jcea has quit [Quit: jcea]
Ecran has quit [Quit: Going offline, see ya! (www.adiirc.com)]
KempfCreative has quit [Ping timeout: 265 seconds]
treora has quit [Remote host closed the connection]
ygrek has quit [Ping timeout: 256 seconds]
treora has joined #ipfs
MDude has quit [Quit: Going offline, see ya! (www.adiirc.com)]
_whitelogger has joined #ipfs
Angel has quit [Read error: Connection reset by peer]
joocain2 has quit [Ping timeout: 240 seconds]
joocain2 has joined #ipfs
dwilliams has quit [Ping timeout: 258 seconds]
storms_ has joined #ipfs
fleeky has quit [Ping timeout: 256 seconds]
RBB has quit [Remote host closed the connection]
airgapp has joined #ipfs
fleeky has joined #ipfs
gimzmoe has quit [Ping timeout: 265 seconds]
gimzmoe has joined #ipfs
fleeky has quit [Ping timeout: 265 seconds]
fleeky has joined #ipfs
fleeky has quit [Ping timeout: 256 seconds]
ylp has joined #ipfs
fleeky has joined #ipfs
bengates has joined #ipfs
bengates has quit [Remote host closed the connection]
bengates has joined #ipfs
mytekp[m] has joined #ipfs
drathir has quit [Ping timeout: 264 seconds]
mytekp[m] has left #ipfs ["User left"]
drathir has joined #ipfs
nodewire has joined #ipfs
drathir has quit [Ping timeout: 265 seconds]
<TraderOne[m]>
how to tag bug report as 0.5 specific
drathir has joined #ipfs
<aschmahmann[m]>
I don't think there's a specific Github label, but when you file the issue you should definitely fill out the recommended information in the template which includes the version, OS, how you produced the bug, etc.
<aschmahmann[m]>
Trader One: ^^
RingtailedFox has quit [Ping timeout: 260 seconds]
<TraderOne[m]>
How to add label to report? I do not see it
rendar has joined #ipfs
<aschmahmann[m]>
labels are on the right side of the page in Github, but if you file a bug it will automatically be tagged as a bug which should be all you need
<aschmahmann[m]>
similarly the enhancement and feature request templates automatically add the labels
pecastro has joined #ipfs
fazo96 has joined #ipfs
jeeebz has joined #ipfs
<jeeebz>
Hello there !
<jeeebz>
How can I check that go-ipfs is build with openssl ?
Pie-jacker875 has quit [Quit: No Ping reply in 180 seconds.]
Pie-jacker875 has joined #ipfs
JRWR has quit [Read error: Connection reset by peer]
JRWR has joined #ipfs
ipfs-stackbot has quit [Remote host closed the connection]
Alkhemy has quit [Quit: ZNC 1.7.5+deb1~bpo10+1 - https://znc.in]
zopsi has quit [Quit: Oops]
Alkhemy has joined #ipfs
zopsi has joined #ipfs
ipfs-stackbot has joined #ipfs
nodewire has quit [Quit: exit]
micro` has quit [Remote host closed the connection]
dethos has joined #ipfs
MDude has joined #ipfs
Ecran has joined #ipfs
<TraderOne[m]>
siderus is the same as ipfs-desktop?
<swedneck>
it's different code, but it performs the same function
<swedneck>
fwiw there's a room for siderus orion: #siderus-orion:matrix.org
gimzmoe has quit [Ping timeout: 256 seconds]
<TraderOne[m]>
I haven't used any of these. For regular user its just interface to MFS?
airgapp has quit [Quit: airgapp]
rardiol_ has quit [Ping timeout: 250 seconds]
<swedneck>
you can look at https://webui.ipfs.io, it's 90% the same thing as ipfs-desktop, just in the browser
gimzmoe has joined #ipfs
xcm has quit [Killed (livingstone.freenode.net (Nickname regained by services))]
<it-xp[m]>
I have one question about grants, which touch political nuances. I am live in Crimea, which is region under US sanctions. From one side, I'm understand that a decentralized free community here, but in case if I am, or somebody like me, will awarded for own R&D a grant, it can caught some problems with receive money, if sender under US laws, or GB, or other political structures, which support sanctions too. Do someone reach
<it-xp[m]>
same problems, or IPFS community oversovereign and if idea really cool, it will granted in any case?
<TraderOne[m]>
it-xp: get swiss bank account
RBB has joined #ipfs
fleeky has quit [Ping timeout: 260 seconds]
<it-xp[m]>
Trader One: hm... I hope it will be ease for me, because it can reach same problem. thanks for advice
kivutar has quit [Ping timeout: 265 seconds]
<lordcirth>
Trying to build rc1 as a nix package - getting "build ./coverage/main: cannot find module for path ./coverage/main"
<lordcirth>
All I did was change the source from 0.4.23, and change to go 1.13. Is there something else I need to change?
fleeky has joined #ipfs
kivutar has joined #ipfs
fazo96 has quit [Ping timeout: 256 seconds]
fazo96 has joined #ipfs
mighty-pirate[m] is now known as difmul-nislur[m]
<it-xp[m]>
<TraderOne[m] "it-xp: get swiss bank account"> nop. it is not a variant for me, because I have no money for minimum deposit. We are works on that R&D a long time, all team members must works in different commercial spheres just to survive, working in parallel on our projects, driven by one enthusiasm, for example I am live on $400 per month, which is give me one my friend just for allow me do what I do without interruptions on
<it-xp[m]>
side tasks, but others have a families and dramatically low income. That people are geniuses, but they have to sell their time in order for allow some capitalist to earn money by common business. That why we are need support - for free needed people from banal everyday problems, break they day of hamster and direct all their creativity and passion to really great things.
benjamin_w has quit [Quit: Connection closed for inactivity]