159800+ entries in 0.11s
jhvh1: 3. Made a decision
to
turn our will and our lives over
to
the care of God as we understood Him.
BingoBoingo: Acceptance is
the answer. You don't *have*
to be such a downer about
things.
BingoBoingo: That doesn't look like an answer
to zee question
ppsk: are
there any other blogs worth reading, similar but not necessarily
the same as Mircea's?
☟︎ ppsk: is
there any reality where you can read
that line and not automatically imagine it in an austrian accent
hanbot: *
tmsrcat (~tmsrcat@unaffiliated/hanbot/bot/tmsrcat) has joined #trilema-hanbot << yeah it was all my account setup's fault,
thanks phf &
trinque. hopefully i'ma manage
to make something useful out of
this.
shinohai: I wonder how ben_vulpes and his SO ever had children without a blockchain app
to record menstrual cycles on.
mod6: <+shinohai> I almost hate
the fucking word `blockchain` by now <<
these guys are funny huh?
shinohai: Ah buenas
tardes mircea_popescu !
a111: Logged on 2017-09-04 18:14 shinohai: I almost hate
the fucking word `blockchain` by now
a111: Logged on 2017-09-04 11:51 phf: problem is
that nickserv doesn't say
that anymore,
the message is still
the same, but it now adds some control sequences
that i
think make
the font bold or italic or something in
the legacy irc clients (???)
shinohai: I almost hate
the fucking word `blockchain` by now
☟︎ trinque: mark of
the beast, eh danielpbarron ?
trinque: asciilifeform:
http://archive.is/LTf4O << relatedly "We see it as a stepping stone
to a future where central banks issue
their own [cryptocurrency] at some point." says UBS reptile
trinque: hanbot: it is indeed expecting
to see its own nick come back in
those strings.
hanbot: ty phf, i'll
try
that. also
the bot identifies as me (grouped
to my acct); if it was expecting bot's nick maybe
that's a problem...
a111: Logged on 2017-09-04 11:51 phf: problem is
that nickserv doesn't say
that anymore,
the message is still
the same, but it now adds some control sequences
that i
think make
the font bold or italic or something in
the legacy irc clients (???)
jhvh1: asciilifeform:
The operation succeeded.
phf: problem is
that nickserv doesn't say
that anymore,
the message is still
the same, but it now adds some control sequences
that i
think make
the font bold or italic or something in
the legacy irc clients (???)
☟︎☟︎ a111: Logged on 2017-09-04 06:58 hanbot: say
trinque :
tyvm for making
this ircbot & post. i can get it
to connect and authenticate, but not
to join a channel (target channel was given along with port nick etc). can i make it join after it's connected?
hanbot: say
trinque :
tyvm for making
this ircbot & post. i can get it
to connect and authenticate, but not
to join a channel (target channel was given along with port nick etc). can i make it join after it's connected?
☟︎ mircea_popescu: find one bad key, find another 8 keys weak
to
the previously unknown other-prime
mircea_popescu: interesting how
the phuctored list goes longer over
time
mircea_popescu: what could have possibly happened. went back into
the soup
that spawns
them.
BingoBoingo: lol, whatever happened
to eskimo bob and his coinless heat mine
BingoBoingo: <asciilifeform> maginumberz are evil. <<
They also have boring
tulpas
PeterL: anyway, I am off
to bed now
PeterL: in implementing keccac, do we really need
to have special case functions for 256 bit and 512 bit outputs? couldn't we just define it as
the variable length output function and
then if somebody wants 256 bit output
they just choose
that as
the length?
PeterL: speaking of github, a while ago I was reading
through some random code
there, and
they had a variable which was about 75 characters in length. I understand
trying
to make your variable names meaningful, but
that is just absurd!
PeterL: right, I
think if we implement it it would be quite smaller
a111: Logged on 2017-09-02 16:44 mircea_popescu: one major point is
that other
than mpfhf which has been well implemented
thanks
to peterl, sina and ben_vulpes (and
to some degree researched -- speaking of which, still cooking ben_vulpes ?),
there's keccak which HASNT yet been implemented much ; and we really could use a fixed-block hash function
that's any good.
PeterL:
http://btcbase.org/log/2017-09-02#1709989 << I was reading
through
the keccac documents, got about 90% of it implemented in python,
then said
this is ugly and horribly inefficient, I should
try ada, and have been leaning ada
the past couple weeks
☝︎ PeterL: my brother-in-law said he
tried it,
the fires smelled horribly of dogs (he has 3 dogs)
PeterL: it is just
to get
the fire going, you only need a pinch
a111: Logged on 2017-08-29 22:50 BingoBoingo: Ah fine, I'll start keeping
the sawdust/bar oil slurry
mircea_popescu: "and who did you see at
the crime scene ?" "Other Person" "Ah, so not
this one ?
Thank you. Your honor, no further questions."
trinque: only point I'm looking for an operator fee, can
then do as many ops as one likes.
trinque: in fact my fee for
the bot operation comes at
time of deposit. say you want
to deposit 5btc. it may ask you
to deposit 5.00004821.
mircea_popescu: see, way it works is, acct requests a deposit address. you look if you have one, if you don't you create and communicate. if it gets paid you sweep it, and remove it off "there's one". if it isn't paid you just reuse it next
time
trinque: if
that doesn't bother anyone, can remove
the step, yep.
trinque: the
thought re OTP is if I don't force people
to verify one, I'm letting allcomers generate "chosen-plaintext" for a particular key
trinque: all
that's left for a usable first cut is a payment
to a particular invoice, and a command
to list one's inbound and outbound invoices