log☇︎
2403 entries in 0.725s
assbot: Request successful, get your OTP: http://w.b-a.link/otp/0dfa4210ab9a2da2
assbot: Request successful, get your OTP: http://w.b-a.link/otp/f9de3c72f76f614e
assbot: Request successful, get your OTP: http://w.b-a.link/otp/07fa06bebb8415a5
assbot: Request successful, get your OTP: http://w.b-a.link/otp/9108da815414d5d4
assbot: Request successful, get your OTP: http://w.b-a.link/otp/3c714a5f55f151ab
danielpbarron: ;;later tell Rozal New rating | Rozal > -10 > cazalla | SCAMMER - Stole 1 BTC from me, and is a known scammer on other nicks http://pastebin.com/ApyavW5T. DO NOT TRADE / DEAL. << pastebin is your signed OTP..
mircea_popescu: TheNewDeal just decode the otp and send !v decodedotp
davout: as in 'wanna timestamp some stuff? fine, verify with and otp"
assbot: Request successful, get your OTP: http://w.b-a.link/otp/721476ec38fdf8b8
assbot: Request successful, get your OTP: http://w.b-a.link/otp/9d9547d664ea4ebf
assbot: Request successful, get your OTP: http://w.b-a.link/otp/9f1f7a77bb5ab2a1
kakobrekla: chan !up is for non otp use
kakobrekla: otp !up should work only on private
mircea_popescu: it's the missing /n at en of otp giving all sorts of people hell
mircea_popescu: kakobrekla can there be a /n after each otp before encryption pls.
assbot: Request successful, get your OTP: http://w.b-a.link/otp/6a9d8d2d055d69cf
kakobrekla: <PeterL> new voicing model, we still have to join #b-a before verifying otp < yes, no session, recall?
PeterL: new voicing model, we still have to join #b-a before verifying otp
assbot: Request successful, get your OTP: http://w.b-a.link/otp/190b6cfc995f06a2
gribble: http://w.b-a.link/otp/5d95a96032e89e9e is up
kakobrekla: ;;isup http://w.b-a.link/otp/5d95a96032e89e9e
assbot: Request successful, get your OTP: http://w.b-a.link/otp/7e95d1cb8e7c1075
mircea_popescu: ben_vulpes like in chan ? pm it !up it responds with otp, pm it !v otp
ben_vulpes: nope. perhaps the otp machine?
assbot: Request successful, get your OTP: http://w.b-a.link/otp/ec89a1090cd1b971
assbot: Request successful, get your OTP: http://w.b-a.link/otp/46ae34a617b1519d
assbot: Request successful, get your OTP: http://w.b-a.link/otp/08d27186c6ed6b39
assbot: Request successful, get your OTP: http://w.b-a.link/otp/f4c7a7785fd43f96
assbot: Request successful, get your OTP: http://w.b-a.link/otp/5fcd835b15264557
assbot: Request successful, get your OTP: http://w.b-a.link/otp/9493f77dcc359a13
assbot: Request successful, get your OTP: http://w.b-a.link/otp/d625cacf59990e9f
assbot: Request successful, get your OTP: http://w.b-a.link/otp/1f7f6d235233d678 ☟︎
kakobrekla: each auth worth command gets own otp
mircea_popescu: asciilifeform: microshit wireless kbd crypts with xor. << OTP ? :D
gribble: Request successful for user ben_vulpes, hostmask ben_vulpes!~ben_vulpe@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
gribble: Request successful for user felipelalli, hostmask felipelalli!~Thunderbi@201.82.158.149. Get your encrypted OTP from http://bitcoin-otc.com/otps/4C0AFCCFED5CDE14
gribble: Request successful for user irdial, hostmask irdial!~irdial@unaffiliated/irdial. Get your encrypted OTP from http://bitcoin-otc.com/otps/5E16D36EDB3240F9
gribble: Request successful for user ben_vulpes, hostmask ben_vulpes!~ben_vulpe@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
asciilifeform: nanotube around? yesterday i updated my key (new exp date, same fingerprint); still getting 'Error: Problem creating encrypted OTP file.' from gribble.
asciilifeform: anyone else getting 'Error: Problem creating encrypted OTP file.' from gribble today ?
Naphex: the servers only send to any queue with user confirmation (email, otp, password
gribble: Request successful for user ben_vulpes, hostmask ben_vulpes!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
gribble: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: Request successful for user rdymac, hostmask rdymac!uid31665@gateway/web/irccloud.com/x-bfzytzxcmxfkubcc. Get your encrypted OTP from http://bitcoin-otc.com/otps/6930CFE70FA4130C
mircea_popescu: <gribble> Request successful for user mircea_popescu, hostmask mircea_popescu!~Mircea@pdpc/supporter/silver/mircea-popescu. Get your encrypted OTP from http://bitcoin-otc.com/otps/8A736F0E2FB7B452
Adlai: punkman: ugh, it's sending me an encrypted otp, but responds to eauth with "Error: You have not registered a GPG key. Try using bcauth instead, or register a GPG key first."
gribble: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: Request successful for user TheBroker, hostmask TheBroker!bec3cce4@gateway/web/freenode/ip.190.195.204.228. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AB7FCD6D06C6433
gribble: Request successful for user TheBroker, hostmask TheBroker!bec3cce4@gateway/web/freenode/ip.190.195.204.228. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AB7FCD6D06C6433
gribble: Request successful for user wangxinxi, hostmask xinxi!8984fa09@gateway/web/freenode/ip.137.132.250.9. Get your encrypted OTP from http://bitcoin-otc.com/otps/331894345B459329
gribble: Request successful for user mpoe, hostmask mpoe!~Mircea@pdpc/supporter/silver/mircea-popescu. Get your encrypted OTP from http://bitcoin-otc.com/otps/EE2BDEF602DD2D91
gribble: Request successful for user ben_vulpes, hostmask ben_vulpes!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
gribble: Request successful for user DanielKrawisz, hostmask DanielKrawisz_!~quassel@184.75.223.42. Get your encrypted OTP from http://bitcoin-otc.com/otps/101BBC10F86C4A64
gribble: I have not seen Request successful for user nubbins`, hostmask nubbins`!~leel@stjhnf0157w-142163081094.dhcp-dynamic.FibreOP.nl.bellaliant.net. Get your encrypted OTP from http://bitcoin-otc.com/otps/CF2950F23C844002.
gribble: Request successful for user JuliaTourianski_, hostmask JuliaTourianski_!1896e2e7@gateway/web/freenode/ip.24.150.226.231. Get your encrypted OTP from http://bitcoin-otc.com/otps/10572E349297B40F
gribble: Request successful for user artifexd, hostmask artifexd!sid28611@gateway/web/irccloud.com/x-nfmpjndnxxclhbjm. Get your encrypted OTP from http://bitcoin-otc.com/otps/11D1433947A3327A
gribble: Request successful for user jamesonwa, hostmask jamesonwa!~jamesonwa@2601:8:a400:178:ada8:a831:f99d:b226. Get your encrypted OTP from http://bitcoin-otc.com/otps/EE5B1CCF6A25351D
gribble: Request successful for user thestringpuller, hostmask thestringpuller!~leflor@99-39-97-12.lightspeed.tukrga.sbcglobal.net. Get your encrypted OTP from http://bitcoin-otc.com/otps/0FF2943DA179E169
gribble: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: Request successful for user ben_vulpes, hostmask ben_vulpes!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
gribble: Request successful for user TheNewDeal, hostmask TheNewDeal!b861d201@gateway/web/cgi-irc/kiwiirc.com/ip.184.97.210.1. Get your encrypted OTP from http://bitcoin-otc.com/otps/DFBEC17DF96DFB77
gribble: Request successful for user BlueMeanie4, hostmask BlueMeanie4!~chatzilla@ip-64-134-220-97.public.wayport.net. Get your encrypted OTP from http://bitcoin-otc.com/otps/DCB374BF51587535
mircea_popescu: then you decrypt the otp and go ;;everify freenode-blabla
gribble: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: Request successful for user BlueMeanie4, hostmask mircea_popescu!~Mircea@pdpc/supporter/silver/mircea-popescu. Get your encrypted OTP from http://bitcoin-otc.com/otps/DCB374BF51587535
gribble: BlueMeanie4, when you get the challenge string, use this command: (everify <otp>) -- Verify the latest encrypt-authentication request by providing your decrypted one-time password. If verified, you'll be authenticated for the duration of the bot's or your IRC session on channel (whichever is shorter).
gribble: Request successful for user BlueMeanie4, hostmask BlueMeanie4!~chatzilla@ip-64-134-220-97.public.wayport.net. Get your encrypted OTP from http://bitcoin-otc.com/otps/DCB374BF51587535
gribble: Request successful for user petenineteen, hostmask petenineteen!~petepolac@23.252.197.142. Get your encrypted OTP from http://bitcoin-otc.com/otps/7EB744F873D038C0
gribble: Request successful for user petenineteen, hostmask petenineteen!~petepolac@23.252.197.142. Get your encrypted OTP from http://bitcoin-otc.com/otps/D4ECFBB385737831
gribble: Request successful for user tylander, hostmask tylander!~tylander@71-14-6-178.static.gwnt.ga.charter.com. Get your encrypted OTP from http://bitcoin-otc.com/otps/D40DAE000726DA10
ben_vulpes: <mike_c> step 1: make OTP like gribble so i can curl it << i'm leaning more towards a gpg-encrypted api; that is to say, curl -X POST -d file_with_signcrypted_order_blob.txt api.van-ads.com/v1/drinkingrecord/buy
mike_c: step 1: make OTP like gribble so i can curl it
gribble: Request successful for user ben_vulpes, hostmask ben_vulpes!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
BingoBoingo: ben_vulpes: I've been having similat troubles retrieving my otp
gribble: Request successful for user antonosika, hostmask AntonOsika!55e5eda8@gateway/web/freenode/ip.85.229.237.168. Get your encrypted OTP from http://bitcoin-otc.com/otps/86AC5789F93ED2E7
mircea_popescu: and add a fucking cr , im sick of fishing the otp out from 33ae4284-cdba-46a1-b0ae-8f94f23b74acmirce
gribble: Request successful for user ben_vulpes, hostmask ben_vulpes!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
eregister: says incorrect otp
gribble: Request successful for user benkay, hostmask ben_vulpes!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
gribble: Request successful for user benkay, hostmask benkay!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
gribble: Request successful for user RebeccaBitcoin, hostmask RebeccaBitcoin!461a7a92@gateway/web/cgi-irc/kiwiirc.com/ip.70.26.122.146. Get your encrypted OTP from http://bitcoin-otc.com/otps/2DE03C7C54AF3F42
mircea_popescu: from what i gather, your problem was that you were using an old, cached and therefore expred otp ?
nanotube: fluffypony: the20year's problem was his browser was caching the old encrypted otp. heysteve's is probably same?
mircea_popescu: fluffypony likely they were using a stale otp
HeySteve: gribble says my OTP is incorrect but it works with altgribble. dunno what's up
gribble: Request successful for user DreadKnight, hostmask DreadKnight!~DreadKnig@unaffiliated/dreadknight. Get your encrypted OTP from http://bitcoin-otc.com/otps/F6A23D326FDF1035
gribble: Request successful for user DreadKnight, hostmask DreadKnight!~DreadKnig@unaffiliated/dreadknight. Get your encrypted OTP from http://bitcoin-otc.com/otps/F6A23D326FDF1035
gribble: Request successful for user DreadKnight, hostmask DreadKnight!~DreadKnig@unaffiliated/dreadknight. Get your encrypted OTP from http://bitcoin-otc.com/otps/F6A23D326FDF1035
mircea_popescu: <gribble> Request successful for user mircea_popescu, hostmask mircea_popescu!~Mircea@pdpc/supporter/silver/mircea-popescu. Get your encrypted OTP from http://bitcoin-otc.com/otps/8A736F0E2FB7B452
mircea_popescu: you can keep it ignored really. the otp url never changes
gribble: Request successful for user DreadKnight, hostmask DreadKnight!~DreadKnig@unaffiliated/dreadknight. Get your encrypted OTP from http://bitcoin-otc.com/otps/F6A23D326FDF1035
gribble: Request successful for user rawted, hostmask Rawted!~Rawted@66.55.134.215. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AC353E7BF1AD95E
gribble: Request successful for user rawted, hostmask Rawted!~Rawted@66.55.134.215. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AC353E7BF1AD95E
gribble: Request successful for user Xplosionist, hostmask Xplosionist!~cross@65.207.51.211. Get your encrypted OTP from http://bitcoin-otc.com/otps/F1410E75EFA0D834
gribble: Request successful for user benkay, hostmask benkay!~user@unaffiliated/benkay. Get your encrypted OTP from http://bitcoin-otc.com/otps/2AFA1A9FD2D031DA
mike_c: this trilema post needs a OTP to decode, yes?
cazalla: thestringpuller: i think it was lag + otp page was cached