tmsr - Search: i

48500+ entries in 0.331s

robbinhood: I was trying to learn computer programming

robbinhood: finished highschool when I was 20, then there was 1 year break of study

robbinhood: no but I work as a freelance translator

robbinhood: I'm 25 and still in College

mircea_popescu: "yes im in china" is a very wasteful way to answer that question. try something like x neighbourhood y city, which is so and so and here's a pic i took last week on my blog.

robbinhood: yes, i'm in China. I'm male

RagnarDanneskjol: i identified 4f, 2m

robbinhood: I'm here to talk about the translator position

shinohai: I never understood that, the pop bottle thing. Mexican meth is like super cheap, all but the poorest of poorfags could get some even.

BingoBoingo: Most common use of retirement vehicle I remember from old country is where the fail kids live in their Baby boomer parent's yards.

mircea_popescu: i dunno how this "retirement vehicle" thing became popular (i could guess) ; but it's evident.

shinohai: I can think of no more useful assistant to have in a 3rd-world country. Those 3 am impacted wisdom teeth are no joke.

BingoBoingo: I just have to say, bless Venezuala's economy for making my humiliation sessions so affordable.

shinohai: I guarantee you won't go home hungry.

BingoBoingo: I am in caveman/parrot phase.

mircea_popescu: BingoBoingo i... have my doubts :D

mircea_popescu: diana_coman ah i see, missed that.

mod6: <+trinque> I'll be having wisdom teeth sawed out in a bit. Will be available for botops much later, when various sedatives wear off. << gl!

mircea_popescu: took like 5 passes to make one small enough, also. "i've never done this before".

mircea_popescu: i dunno, one actually got A CAVITY. years ago. dentist dutifully put a tiny obturation on it and that's been all.

mircea_popescu: i still have mine. apparently they work well.

trinque: I'll be having wisdom teeth sawed out in a bit. Will be available for botops much later, when various sedatives wear off.

mircea_popescu: thanks god you said anything lmao, i'd have totally forgotten tis fri today o.O

mircea_popescu: o shit i have to pick up suits today.

Kev: I did my School in China before Uni, and take my degree in Singapore

Kev: But I speak with my parents with Mandarin, and school mate or friend more by Cantonese

Kev: I do both

BingoBoingo: http://btcbase.org/log/2017-12-13#1750325 << Sorry I missed this earlier shinohai. They actually are not on every street corner. What's common are real estate agents. ☝︎

a111: Logged on 2017-12-15 02:34 asciilifeform: http://btcbase.org/log/2017-12-14#1751807 << the fg link goes to my www , naked , which imho is not obviously relevant : i recommend https://archive.is/CGQkR instead

diana_coman: http://btcbase.org/log/2017-12-15#1751825 <- there is the FG banner that is quite obvious; in any case, I'm still hoping there will be a tmsr isp hence the s.nsa shop page back so that I can link to it directly ☝︎

a111: Logged on 2017-12-15 01:57 phf: diana_coman: since you basically split from mpi, i put you into a separate project http://btcbase.org/patches?patchset=eucrypt

a111: Logged on 2017-12-15 01:57 mircea_popescu: diana_coman one that I actually bought link to http://www.dianacoman.com/2017/10/02/some-costs-of-importing-randomness/ neh ? mightaswell...

asciilifeform: http://btcbase.org/log/2017-12-14#1751807 << the fg link goes to my www , naked , which imho is not obviously relevant : i recommend https://archive.is/CGQkR instead ☝︎☟︎

a111: Logged on 2017-12-14 22:51 phf: hmm, there's a bit of complexity there as far as producing files/directories shuffle, which might take longer, but i'll start with paring things down. i haven't yet seen diff/patch sources closely!

asciilifeform: http://btcbase.org/log/2017-12-14#1751803 << at one time i linked to 'diff' src here, when hunting for ordering nonuniformity that turned out to be a uniturdism . it made koch's war crime, look clean. ☝︎

mircea_popescu: diana_coman one that I actually bought link to http://www.dianacoman.com/2017/10/02/some-costs-of-importing-randomness/ neh ? mightaswell... ☟︎

phf: diana_coman: since you basically split from mpi, i put you into a separate project http://btcbase.org/patches?patchset=eucrypt ☟︎

phf: hmm, there's a bit of complexity there as far as producing files/directories shuffle, which might take longer, but i'll start with paring things down. i haven't yet seen diff/patch sources closely! ☟︎

mircea_popescu: but i suppose you're right, a correct v-differ would just follow the extant protocol properly and not have the problem

