"they're skewed more heavily towards immigrant groups and minority groups. There's a reason why some folks try to keep them away from the polls."
And there's a reason you, Mr., President, want them to be forced to go to the polls. Same reason. You believe it gives you and your allies an advantage.
Of course, that presumes there is a concerted effort to keep these groups away from the polls to start with, and I dispute that, but we can disagree on that and still find fault with the initial proposal, that voting be mandatory.
Oh, and getting the money (or even the influence of money) out of politics by making voting mandatory? That was a sly joke, right?
And this works fine even if the time differences are 'positive' or 'negative'?
It's when LocalTime appears in the future that the fun begins. Snap LocalTime back a few seconds to sync with CurrentbaseTime, feh, probably livable. But make it more than an hour, and do you risk having all of those log entries either being reset to some arbitrary time, or do they have to disappear? And my password change? And the front door alarm entry? Did that get re-timed, or deleted, or marked as suspicious?
We are going to use the concept of synthetic time to resolve these issues.
I know this is nontrivial. So will the IoT deal with this sufficiently? Do many systems deal with this well?
Ditto. PostgreSQL ha been sold for real money for a long long time. Developers who made a living off their applications used it and made a living. many of them.
If 'the government' (pick one as you wish) wasn't fighting the murder-for-hire market, they could expand into a viable market and openly sell both the service and the risk.
It's inane to blame prohibition for this in any way, unless your point is that unsavory individuals tend to flock to unsavory markets, and the results when they do unto others before they are done unto would somehow be mitigated if 'the government' wasn't so darned restrictive.
This could easily happen to a site trafficking in aluminum billet shift knobs.
This is Big Deal at work. We saw nothing like this with Softcard or Google Wallet, and most of the causes are related to sloppy onboarding. Right now we are writing off almost all losses, but that's only until we resolve the major problems.
This is not just the onboarding however, and we will see changes in how these charges are authed.
I'm beginning to like Agile. I don't have to wait 2 months to find out my next release is being delayed another 2 months. In Agile I get disappointed every two weeks.
This is not sarcasm. My users now get told their fix will be in weeks, not months, and no finding out 2 months later that's another 2 months. Yes, they still wait 2 months, but it feels better. To them.
0. Netflix will charge the end ISP (Comcast, for instance) with throttling or pay-to-play.Lawsuit.
1. ISP (Comcast for instance) will claim this is the fault of the lousy Netflix connection (through Cogent, for instance), and maybe even sue the connection provider.
2. Netflix's provider (Congent, for instance) will disclaim any responsibility, maybe even sue Comcast (for instance), you know, slander.
3. After a few years, customers will buy the higher tiers of service from Comcast (for instance).
4. Before that, customers will buy the higher tier of service from Netflix, the one that has such better speed and performance, the one that is connected directly to their ISP (Comcast, for instance).
They may be wrong, but they are working for the Left in America.
Owning the majority of the media is wording. Winning elections is working. The courts are working. And they are now beginning on usurping local police.
For $700-$800+ you've solved the microphone problem. Look for used, maybe save half.
Maybe a Shure BLX14, $300
An Audio-Technica System 8 might satisfy your needs, $200 +/-
Then go fix your speaker placement and EQ the room. The Countryman likes a slight cut at 600Hz for vocals, choose the capsule cover carefully. The A-T mic I don't know well.
".dev,.lol,.app,.blog,.cloud and.search.".dev certainly has usefulness well beyond Google. ICANN should refuse this outright..app? After the fight with Apple, let ICANN deny both of them..cloud? See.dev for the explanation..lol? More of the same..search? Ask Yahoo, Microsoft, and Steve Wolfram about this..blog? Remarkably tone deaf.
ICANN should specifically refuse not only Google, but any Google-related applicant.
Unimaginable. I'll be looking to file comments on these with the relevant parties.
It's the return fire your want to suppress, as well as those last few outgoing rounds.
And the possibility that they move just a little bit and continue to fire. Your underestimate the resiliency and determination of good snipers. You had best kill them first shot.
You obviously are neither a commander nor a soldier.
Soldiers want to kill as easily as possible, lest they be killed.
Commanders want killing to be as easy as possible for their troops, to both win and get troops back.
From the movie 'Patton': "I want you to remember that no bastard ever won a war by dying for his country. He won it by making the other poor, dumb bastard die for his country."
"If you wound someone, one of their comrades has to drag them back to cover."
This is not universally true. Sometimes killing is an excellent outcome.
And then there is the problem of roles. You can wound a MRAP driver and cause problems, but you'll want to kill the sniper with the first shot, lest they continue shooting.
Ditto. My phone is handier than my wallet, and I can pull up Softcard, PIN in, and tap faster than you say 'oh, please....'. And you're gonna be fishing for another penny to save time with exact change.
Disclaimer - I work for a Softcard partner, and am sort of sad to see it go to Google. But hopefully it will become the main competitor to Apple Pay, which is for us an interesting problem. All is not bliss in Apple Pay land.
Major retailers track auth processing on the order of milliseconds. Online retailers track them down to tens of microseconds. Most acquirers commit to no more than a 2 second response. Varying from this regularly by 100 milliseconds is a three-alarm emergency. These retailers call them on the carpet when they see this. It's considered 'friction', and they want 'frictionless' transactions. Once you click 'buy', they want this to happen fast fast fast.
In the old days, sonny, a 10 second auth was the goal when your terminal DIALED UP THE AUTH SYSTEM THROUGH A MODEM. USR made a killing selling Total Control model pools with a special warble that would train the terminal modem in 3 seconds. Every other modem struggled to train up a 110 baud connection in 3-6 seconds. With a TC hub, you could hope for a 6 second auth.
If you're waiting more than 6 seconds to see 'APPROVED' on the terminal screen, something is not working as it should. Most likely the retailer.
Slashdot Mirror
"they're skewed more heavily towards immigrant groups and minority groups. There's a reason why some folks try to keep them away from the polls."
And there's a reason you, Mr., President, want them to be forced to go to the polls. Same reason. You believe it gives you and your allies an advantage.
Of course, that presumes there is a concerted effort to keep these groups away from the polls to start with, and I dispute that, but we can disagree on that and still find fault with the initial proposal, that voting be mandatory.
Oh, and getting the money (or even the influence of money) out of politics by making voting mandatory? That was a sly joke, right?
And this works fine even if the time differences are 'positive' or 'negative'?
It's when LocalTime appears in the future that the fun begins. Snap LocalTime back a few seconds to sync with CurrentbaseTime, feh, probably livable. But make it more than an hour, and do you risk having all of those log entries either being reset to some arbitrary time, or do they have to disappear? And my password change? And the front door alarm entry? Did that get re-timed, or deleted, or marked as suspicious?
We are going to use the concept of synthetic time to resolve these issues.
I know this is nontrivial. So will the IoT deal with this sufficiently? Do many systems deal with this well?
Ditto. PostgreSQL ha been sold for real money for a long long time. Developers who made a living off their applications used it and made a living. many of them.
You dismiss it out of hand to your disadvantage.
So it's a cluster, um,whatever.
If 'the government' (pick one as you wish) wasn't fighting the murder-for-hire market, they could expand into a viable market and openly sell both the service and the risk.
It's inane to blame prohibition for this in any way, unless your point is that unsavory individuals tend to flock to unsavory markets, and the results when they do unto others before they are done unto would somehow be mitigated if 'the government' wasn't so darned restrictive.
This could easily happen to a site trafficking in aluminum billet shift knobs.
This is Big Deal at work. We saw nothing like this with Softcard or Google Wallet, and most of the causes are related to sloppy onboarding. Right now we are writing off almost all losses, but that's only until we resolve the major problems.
This is not just the onboarding however, and we will see changes in how these charges are authed.
Growing pains. I'm not excessively worried yet.
I've been using Softcard for almost a year. Who's copying who?
Our third major release in 18 months is going out in two weeks. We have not yet sunk into the quicksand.
I'm beginning to like Agile. I don't have to wait 2 months to find out my next release is being delayed another 2 months. In Agile I get disappointed every two weeks.
This is not sarcasm. My users now get told their fix will be in weeks, not months, and no finding out 2 months later that's another 2 months. Yes, they still wait 2 months, but it feels better. To them.
0. Netflix will charge the end ISP (Comcast, for instance) with throttling or pay-to-play.Lawsuit.
1. ISP (Comcast for instance) will claim this is the fault of the lousy Netflix connection (through Cogent, for instance), and maybe even sue the connection provider.
2. Netflix's provider (Congent, for instance) will disclaim any responsibility, maybe even sue Comcast (for instance), you know, slander.
3. After a few years, customers will buy the higher tiers of service from Comcast (for instance).
4. Before that, customers will buy the higher tier of service from Netflix, the one that has such better speed and performance, the one that is connected directly to their ISP (Comcast, for instance).
5. Profit!
And little has changed.
They may be wrong, but they are working for the Left in America.
Owning the majority of the media is wording.
Winning elections is working.
The courts are working.
And they are now beginning on usurping local police.
Only opposition can still them, obviously.
Any of the Sennheiser or Shure wireless packs.
Countryman E6 type headset. Best every
For $700-$800+ you've solved the microphone problem. Look for used, maybe save half.
Maybe a Shure BLX14, $300
An Audio-Technica System 8 might satisfy your needs, $200 +/-
Then go fix your speaker placement and EQ the room. The Countryman likes a slight cut at 600Hz for vocals, choose the capsule cover carefully. The A-T mic I don't know well.
Are we going to permit 'inadvertently shed" fingerprints also?
Oh, wait...
Actually, there is no technical reason to limit .TLDs to a single registrar. Oh, wait...
I got to pile on about this.
".dev, .lol, .app, .blog, .cloud and .search." .dev certainly has usefulness well beyond Google. ICANN should refuse this outright. .app? After the fight with Apple, let ICANN deny both of them. .cloud? See .dev for the explanation. .lol? More of the same. .search? Ask Yahoo, Microsoft, and Steve Wolfram about this. .blog? Remarkably tone deaf.
ICANN should specifically refuse not only Google, but any Google-related applicant.
Unimaginable. I'll be looking to file comments on these with the relevant parties.
I used a DUN connectoid, but. Wildcat! was fun.
Trumpet Winsock.
Next question.
It's the return fire your want to suppress, as well as those last few outgoing rounds.
And the possibility that they move just a little bit and continue to fire. Your underestimate the resiliency and determination of good snipers. You had best kill them first shot.
You obviously are neither a commander nor a soldier.
Soldiers want to kill as easily as possible, lest they be killed.
Commanders want killing to be as easy as possible for their troops, to both win and get troops back.
From the movie 'Patton': "I want you to remember that no bastard ever won a war by dying for his country. He won it by making the other poor, dumb bastard die for his country."
If only Patton had said that.
"If you wound someone, one of their comrades has to drag them back to cover."
This is not universally true. Sometimes killing is an excellent outcome.
And then there is the problem of roles. You can wound a MRAP driver and cause problems, but you'll want to kill the sniper with the first shot, lest they continue shooting.
Ditto. My phone is handier than my wallet, and I can pull up Softcard, PIN in, and tap faster than you say 'oh, please....'. And you're gonna be fishing for another penny to save time with exact change.
Disclaimer - I work for a Softcard partner, and am sort of sad to see it go to Google. But hopefully it will become the main competitor to Apple Pay, which is for us an interesting problem. All is not bliss in Apple Pay land.
"There is at least a 5 second processing time. Closer to 10 seconds in most cases"
The acquirer takes 2 seconds tops. 60-200 millisecond round trip.
The rest are POS issues, and even small stores have systems that don't take 7 seconds to give the operator the thumbs up...
Major retailers track auth processing on the order of milliseconds. Online retailers track them down to tens of microseconds. Most acquirers commit to no more than a 2 second response. Varying from this regularly by 100 milliseconds is a three-alarm emergency. These retailers call them on the carpet when they see this. It's considered 'friction', and they want 'frictionless' transactions. Once you click 'buy', they want this to happen fast fast fast.
In the old days, sonny, a 10 second auth was the goal when your terminal DIALED UP THE AUTH SYSTEM THROUGH A MODEM. USR made a killing selling Total Control model pools with a special warble that would train the terminal modem in 3 seconds. Every other modem struggled to train up a 110 baud connection in 3-6 seconds. With a TC hub, you could hope for a 6 second auth.
If you're waiting more than 6 seconds to see 'APPROVED' on the terminal screen, something is not working as it should. Most likely the retailer.
If I intend to use my Softcard, I've opened it, entered my PIN, and put it back in my pocket on the way into the store, or while I'm in line.
This is not so hard.
Let them print your check for you and it won't be 2 minutes.