691400+ entries in 0.423s
davout: their "Fair rate(TM)" is pretty ridiculous
too
davout: that doesn't change
the point
pankkake: * Managed Bitcoin wallet in
the cloud
assbot: CoinJar for iPhone on
the App Store on iTunes
davout: so, i
thought like you, but
the facts seem
to
tell a different story
davout: pankkake: well, i pointed out
the fact
that
their new policy didn't mean shit
taken on its own, however it appears
there are some wallets
that are back in
pankkake: do
they really allow bitcoin applications, or is it yet another redditation?
dub: which is a change from last
time I
thought about it
dub: just making an observation, we
tend
to run close
to
the front of
tech
trends over here and it struck me
that apple are pretty much invisible outside of mobile
davout: also,
they're finally sucking
the bitcoin cock :D
davout: dub: well, osx is pretty good for ui imo, so i'm happy
this way
davout: i keep raging about it each
time i use a windows comp, and i don't use gui when i use linux
davout: pankkake: i use it everyday, and imo it's
the best window management, it never feels like it gets in
the way
pankkake: it's just not ergonomic. makes you work a lot with
the mouse for nothing
dub: I don't need unix at my end
terminal and its only a couple of clicks away
pankkake: with
the worst window management ever
davout: jurov:
the gorgeous
trashcan is ridiculous indeed
davout: dub: a feature i like it's
that
their OS is a unix
dub: thats not just idle fanboy hatred either,
they have a lot of mobile handsets around but beyond a few music heads (who suffer extreme lock-in) I don't know any actual users
dub: apple only does stupid features so its unfair
to pick on
this
fluffypony: yeah I quite like Apple and I
think
that's a stupid feature
to focus on
jurov: one has
to be apple hater
to find such "features" ridiculous?
adrrr: pankkake: mostly,
there is apple haters :D
pankkake: "That is a gorgeous
trash can," Federighi said. "You wouldn't believe how much
time we spent crafting a
trash can."
pankkake: "Yosemite has cleaner and clearer icons along
the bottom of a Mac screen, including
the apps
that usually value function over beauty." wait
there are macapps
that value function?
assbot: Apple OS X 10.10 Yosemite:
The
Top 6 New Features
davout: the sec will have
to go feck itself eventually
davout: for example,
the service call "monitor bitcoin address xyz for x days" is common between a deposit address creation, and an invoice creation
davout: they need
to go in
the ledger, also
these
transactions may share properties
davout: sure, but
they all need
to be accounted for
Naphex: or an exchange
transaction != payment
transaction
Naphex: davout: but an exchange
transaction != a bitcoin
transaction
davout: it needs
to record
transactions
Naphex: but why does it have
to also manage
the wallets, and record user
transactions, and process payments
Naphex: well,
the exchange api will be
that sequential queue.
davout: how does having it as a separate
thing help ?
davout: it *has*
to be a sequential queue
that's processed FIFO
davout: well, look at
the
trading for example
Naphex: and eventually you will have
to split it
to scale
Naphex: i just
think one big app
to handle wallet api, exchange api, payments api might just be
too big
davout: there is a blockchain watching process
that notifies
the models when it sees an incoming payment
Naphex: see, now will
that api do payments processing as well in
the same big app?
davout: it's not built in
to
the app
davout: yeah, we have
that
too,
the web interface is a module
that hooks into
the API
Naphex: they come up with servicing in mind, and
the same way a client hooks up
to
them web platforms hook up as well
Naphex: and payment nodes
to process payments and get auto notifications from
them
Naphex: exchange nodes can be accessed
to convert
the currency
Naphex: and
they can handle
their duty, wallet nodes can be used by clients
to connect and manage
their wallets
davout: Naphex: you're bound
to have quite some coupling
xmj: no need
to reinvent wheels if you already have a stack of
them.
Naphex: now i know services are secure and
they stay clean and sharp
to
the point code
xmj: benefit: you can reuse
those parts more easily across customers.
Naphex: <+davout> Naphex: i don't
think splitting apps would make it less vulnerable, on
the contrary, having only one attack surface is easier
to manage <<
Naphex: but i have done a lot of
that for embedded and it worked out very nice
Naphex: but rarely i have
to do
that for backends, as in hardware nowadays is
too fast
to care
Naphex: i do
the same in jave, write JNI if
there are bottlenecks or
too slow performing native functions
Naphex: python's not bad.
twisted python is perty okay
xmj: By
the
time you have serious scaling issues, you can always write
things in Cython.
xmj: I really really like Python, because it's legible and fast
to write prototypes in.
xmj: matter of
taste i guess.
Naphex: but i don't use servlets or other middleware, so
there's
that.
Naphex: then you got really good
tools, and profilers and debuggers
Naphex: xmj: its pretty lean, fast,
threading is a dream and NIO is great and fast and easy
to implement
xmj: Naphex: Java seems a popular choice for financial
transaction backends
davout: api for example, we leverage a lot of code
that already exists,
the extra part is a couple of models and
their business logic,
the e-commerce plugins are separate ofc
fluffypony: I hear he's switching
to Swift after watching
the Apple demo on Monday
davout: Naphex: i don't
think splitting apps would make it less vulnerable, on
the contrary, having only one attack surface is easier
to manage
Naphex: since merchant are going
too need merchant reports, invoice listings, button generators, cart generators, apis and plugins
to intergrate in popular ecommerce platforms
xmj: Naphex: what language do you write
that one in?
Naphex: probably but
that opens a whole lot of room, for vulnerabilities, bugs, spaghetti code, maintainance problems
davout: also, a lot of code
to check for incoming payments and
track
them properly is shared
Naphex: i
think exchange / payment services are
too big fields
too keep under same app
davout: i like
the idea of having a single app
to maintain
Naphex: but
the merchant services will be a whole differnt app with merchant in mind, and all
the features
that come with merchant gateways
davout: i mean can't a merchant request
to be paid 12.34 EUR and receive exactly
that ?
Naphex: so atleast
they share same wallet/account
davout: you don't do
the exchanging ?
Naphex: well interlink code is needed anyway, for wallet apps and
the rest
Naphex: then BTCXPay for payments / BTXChange for
trading/exchanging
Naphex: and unifing
the wallets so
they can interlink
Naphex: i mean we're working on finalizing
the payment/merchant gateway as well. but we're building
them as separate projects
to avoid clutter
Naphex: no i mean just in general,
the code
the platform etc
davout: you mean on
the front page ?
Naphex: won't it clutter up with all
the merchant features?
Naphex: you're doing merchant services / exchange under
the same platform?
davout: since we're launching merchant services at about
the same
time and
that we're going
to have a single landing page it needs some lifting
Naphex: just change Bitcoin-Central
to Paymium on front page, and you're about done :P
davout: it's scheduled,
the UI designer is going crazy :D
Naphex: i'm working on a realtime protobuf interface for
trading, with incremental streamed updates and realtime orders.
Naphex: and just sell
that mass improved
Naphex: also why would someone just roll another fast interface when
they can roll a high performance i/o protobuf one
davout: Naphex: no i didn't, it's on
the backburner currently
Naphex: no worries, every
time someone does it a shiba inu dies