46200+ entries in 0.319s
a111: Logged on 2017-12-15 23:05 asciilifeform: 'Shahnaz took out more than
a dozen credit cards earlier this year and used the money she borrowed to buy cryptocurrency and send it abroad, according to an indictment filed by US attorneys in federal court.'
a111: Logged on 2017-12-15 20:02 BingoBoingo: Any waterfalling continues to fail: "In
a court filing, prosecutors noted that due to the volatility of the Bitcoin market, both coins risk losing value. Both the BTC and the BCH have already been transferred to government-controlled wallets. The new round of seized digital currency belonged to
a Utah man named Aaron Shamo, whom prosecutors say led
a multimillion-dollar ring of counterfeit pharmaceuticals, including oxycodone and
ben_vulpes: as i said recently to
a friend, "heck yeah that sounds like just the thing the world has been missing until right this very moment! buy anything other than bitcoin, wouldja? keep malia free for another decade..."
ben_vulpes: This is where the special features of MobileCoin come in. The currency is designed to utilize an Intel processor component known as Software Guard Extensions, or
a "secure enclave."
ben_vulpes: it's really the only way they can make waves about folks doing this kind of deed. anyone with half
a brain
a) is not entrappable like this b) has the requisite half ounce of paranoia to foil the wallet inspectors at ft meade
BingoBoingo: alprazolam that were sold on Dark Web marketplaces. Shamo was arrested over
a year ago -- his trial has not yet been scheduled. On Tuesday, US District Judge Dale Kimball allowed the sale to proceed. Once sold, the money would go to an account held at the Treasury Executive Office for Asset Forfeiture."
BingoBoingo: Any waterfalling continues to fail: "In
a court filing, prosecutors noted that due to the volatility of the Bitcoin market, both coins risk losing value. Both the BTC and the BCH have already been transferred to government-controlled wallets. The new round of seized digital currency belonged to
a Utah man named Aaron Shamo, whom prosecutors say led
a multimillion-dollar ring of counterfeit pharmaceuticals, including oxycodone and
☟︎ shinohai still has all the re-written #b-
a wiki articles nonetheless ....
shinohai: I've been meaning to do
a totally new, 2018 trilema writeup of all that.
mircea_popescu: shinohai was there
a noob primer for this i keep forgetting
mircea_popescu: in the meanwhile -- it'd be
a very good idea to make yourself
a pgp key and register it with deedbot.
mircea_popescu: you worded as
a freelance translator online, on one of the "hire freelancers" websites, such as freelancer.com
robbinhood: no but I work as
a freelance translator
mircea_popescu: is this your last year ? or is it
a 2nd undegraduate you're completing ?
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.
mircea_popescu: "economic unpriviledged status" is always
a personal failure.
shinohai: Rolling RV meth labs are
a close second.
BingoBoingo: Retirement vehicle is
a different kind of poverty than trailer park. Trailer park trailer is not mobile denotes still greater poverty.
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: Turns out self study and hardware store spanish was insufficient to offer
a tremendous fluencey on arrival, so venezualan girl has been retained to speed up the fluency acquisition process.
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: i dunno, one actually got
A CAVITY. years ago. dentist dutifully put
a tiny obturation on it and that's been all.
BingoBoingo: In other discoveries... My venezualan spanish teacher is
a dentist by training.
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: in case anyone's curious, the 20 bux was for encouraging the folk who made viking age, which is
a quite passible browser game. sorta old warcraft style graphically, othertwise
a tower defense married to the old bonbon "city development" azn thing.
☟︎ mircea_popescu: Kev ok, so you're
a guy, living in shenzen (where ?), and you'd like to work for the republic.
RagnarDanneskjol: Kev - Mircea is here if you'd like to talk to him about the translation work and tell him
a bit about yourself
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!
mircea_popescu: that came out
a lot dumber than intended. how about "plenty of time yet"
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!
☟︎ lobbesbot: Logged on 2017-12-14 22:44:09: <danielpbarron> this is
a real testement to quality of S.NSA and its products
mircea_popescu: in other news, anyone wanna do
a 20bux paypal for me ?
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: yes, and they won't make
a difference!
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: the reason why we have issues with +++ and --- is because vdiff specifically ignores the @ ... @ bits when postprocessing
a patch.
a complete vdiff-er wouldn't have to do that kind of post processing and can produce
a valid patch always
a111: Logged on 2017-12-14 19:55 mircea_popescu: you ~could have
a diff format whereby first line is x y z with x = total line count, y notation line count z data line count, and then instead of +++ --- bs you just have line count references in the notation part.
mircea_popescu: asciilifeform you don't specifically need
a manifest, as per discussion (have you been reading the discussion ?) ; can just follow the hashes.
a111: Logged on 2017-12-14 21:16 mircea_popescu: but this is why this discussion was so important : it has in fact emerged that the correct implementation of diff would first
a) calculate hash of all files in each dir ; then b) process moves and only then c) do the diffing.
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
a111: Logged on 2017-12-14 20:59 trinque: problem stemming from that unix uses file path as
a matter of identity, and allows this to be mutable (!)
phf: mircea_popescu: well, empty file does have
a shasum
mircea_popescu: phf no such thing as empty lines. put
a fucking comment in there.
mircea_popescu: anywya, this system'd be purrfect : if hash unchanged, "this is THE SAME file by
a different name (or path, same thing" ; if hash changed "this is DIFFERENT FILE by same name"
phf: not restricted to moves by the way, there's also copy. there's
a certain symmetry lost though. if you say make
a genesis with 3 empty files
a b c, then they are fresh line patches. but the patch against that that creates another 3 empty files puts cp
a x; cp
a y; cp
a z; in the prelude instead
mircea_popescu: but this is why this discussion was so important : it has in fact emerged that the correct implementation of diff would first
a) calculate hash of all files in each dir ; then b) process moves and only then c) do the diffing.
☟︎ 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: also, if it dies
a flaming death in this case that'd be very acceptable, and fuck you for keeping duplicates like that.
phf: what if you have /
a/foo and /b/bar/foo, /b/qux/foo where all foo are identical?
mircea_popescu: this'd require all file movements to be
a separate patch, as you can't both move and edit in the same go. which imo is bonus the right thing
phf: say you have /
a/foo and you have /
a/bar/foo where both foo are identical. you're running diff -ruN
a b, what is the expected behavior?
mircea_popescu: if you have
a :
a/b
a/c and b : b/b b/d/c it is thereby evident upon diffing
a and b that c was moved from
a/ to b/d/ if
a/c contents === b/d/c contents.
phf: you can communicate that information through
a patch format, but that's not something ~diff~ can guess about
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".
mircea_popescu: but you can know that one foo is in
a and the other not
phf: there's no way of knowing without having
a complete history of states whether or not foo was moved or removed
phf: if you do mkdir
a; touch foo; touch
a/foo; mv foo
a/foo;
mircea_popescu: "the difference between
a/fuckyoustallman.c and b/fuckyoustallman.c is 1) that one's in
a and the other in b ; 2) no further"
phf: fwiw diff can't even know that
a file has been moved
trinque: problem stemming from that unix uses file path as
a matter of identity, and allows this to be mutable (!)
☟︎ 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
phf: sure, but diff's way of indicating change is to show what happened to
a file, that is all the lines of the file got deleted
phf: well, moving of the file is
a filesystem operation, what does it have to do with ~diffing~?
mircea_popescu: i don't know how it allows if i can't move
a god damned file.
mircea_popescu: and
a file's fucking name is its absolute path, not the last bit thereof.
mircea_popescu:
a file is not "its contents and AN ARBITRARY TRUNCATION OF ITS NAME"
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