mircea_popescu: in other postapocalyptica, this is how the "civilised world" looks nowadays : https://pbs.twimg.com/media/C2ngov8WgAA6ctd.jpg
mircea_popescu: because somehow the astroturf "democratic" groundswell failed to materialize. but it's all ok.
mircea_popescu: and on the other side of idiot isle, theguardian (NOT A FAKE NEWS! NOT A FOREIGN INFLUENCE AGENT!) is doing about 50% of the official coverage ; quotes soros (NOT A US-CONVICTED FUGITIVE!) and harps about how in 2015 trump might have hired actors to clap.
mircea_popescu: and in other lulz, 208.178.195.210 (global-crossing-argentina-s-a.xe-0-1-0.ar3.eze1.gblx.net) is currently losing about half my traffic
mod6: but I'm so glad I wrote these.
mod6: these automated tests could use some serious cleanup and refactoring -- they work fine, just not very pretty, etc.
mircea_popescu: phf the problem with the bolt-ons being that why are you bolting on, use the language of the boltons instead.
mircea_popescu: mod6 there';s a bot you can fuck around with if you wanna try it out.
asciilifeform: so, if it's an x86 box, this means that no opcode executes on it, from cradle to grave, that didn't come out of (hypothetical) compiler with mandatory bounds/type checks.
asciilifeform: mod6: i can't speak for others, but i specifically am interested in a ~0-c~ box.
phf: if you take any of the canonical bignum-in-lisp implementations and port them to tinyscheme, multiplication of one 5 digit number by another 5 digit number takes ~seconds~. optimization is left as an exercise. i suspect some of the routines can be implemented as opcodes.. you could also take that numeric thing asciilifeform extracted out of gnupg and bolt it to tinyscheme as a PoC
asciilifeform: mod6: theoretically. but, as phf observed earlier in this thread, certain entirely necessary things are impractical to retrofit to it (e.g., bignum)
phf: scheme48 comes closets to sane lisp imo, it was written on a lisp machine, and comes with a lot of very sane batteries (the library is clearly inspired by cl)
asciilifeform: without megatonne of 'libraries' that make the overall mass of the system quickly approach and exceed that of cl
asciilifeform: mod6: scheme is neat on paper (~50 pg. exhaustive spec! at least before the poetterings got to it in rev. 6) but you will find that it is ~impossible to program in the language that appears in that document
asciilifeform: (nor does the old far necessarily deserve anything else)
asciilifeform: defective in all kinds of ways but it isn't as if another is to be had.
asciilifeform: to asciilifeform commonlisp is rather like i imagine an old, nagging wife is for old man
asciilifeform: mod6: i have nfi what 'general feeling' would mean, there is no homogeneous writhing mass here
mod6: (i ask all of the questions because im simply curious, and it seems to be such a broad range of different dialects, if that's even a way to put it)
phf: these days when you say "lisp" you usually either mean an equivalent of "algol" or "common lisp" specifically
phf: then you have a version of LISP for project mac called MACLISP, also capitalized. but it shares so much with LISP that you can call it LISP too
asciilifeform: mod6: it was from early literature, and from dark ages machines with no shift key. and so folx who learn of the existence of lisp from encyclopaedia in school, tend to LISP
phf: well, i think, if you're trying to communicate clearly, LISP means thing that mccarthy wrote, and then spinoffs of that, LISP 1.5, 1.6
asciilifeform: phf: to be fair, the main (other than lisp1-ness) semantic diff b/w scheme and lisp1.5 was static scope. which made its way into cl.
asciilifeform: ftr phf is the one and only serious lisp d00d i ever ran across who capitalized.
phf: this is not really the case with scheme, T, clojure, etc.
phf: there's a lineage of lisp, which is significantly mutually compatible. LISP, maclisp, interlisp, zetalisp. common lisp is a standardization attempt on top of those. for example if you take eliza code (written for LISP 1.5) you can make it run on common lisp without any transformations (need to provide some missing forms though)
mod6: <+phf> no in scheme land you have mit scheme and scheme48 << with these, which one is more preferred? or why choose one over the other?
asciilifeform: mod6: likewise, there are cltrons (e.g., sbcl) that -- at least in theory -- can compile selves to x86
asciilifeform: the c?
mod6: is there any big hang-ups about chicken scheme?
phf: asciilifeform: i wonder how much of scar was removed in sbcl. i know while newman was still hacking, he removed a lot of gunk. i vaguely suspect that cmucl can't be improved without tackling the bootstrapping problem, which is probably going to look very similar to sbcl's solution
asciilifeform: also the thing is chock-full of os-specific conditionals
mod6: oh, yeah. almost forgot... having the feather stems in the pillows is the worst. i refuse to use them for that reason. nothing worse than those things poking you in the face.
mircea_popescu: phf enjoy it while it lasts bub, i had the same thing in my 20s/early 30s
asciilifeform: (things that are there to work around $bug, which in turn stems from workaround of $bug2, etc)
asciilifeform: phf: i've spent last hr or so reading cmucl code, more or less at random, and am struck by the sheer proportion of scar tissue
mod6: omg. i bet the bolognese is awesome.
mircea_popescu household goes through >100k calories / week and all the girls are dieting.
mircea_popescu: yesterday was a 2 gallon pot of bolognese with smoked mozarella. today was 7 sushi rolls. this isn't counting the pastries, cookies, cocktails etc.
phf: also the sbcl os patch, applies cleanly against sbcl_0_9_14, but is missing the forth bootstrap that nyef's talking about
phf: sometime in the early 2000s my family basically lived on what we called wolf diet. small bits and pieces, like nuts and fruit for two three days, but then once in three or four days we'd cook a giant steak or roastbeef or such. there was no reason for it, just sort of gravitated towards..
mod6: i'd get medieval on someone if they did that to my salami
mod6: i was at the deli the other day, buying up all the meats... and just remembering, and getting even pissed about the thought of some asswads substituting soy in for fat.
mircea_popescu: anger's from the blood. what he's got, it's definitely bile.
phf: hmm, i thought russian disdain is usually a lot colder, refined. sort of like nabokov talking about what make lolita appealing to the american public.
mircea_popescu: (nyef = alistair bridgewater, from the pw:rn subdirectorate of intel)
mircea_popescu: phf that shitty "lisphacker.com" thing that spits the most obnoxious errors, really bitch, "no such key" ?
mircea_popescu: http://log.irc.tymoon.eu/freenode/lisp?from=2015-12-20T19 << there's a log, insanely shitty with too much js to run, but i think it may go back usefully.
mircea_popescu: they should hang kids in jr high by their ballsac until they learn to blog every day.
jurov: asciilifeform: i think these somebodies went on to make their own lisp dialect, using python build system or jvm or llvm or somesuch
phf: "<nyef> (Speaking as someone who wrote his own standalone Forth and then used it to load a stripped-down hacked SBCL core on bare metal x86.)"
asciilifeform: phf: this is theoretically solvable. but it's a c proggy.
phf: i'm pretty sure he was doing around the same time as you were doing loper, so i'm surprised you haven't seen it. i think he might've been doing it under TUNES umbrella
mircea_popescu: theroetically you can lick your own anus.
phf: asciilifeform: there are text files (he makes adequate technical logs of most of his efforts. i'm using his notes to recreate arm port for cmucl), but i won't be able to find them at the moment (i'm not on my main machine)
asciilifeform: theoretically you can, e.g., host www on just an uart.
asciilifeform: mircea_popescu: what i wanted to establish was the ~whynot~
mircea_popescu: but they can't.
mircea_popescu: honeslty, should probably go with whatever either phf used to run btcbase or ben_vulpes used to run candi.
asciilifeform: in fact we had the thread!!
a111: Logged on 2016-09-17 02:57 mircea_popescu: how can you lot put up with these idiots ?
ben_vulpes: i was certain that we'd done the 'omg cmucl compilation' lolz thread before; is this a time loop? where are picard and riker
asciilifeform: http://www.ljosa.com/~ljosa/doc/encycmuclopedia/devenv/README-build-instructions.txt << phf if this is current, then i am officially cured of all desire to have anything to do with the thing
ben_vulpes: dog if that's a jet fighter i'm the ceo of apple
asciilifeform: is the idea 'read the code for a month and then MAYBE you will realize in what order to build'
asciilifeform: phf (or anybody else?) -- dare i ask, how the fuck does one BUILD IT
asciilifeform: * I do not know what this object should be or how it got there,
asciilifeform: * pointing to a free page, because these are newly allocated
asciilifeform: * usage, at startup there should be 4 objects in static space
asciilifeform: * happening is that when a core is loaded, there is some static
asciilifeform: y'know, this is how folx end up on a scaffold with mircea_popescu pissing down their neckstump
asciilifeform: srsly, all 4 links under the 'Developer info' category, are duds
asciilifeform: phf: https://www.cons.org/cmucl/doc/ << lulzy, ALL of the building instructions for cmucl -- 404 !!
asciilifeform: interviewer: 'what's the proof'
asciilifeform: (d00d ~does~ offer a schematic for 'keyboard and vga' using modern micro, at the end of the page, though)
shinohai: They were SO CLOSE
asciilifeform: (my log tail looks quite like thestringpuller's paste)
asciilifeform: thestringpuller: it's up but blackholed
asciilifeform: and i can see why they do it, even buying ~one~, e.g., UART, today, is not easy
asciilifeform: folx keep makin' these nonsense abortions.
asciilifeform: phf: aha. the z80 is ~decorative on such a box.
phf: well, it's a lispm kind of architecture, with a single central controller, and extension boards of various degrees of dirty. though i guess the real "core" here is the opaque STM32
phf: it uses the word "modern" a lot, but from cursory glance it doesn't look insane
ben_vulpes: for pete_dushenski on the topic of studded bike tires https://www.youtube.com/watch?v=6q5IYSrLFUY
deedbot: http://qntra.net/2017/01/tim-draper-theranos-targeted-by-conspiracy/ << Qntra - Tim Draper: Theranos Targeted By "Conspiracy"
trinque has had plenty of good coding afternoons where one person drove keyboard and >=1 others hollered and pointed
trinque: one can see what was useful in the experiment and not get fixated on the particular implementation
trinque: and aside all other bullshit uses of "social coding", that ~was~
trinque: http://btcbase.org/log/2017-01-19#1605315 << yet shouldn't be overlooked that several folks came to play immediately when there was a shared repl available
mircea_popescu: i guess i haven't worn these since i was last on roof.
mircea_popescu: "i'm so terrifying of talking to that cute wallflower i'ma revolutionize the $name like $name for $name instead!11"
trinque: see the conferences, "social coding", hackathons, etc
trinque: nah, the idea that these guys are using this as a substitute for healthy human interaction is spot on.
asciilifeform: maggots dun have plans, or objectives, they simply eat.
mircea_popescu: it's quite evident from their gestalt they're coding with flashlight under the covers.
mircea_popescu: incidentally, if the various dreppers etcs actually had any friends, the whole rot wouldn't exist in the first place.
mircea_popescu: good brothel = many whores, small building. not vice-versa. that's called "beachfront property".
mircea_popescu: i must say candi_lustt made it obvious lisp is workable development. way the fuck faster than figuring out which stdio to include and dumb shit like that
mircea_popescu: my model is... well, aptly put, stick shift. ie, even if dudes wanna bitch about lisp, because "c is faster", the above STILL APPLIES
mircea_popescu: yeah and then interpreter bitches if wrong types, so it catches size issues by default.
asciilifeform: if cpu wants to move, add, subtract, etc. a bitstring, it has a length glued to it, and a type (that indicates, among other things, what it means to 'add' it, say), also glued to it.
asciilifeform: on a proper lispmtronic comp, there is no juggling of 'pointers' or any other naked, unannotated bitstrings.
asciilifeform: it did, though not in the peculiar 'stick shift' way described by mircea_popescu earlier
mircea_popescu: i suppose its tagged memory model does pretty much a superclass of the above
mircea_popescu: i don't want the functionality exposed.
asciilifeform: on a proper lispm (definitionally) it is done by the iron.
asciilifeform: mircea_popescu: in sane programming system (e.g., lisps) nobody gets to point to 'memory address'. they point to an item that necessarily and unseparably carries not only address (not visible to or alterable by the operator, normally) but also a type and -- when the thing is >1 machine word in size -- a size.
mircea_popescu: if you provide buffer size, and it is the correct buffer size for offset, you can read that many bits.
mircea_popescu: if you fail to provide the buffer size, cpu reads 0 bits from address specified.
mircea_popescu: that doesn't mean the cpu die must be cast in such a way as to allow anyone else to do it.
asciilifeform: mircea_popescu: for so long as memory is sold as a dumb capacitor grid, cpu can necessarily address all of it (that is, all of the connected ones)
mircea_popescu: i want the cpu to not be physically capable of addressing it.
asciilifeform: the simplest way to do this using current off-the-shelf hardware is to not expose the pointers.
mircea_popescu: it must not be possible to read from x unless you correctly specify the ring size.
asciilifeform: how cpu physically moves the bits, is quite separate question from what operator thinks about.
mircea_popescu: cpu can only address memory if the correct size (0a) is provided for 0x88faf0.
mircea_popescu: cpu can not address memory in the sense of "from here to eternity".
mircea_popescu: not necessarily operator, but also none of the current straight on addressing bs.
asciilifeform: holy fuq why would you give the operator raw pointers.
mircea_popescu: you'll be left with the last 10
mircea_popescu: your pointer is 0x88faf0:0a and god help you, if you wish to write 500 bytes in there all the better.
asciilifeform: (instead of 1 model of computation, you now have 3 -- that you know about. plus others, unwanted, resulting from interactions b/w the 3.)
asciilifeform: at the cost of destroying whatever conceptual integrity machine might otherwise have.
asciilifeform: they make it possible to actually do any work on von neumann monstrosity.
asciilifeform: interrupts, dma, are relics from dark age when there was 1 cpu and it cost most of what the machine cost.
asciilifeform: is how i got there.
a111: Logged on 2017-01-19 17:49 asciilifeform: the two major caltrops re 'iron lisps on x86' are 1) interrupts 2) dma
mircea_popescu: http://btcbase.org/log/2017-01-19#1605218 << actually non-interrupt / non-dma (and possibly tagged ram) is about the reason to make own fpga cpu
asciilifeform: name 'bytecode' simply came about because making the opcodes 1 octet long is convenient
asciilifeform: well ~all interpreted programming languages use 'bytecode' or some variant (i.e. emulator for fictional cpu that fits the task)
asciilifeform: trinque: i must note: just because asciilifeform barfed, does not mean that a clean solution to the problem cannot exist. only that he did not find one.
a111: Logged on 2017-01-19 17:31 asciilifeform: seems like a fully-musltronic, work-ready linux is possible, then.
phf: thestringpuller: which string did you use originally?
asciilifeform: sorta what asciilifeform tried to do (then barfed.)
asciilifeform: they both violate whatever sane execution model you pick
asciilifeform: the two major caltrops re 'iron lisps on x86' are 1) interrupts 2) dma
phf: actually it's all a lot more clearer when you read the early cmucl papers. the mess grew in unix user space..
asciilifeform: (this imho is quite sorry state, you oughta be able to go from the executable TO the lisp representation without ANY info loss)
asciilifeform: these are just asm macros neh ?
asciilifeform: then thing has a chance of working correctly.
asciilifeform: also (and iirc i discussed this on my www at one point) the correct approach is to ditch the native compiler, in favour of the interpreter, hand-compiled to fit in L0 cache
phf: there's some strategy in building multithreading in a lisp that all the commercial lisps share with cmucl and that's different from sbcl, but i'm not quite sure what it is yet
phf: re cmucl threads i think that it doesn't always preempt correctly. like it has explicit yield, which you don't always have to call, but it being there implies. also hunchentoot wasn't working right without putting a yield somewhere in the scheduler. it's all very vague, because i've not spend any time looking at it
asciilifeform: (then perhaps some luxuries, e.g., 'midnight'. then x11 and ratpoison. is pretty much all.
phf: well, stali has a musltronic pdf reader and web (they have their own wrapper around webkit, called st i believe, which is literally just a frame with addressbar)
asciilifeform: seems like a fully-musltronic, work-ready linux is possible, then.
phf: no, i'm not that far in the stack to tackle threading. because of goals, if i do, or once i do rather, i'll just work on making them better green threads, rather than native.
trinque: http://btcbase.org/log/2017-01-19#1605148 << https://cgit.gentoo.org/proj/musl.git/tree/app-editors/emacs/files << without claims to the sanity of anything done
asciilifeform: as in, 'the locking system is defective in yet-undiscovered way, proggy fandangoes over own toes'
phf: well, you were right, it's the lack of threads. you can't build for cmucl green threads like it's native.
asciilifeform: instead ought to simply have 1 permanently-running instance of the runtime per cpu core
phf: cmucl is basically a very straightforward lisp machine port, so there's less unixisms built in. sbcl is modernized for unix, but with corresponding tradeoffs
phf: one of the major reasons why porting cmucl might be easier, a lot more naive image construction (doesn't have that whole sb! sb- machinery), and lack of threads
phf: who knows with threads, i wouldn't be surprised if sbcl touches them in very inappropriate, glibc specific ways
phf: there's was a wip fork of making linux-unix.lisp talk directly using syscalls without libc. that's probably lowest common denominator
trinque: phf: the gentoo musl overlay has sbcl patches iirc. gotta forgo threads
phf: so i don't know how sbcl does it, but cmucl has unix.lisp, which kernel relies on early on in the operation, and yes, contains all the "talk to the world" crud. cmucl actually does some hack where only subset of unix is used for operations and then when you (require unix) it adds some of the userspace
asciilifeform: all of the crud that will have to be rewritten on (hypothetical) sbcl-on-iron, conveniently.
asciilifeform: ... what does the thing even ~need~ libc for?!
phf: did anybody do a musl sbcl? i have a musl cmucl in the backlog, but way down the list (perhaps once i get this x60 going)
jhvh1: asciilifeform: The operation succeeded.
asciilifeform: lulzy, they even issued little axes for this work.
asciilifeform: https://archive.is/stOV3 << in other olds >> elaborate yarn re 'mysterious' habit of u.s. soldiers, of bashing in the heads of killed goatfuckers. presented as 'atrocious' and 'senseless' etc. and i read whole spittoon waiting for the obvious reason to be mentioned, and of course was not (ground beed the face, and you dun need to worry whether you executed the hit on exactly the right d00d..)
phf: so i called the new branch of the bank i'm transferring to, they confirmed the ifsc number. i'm not sure what i prefer, the fed theory or the incompetence theory. either...
mircea_popescu: incidentally this'd have been a great show, i imagine, guy going on street idly, happening on meat shop just as the truck unloads, and generally doing a grand blond a la chaussure noire but a la russe.
asciilifeform: or would have been if the planets had been aligned differently, etc.
asciilifeform: note, i will not claim that there is necessarily still fish at that particular meat shop.
mircea_popescu: well supposedly in moscow there also lived a fellow who always found fish at the meat shop and to this day has nfi what everyone was on about.
mircea_popescu: about there.
mircea_popescu: conversely of course, every dollar you do take out of the us hurts the usg considerably ; i'd guess the going rate is 130k expatriated is about equivalent to shooting a nypd officer in the face.
mircea_popescu: also why eg apple doesn't wire to new york the proceeds of sales in paris.
mircea_popescu: (and if you try to drive cash to mexico they'll try and steal it ; and if you eg open a foreign corp with a subsidiary in the us and send the money home they'll pretend you're engaging in money laundering, and in general expatriating your wealth is generally more difficult than it's worth, which is why sane people do not live in the us.)
mircea_popescu: they very transparently pretend ineptitude, but it's pretty clearly fed instructions.
phf: in unrelated lulz a u.s. retail bank is unable to send an international wire transfer. i bring a piece of paper with all correct requisites. half the numbers "i don't know what this number is", so follow up with calls for numbers from the fucking paper that, who could've predicted, are required. write down the numbers on their end incorrectly. the last part of saga: they now claim one of the numbers is invalid, but if you simply google for it it comes up
mircea_popescu: if you believe this is how it works, all the better.
mircea_popescu: anyway, so krebs has sob story about how republic successfuly denies empire comms ; and wants to add some sort of "but we pay to house some random bums for the rest of their lives so it's all ok"
trinque: and you get to be an elite renegade hacker on the dole, no less
mircea_popescu: hey, it's how you get the ssi rite ?
asciilifeform: 'According to the statement of facts filed with the plea agreement, Shames developed malicious software, known as a keylogger'
asciilifeform: in other lulz, https://www.justice.gov/usao-edva/pr/college-student-pleads-guilty-developing-malicious-software
mircea_popescu: phf it's entirely unclear what ssl is supposed to provide. it might have been of marginal utility prior to their nsa merger, but these days it's utter waste of time. treat all freenode connections as plaintext.
asciilifeform: mircea_popescu: 'works' ain't their objective. area denial, is.
mircea_popescu: you understand nothing they leveraged works ? they ain't got a browser. google is trying to rescue 20 years of weveling with dubious results. there's no python 3. there's no ipv6. there's no trb. there's no eth. there's nothing. NOTHING.
phf: seems like freenode upgraded all their servers to letsencrypt, meaning that you can't just verify ssl's fingerprint once a year. instead each server has own ssl, updated once in 90 days.
mircea_popescu: turns out i can bit mit with one hand while watching porn. they'll leverage what, they got nothing.
mircea_popescu: anyway, the "leverage ecosystem" ie, "someone else will do our work for us" is very much usg.dos style, but also very much hopeless. seriously, they'll leverage ?
asciilifeform: trinque: recall, the drepperites are getting ready to break glibc so that no moar clasical emacs.
trinque: gotta just stop; I'm never installing another emacs version again
asciilifeform: turns out -- the fungus is in full bloom.
asciilifeform: 'We can leverage the rapidly-growing crate ecosystem. We can drop support legacy compilers and platforms (looking at you, MS-DOS).'
asciilifeform: 'If you’d like to join us, there’s plenty to do. You could: Port a small C function in lisp.h to lisp.rs. Port your favourite built-in elisp function to Rust.'
mod6: http://btcbase.org/log/2017-01-14#1602666 << some very early, news to report: I've successfully implemented this fix into the forthcoming version of V (99994), and all original and new automated tests passed.
BingoBoingo: <asciilifeform> ick no american synthetic turdolade plox. << AHA, you've had your fill of polyurethane foam? How much still adheres to the hands?
mircea_popescu: incidentally : the 80s 37yo virgin never killed anyone. just wore his disco suit and applied himself.
mircea_popescu: some crossover with tintin, but meh. the great us equivalent would be i guess popeye
asciilifeform: the thing was massively multilayer lampoon of various cultural gibblets
mircea_popescu: did they have that in ru ?
mircea_popescu: (incidentally, the characters look like ripoffs of lucky luke antagonists)
mircea_popescu: that doesn't really look like it's earlier than the lslilll
asciilifeform: the canonical head-lightbulb in my head.
mircea_popescu: it's an old leisure suit larry idea. I SAW THE FACTORY
mircea_popescu: body very replaceable, just unscrew the head.
asciilifeform: like one's own motherfucking body.
asciilifeform: this is ftr the WORST possible kind of tech, which is why i even mention it here:
mircea_popescu: well then may i recomend a tardis.
asciilifeform: was ~just right~ consistency though, and didn't feel like roasting in own juices from the sheer thermal insulation power
mircea_popescu: i think they use a mechanic plucker, ~beat carcass with sticks
asciilifeform: tell this to the americans.
asciilifeform: i might have to use mircea_popescu's method. but it will take thousand years, because my proper pillow had 0 feather stems.
asciilifeform: ick no american synthetic turdolade plox.
shinohai says nothing about the cat at midnite again
asciilifeform: *feather pillow
asciilifeform under voodoo curse; 50-year-old genuine feature pillow finally detonated in the wash, made for 2+hrs of wetvac, and 'where the fuck do i get one of ~these~' experience
shinohai: I was looking into that time when Ver doxed the guy over (at the time) $50 and found that gem
thestringpuller: asciilifeform: "During the manufacturing process, a unique set of keys are generated and stored in the processor’s fuse array. One of these fuse keys is not known by Intel and is one of the components used to form the basis for consistent derivation of subsequent sealing keys." << in other snorefest. "Unknown" to Intel during manufacturing...uh huh...
mircea_popescu: anyway, as far as "online web industry" is concerned, definite signs of a trumpocalypse. sort-of how there was a pre fdr and a post fdr or a pre lincoln and post lincoln america ; there's going to be i suspect a pre-trump and a post-trump web
thestringpuller: all the SEO people I know ended up going into machine learning
mircea_popescu: which kinda makes me suspect the whole field's ripe for a generation change. "feminism" is certainly shattered post trump, so it looks like there may be a 6th wave brewing. and the 2nd generation seo dorks who came online with the "social media" revolution and web 2.0 idiocies are mostly falling back into regular jobs and boring marital arrangements so there's a void, to be filled.
mircea_popescu: oh and in other "people form the future : the next generation" http://d2vepvd49xw1a6.cloudfront.net/wp-content/uploads/2016/07/02071929/brian-dean-1.png
mircea_popescu: http://www.charlestoncitypaper.com/charleston/how-not-to-depict-trump-wave-feminism/Content?oid=6423315 << in other buttlulz
mircea_popescu vaguely recalls blowing the dude's "cover" sometime in 2013 or w/e that glbse shares scam happened.
shinohai: Best I can tell he posted a link to theymos' personal info