Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Payment Request API

w3.org

Post reply on HN
Print view View original

31–40 of 128 posts

Re: Payment Request API

#31

Post by RandomInteger4 »

swiley wrote: post #28
throwaway284534 wrote: post #22

Earlier quoted context omitted.

The W3C is run by the same peers who frequent this and other tech forums. You can help by contributing to the organization, or you could hope for some internet points with snarky remarks. Which do you want to be remembered for?

Alright "run" wasn't the right word, "heavily influenced by" is probably better. They just seem to continuously standardize things that are very user hostile and only serve content distributors.

If people want to make money of the content they produce and other people are happy to pay them, then what's the problem?

Re: Payment Request API

#32

Post by jimktrains2 »

lsaferite wrote: post #30
jimktrains2 wrote: post #21

Earlier quoted context omitted.

Just a clarification, a credit card number is an iin, pan, and checksum. http://jimkeener.com/posts/everyday-numbers-1

Interesting that the post says the term BIN (vs. IIN) isn't commonly used anymore, but it's practically the only thing I've heard them called in the last 10+ years of ecomm dev.

I've seen both. When I wrote the post all the docs from the gateways I had access to called then iin with a historical note on bin. I done have access to those docs anymore though.

Re: Payment Request API

#33

Post by octalmage »

gobengo wrote: post #20

It's exciting and all that this API could make us not have to type in our credit cards so often. But the same API should also be able to let us choose which wallet to pay cryptocurrencies from.

Cryptocurrency support is something they're very interested in.

Re: Payment Request API

#36

Post by detaro »

swiley wrote: post #28
throwaway284534 wrote: post #22

Earlier quoted context omitted.

The W3C is run by the same peers who frequent this and other tech forums. You can help by contributing to the organization, or you could hope for some internet points with snarky remarks. Which do you want to be remembered for?

Alright "run" wasn't the right word, "heavily influenced by" is probably better. They just seem to continuously standardize things that are very user hostile and only serve content distributors.

> continuously standardize things that are very user hostile and only serve content distributors.

Example Nr 1 you are going to quote is the DRM stuff (understandably, it's the most controversial for good reasons, both inside and outside W3C). What other very user hostile examples are there?

Re: Payment Request API

#37

Post by sadlyNess »

canremember wrote: post #17
askvictor wrote: post #11

Earlier quoted context omitted.

To enable micropayments for content such as news.

True micropayments integrated in browser would be amazing. Imagine instead of ads or subscriptions, you could pay a few pennies for an article. It would revolutionize online content, in a good way. Nobody would be willing to pay for clickbait type stuff, but I think people would be willing to pay for quality content and journalism.

There's been a debate for a while now about this. Clay Shirky, Walter Isaacson, Jakob Nielsen, Norman Hardy, Kevin Kelley and others have expressed arguments for and against(mostly for) micropayments. But there's yet to be a success story, most early implementations failed(BitPass, Ezcash, Peppercoin) but that was before cryptocurrencies. Now there's a new crop(Steemit, 21.co?, etc) that are trying again. Interesting to see how this will all pan out.

Re: Payment Request API

#38

Post by kyrra »

microcolonel wrote: post #29
ChrisMorrisOrg wrote: post #25

Not sure if this is still the case, but Marcos from Mozilla did a talk on this at CampJS earlier this year. Apparently Chrome will send data about the items purchased to Google, even if you’re using a payment provider completely unrelated to Google. Unlike Chrome, Firefox will apparently not send data about what you purchase back to Mozilla. Edit: https://twitter.com/chrismorrisorg/status/896352427426799618

Is there a source for this? That seems like a pretty outrageous thing for a browser to do.

Agreed. I'd also like to see the source for this, as I can't find it mentioned anywhere on the Chrome sites about PaymentRequest or any of the top sites talking about Chrome Payment Request.

Re: Payment Request API

#39

Post by andai »

ChrisMorrisOrg wrote: post #25

Not sure if this is still the case, but Marcos from Mozilla did a talk on this at CampJS earlier this year. Apparently Chrome will send data about the items purchased to Google, even if you’re using a payment provider completely unrelated to Google. Unlike Chrome, Firefox will apparently not send data about what you purchase back to Mozilla. Edit: https://twitter.com/chrismorrisorg/status/896352427426799618

Isn't that information already sent if you sync your history?

Re: Payment Request API

#40

Post by 482794793792894 »

microcolonel wrote: post #29
ChrisMorrisOrg wrote: post #25

Not sure if this is still the case, but Marcos from Mozilla did a talk on this at CampJS earlier this year. Apparently Chrome will send data about the items purchased to Google, even if you’re using a payment provider completely unrelated to Google. Unlike Chrome, Firefox will apparently not send data about what you purchase back to Mozilla. Edit: https://twitter.com/chrismorrisorg/status/896352427426799618

Is there a source for this? That seems like a pretty outrageous thing for a browser to do.

Don't think there's recordings of CampJS for this year, but on the schedule [1] there's a talk about it listed by Marcos Caceres. You could probably ask the guy on Twitter (@marcosc).

[1] http://viii.campjs.com/sessions/#payments

Post reply on HN