3600+ entries in 0.021s
mod6: Yup, there are some more that I want to add in there as well. Got them on the conveyor.
mod6: Thanks, asciilifeform
mod6: Lords and Ladies of The Most Serene Republic: The Bitcoin Foundation's vtree has been updated with asciilifeform's Aggressive PushGetBlocks vpatch. The TRB-HowTo Guide has been updated as well.
mod6: jurov: Hi, can you take a look and see if there is an email from me stuck in the btc-dev queue? I did check the signature was valid before I sent, but nothing has been posted yet.
mod6: Well, with that removal, shinohai is clear, and may become a customer if he so desires. :]
☟︎ mod6: Oh perhaps lobbes removed it.
mod6: Oh maybe the deedbot webpage isn't up to date. Lemme check the rep link above.
mod6: Mocky: Like he said, I think he's got another arrangement paid up. But there is the other question of the -2 from lobbes. And there was a rule we put in place a while ago, whereby if a TMSR Lord had neg-rated you, you couldn't become a customer.
mod6: If you and lobbes make amends, you could be a Pizarro customer.
mod6: I've got a boat load of ATC still.
mod6: As long ago as S.WOL closed, the Foundation was started up the same month.
mod6: where does the time go, eh?
mod6: jesus, that was in '14
mod6: thanks for the 0.00000002
mod6: ok, will do. if i even do, they're probably from projects that are not TMSR~ anyway. so who cares.
mod6: Hah, I dunno, maybe I'm making that up.
mod6: Ah, alright. Just thought I'd bring it up as most "CHANGELOG"s that you see out there grow upwards.
mod6: After looking at PeterL's blogpost, was curious if there had been any consideration into if a manifest file should grow up or down (i.e. newest change first, or newest change last in the file). This is purely a cosmetic thing, I suppose it would be up to the author too. Probably why trinque didn't touch on this in the post either
http://trinque.org/2018/06/02/v-manifest-specification/ mod6: Maybe a "developer license" isn't a bad idea either. Could raise some capital, and constrain the source code to those who promise not to share it and who want/need it.
☟︎ mod6: have fun, mircea_popescu
mod6: Identity as such will be condemed, indeed.
mod6: I'm saying in the instance of inquisition. I don't think there is any way to separate a willful liar from someone who lost control of their key.
☟︎ mod6: well, any defendant of such an accusation would have to ask Lordship to /believe/ they didn't do it; not sure how they would ask Lordship to /verify/ they are telling the truth.
mod6: I figured, can't really help it with the old client. Was thinking maybe there is a new one in the works with some stuff that need not be open sores.
mod6: Or am I being retarded here?
mod6: What if, you gave out the S.MG binary client, and along with it, an example client. Void of code that you would consider "trade secrets". This way people can use the example to get their own off the ground with the most minimal information required to do so?
mod6: it does work this way ^, must have key registered with the server to even log in.
mod6: Anyway Gentlemen, I think that currently this comes down to: 1) "How much do I trust the man standing next to me?" and 2) What are the consequences should others betray and leak my valuable assets?
mod6: I see this as even beyond the Eulora scenario, stretching out to any TMSR~ source; I just don't see a good way to solve it right now, other than being selective with who gets rights to see the $src.
mod6: It seems like a burden to thrust these decisions upon the L1 however, should someone defect and leak the sensitive materials.
mod6: and as far as the eulora client, maybe S.MG wants the source to remain closed, this is for them to decide.
mod6: nope, but who knows. maybe someone finds a winner-takes-all-zero-day, to be used at time X.
mod6: I'm not sure that we have the correct abilities to do such a thing at this time, at least on a policy based level.
mod6: I would like for TMSR~ to retain it's own code; for many reasons, including preventing other possible fraud and snake-oil salesmen... a variety of things have been written about on the subject in here actually.
mod6: I'd like to say, that I don't think that it's an over all /bad/ idea, I'm just not sure if it's a good idea either. I think this might just be a case-by-case basis.
mod6: Another thing, I was thinking about was: Perhaps shipping the source to all L1, maybe let people request this themselves.
mod6: Another scenario that I was kind of thinking about is where: Lord X encrypts $src_code, drops it into deedbot, and $src_code is encyptped to {a,b,c,d}. Upon a future date, person 'a', is drummed out and neg-rated. Nothing stops person 'a' from still decypting that $src_code with his key, neg-rated or not. This is not wholly differnt than before... just saying that there's no "backsies".
mod6: Well, my fear is that: Lord X encypts $src_code, to {a,b,c,d} ; as was said before, it would be impossible to tell if $src_code was leaked by X, or a,b,c or d. (This was stated earlier too).
mod6: what may happen in the future; trust between two or more people might not be the same as it is today.
mod6: When given the prospect of asking someone in L1 to hold long-term, or indefinite secrets as opposed to short-term secrets, it gets much harder to evaluate the trust or risk. One can not predict
mod6: I've been trying to see how this doesn't end up with a bunch of finger-pointing once someone's source code is inevitably leaked. (If it can happen, it will happen.)
mod6: From the earlier discussion, I tend to see a lot of points from all sides. And quite an interesting discussion. I've been thinking on it all day.
mod6: Ok well, I'm all caught up here.
mod6: evenin', gonna step through these logs here.
mod6: In other news, BingoBoingo has accepted the position as Pizarro Manager, and officially will take over in this role after the August Statement is published in the first few days of September. Congrats to BingoBoingo!
mod6: This is the current Pizarro BTC balance ^.
mod6: !Qcalc 6.21445021 - 0.46713262
mod6: ignore this ^ some of my previous balance was added into that.
mod6: Remaining Pizarro Balance: 5.83211428 BTC
mod6: !!v 43D6BFBE080DEEA6D24BCF04F12AFCEF9521797DC62C0B3749E97370D586A36C
mod6: !!pay jurov 0.46713262
mod6: Pizarro's bitcoins have been sent to my deedbot account in the amount of: 6.21445021 BTC
mod6: i need the man to stay content with his situation, he's the boots on the ground.
mod6: BingoBoingo: I'm gonna let you think about it for a few days if you need. Think about if you really want to take on major parts of this role. I think you ~can~ do it. But, I don't want you to feel overwhelemed or pushed into it either.
mod6: Hey, nothing against BingoBoingo. At all. He has been through a battle, this is true.
mod6: And I agree that the man could be good at it. But I tend to believe a man when he says "hey, I need instructions, day to day".
mod6: But I missed what you were asking, you were asking if I was going to promote BingoBoingo. I totally didn't even get that until just now.
mod6: <+a111> Logged on 2018-07-02 18:37 mircea_popescu: well... so what are you gonna do, promote in house i suppose ? << you know, when we talked about this a week ago... it never even considered BingoBoingo , not because i think he's not a person or any such nonsense. But because when we started this ventue, he said that he needed strict guidence.
mod6: And to the point of BingoBoingo, he has said before that he wants direction from a manager. As he said earlier tonight.
mod6: I sent out personalized letters to two Lords asking if they wanted to fill the role. I didn't sit back and kick it.
mod6: I have no idea. I'm just trying to swim upstream here, Sir.
mod6: So, a job description would be helpful.
mod6: To your question "hire someone that what ?" : That manages the day-to-day task for BingoBoingo, does accouting tasks (reporting, invoicing, payments), can possibly lend a hand with sysadmin tasks. That sort of thing.
mod6: mircea_popescu: hmm?
mod6: And BingoBoingo, yeah, that's the plan. I'll do the best I can at this, but the more I learn about what was all involved day-to-day with ben_vulpes, the more I'm worried that I'm ill-equiped to do this work.
mod6: Yeah, I need to write up a job description.
mod6: I understand if this doesn't happen right away, but eventually, position will need to be filled. The offer stands, even if it stands for some time.
mod6: (at the end of the month, invoices will be sent)
mod6: mircea_popescu, diana_coman : Give me a thumbs up if you believe the box is ready for you to do your testing, and I'll invoice mircea_popescu.
mod6: No, this isn't really for me. And more-over I have too much to do already.
mod6: I'd like to remind everyone here that Pizarro still desperately needs a manager, please inquire within if you're interested.
mod6: mircea_popescu, diana_coman : Ben and I have been pouring over the numbers (as i'm getting an education here), and the prorated cost for the rest of July for UY3 will be: 0.03542985 BTC
mod6: I'm happy to announce that The Bitcoin Foundation's 2nd TRB node is fully sync'd and will be added to the list of Advertised Republican Nodeds.
mod6: (and update the howto guide with that info)
mod6: <+asciilifeform> mine - yes, iirc mod6's also, and diana_coman's << aha, mine have been good, when the hardware has been sane. so, if I can find the time still this month, I want to add that vpatch to the main vtree @ thebitcoin.foundation
mod6: asciilifeform: oh, interesting, thought it was netbsd
mod6: <+shinohai> goes well mod6 and u? << oh not bad, busy asf.
mod6: hey shinohai, how's it goin?