log☇︎
152800+ entries in 1.205s
mircea_popescu: there ISNT a bmw here. it's varnish or nginx. that's it. not like i'm running unheard-of-software
mircea_popescu: i can buy a fucking bmw.
mircea_popescu: see jurov, the thing is... i have the OPTION to not own obscure exotic cars whose maker went out of business shortly after starting because he sucked.
jurov: i have 14y old daewoo, we can split "never ever" hairs but the end result and frustration is the same
mircea_popescu: "musta been a different car - and - gasoline combination i guess. going back (on foot) to gas station trying some more combos"
mircea_popescu: "yes i know five billion people found it before. and yet..."
mircea_popescu: "sorry honey, can't come to dinner, i'm apparently unable to find the entry to the brooklyn bridge today"
jurov: and i don't enjoy that, too. but such is life.
jurov: haven't i wrote somewhere that every productive day ends with patch or bugreport?
mircea_popescu: it would have been cheaper to buy a server. if i were to bill 8 hours it'd be enough to buy a fucking rack, and that's for doing stuff i actually like doing.
mike_c: nginx always works. I have never been disappointed in it. Recommending shit to people is always a -EV process, but.. ☟︎
mircea_popescu: finally found a way to do that. EXCEPT it injects random data at random intervals, i end up with "ips" like "8�b]"
williamdunne: jurov: "Because potentially it could make money, its an excuse to learn more tech, and there is little risk in terms of what I could lose by doing it"
trinque: jurov: sounds like someone who doesn't deserve a loan begging with "no dude, I'll like, do anything, man!"
mircea_popescu: mike_c yeah, im a day wasted in here. i could waste another one. sure.
williamdunne: I mean the platform, not the general idea of selling future income
williamdunne: Its not really a unique idea though, been done twice as far as I can tell. Both started in US but had obvious legal issues come up
williamdunne: Indeed, I'm not talking bout some sort of service where 100 people deposit money and then a "money manager" decides who to invest in
assbot: Logged on 28-04-2015 16:33:22; williamdunne: i.e I sell 40% of all my future income for xx btc today
cazalla: http://log.bitcoin-assets.com/?date=28-04-2015#1113823 <<< but the grocer isn't engaged in things similar to the mafioso such as robbing other businesses, so i don't see how the analogy fits.. if ya gonna throw rocks, steal beauty products and impede mr fireman's ability to put out fires by cutting hoses, why not open up on them too? ☝︎
ascii_field: i'd be open to a purely gnumake-based thing instead of the sh ☟︎
trinque: just thinking through it; I have no need to change nor authority to change a process that works for them
trinque: to synthesize one point from that pile, I want the computer to strongly enforce relationships for me, not to mindlessly build because I'm too lazy
trinque: this is how I build out to current release
trinque: ok, this is how I get to the point where I can work on feature X
trinque: that's really *all* I want
trinque: ascii_field: if there were even something which made the relationships between patches data, I would be satisfied.
ascii_field: davout: i took an 'aerolinas argentinas' bag home
davout: ascii_field: i have some "Air France" branded ones if you're into sophisticated barfing
trinque: I promise to barf myself if XML creeps in
ascii_field: when i suddenly am expected to care what's in some xml turd, or expose a box to the net just to fetch changes, or similar atrocities - i reach for barf bag
trinque: I agree
ascii_field: for the record, i use all kinds of odd tools internally
ascii_field: trinque: and if any of you produce a 100kB patch, and i barf on general principle and refuse to have anything more to do with project, don't say i didn't warn that vcs is harmful.
ascii_field: use it, so long as i don't have to know anything about it
davout: if darcs is able to output clearsigned unix patches i really don't see a reason not to use it, we can still review small individual units of work, and ascii_field's patches integrate gracefully
ascii_field: i can't pipe a branched repo to a line printer
trinque: git solves this problem, and I can even email you a patch directly out of git
ascii_field: and more importantly, wtf should i have to care
trinque: but then I've been all through the internals of it
trinque: I don't agree with "hidden" re: the state of git
trinque: it's a shitty interface and I'm not dealing with it
trinque: I think hackers here would just like to collaborate via something other than email
trinque: I agree 100% that "canonical" as the outside world is made to see it should not be a git repo
ascii_field: it is how i specified a de-crufted subset of 0.5.3's files on day 1
ascii_field: it is worth repeating precisely -why- i specified 'unix patches' to be the canonical representations
trinque: ben_vulpes uses git in his day to day work, and I'm sure for a reason
trinque: sure, I see room for collaborating on feature branches though
ascii_field: i mean, when you write own contributions, you can generate them however you like
trinque: ascii_field: I would be pleased with a process that allowed for that, but that there is only one route to "released"
davout: ascii_field: i hear your points
ascii_field: i don't have the neutron bomb yet. so we're stuck with flamethrowers
trinque: ascii_field: I am referring to you, not an industry
ascii_field: trinque: it is a mistake to conclude that i am bringing deep wisdom from some 'respectable society' profession here. i am deliberately and profanely pissing on 'best practices'
trinque: and I respect that
trinque: it should be noted that ascii_field's profession as I understand it is knowing how attacks occur
ascii_field: but this is not what git aficionados want. they expect -me- to use it if i want to participate
ascii_field: Adlai: it is a mistake to conclude that i trust
trinque: right, I can guarantee at least that I have no qualms screaming at a person that's done wrong
davout: ascii_field: i'm with trinque here, it's a social problem, not to be solved by tools
trinque: the process of managing a bunch of feature branches and shit, I want a tool
williamdunne: Ah okay, not sure if I can help with that.
trinque: gits data model is... lemme see if I can remember; it's been a while since I wrote a postgresql fdw into it
ascii_field: i do -not- want nonhumanreadable state in source.
davout: they're functionally equivalent, but i guess that if darcs is a better fit, why not
Adlai: the real problem is technophobia, "I trust nothing other than butterflies and sed"
davout: Adlai: you're probably right, i think the difference isn't that important though, the point of the wot is to make an identity valuable
davout: trinque: that's one thing, the other is: whenever i pull i want to verify it independently
davout: Adlai: well, from what i understand of the docs, you can sign -individual commits- which is a new feature because originally it could only do what you say
trinque: prudent I think to discuss which DVCS to use
williamdunne: I'll keep my commits thank you very much
davout: mircea_popescu: i think you can sign commits, also it can't really be less gpg-friendly than throwing tarballs around
trinque: I am also in favor of git
davout: while github is not an option i'm with williamdunne here, git is nice and having a foundation-operated git server would be a good thing imo
trinque: not committing to it while I can't guarantee I'll execute
trinque: if I find the time maybe I will
trinque: who says I am
jurov: should i make such list? and on therealbitcoin or some other domain?
williamdunne: Ahh, I assumed MP meant the varnish code
mircea_popescu: jurov how do i contribute signed non-bitcoin code to the great codex ?
jurov: i see
mircea_popescu: someone be so kind to leave a comment on trilema so i see if teh ip is alright ?
mircea_popescu: i think i actually got it.
lobbes: <williamdunne> ... If I believe paymium will possibly fail, but that you're going do something great in the future, I would be better off investing in you than paymium << In this case, wouldn't you just wait until he creates the project you think -will- succeed and invest in that?
mircea_popescu: anyway, at least now i know what needs fixing
mircea_popescu: heh. mkay, i got it, now it's terribly broken :D
williamdunne: davout: If I believe paymium will possibly fail, but that you're going do something great in the future, I would be better off investing in you than paymium ☟︎
davout: that's kind of a basic mistake here, assuming you can invest in things, if I buy a bitcoin asset I'm really investing in the people running it, not in some ethereal abstract "thing"
williamdunne: Its also more restrictive, as its not restricted to projects. i.e a student could use it if doing some sort of professional degree
williamdunne: X Y and Z have a number of other metrics you can use to attain success i.e revenue growth
davout: "i didn't even get to try projects X and Y because the market told me it was retarded", on the other hand Z was pretty successful"
williamdunne: I'm hoping it just increases the velocity, so shitty stuff fails sooner and good stuff succeeds sooner
mircea_popescu: and if i do, it's wasted.
mircea_popescu: 448 lines. i am not happy with a dollar a line. not that i'm getting paid or anything.
mircea_popescu: moreover, if i do know some guys who trust him, the cost of obtaining a new Takashi Takizawa is not equal to s/Takashi Takizawa/Takashi Takizawa/
mircea_popescu: but maybe i know someone who does trust him ?
mircea_popescu: just another $500 an hour service i do for the world.
mircea_popescu: yeah, i am looking forward to reviewing random code for free.
mircea_popescu: so what's the wot vote, do i thank " Takashi Takizawa" for his work and download random code offa da github ?
davout: i don't get how the structure can be "dynamic modular" and then "cause problems" when stuff isn't built right into apache