238400+ entries in 0.152s
mircea_popescu: (alf would have liked
this one,
the rats live so closely packed
they have cultural constructs re intramural participation in sexual congress -
the woman is offended but subverts it as normalcy. OF FUCKING COURSE
the "next door neighbour" would play music
to go with our intimate discussions.
this is soviet america and
the walls are
thin!)
mircea_popescu: total fucking casual-boner-archy
that
thing, and utterly unwatchable. i used
to mock romanians a decade ago as "o populatie cu mize mici" ie, a population with low stakes. but lawds have mercy,
the hopes, aspirations, projects and projections of
the contemporaneous ustard (stanford grad & waitress-journaho) barely cover a used bottlecap.
mircea_popescu: in which vein, /me watched a half hour of something last night, because i
tried
to do a christina applegate retrospective. holy shit
that girl has been in all
the shitty snl derivative crap. how do
these idiots even live, how do
they get out of bed ?
that ben affleck imbecile, he's like baudoinia, blackening
the walls of anywhere alcohol is customarily found. unfunny as cancer, stupid as broken shoelaces, ubiquitous as a sac
BingoBoingo: Freenode isn't deterministic enough
to have a "normal" way of doing anything.
walter: and
then somehow
to generate a key _properly_
walter: no, 'walter' is registered. I need
to come up with a sane available nick
mircea_popescu: check it out, you weren't late
to
the party after all ?
walter: mindread :).
Thanks for
the links, I'll dig
the logs for
the
topics
BingoBoingo: <mircea_popescu> why
the fuck is va' fa'n culo spelled as one word with a double f ? cosi fan'
tutte is not cosiffantutte ? <<
ty fxd
mircea_popescu: afaik
the pogo is
to date
the only
tmsr-certified digital computer.
mircea_popescu: we really should systematize
the "box verification"
thing, with a view
to actually certify hardware configurations.
mircea_popescu: also in which vein, see
the discussion re busybox and
the complete
trb machine
tmsr created for deployment on pogos (and
the whole discussion with pogos) ; also perhaps of interest
the failure
to create a useful gentoo and so forth.
☟︎ walter__: I don't.
Too late
to freenode short names party
mircea_popescu: may want
to de-__ your name first if you actually own "walter"
walter__: considering
the horrible situation with x86 laptops I wonder if Asus C201 (again from
the Libreboot compatibility list) is "the cure"
walter__: but
that would be going even further back in history
walter__: my other guess was
the idea was
to hunt
the last machine with a CPU without microcode updates
mircea_popescu: anyway,
that's what "2005" means in
this context, "when lenovo got
the brand".
walter__: although according
to asciilifeform Libreboot can burn
the machine
walter__: if it's about Libreboot
then
the "last one" is X200 of 2008
mircea_popescu: famously rms claims
to have been using one ; which claim was meanwhile experimentally falsified here.
mircea_popescu: which
turns out
to be a much higher bar
than
the general population realises, and experimentally reduces
to
the various
thinkpads of
the end of ibm / start of lenovo era.
mircea_popescu: walter__
the 2005 was just a reference
to something i mentioned, iirc in a discussion with asciilifeform ; it's not an exact date (fwiw i use
ts etc). but
the idea is - a laptop which runs with no binaries whatsoever.
walter__: those are X32 and X41 according
to
thinkwiki
walter__: reading logs I found some mentions of exactly "2005"
thinkpads but cannot see why
mircea_popescu: why
the fuck is va' fa'n culo spelled as one word with a double f ? cosi fan'
tutte is not cosiffantutte ?
mircea_popescu: i've watched about a half hour of
tv
total since seinfeld.
ben_vulpes: mircea_popescu: seen any of
the hbo show 'westworld'?
mircea_popescu: kinda been going like
that, 2015 > 2014
then 2016 > 2015
BingoBoingo: The pete_dushenski anals of 2016 are detailed, but prolly missing something. 2016 seems
to be banner year for republic.
phf: "skilled and
talented chosen over ny
times writers and editors, is
this
the beginning of fashism?"
mats: ('scuse
the mobile site)
mats: i believe
the 'ex' suffix is
the chip, is
that right?
mats: way
to denigrate
the suffering of
tens of millions dead because you want
to make an incendiary political statement
mircea_popescu: what's with mats
thinking random spamsites have anything
to do with
the world.
shinohai: Lets just plug in
this charger .... OH SHIT
mircea_popescu: incidentally i'd say
the arrangement as present is also
the right
thing. bot should send raw bytes ; wwwtron should send escape codes.
phf: for example in
the original
there's a byte sequence \xc3\xb0, it's a valid utf-8 for code point #240, which if it renders looks like `ð' and in html can be represented as ð
jurov: ^ my aubergine came back as raw bytes f0 9f 8d 86 but in
the html log it is 🍆
phf: nah, in
the first case bot's sending raw bytes on
the
the wire (which are valid utf-8 for a bogus code point sequence), in
the second case
the raw bytes have been intrepreted as code points and are sent as html escape codes for code points.
mircea_popescu: other
than "unicode is fucking evil" i have no moral from
this wasted hour.
phf: yeah it does, but in
this case
the byte sequence is untouched, because
the original byte sequence is valid utf-8.
the disparity seems
to come from
the fact
that a111 sends utf-8 sequence, where's website renders it as unicode code points.
mircea_popescu: just did a hexdump on
the logfile.
the relevant portion "or ðŸ†if" reads hexdump or ðŸ†if0000000 726f c320 c2b0 c29f c28d 6986 0066
jurov: does a111 keep as-came-from-wire copy of logs? i'd recommend
to.
mircea_popescu: which is why
the belief
that a111 mangles something. because otherwise how is my irc client distinguishing ?
mircea_popescu: but my same client does NOT misreport OTHER instances of "🍆" as " �" when
they are ~not~ spoken by a111
mircea_popescu: so : for ~some reason~ my client reports a111 as saying " �" whereas
the webpage reports it as saying "🍆"
jurov: hexdump of my log (just fyi, does not mean my client did not massage it
too):
jurov: i
think ben_vulpes' client magled it, i see all
the aubergines fine, except his
mircea_popescu: the other one only appears pasted by me. so apparently i have an issue whereby unicode
transforms into bs.
mircea_popescu: ben_vulpes</a>: heh,
today i learned
the unitards are so fully vested in
the anti-sex brigade
that U+1F346 or 🍆if my client doesn't mangle it
phf: mircea_popescu: but
that was pasted by you!
a111: Logged on 2016-12-04 17:25 mircea_popescu: except it isnt :
the website shows ðŸ�†if whereas a111 says ðŸ†.
these
two will appear
the same in
the btcbase log, but i
trust you see
them different in
terminal ?
phf: where does
the website show
the first sequence anywhere?
mircea_popescu: mircea_popescu</a>: except it isnt :
the website shows �if whereas a111 says 🍆.
these
two will appear
the same in
the btcbase log, but i
trust you see
them different in
terminal ?
phf: and
the original sequence
that ben_vulpes sent ~can~ be parsed as valid utf-8, so it gets mapped
to some code points and rendered a such.
phf: so apparently cl-who's escape-string which produces
the ð... bits simply
takes character's char-code which in sbcl corresponds
to character's unicode code point
mircea_popescu: ben_vulpes: heh,
today i learned
the unitards are so fully vested in
the anti-sex brigade
that U+1F346 or 🍆if my client doesn't mangle it << pasted from page source of
the log
phf: well,
that's what i'm saying is
that i can't find
the second ("expected
to say") sequence anywhere on btcbase
mircea_popescu: it was expected
to say (in part) : U+1F346 or C3B0C5B8EFBFBDE280A0if
a111: Logged on 2016-12-04 05:07 ben_vulpes: heh,
today i learned
the unitards are so fully vested in
the anti-sex brigade
that U+1F346 or ðŸ†if my client doesn't mangle it, goes by
the name of /aubergine/
phf: a111 is producing
the first sequence on
the wire
phf: i can't actually find anywhere where website is ~producing~
that second sequence (besides your own lines)
mircea_popescu: not
the right bytes, not even
the right byte count, and now i suspect
this is enough for priviledge escalation in a111 or any other item which uses
the same unicode libs.
a111: Logged on 2016-12-04 05:07 ben_vulpes: heh,
today i learned
the unitards are so fully vested in
the anti-sex brigade
that U+1F346 or ðŸ†if my client doesn't mangle it, goes by
the name of /aubergine/
phf: what a111 should say should be identical
to what
the website says
though, let me check
phf: well, it isn't in a sense
that ben_vulpes sent a sequence of bytes
that can't be parsed as valid utf-8
mircea_popescu: except it isnt :
the website shows ðŸ�†if whereas a111 says ðŸ†.
these
two will appear
the same in
the btcbase log, but i
trust you see
them different in
terminal ?
☟︎ phf: sure, and
that works. sending utf-8 byte sequence for u+1f346 is correctly preserved
through (which is also
the case for all
the other unicode
that's being sent, like
thumbs up)
phf: what was
the original byte sequence you sent?