The article doesn't even specify whether the T-mobile customer was the caller or the callee who couldn't be reached. Lots of passive voice and non-specific wording.
Higher than normal means that they pushed out earlier releases, despite causing a fair number of BSODs. The number of errors is just much higher this time around. The high number of issues caused by an automatic update should be near zero, even after accounting for third party software. And that really was the case for service packs in all earlier releases of Windows.
The new updater constantly makes bad assumptions, especially regarding the layout and size of EFI system partitions. The number one cause of a blue screen after an update seems to be a broken boot configuration that Windows also can't fix with it's automatic startup repair.
Yes. With each new twice-yearly release, all the Microsoft drivers have their dates bumped to match the OS build date, even when nothing is changed or fixed. Even if you block/hide a particular driver via Windows update, the "new" driver from the next build gets auto installed again.
You're right. But the article doesn't actually say this except indirectly.
Here is the quote from the actual FCC report that explains it much better than any of the articles that were written without digging at all:
7. Beginning in June and continuing through the summer of 2016, the Commission received complaints from three rural incumbent LECs in Wisconsin. These complaints, which were filed in the Commission’s rural call completion e-mail box, alleged over 40 incidents in which T-Mobile customers were unable to complete calls to consumers served by these three rural providers. Many of the complaints reported that the calling party heard ring tones on call attempts that failed to reach the rural customers. The Enforcement Bureau (Bureau) served these complaints on T-Mobile and requested that the Company contact the complainants, investigate and resolve the problems, and submit reports of its investigations to the Bureau. In two instances, the Bureau pointed out to T-Mobile that the Commission’s rules prohibit sending ring tones to the calling party before the called party is alerted to an incoming call.
8. T-Mobile subsequently filed with the Bureau reports of its investigations of the complaints. In each instance, T-Mobile reported that it had handed the call off to an intermediate provider for delivery, and that any reported problems had been “resolved.” T-Mobile stated that it believed that the actions taken by intermediate providers in response to each complaint had remedied all problems and did not specifically address the ring tone issue raised in some of the complaints.
They were trying to cover up that their customers weren't actually getting service they were paying for. They collected more than $40M from affected rural customers in service fees - totally fair.
Because you're fraudulently leading the person to believe that there's no problem with the T-mobile customer's signal/reception and that they are just not answering.
If you release using alkaline batteries against a competitor with baked in li-on, you'll probably lose.
That depends heavily on the product. If it's something I know I'll be using 10 years from now, I want some sort of guarantee of battery availability when I've hit the limit of charge cycles. For a Canon DSLR camera, it's fine - there will definitely be replacement batteries out there. If it's a small tool or gadget that won't ever have huge marketshare, there's no way I don't want alkaline or NiMH AA batteries. But to be honest, things like my flashlight get alkaline batteries - the batteries last 3-5 years depending on usage patterns and the investment for rechargeables probably will never be worth it.
Even in its Google incarnation, it could federate with any server that implemented the protocol (much like email) - you didn't even need to touch Google's servers. The UI was only one implementation. Of course, UI was the hardest part of designing something like that and probably failing that is what killed it.
Sure you can play Spotify with it. Just buy an iPhone or iPad and use airplay to stream to it. Of course you already have to have one of those just to set it up. Out of box setup is iOS only. Not even Mac OS.
No, it doesn't make it louder per se. But the distance between the quietest sound possible and the loudest sound possible is increased. So the loudest thing is louder, assuming that your volume is adjusted to make everything else roughly equal.
I admit I haven't seen a whole lot of vinyl up close, but I think the gap between the groves it's usually wider than the grooves themselves. If you can tighten manufacturing tolerances without making the record too fragile to play, I could imagine it still being possible.
And then there's this, from the patent:
the mastering process further includes applying a so-called Rheinsche Füllschrift process to ensure that, in quieter parts of the audio, the groove spacing is reduced whereas in louder parts of the audio, the groove spacing is increased
It's probably more generational than you realize. What is easy to parse visually is whichever is in the more familiar style. If you primarily use other apps designed in a similar way, then a redesign in that style will make whatever you're using more parse-able.
I'm early millennial and I've never really used Google Flights. When looking at both, I think the first one is much easier to understand, even if the more advanced features aren't available until after you search. Think about the "save icon" as a very basic example. If you've never used a floppy disk, it's just a meaningless symbol that doesn't make sense unless you have some sort of historical context to tie it to.
Slashdot Mirror
2001 is after "up to 2000," you know.
The article doesn't even specify whether the T-mobile customer was the caller or the callee who couldn't be reached. Lots of passive voice and non-specific wording.
They're following the antivirus markets - free/cheap users are guinea pigs.
I've never even seen the term RS2, but I much prefer the simple version numbers like 1709 with the month and year, even if the month code is a lie.
Higher than normal means that they pushed out earlier releases, despite causing a fair number of BSODs. The number of errors is just much higher this time around. The high number of issues caused by an automatic update should be near zero, even after accounting for third party software. And that really was the case for service packs in all earlier releases of Windows.
The new updater constantly makes bad assumptions, especially regarding the layout and size of EFI system partitions. The number one cause of a blue screen after an update seems to be a broken boot configuration that Windows also can't fix with it's automatic startup repair.
Yes. With each new twice-yearly release, all the Microsoft drivers have their dates bumped to match the OS build date, even when nothing is changed or fixed. Even if you block/hide a particular driver via Windows update, the "new" driver from the next build gets auto installed again.
You're right. But the article doesn't actually say this except indirectly.
Here is the quote from the actual FCC report that explains it much better than any of the articles that were written without digging at all:
7. Beginning in June and continuing through the summer of 2016, the Commission received
complaints from three rural incumbent LECs in Wisconsin. These complaints, which were filed in the
Commission’s rural call completion e-mail box, alleged over 40 incidents in which T-Mobile customers
were unable to complete calls to consumers served by these three rural providers. Many of the complaints
reported that the calling party heard ring tones on call attempts that failed to reach the rural customers.
The Enforcement Bureau (Bureau) served these complaints on T-Mobile and requested that the Company
contact the complainants, investigate and resolve the problems, and submit reports of its investigations to
the Bureau. In two instances, the Bureau pointed out to T-Mobile that the Commission’s rules prohibit
sending ring tones to the calling party before the called party is alerted to an incoming call.
8. T-Mobile subsequently filed with the Bureau reports of its investigations of the
complaints. In each instance, T-Mobile reported that it had handed the call off to an intermediate
provider for delivery, and that any reported problems had been “resolved.” T-Mobile stated that it
believed that the actions taken by intermediate providers in response to each complaint had remedied all
problems and did not specifically address the ring tone issue raised in some of the complaints.
They were trying to cover up that their customers weren't actually getting service they were paying for. They collected more than $40M from affected rural customers in service fees - totally fair.
That's absolutely right. And because they didn't, they were fined
Because you're fraudulently leading the person to believe that there's no problem with the T-mobile customer's signal/reception and that they are just not answering.
That is not the original meaning of Ring tone. This refers to the sound a caller hears after dialing and thinks your phone is ringing.
Energizer owns both Rayovac and Eveready.
Electronics, usually. An ancient cassette Walkman will play slightly too slow.
If you release using alkaline batteries against a competitor with baked in li-on, you'll probably lose.
That depends heavily on the product. If it's something I know I'll be using 10 years from now, I want some sort of guarantee of battery availability when I've hit the limit of charge cycles. For a Canon DSLR camera, it's fine - there will definitely be replacement batteries out there. If it's a small tool or gadget that won't ever have huge marketshare, there's no way I don't want alkaline or NiMH AA batteries. But to be honest, things like my flashlight get alkaline batteries - the batteries last 3-5 years depending on usage patterns and the investment for rechargeables probably will never be worth it.
Even in its Google incarnation, it could federate with any server that implemented the protocol (much like email) - you didn't even need to touch Google's servers. The UI was only one implementation. Of course, UI was the hardest part of designing something like that and probably failing that is what killed it.
Google Wave failed. Apache Wave is also dead as of Jan. 2018.
On the app store, are you looking at the India-only version?
Relevant link: https://m.hello.com/en/downloa...
Worse, it's probably an app with an HTML/Javascript based UI. Good luck distracting people at work, if it's not available on PC.
Sure you can play Spotify with it. Just buy an iPhone or iPad and use airplay to stream to it. Of course you already have to have one of those just to set it up. Out of box setup is iOS only. Not even Mac OS.
We're talking about music here, and there is very little content that isn't stereo or mono.
No, it doesn't make it louder per se. But the distance between the quietest sound possible and the loudest sound possible is increased. So the loudest thing is louder, assuming that your volume is adjusted to make everything else roughly equal.
I admit I haven't seen a whole lot of vinyl up close, but I think the gap between the groves it's usually wider than the grooves themselves. If you can tighten manufacturing tolerances without making the record too fragile to play, I could imagine it still being possible.
And then there's this, from the patent:
the mastering process further includes applying a so-called Rheinsche Füllschrift process to ensure that, in quieter parts of the audio, the groove spacing is reduced whereas in louder parts of the audio, the groove spacing is increased
Larger dynamic range, I'm sure. Stupid dumbed down writing.
It's probably more generational than you realize. What is easy to parse visually is whichever is in the more familiar style. If you primarily use other apps designed in a similar way, then a redesign in that style will make whatever you're using more parse-able.
I'm early millennial and I've never really used Google Flights. When looking at both, I think the first one is much easier to understand, even if the more advanced features aren't available until after you search. Think about the "save icon" as a very basic example. If you've never used a floppy disk, it's just a meaningless symbol that doesn't make sense unless you have some sort of historical context to tie it to.
Type it into a regular Google search instead of the new event form and it works fine.