A bit off topic but I was a tad disappointed that Sean Young wasn't used (I think I would have heard if she was) to play the head of Tyrell Corporation.
The Tyrell Corporation went bankrupt, after the global blackout caused by an EMP detonation (presumably done by replicants), and the remains of the company were bought by the Wallace Corporation.
Hasn't that always been the case with any Microsoft software? Their users are constantly struggling with the uncertainty principle and can often make a system collapse merely by observing it.
Hence all the telemetry in their products.
(And, not sure if I mean to be funny, informative, insightful, etc...)
The more you can verify, the less you need to rely on trust. But how do you verify that a VPN provider is well-behaved?
Simple: (a) Register with multiple VPN providers. (b) Make threats against the President using different aliases through different VPNs. (c) See who the Secret Service comes looking for.
Perl 5 was Larry Wall's rewrite of Perl 4, and was widely seen as a huge improvement and a mature language.
Perl 6 was the community's rewrite of Perl 5.
That the horse committee didn't improve the design should be no surprise, and it certainly shouldn't reflect on Larry Wall. People really wanted a lot of those features, but more people don't want it to get that complicated and won't use it. Personally, I switched to Ruby.
Conversion rates in the checkout flow are a key measure for ecommerce sites. 46% of e-commerce shoppers abandon the checkout process during the payment phase, signaling frustration with the complexity and redundancy of re-entering form data or tracking down payment information. Even a small increase in the success rate of checkout make a direct impact on your site’s bottom line, while improving the shopping experience for customers.
Many problems related to online purchase abandonment can be traced to checkout forms, which are user-intensive, difficult to use, slow to load and refresh, and require multiple steps to complete.
Sure, this API may make things simpler for you -- the purchaser -- but it seems the focus is on benefiting the seller. Perhaps a narrow distinction, but one that may matter if/when push comes to shove and a side must be chosen by the developers.
Another thing to consider: Since this is implemented in the browser, if you use multiple browsers to shop, then you'll have to store your information in each browser rather than once on the websites on which you shop -- unless the browser vendors can cooperate on a single, shared data storage method.
*any* website can query your browser for available payment info.
Nonsense. That is NOT what TFA says, and that is not how it currently works in Chrome.
From TFA:
The researcher notes that sites that don't sell any products or advertisers could abuse the API to fingerprint and profile users (detect what payment options each user/browser has stored in its settings), or detect when the user is paying from a normal or incognito mode session.
Though, it's unclear as to what information can be queried. And whatever Chrome has implemented isn't the final API being developed.
With the data stored in the browser, then *any* website can query your stored payment info.
Bullcrap. This is totally wrong. RTFA... or download the latest Chrome and try it.
From TFA:
The researcher notes that sites that don't sell any products or advertisers could abuse the API to fingerprint and profile users (detect what payment options each user/browser has stored in its settings), or detect when the user is paying from a normal or incognito mode session.
Though, it's unclear as to what information can be queried. Furthermore, whatever Chrome has implemented isn't the final API being developed.
Because the alternative to sharing your password is to keep it secret and type it each time you need it. But the alternative to your browser storing your CC# is that it is stored by every online merchant you buy from.
Unless you specifically ask the website to store your CC info, it's not saved beyond that transaction (or it's not suppose to be saved). This is why you need to re-enter it otherwise. With the data stored in the browser, then *any* website can query your stored payment info.
How about YES. It is implausible that this will be any worse than the existing system.
Read TFA. If the payment info is stored in the browser, then *any* website can query your browser for available payment info. In addition, the browser maker - Mozilla, Microsoft, Google, etc... - could (will) have access to this info and any transactions.
As it is now, for me at least, is that, with the exception of Amazon, I don't save my payment information on any website and prefer to re-enter it whenever I make a payment. Furthermore, on sites other than Amazon, I almost always use a virtual credit card (ShopSafe) so the CC info is different for each vendor/purchase - rendering storing it in the browser useless.
The researcher notes that sites that don't sell any products or advertisers could abuse the API to fingerprint and profile users (detect what payment options each user/browser has stored in its settings), or detect when the user is paying from a normal or incognito mode session.
Just great. Then any website could query your browser for available payment information.
Payment providers like PayPal or Amazon might not be on board with this new API since it makes them obsolete, but almost everyone else is.
Or because, in the case of something like Amazon Payments or "Pay with Amazon" they actually need to store your payment information to process transactions that occur outside the browser. If I'm using that, I don't need my browser to handle it too.
In many ways, the Payment Request API is a much secure method of handling online transactions, but it's not perfect either.
For starters, browser makers now have a full view of your finances and transactions, a situation that some people might not like, and will refuse to store any such information in their browser.
Ya think? I imagine the above will be a non-starter for many. Like I want Mozilla, Microsoft or Google accessing my CC transactions.
Fantastic... you decided to compare the crushed optimism of cancer patients.. with the election results of the United States almost a year ago. Back under the bridge Troll... we won't pay your taxes.!!!
Hey anonymous fuckhead. My wife died of a brain tumor in 2006 *and* I didn't vote for Trump, so I understand crushed optimism.
Number of times I wanted to listen to music in the past week? 3.
Number of times I wanted a translation in the past, Oh, I dunno, 50 years? 0.
On the other hand, it'll probably be a lot more useful than any of the new "features" they keep shoehorning into Firefox. (Just added lockPref("browser.newtabpage.activity-stream.enabled", false); to my mozilla.cfg file.)
Star Trek usually considers the moral and philosophical implications of choices, but so far there has been very little of that in Discover
That would be science fiction. CBS isn't in the sci-fi business....
Too true. Furthermore, The Federation is suppose to be a society without money, yet Star Trek: Discovery (STD) is the first Star Trek series we must explicitly pay to watch.
(Note: I'm not paying CBS to watch one show (even if it came with a Happy Meal and a hand-job).)
Slashdot Mirror
A bit off topic but I was a tad disappointed that Sean Young wasn't used (I think I would have heard if she was) to play the head of Tyrell Corporation.
The Tyrell Corporation went bankrupt, after the global blackout caused by an EMP detonation (presumably done by replicants), and the remains of the company were bought by the Wallace Corporation.
2. The death scene at the end was just.. perfect. The falling Snow.
It's good symmetry with (spoiler) Batty's death in the original film, but, you sure he's dead?
But they should sit just 3 feet from a UHDTV of the same size, ...
There are better ways of going blind, like masturbating.
Hasn't that always been the case with any Microsoft software? Their users are constantly struggling with the uncertainty principle and can often make a system collapse merely by observing it.
Hence all the telemetry in their products.
(And, not sure if I mean to be funny, informative, insightful, etc...)
But Elon Musk "has a history of some pretty pie-in-the-sky promises,"...
Elon Musk announced that SpaceX is developing a direct-to-home pie delivery service.
The more you can verify, the less you need to rely on trust. But how do you verify that a VPN provider is well-behaved?
Simple: (a) Register with multiple VPN providers. (b) Make threats against the President using different aliases through different VPNs. (c) See who the Secret Service comes looking for.
... creating silent (but still-active) music streaming.
Dear My ISP,
Why is my reported usage so high? I swear I don't use that much data.
Sincerely,
Confused Customer
You don't understand what Perl 6 is.
Perl 4 was very popular.
Perl 5 was Larry Wall's rewrite of Perl 4, and was widely seen as a huge improvement and a mature language.
Perl 6 was the community's rewrite of Perl 5.
That the horse committee didn't improve the design should be no surprise, and it certainly shouldn't reflect on Larry Wall. People really wanted a lot of those features, but more people don't want it to get that complicated and won't use it. Personally, I switched to Ruby.
In short: Perl 5 is, simply, good enough.
Conversion rates in the checkout flow are a key measure for ecommerce sites. 46% of e-commerce shoppers abandon the checkout process during the payment phase, signaling frustration with the complexity and redundancy of re-entering form data or tracking down payment information. Even a small increase in the success rate of checkout make a direct impact on your site’s bottom line, while improving the shopping experience for customers.
From Payment Request API
Many problems related to online purchase abandonment can be traced to checkout forms, which are user-intensive, difficult to use, slow to load and refresh, and require multiple steps to complete.
Sure, this API may make things simpler for you -- the purchaser -- but it seems the focus is on benefiting the seller. Perhaps a narrow distinction, but one that may matter if/when push comes to shove and a side must be chosen by the developers.
Another thing to consider: Since this is implemented in the browser, if you use multiple browsers to shop, then you'll have to store your information in each browser rather than once on the websites on which you shop -- unless the browser vendors can cooperate on a single, shared data storage method.
*any* website can query your browser for available payment info.
Nonsense. That is NOT what TFA says, and that is not how it currently works in Chrome.
From TFA:
The researcher notes that sites that don't sell any products or advertisers could abuse the API to fingerprint and profile users (detect what payment options each user/browser has stored in its settings), or detect when the user is paying from a normal or incognito mode session.
Though, it's unclear as to what information can be queried. And whatever Chrome has implemented isn't the final API being developed.
With the data stored in the browser, then *any* website can query your stored payment info.
Bullcrap. This is totally wrong. RTFA ... or download the latest Chrome and try it.
From TFA:
The researcher notes that sites that don't sell any products or advertisers could abuse the API to fingerprint and profile users (detect what payment options each user/browser has stored in its settings), or detect when the user is paying from a normal or incognito mode session.
Though, it's unclear as to what information can be queried. Furthermore, whatever Chrome has implemented isn't the final API being developed.
Butterflies flap their wings in Denver and radar systems go nuts.
Because the alternative to sharing your password is to keep it secret and type it each time you need it. But the alternative to your browser storing your CC# is that it is stored by every online merchant you buy from.
Unless you specifically ask the website to store your CC info, it's not saved beyond that transaction (or it's not suppose to be saved). This is why you need to re-enter it otherwise. With the data stored in the browser, then *any* website can query your stored payment info.
How about no.
How about YES. It is implausible that this will be any worse than the existing system.
Read TFA. If the payment info is stored in the browser, then *any* website can query your browser for available payment info. In addition, the browser maker - Mozilla, Microsoft, Google, etc... - could (will) have access to this info and any transactions.
As it is now, for me at least, is that, with the exception of Amazon, I don't save my payment information on any website and prefer to re-enter it whenever I make a payment. Furthermore, on sites other than Amazon, I almost always use a virtual credit card (ShopSafe) so the CC info is different for each vendor/purchase - rendering storing it in the browser useless.
The researcher notes that sites that don't sell any products or advertisers could abuse the API to fingerprint and profile users (detect what payment options each user/browser has stored in its settings), or detect when the user is paying from a normal or incognito mode session.
Just great. Then any website could query your browser for available payment information.
Payment providers like PayPal or Amazon might not be on board with this new API since it makes them obsolete, but almost everyone else is.
Or because, in the case of something like Amazon Payments or "Pay with Amazon" they actually need to store your payment information to process transactions that occur outside the browser. If I'm using that, I don't need my browser to handle it too.
In many ways, the Payment Request API is a much secure method of handling online transactions, but it's not perfect either.
For starters, browser makers now have a full view of your finances and transactions, a situation that some people might not like, and will refuse to store any such information in their browser.
Ya think? I imagine the above will be a non-starter for many. Like I want Mozilla, Microsoft or Google accessing my CC transactions.
Trump thinks there's coal on the Moon.
Vice President Pence Vows US Astronauts Will Return To the Moon
Some of us don't like things turning themselves back on. If i set something off, i want it off until i personally decide i want it back on.
I feel that way about my dick.
Fantastic... you decided to compare the crushed optimism of cancer patients.. with the election results of the United States almost a year ago. Back under the bridge Troll... we won't pay your taxes.!!!
Hey anonymous fuckhead. My wife died of a brain tumor in 2006 *and* I didn't vote for Trump, so I understand crushed optimism.
Overall 57% of uses showed no benefits for either survival or quality of life.
Almost the same ratio for Republicans in the U.S. House and Senate. </non-sequitur-political-rant>
His name is Allan Doctor? I guess his career was a foregone conclusion.
Ya, but... T. J. Hooker was a cop.
Number of times I wanted to listen to music in the past week? 3.
Number of times I wanted a translation in the past, Oh, I dunno, 50 years? 0.
On the other hand, it'll probably be a lot more useful than any of the new "features" they keep shoehorning into Firefox. (Just added lockPref("browser.newtabpage.activity-stream.enabled", false); to my mozilla.cfg file.)
Use your existing analog headphones with the included adapter ...
Which is a separate Bluetooth-enabled feature phone, with a headphone jack.
Star Trek usually considers the moral and philosophical implications of choices, but so far there has been very little of that in Discover
That would be science fiction. CBS isn't in the sci-fi business. ...
Too true. Furthermore, The Federation is suppose to be a society without money, yet Star Trek: Discovery (STD) is the first Star Trek series we must explicitly pay to watch.
(Note: I'm not paying CBS to watch one show (even if it came with a Happy Meal and a hand-job).)