618700+ entries in 0.326s
mircea_popescu: "freenode group registration is currently suspended, as
the group registration process became significantly backlogged
to
the point
that it was not viable
to continue
taking new registrations.
This is an unfortunate side-effect of
the combination of
the following"
mircea_popescu: you don't have
to name
the group =
the channel do you.
teward: (#bitcoin-* is
typically considered #bitcoin, like #anything-* is #anything)
teward: mircea_popescu: unless #bitcoin-assets is its own Group Registration, it falls in
the #bitcoin* namespace
mircea_popescu: and yes, freenode policy is
to cloak bots by maintainer.
bounce: for freenode, whoever has access
to
the backend and can fix it if it goes amok
RagnarDanneskjol: uhh,
thought some person needs
to secure keypair for anygiven bot - like I assume kako has assbot's
bounce: only after icahn badgered
them
to do it for months
mircea_popescu: bounce omidyar has figured out paypal / website payments are dead in
the water, selling it while he's ahead of
the curve.
bounce: ebay
to spin out paypal again. huh.
mircea_popescu: (easy
to arb,
too, go on fiverr, have 20 people write articles, get 2 accepted by coindeks, profit)
mircea_popescu: $90 buys you an hour's work of a professional.
their articles are 15 minute jobs by 3rd worlders. 9 bux is a gross exaggeration.
bounce: s/combines/spits out/ (from
the combination, etc.)
bounce: now I wonder, if you provide an oracle
that combines a programmatically generated key from (secret) seed and (public) user number, would
that be enough
to recover
the secret?
nanotube: mircea_popescu: re db queries - depends on frequency of gribble queries. if you'd be querying gribble more
than once per 15 min, get
the db.
mircea_popescu: bounce notrly. you use a single address chiefly because
that way mitm is pointless.
mircea_popescu: MolokoDesk maybe instead of hashing,keep a serial of when people go .deposit and use
that,
mircea_popescu: bounce actually hashing isn't even
the right approach, should serialize.
mircea_popescu: easy enough for anyone
to
test it, send 10k satoshi see if you get it.
bounce: you start having problems well before 10000,
that with hash collissions and everything
MolokoDesk: what's
the likely volume of
the pooled wallet for what... 50 people?
mircea_popescu: and if it becomes a problem we move
to 6 or w/e. not
that any irc chan ever had 10k members online.
MolokoDesk: 10k
transactions. oh. each user has a unique 4-digits always
the same.
their "account number" sure.
MolokoDesk: uh, what chance of
two people randomly choosing
the same 4-digit deposit suffix?
MolokoDesk: ok. with
two audit
trails
that should be bulletproof, if it's all done in
this channel
the published channel logs are a matter of record.
the payment extension also keeps an audit
trail and a database.
mircea_popescu: hardened systems means among other
things breaking
the convenient assumptions of
the enemy.
mircea_popescu: and you only have one address in your wallet, and pay from it whenever someone asks and
that's
that.
MolokoDesk: "oh gosh,
that guy revealed
the check digits of his paymet.. I'm going
to make a payment
to
the same person for no reason with
THE SAME LAST DIGITS!" = not likely
to be motivated by anything.
mircea_popescu: one doesn't presume anything.
this is how
the system works.
MolokoDesk: I guess one presumes nobody wants
to give people money at random.
mircea_popescu: no need for any of
that. you just use a hash of
their userid
to generate a 4 digit pin, and credit
to
their acct all deposits
to your address
that have
that pin for last 4 digits.
MolokoDesk: they send you a microchange digit set and you confirm on
that.
mircea_popescu: Hi MP. Please send
to 1blabla make sure last 4 digits are 1944
MolokoDesk: so
they just say "that wallet was mine"?
mircea_popescu: ~~~ [Use last 4 decimals encoding
to identify owner]~~~
MolokoDesk: so all you really now is
that some wallet somewhere sent you btc.
MolokoDesk: right. how does one put money into
the account in one's nick.
mircea_popescu: Send X Bitcoin
to Y address. [Use last 4 decimals encoding
to identify owner] <
kakobrekla: <mircea_popescu> kakobrekla aren't you glad you closed pritni. < is not
that simple.
MolokoDesk: ok. so
they don't need
to register a wallet ID with WoT?
MolokoDesk: they'd be sent back
to
the originator or just forfeited.
MolokoDesk: random payments from unregistered wallets would sit in an account with no owner until someone registered
them, but
that's not a sound practice.
MolokoDesk: ok, for
the payment system, it would create accounts based on wallet of origin of incoming payments.
those would be
the same wallets registered in web of
trust/gribble, I presume.
deedBot: (switching DEEDBOT_CHAN from #cex-squawk
to #bitcoin-assets)
deedBot: (switching DEEDBOT_CHAN from #cex-squawk
to #bitcoin-assets)
MolokoDesk: just realized
that
Tao_Jones has a "joke" payment system in it called luzcoin it's not a real coin, it just keeps accounts for people in one IRC channel elsewhere and
they mess about with it rhetorically. it has a mining back end
that increments
the accounts in a sporadic lottery.
mircea_popescu: it HAD
to ruin
the 31bn bet, and
then die right after ?
bounce: so much for "leveraging
the synergy"
bounce: well, how can it be if I get called
to explain
the joke?
bounce: heroku and google apps both, "for
the resiliency"
MolokoDesk: well, I can write
the payments extension but deciding where
to run it may be a different issue.
mircea_popescu: you can use any wp installation
to basically probe for free or whatever else.
mircea_popescu: don't even get me started on
the
topic of wordpress lmao. fucktards put a ddos hole in
their xmlrpc
bounce: this isn't usually a problem among
the, let's call
them "usenet crowd". people who're reasonably good at discussing more
than one
thing per email and are
technically minded so don't
take it
too personally when asked
to answer a
technical question.
MolokoDesk: for example I deleted wordpress from
this VM. I don't use it and didn't even want it
there.
mircea_popescu: MolokoDesk
these days, security mostly relies on not updating
to
the newest set of bugs.
MolokoDesk: as 'security' best practices is mostly don't use certain language constructs, or coding practices
that allow exploits from web input.
mircea_popescu: and so management has
to fly people all over back and forth all day.
mircea_popescu: bounce
the motherfucking answer! is
the reason face
to face productivity is better, btw. as expensive
travel is, sometimes it's unavoidable, as people will mousy over emails for a year if given
the chance
MolokoDesk: I'm
thinking more of operating system updates, security patches, surveillance.
mircea_popescu: well, good code means you won't have
to do it constantly, cause good code never breaks :D
MolokoDesk: yeah, I
think
that was a symptom of long-term interests in other
things.
MolokoDesk: it's not so much not knowing, it's having
to do it constantly.
mircea_popescu: MolokoDesk if you're wondering,
the entire line was prompted by <MolokoDesk> ok. I'll look into
this. I'm not a security guy and linux admin is not something I do regularly
bounce can't get recruiters, hr peeps, or even first line support idjits
to f'n answer
their emails.
bounce: you lack "answer
the question" skills, eh. well, not
the only one.
mircea_popescu: mkay. if you're under 30 stfu and learn some unix admining, it can't hurt you. if over 30 you probably have a point focusing on other
things.
MolokoDesk: or are you asking whether I grasp
the
troll aesthetic?
mircea_popescu: because i am
trying
to determine whether
telling you
to stfu and learn some unix admining is a good policy or not