mircea_popescu: i am in a word proposing to put all the @@ type adnotations in the begining ; and all data at the end

phf: i'm not sure where inband-ness even comes from. patch format has a header of a format 'command used to produce this diff\nsource file\ndestination file\n@@ specific numbers of lines to follow @@\nlines"

phf: i'm not sure this is necessary, patch already contains line count information in the @ ... @ part

ben_vulpes: if i recall correctly, the empty files are necessary to hold the output of trbs compilation process

asciilifeform: i dunno that the addition of a knob to divorce from the idiocy of unixpathism , is really escapable

asciilifeform: and does away with the horror chamber of 'i moved a file, where did the 10 MB of crud come from'

a111: Logged on 2017-01-05 00:29 asciilifeform: so, one possible diff might be : \4\i'm \+15\quite certainly \80\not fucking learning an aminoacid matrix to be able to use diff i tell you that

asciilifeform: the tragicomic part is that i picked plain old diff for vtronics 'so that patches will be readable'

phf: (fwiw so far i've been using patches prelude to stuff metainformation there. one interesting property of patching an already pressed lisp system, is that you don't want a clean press. instead you want to find what state your system is, and then press it further down the chain. but because you don't want to restart the system likewise, you want some additional actions performed as you're moving down the press chain. so i've been using prelude as a place

asciilifeform: you could in phf's unified-namespace thing, but i dun see how else otherwise

mircea_popescu: we evidently also ~could~ add filename to the hash. but i dun wanna.

asciilifeform: mircea_popescu: it's a cmachineism -- 'hey this register CAN haz a 0 in it, ergo lengths of 0 are permissible'. observe that i banished this idiocy from ffa planet

a111: Logged on 2017-11-14 22:08 asciilifeform must invoke herr babbage, 'i cannot rightfully apprehend the confusion of ideas...'

mircea_popescu: tbh i don't even understand why the machine permits such insanity. an empty file is very much a http://btcbase.org/log/2017-11-14#1738478 trigger ☝︎

mircea_popescu: if you put empty files in your project i will personally chase you down in the afterlife.

mircea_popescu: empty files* i mean

phf: (that was by the way how btcbase patcher worked for a long time, until i had to modify it because there are placeholder items in bitcoin source code that are at different filepaths)

mircea_popescu: kinda what i said above

mircea_popescu: i dun get what the problem is.

mircea_popescu: then WHY!!!! can't i use it to move files!!11

mircea_popescu: when i say diff a/foo b/foo, diff fails to output "one is in a, the other in b" as the first fucking item on its list of differences. this is because the (idiots) that made diff thought they gain something by eliding "the trivial case".

phf: diff has two things that it can signal: an addition of a line, and a deletion of a line, which is in line with what it claims to diff, i.e. diffing of lines

mircea_popescu: if i edit glib.c and replace line 50 with "fuck you stallman", and then try to compile glib.c, i get an error. if i edit glib.c and MOVE glib.c to /fuck/you/stallman/glib.c, and try to compile glib.c, i get an error

mircea_popescu: i don't know how it allows if i can't move a god damned file.

phf: but anyway, i'm not convinced that file management is a proper concern for diff. we could add it to a diff format, by placing some instructions in the prelude (which is normally ignored by unix patchers). rm src/foo.c, mv src/foo.c src/bar.c which can be used as instructions for reader with non compliant patchers, or parsed by the vpatcher to be executed. this is all incredibly inband, but conforms to the medium

phf: actually phf-shiva-swank is still broken in the experimental patchset, because it was produced by vdiff/patch combination (vdiff made some claims of shasums, which patch didn't verify. the fact that i should've verified the press is a different question)

phf: well, this goes back to the threads about whether or not it makes sense to patch sigs on your workbench. i use patch in my workflow frequently outside of pressing a tree to bring things from one state into another. i might have a dozen of unsigned patches, that i'm working with that won't see the light of day

phf: i don't think that's a good idea, but i can't articulate an objection. vpatch now needs to know about your wot and wot management, or else the process of patching now becomes explicitly providing a pub key, a corresponding sig and a vpatch itself.

phf: i thought that's what you were talking about?

phf: from that perspective both vdiff and vpatch ~could~ also produce a corresponding sig, in which case the protocol is that patch/diff produce an always valid vpatch (i.e. vpatch/sig combination)

phf: chain validation needs to only go as far as "does the hash on the file that i'm about to patch corresponds to what i expect"

phf: well, signature validation is done by gnupg, i don't see any reason to bring that whole thing in, and there's very little reason to system("gnupg ...")

phf: take existing stuff, strip it down to just what we already have -ruN functionality. i think that the actual tools should be vdiff and vpatch, that is they do shasuming themselves and produce proper vpatches/apply proper vpatches, but without chain or signature validation.

phf: http://btcbase.org/log/2017-12-14#1751602 << i have some ideas of the first steps, that is i can make backwards compatible vpatched diff/patch ☝︎

a111: Logged on 2017-12-10 21:23 nocko: I was linked to FFA guide, started looking around and am now here. I cannot say that I yet have half an idea what's going on... but hello.

a111: Logged on 2017-01-05 00:49 mircea_popescu: i do not wish to live in a world where people can make patches consisting of 512kb lines of a

mircea_popescu: maybe he bites the bullet and makes special files. or who the hell knows. i'm curious.

mircea_popescu: i'm letting him contribute, what. he understands what the problems are.

asciilifeform: it's what i do for a living.

mircea_popescu: in fact, i expect it will be the MAJORITY of work for humans in the future.

asciilifeform: fwiw i do it ~all day, ~every day.

asciilifeform: if mircea_popescu decides to have the eulora programmers not only copy the thing verbatim, as if v never existed, but to retype it, and whack'em with a stick for each mistyped letter, who am i to object . it's his proggy.

mircea_popescu: yes we don't have a gns yet, but this doesn't excuse us from... doing the same computations by hand as if we had it! it's not suddenly allowable to go "well since i have no running water i therefore do not wash". no bitch -- since you have no running water, you walk fifty miles uphil each way to GET water in a bucket. still wash.

a111: Logged on 2017-12-14 16:13 phf: rs~ might a little bit more meaning out of the press namespace. one pill to satisfy later group of people would be to come up with a filesystem hierarchy standard, i.e. you always press at the same root, but you're pressing into a tmsr namespace. so it'll be /bin/bitcoin/... /lib/mpi/...

mircea_popescu: http://btcbase.org/log/2017-12-14#1751486 << i considered this. it's not evidently broken, but i think it subtly is broken, and the principal cause of the failure of the unix actually -- a failure to correctly handle namespaces. ☝︎

a111: Logged on 2017-12-05 15:11 asciilifeform: and in general i dun expect any of it to be paid for, there is no tradition of any such thing. but i do have the possibly naive expectation of the work not to be shat on.

a111: Logged on 2017-12-14 15:39 asciilifeform: i.e. why can't 'eucrypt' be a ~sibling~ dir to 'mpi'

a111: Logged on 2017-12-14 15:38 asciilifeform: the 1 thing i still don't fully understand is why diana_coman's subdir gotta move

mircea_popescu: that's also why poor people, stupid people (but i repeat myself) and socialists, "democrats", pantsuits etc are so fucking unfunny. too hope-y, or rather, their intellects are too dysfunctional to handle contradiction, of whatever kind.

asciilifeform: ( and the supposed converter boxes, dun work worth a shit. ) but iirc i already mentioned this.

ben_vulpes: yeah, this i know.

asciilifeform: possibly i can guess what ben_vulpes wanted... answr is, there is 0 ionospheric propagation at any of the spectrum the cheapo rtl dongle is able to pick up.

asciilifeform: http://btcbase.org/log/2017-12-14#1751421 << ben_vulpes wtf is 'low bandwidth radio space' ??! how does this differ from 'low thickness physical space' ? how do i parse yer sentence ? ☝︎

phf: err, yes, i was going to say slackware, but they are sloppier than bsd

asciilifeform: i like phf's unification idea. even if it means that at some point i gotta regrind fg-genesis.

phf: actually, i think fg is the only exception

asciilifeform: i happen to see the entire unix directory scheme as idiocy

phf: rs~ might a little bit more meaning out of the press namespace. one pill to satisfy later group of people would be to come up with a filesystem hierarchy standard, i.e. you always press at the same root, but you're pressing into a tmsr namespace. so it'll be /bin/bitcoin/... /lib/mpi/... ☟︎

asciilifeform: though i'll admit that i personally dun get the fixation with moving mpi to being a subdir of $newproj.

asciilifeform: i'ma leave it for diana_coman , mod6 , phf , mircea_popescu , et al, to consider which pill is less barfatronic, and possibly conceive of another.

phf: i didn't necessarily need the illustration, because i understood what you were saying, my point was merely that it's sad state of things