spolu

12 ms·

91.
Mail Avenger: get rid of spam for good(mailavenger.org)
9 points by spolu 10y ago|1 comments
92.
by spolu 10y ago
The source code is available here: https://github.com/spolu/settle
93.
by spolu 10y ago
A friend of mine shared this this morning right before I released the blog post (translated from French): > It reminds me of the US before the introduction of the FED in 1913, each bank "issued" its own currency. Money was exch
94.
Stripe Gallery(stripe.com)
2 points by spolu 10y ago|0 comments
95.
by spolu 10y ago
hahaha! Excellent remark, I didn't think of this one.
96.
by spolu 11y ago
Following in up on this we just rolled out `application_fee` on the Order Pay endpoint ( https://stripe.com/docs/api#pay_order ). It'll behave as expected if you're familiar with the connect `application_fee`.
97.
by spolu 11y ago
Following in up on this we just rolled out `application_fee` on the Order Pay endpoint ( https://stripe.com/docs/api#pay_order ). It'll behave as expected if you're familiar with the connect `application_fee`.
98.
by spolu 11y ago
(Stripe engineer here) Running firefox as well and indeed they run a bit slow. Mea culpa. I'll let the right person know!
99.
by spolu 11y ago
So this confirms the approach that we have in mind: the ability to setup a fee at order creation as it is the case in Connect (per charge there). Very :+1: on this.
100.
by spolu 11y ago
(Hi Stripe Engineer here) Relay is a way for merchants to route products to channels. We certainly don't want to replace Shopify (with whom we're pretty close) but just give merchants an easy way to expose product information to a
101.
by spolu 11y ago
(Stripe Engineer working on Relay here) Indeed there is no way to do so at the moment. But we have that on our radar and we'd like to construct something that makes sense for apps and sellers. Some questions related to that: How would
102.
by spolu 11y ago
re Inventory: we want to provide live product availability information to the developer through our API. We encourage app developers to GET latest product info from our API before even rendering a potential Buy Now button. To make that poss
103.
by spolu 11y ago
Very thoughtful analysis! (Stripe engineer working on Relay here) Getting retailers on-board is definitely core to the success of Relay. As announced today Saks and the SAP Hybris platform are live on Relay and we're working with numer
104.
by spolu 11y ago
Feel free to repost your comment here!
105.
by spolu 11y ago
Hi! Stripe engineer here. On Apple apps, if you're integrating Relay, you're encouraged to use Apple Pay for seamless transactions! Apple is perfectly fine with that if this is not an in-app virtual good purchase. Also as pointed
106.
Productivity note-taking in the terminal(gist.github.com)
1 points by spolu 11y ago|0 comments
107.
Buck Institute for Research on Aging(en.m.wikipedia.org)
1 points by spolu 11y ago|0 comments
108.
by spolu 12y ago
> "It is the responsibility of each node v to ensure Q(v) does not violate quorum intersection". Failing to ensure quorum intersection in my quorum slices choice will have local repercussion and may befoul nodes that depend on
109.
by spolu 12y ago
Well in bitcoin, of course, trust would map to computing power.
110.
by spolu 12y ago
I think this page should answer your questions: https://medium.com/a-stellar-journey/on-worldwide-consensus-...
111.
by spolu 12y ago
(disclaimer: I had early access to the white paper for review) Sybil attacks are not really directly applicable here since each node in the system picks its own quorum slices (basically the set of nodes that it trusts). There is no notion o
112.
by spolu 12y ago
(disclaimer: I had early access to the whitepaper for review) You should look in the white paper[0] to the definition of an FBAS which differs from epaxos (while epaxos is egalitarian, SCP is federated). All related proofs are included in t
113.
Twitter Engineering – Opensource(engineering.twitter.com)
1 points by spolu 12y ago|0 comments
114.
by spolu 12y ago
Really cool execution. Love the cyphertext view. The key exchange seems a little non-secure given the length of the sharing URL? How does it work?
115.
by spolu 12y ago
The story behind this project is awesome. Built by the team behind AppGratis which got huge and was then shut down by Apple. They're now back full steam with this project.
116.
by spolu 12y ago
The story behind the service is definitely interesting. Made by the team behind AppGratis which was huge at some point but were shut down by Apple.
117.
by spolu 12y ago
This the most extreme Gist I have ever seen. So fun to see a functional browser implemented with only a few lines of code. Disclaimer, I'm on of the dev being Thrust. That's exactly why we built Thrust, but @morganrallen pushed th
118.
by spolu 12y ago
Well it's handled by Node directly right?
119.
by spolu 12y ago
It can be binded in C++ yes
120.
by spolu 12y ago
Yes exactly. I started coding in Python 2 days ago so I went with what I found (asyncio) but it could be easily recoded in Python2!

More ›