1400+ entries in 0.398s
jurov tries to compile #include <
string.h> int main(){char *foo ="abcd"; memfrob(foo);}
mircea_popescu: asciilifeform in the good news department - progressing illiteracy means they've moved on from featuritis to fixing comments in the code so it no longer includes the
string "retarded" and all " he" is replaced with "erzsjebet".
mircea_popescu has said "AT THE VERY FUCKING LEAST!!!1 separate this mess into
string.h and non-
string.h god damned it!!1"
assbot: Logged on 31-10-2015 16:17:23; jurov: *every* time i did anything nontrivial with #include <
string.h> it ended up by drawing stuff on paper
jurov: *every* time i did anything nontrivial with #include <
string.h> it ended up by drawing stuff on paper
☟︎ jurov: btw, that "
string" = "byte array" thing, specifically people who like to do pointer arithmetic around it caused enough grief i won't miss it at all
jurov: and "concept of
string".. something has to give, in this case "
string"===="byte array"
phf: jurov: variadic anywhere in your
string handling machinery means that you no longer have a meaningful concept of
string, i.e. nth printable character is an nth object in array, instead everything that you manipulate is a stream with a state machine attached. be that utf-8 at the encoding level, or ucs-4 at the storage level which brings in surrogates and supplementary characters
pete_dushenski: borat over-the-shouler g-
string in prison black and white stripes
mircea_popescu: but derived from what, a line of code is just a meaningless
string trinque: punkman: I don't either, likely due to
string quoting in programming.
mircea_popescu: once you buy into the theory that "the state isn't the CAUSE of criminality but the protection from it", you'll necessarily swallow the "science is the path to knowledge"
string all the way into "paradigm good".
phf: ben_vulpes: for something like gnuplot i've discovered that learning all kinds of fancy ways you can output a
string with #'format is a lot more useful skill then learning a specific library. short of writing an equivalent of gnuplot command ast you're going to run into impedence mismatch one way or another
ascii_field: the other thing, you are not decrypting the
string !
mircea_popescu: and that said, i am probably in the top 1% when it comes to understanding the higher level issues involved, which means i canhammer together a search
string like few others. so google would probably be lot more useful to me, were it to be useful at all, than to the general population.
ascii_field: (one CAN use openssl to sign a
string of bits in the customary way)
AgentScully: I'm just going to wear a tshirt and walk around with this
string on my boobs all day.
mircea_popescu: for about a year or so now. so that thing could never have popped out by just going to root. and i doubt he could have had a google
string that led to it, seeing how you know, my romanian is like triplesec.
punkman: trinque: well you can't get nested structures by parsing the same
string twice, it's gotta go in the grammar?
assbot: Logged on 15-09-2015 23:23:53; punkman: I saw a dog steal an unopened bag of cheetos while I was buying some tobacco from a kiosk couple days ago. guy inside shrugs "what am I gonna do, chase the fucking mutt". I wonder if some bum trained the dog, it was wearing a length of
string as a collar.
punkman: I saw a dog steal an unopened bag of cheetos while I was buying some tobacco from a kiosk couple days ago. guy inside shrugs "what am I gonna do, chase the fucking mutt". I wonder if some bum trained the dog, it was wearing a length of
string as a collar.
☟︎ gabriel_laddel: (eval (read-from-
string "(mjr_meta::mjr_meta_use-packages :BASE-PATH \"~/quicklisp/local-projects/lispy/\")")))
gabriel_laddel: (eval (read-from-
string "(mjr_meta::mjr_meta_load-packages :BASE-PATH \"~/quicklisp/local-projects/lispy/\")"))
gabriel_laddel: "Do I like this
string, would I like more from the identity that produced it?"
BingoBoingo: gabriel_laddel: But at some point people want to put arbitray
string on their own.
mircea_popescu: not that the general problem of "i will now emit a
string of bits and you tell me if this is a function" isn't a very interesting ai topic.
pete_dushenski: punkman: doesn't have to be direct
string-pulling, can be 2nd, 3rd order
ben_vulpes: ascii_field: didja ship 99K with the 100K version
string still in or am i misunderstanding something?
mircea_popescu: trinque the tattoo is not as much of a problem as the bs
string. "really needed" because omg
assbot: Need a decrypted verification
string.
gribble: Request successful for user sexy_saffron, hostmask sexy_saffron!42832f42@gateway/web/freenode/ip.66.131.47.66. Your challenge
string is: freenode:#bitcoin-otc:409a509e51d1706626f4fbf803efd3850f8e1bf64f15464d6f0f01ad
BingoBoingo: <joecool> what's the ideal bitcoind version to run nodes with nowadays? << Either 'stator' with protocol ticked to 99999 or anything with a lulzy version
string assbot: Logged on 19-08-2015 00:41:43; asciilifeform: ;;later tell BingoBoingo if you write a patch for the verson
string thing, i'll read it!
BingoBoingo thinks BIP 14 user agent
string when paired with therealbitcoin have serious potential for lulz
assbot: Logged on 16-08-2015 00:54:40; hanbot:
http://log.bitcoin-assets.com//?date=11-08-2015#1235149 << for the record i bungled this, built a (seemingly working nevertheless) frankenstein patch-quilt (dnsseed_snipsnip, thermonyukyoolar_kleansing, kills-integer-retardation, ver_now_5_4_endless_name_string, zap_hardcoded_seeds, showmyip_crud, if anyone's interested).
hanbot:
http://log.bitcoin-assets.com//?date=11-08-2015#1235149 << for the record i bungled this, built a (seemingly working nevertheless) frankenstein patch-quilt (dnsseed_snipsnip, thermonyukyoolar_kleansing, kills-integer-retardation, ver_now_5_4_endless_name_string, zap_hardcoded_seeds, showmyip_crud, if anyone's interested).
☝︎☟︎ BingoBoingo: Looking that way with blocks. Gotta remember Chicoms mine SPV, prolly haven't fiddled that
string yet
phf: mats: well, i actually meant the opposite. classes of attacks can be eliminated by not using c. i think that majority of the attacks come from leaky abstractions. there's no <
string> in c, but there's a null terminated memory region. there's no <sql> in perl, but there's a character array with sql text in it. one of the solutions is to plug abstraction holes on a level of the language, in such a way that you can't not use improved abstractions
☟︎ phf: mats: there's a systematic solution to an entire class of problems. in the poor people world perl "solved" buffer overflows on
string input by closing the abstraction leak, meanwhile introducing its own leaky abstraction, i.e.
string injection attacks. the solution to that problem was known for 50 years now, specifically structured/validated data
phf: r might look like (
string-right-trim '(#\Null) (map '
string 'code-char command))
phf: ben_vulpes:
http://paste.lisp.org/display/152828#1 << read-sequence reads octets (i.e. unsigned bytes) into an array, so you want (make-array size :element-type '(unsigned-byte 8)) and you also want to then explicitly convert an octet array into a
string. later is implementation dependent (since concerns encodings, etc.), ccl has DECODE-
STRING-FROM-OCTETS and sbcl OCTETS-TO-
STRING, both support encodings. since version is ascii, a naive converte
mircea_popescu: (i didn't see the thing in question, for some reason .webm comes out as a
string of bits)
mircea_popescu: homeopathic
string theory. why the fuck not ? the aloe vera wallet.
mats: irc is a
string and tin cans
williamdunne: trinque: punkman: know how I can dump a representation of an object to a
string?
BingoBoingo: I think alf may be onto something with the BIP 14 user agent strings. If nodes are claiming maxint protocol version and not serving a user-agent
string to turd nodes.
ascii_field: that's because the output of 'encrypt' is a base64 turd that isn't expected to coexist with text the way a clearsigned
string is.
ascii_field: mircea_popescu: regardless, can't rely on arbitrary
string staying intact
assbot: Logged on 02-08-2015 16:01:52; ben_vulpes: ;;later tell phf
http://paste.lisp.org/display/152828#1 << do forgive my ignorance, but what am i missing about converting the "command" into a
string? (Adlai, asciilifeform, your eyes'd be appreciated too)
mircea_popescu: trinque i never saw a post from legit (by ip allocation) googlrbot. seen plenty from rogue agents using same user
string BingoBoingo: I mean the connection mean I've basically self doxxed, but my slave name may actually be a less common
string than the IRC nick.
phf: ascii_field: there's a lot of leaky abstractions in the current codebase, starting with "
string" and "bignum". presumably the solution for those will be to port bitcoind to an architecture with tagged memory?
mircea_popescu: "It was just the latest in a
string of calloused comments made by UFC's head honcho -- far from the diplomatic dialogue expected of the largest mixed martial arts organization"
nubbins`: no kidding, every now and then some internal piece of code would return an array of strings as a single, very large
string, with entries separated by the escape
string "#;"
phf: #S(MESSAGE-MESSAGE :START-
STRING #(249 190 180 217) :COMMAND-NAME "version" :PAYLOAD-SIZE 85 :CHECKSUM #(250 5 185 54)) came from the node and the checksum verifies
trinque: ben_vulpes: it's fine; eats a sql
string or sexp version thereof, farts list
mircea_popescu: they're still living off fucking google ads. which work about as good as an ant blowjob. since then, endless
string of failures, briefcase, glass, g+ you name it
ag3nt_zer0: am i supposed to enter the entire text file, including ---Begin Public Key Block----, or just the
string of shit? sorry don't know the technical term...
mod6: i want to make it clear that it seems /slightly less readable/ to me because of: @@ -45,24 +45,6 @@ Object JSONRPCError(int code, const
string& message) << this type of thing.
mod6: @@ -45,24 +45,6 @@ Object JSONRPCError(int code, const
string& message)
mod6: looks like error(const std::
string &&format, ...) does the same gyrations as around _vsnprintf/vsnprintf as my_snprintf. which is kinda strange. my_snprintf must have been added later.
mod6: return value (as always) as the number of characters that would have been written in case the output
string has been large enough. SUSv3 and later align their specification of snprintf() with C99.
trinque: for example an inner join between the schema-describing-tables and the rows describing the grammar was how I wrote a generic to-
string for any language in the ebnf tables
assbot: Invalid verfication
string.
trinque: asciilifeform: dunno, python was choking on the
string silently; maybe I'll investigate more later
danielpbarron: i don't think it's even checking the validity of the tx, and is instead rejecting the hex
string as being too long; I can get my 0.5.3 node to give the same error and it doesn't recognize the method
BingoBoingo rebuilding 0.7-ish client for lulzier version
string mircea_popescu: "o mp, it has much faster
string operations". fuck you.
HeySteve: the thing about Witcher 3 is you can amass a huge inventory of weird parts, like monster tongues and bits of
string trinque: gpg likes your doc just fine, and python has your doc as a
string identical to what was provided
trinque: just python
string nonsense; I should've written this part in bash
ascii_field: it also would be logical for whatever consumes the sooper s33kr17 text
string (e.g., salted password hasher) to actually live in that brass tube.
lobbes: well, my issue thus far is that I'm running lobbesbot on a aws instance seperate from my edis bouncer instance, so the only way I can currently see privmsgs sent to it are by checking messages.log (however, this only returns up to the first 'space' in the
string)