log☇︎
1639 entries in 0.715s
gribble: (last [--{from,in,on,with,without,regexp} <value>] [--nolimit]) -- Returns the last message matching the given criteria. --from requires a nick from whom the message came; --in requires a channel the message was sent to; --on requires a network the message was sent on; --with requires some string that had to be in the message; --regexp requires a regular expression the message (1 more message)
Namworld: Is doing it properly something like just exploiting some autistic kid who can insta-calculate SHA-256 hashes or string used for a SHA-256 hash and ruining Bitcoin for everyone?
mircea_popescu: giving shit allows you to string out the idiots and only the idiots for years, as bfl has recently proven but otherwise as it's been documented ot high heavens already.
gribble: Error: invalid syntax (<string>, line 1)
mircea_popescu: so from any signed stat the string of transactions takes you to the current one.
Wild0wne_: why you crying string?
gribble: Request successful for user afrotec, hostmask afrotec!~afrotec@145.sub-70-194-132.myvzw.com. Your challenge string is: freenode:#bitcoin-otc:7c6ff225203256a97040b871809523e3fd09c49ab161bdf8fc6f7297
ThickAsThieves: string, will it be legit ?
Rulother_: Maybe next time string :)
gribble: Error: unexpected EOF while parsing (<string>, line 1)
kakobrekla: diablo is more nigger than you string and he is a ginger
mircea_popescu: ;;rate bdk_kluge -10 long string of scams. one of bitcoin's worst.
mircea_popescu: ;;rate kludge -10 long string of scams. one of bitcoin's worst.
Vbs: if he's got all your coins you're just hanging by a string then?
ThickAsThieves: string, what do you think of Rift's current model
ThickAsThieves: string argues that is not good enough
benkay: the string to which you're responding, less idiotically phrased.
gribble: Request successful for user matthew_boyd, hostmask matthew_boyd!519fee4e@gateway/web/freenode/ip.81.159.238.78. Your challenge string is: freenode:#bitcoin-otc:7c69b5de91f126915bf512edaa97dc2a0d8c24deb9483ca82fb837b4
deadweasel: our government, you can have them. string'em all up.
ThickAsThieves: they wanted to test how long a scammer can actually string someone along
gribble: (last [--{from,in,on,with,without,regexp} <value>] [--nolimit]) -- Returns the last message matching the given criteria. --from requires a nick from whom the message came; --in requires a channel the message was sent to; --on requires a network the message was sent on; --with requires some string that had to be in the message; --regexp requires a regular expression the message (1 more message)
prof7bit: maybe print the actual error in the alert and not just this string, then i might be able to provide more nformation. I have tried to find out whats wrong with the built in debug consele thing but i don't knwo how to use that.
inhies: i use a GET with the URL to approve teh app, since that is done in a browser, obviously, and then the approval form is a POST, but then it reloads with a GET to the same URL with the verifier string appended
inhies: for me, the page reloads with the verificiation string appended in the URL, but when I try and use it the API says its invalid
mircea_popescu: anyway, i'm putting it off to string of extremely unlikely coincidences.
benkay: peer over tin cans and string
Framedragger: parseval: sure, just note that it's usually trivial (as in, perhaps only change the db configuration string in your app's config) to change the underlying DB (installing and starting a DB server with default config is also usually really simple) - but yeah, would be interesting to see your results eventually, good luck!
tk993: Header is private key block. for the other it is public key block? Are they different structures or how does it know? Or does it just know? Say for example I sent my public key and kept the headers of the private key... does that not matter because all the information is in the string of characters?
jcpham: and string
gribble: Error: invalid syntax (<string>, line 1)
jcpham: TL;DR: Here's what happened. When a password reset is submitted, the user receives a random URL by email containing a random 21 letter string. The algorithm used was bad, so the random string could be brut-forced.
jurov: i like C. Except for string operations where I need pen and paper to visualize where the pointers end up.
mjr___: like i said, everything from old appalachian string bands to skrillex
dub: that is the second time in 48 hours I've been highlighted with almost the same string
bowjob: a string of losses was catastrophic for me
gribble: Error: unexpected character after line continuation character (<string>, line 1)
ThickAsThieves: string, why not get your own account?
mircea_popescu: then again considering the string of insanities sturles was sprouting the other day, it wouldn't surprise me if they run it like that.
ThickAsThieves: i was just gonna say that string!
cole_albon: string puller are you "the girl" somewhere else?
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
ThickAsThieves: for the past two months, the longest string of green candle days is 8, red candles is 2
jurov: yubikey creates a pseudorandom string and you know what the strign is going to be, no?
gribble: Error: invalid syntax (<string>, line 1)
mircea_popescu: why do you string them out like that anyway ?
mircea_popescu: right after ipo s.dice had a string of disasters. first pirate blew up within a week of ipo, froze markets for like a month
gribble: Error: unexpected EOF while parsing (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
pigeons: i have a service that retreives everify and sends me the decrypted string in the udp header of a fake netbios packet
gribble: (last [--{from,in,on,with,without,regexp} <value>] [--nolimit]) -- Returns the last message matching the given criteria. --from requires a nick from whom the message came; --in requires a channel the message was sent to; --on requires a network the message was sent on; --with requires some string that had to be in the message; --regexp requires a regular expression the message must (1 more message)
kakobrekla: http://www.rugatu.com/questions/11266/php-array-to-string-conversion?page=1&focusedAnswerId=11270#11270
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
Anduck: then do ;;bcverify <string>
Anduck: do ;;bcauth and when you get the string
mircea_popescu: basically, it should take the provided string, see how many of the available mpsics regex-match it
gribble: Error: invalid syntax (<string>, line 1)
maximian: I'm lazy… just wanted to replace a string in pympex
mircea_popescu: you can take a string and encrypt it with mpex key right now
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
Chaang-Noi: just wondering, i passed up the free account with no string attached anyway.
Anduckk: mircea_popescu is the string puller!!!
mircea_popescu: 6. you wipe all space/newline in your string
mircea_popescu: because it's a 5 char string starting with =
mircea_popescu: within the signature block, a =j61e type string is the end (cause it's the checksum)
mircea_popescu: i like that string of no
ThickAsThieves: string, you mean no 8mil diff, in regards to XDIFFMAR?
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
gribble: Error: invalid syntax (<string>, line 1)
jcpham: ;;everify the decrypted response string
Namworld: gpg + string parsing/posting
Namworld: and possibly just use dropdowns and aggregate each value in the string
mircea_popescu: "parse this string"
mircea_popescu: what is it, string parsing
Namworld: But in javascript... just get a field for user private certificate and some input field for the string.
topace_: yea but the hash string is a short piece of text
mircea_popescu: if you don't, there's always going to be this lead-up string. first it misses X. then a little more. then a little more still.
gribble: Error: unexpected EOF while parsing (<string>, line 1)
jurov: StarenseN, from what you wrote in the night, it looks like you have trouble escaping the string
gribble: Error: invalid syntax (<string>, line 1)
Bugpowder: a string of good fortune
gribble: Error: unexpected EOF while parsing (<string>, line 1)
kakobreklaa: string(14) "login_required"