--- Log opened Tue Jun 02 00:00:40 2020
00:04 -!- guest534543 [~mix@194.213.208.81] has joined #rust-bitcoin
00:08 -!- Kiminuo [~mix@141.98.103.196] has quit [Ping timeout: 256 seconds]
00:09 -!- guest534543 [~mix@194.213.208.81] has quit [Ping timeout: 260 seconds]
00:53 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
01:17 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #rust-bitcoin
03:02 -!- Nash84Glover [~Nash84Glo@static.57.1.216.95.clients.your-server.de] has quit [Remote host closed the connection]
03:05 -!- Taya34Lockman [~Taya34Loc@static.57.1.216.95.clients.your-server.de] has joined #rust-bitcoin
03:13 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
03:47 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Remote host closed the connection]
05:47 < yancy> One of the reasons I prefer cargo is i'm no expert when it comes to Makefiles, and a really complex Makefile makes c++ with many/complex dependencies too complicated imo.  Besisdes that, maintenance of build deps can lead to a much slower development cycle if upstream deps are changing rapidly.  I have a much easier time keeping up with bleeding edge changes with Cargo than counterparts using C++ and
05:47 < yancy> makefiles.  Granted, cargo and package managers introduce a security hole if you're not vetting the dependency and also not pinning to a specific version so updates can be vetted.
05:48 < yancy> Something I'm not sure if Cargo does, but there is another avenue to introduce a trojan horse if you pin to a version and then the author maliciously changes that version.
05:49 < yancy> seems like that could be solved by hashing the contents along with the version.
05:50 -!- Taya34Lockman [~Taya34Loc@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 265 seconds]
06:51 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #rust-bitcoin
07:03 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-wfhuaxymifzteebb] has quit [Quit: Idle for 30+ days]
08:24 < andytoshi> in fairness cargo does do this, sorta
08:24 < andytoshi> if you try editing the source in your .cargo/ cache it'll notice the hash doesn't match and refuse to compile
08:25 < andytoshi> and if you have a project with a committed Cargo.lock you can be assured that everyone is using the same code
08:25 < andytoshi> it's just that these hashes aren't easy to compute independently and aren't easy to map to any particular git commit
08:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
08:32 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
08:56 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
09:23 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined #rust-bitcoin
09:33 < dpc> Cargo packages do contain git reference BTW, IIRC.
09:33  * dpc sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/kZbOPsPOyfzmgQyvfkEBmbXM >
10:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
10:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
10:11 -!- dr-orlovsky [~Dr_Orlovs@31.14.40.19] has joined #rust-bitcoin
10:23 < dr-orlovsky> sorry guys, I've been out from here for a while - got my server hardware crash so it took some time to get it back. Now will be online checking the logs more regulary
10:23 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory]
10:40 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined #rust-bitcoin
10:43 < notmandatory> Hi all, is there a mailing list or some other forum for longer questions / discussions about using rust-bitcoin projects?
12:34 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
12:34 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
12:42 -!- belcher [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
13:49 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
14:00 < andytoshi> notmandatory: fraid not
14:00 < andytoshi> usually for long discussions people make issues in the rust-bitcoin project
14:01 < andytoshi> even if they're about other projects
14:01 < andytoshi> e.g. there is a long discussion about the minimum rust version there
14:03 < notmandatory> ok thanks andytoshi I might try that.. I'm thinking about creating a mattermost instance for my project, do you think rust-bitcoin ppl would be interested if I created an instance for this project too?
14:04 < andytoshi> if you still need a js-enabled browser to use mattermost, my guess is no
14:04 < andytoshi> lots of people here access IRC by ssh'ing into a server running screen
14:05 < andytoshi> so you really need a text client
14:05 < andytoshi> i have the same issue with slack, rocket, discourse, etc
14:05 < andytoshi> zulip
14:05 < notmandatory> oh I didn't consider that. OK I'll think about that
14:05 < andytoshi> it is probably true that we are losing contributors, on net, by being IRC only
14:05 < andytoshi> but i don't see a good solution
14:06 < notmandatory> I guess a piped tcp connection doesn't cut it due to leaked browser info
14:07 -!- Reyes78Rolfson [~Reyes78Ro@static.57.1.216.95.clients.your-server.de] has joined #rust-bitcoin
14:07 < andytoshi> the issue is not so much privacy for me (thuogh it is for some people) but (a) a general distrust of running javascript from services/apps that are visibly designed against my interests
14:07 < andytoshi> and (b) the logistical difficulty of always being connected, keeping track of unread messages etc
14:07 < andytoshi> in my experience browser based chat programs are uniformly bad at this
14:08 < andytoshi> like, switching channels requires a server roundtrip and hundreds/thousands of ms of latency
14:09 < notmandatory> but with IRC isn't history harder? unless you frequently check the archives
14:09 < andytoshi> not if you're connected 100% of the time :P
14:09 < andytoshi> if you are, yuo have local logs, which are much -easier- than online histories
14:09 < andytoshi> because you can run grep/sed/etc on them and it's extremely fast
14:10 < andytoshi> i think IRC has some means to store history and provide it to people when they first connect. idk if no clients support it, or if freenode doesn't support it, or what, but i've never seen it used in practice
14:10 < andytoshi> but i read some article that claimed it was a thing :P
14:12 < notmandatory> i see.. maybe I'm just not running the right tools will have to investigate that too.. i've just been connecting my client sporadically.. and checking gnusha.org logs otherwise
14:43 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory]
14:46 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Remote host closed the connection]
14:47 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
14:51 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Ping timeout: 240 seconds]
14:52 < gwillen> andytoshi: "IRCv3" might have that, but IRCv3 is fake, it's a speculative protocol that nobody implements
14:52 < gwillen> I think one of the most popular IRC bouncer servers has a protocol for requesting history from the bouncer to the client that might be the closest thing to a standard for this that actually exists
14:55 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined #rust-bitcoin
14:59 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Client Quit]
15:06 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined #rust-bitcoin
15:28 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
15:29 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Quit: notmandatory]
15:30 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has joined #rust-bitcoin
15:30 -!- notmandatory [~textual@cpe-76-169-37-102.socal.res.rr.com] has quit [Client Quit]
15:33 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Ping timeout: 258 seconds]
16:00 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
16:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
16:08 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
16:13 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Ping timeout: 260 seconds]
16:39 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
16:50 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Remote host closed the connection]
17:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
17:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
17:04 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
17:46 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Remote host closed the connection]
17:47 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
18:29 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Remote host closed the connection]
18:34 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
18:39 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Ping timeout: 272 seconds]
20:07 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has joined #rust-bitcoin
20:37 -!- surja795 [~surja795@c-24-62-248-154.hsd1.ma.comcast.net] has quit [Remote host closed the connection]
--- Log closed Wed Jun 03 00:00:40 2020