People can't be trusted to be responsible. This has been clearly demonstrated with widespread harm caused by previously patched security bugs being none the less exploited.
Microsoft can't be trusted to be responsible. This has been clearly demonstrated with tricky/forced migration from older OS versions, data loss, and dead PCs.
You force updates on people seemingly non-stop, several of them cause huge problems, including data loss, and now you're building functionality to remove botched updates?
Here is a radical idea for you: Give us back control of when to apply updates.
Not defer them for a few days. Not select a slower update track. Put a damn setting that makes it our own responsibility to go click the update button again.
- Non replaceable batteries OR OEM refuses to make available replacement batteries - Devices that can't be reasonably easily opened (e.g. require hot air gun to pry away glued-down screen to get into case) - Vendor applies warranty void stickers or attempts to void warranty for effecting a repair via replacement of a battery or modular part
And smaller penalties for: - Devices that are not modular (e.g. things like cameras, speakers, etc. soldered to mainboard) - Vendor commits to OS security updates and/or critical fixes for less than 3 years
I would like to educate myself with IDA for non-commercial use, but Starter is nearly $1000 and doesn't even handle 64-bit binaries. That is ridiculous.
Hex-Rays deprived themselves of corporate licensing last year when, having been unable to familiarize myself with anything but the old free 5.0 edition due to the cost, I could not confidently tell the person who approves the PO that yes, I am fairly confident I can use this tool to solve our problem.
I am very glad to see this competitor come along even if only for the fact it might make someone at Hex Rays re-evaluate their model.
That is total bollocks. You'd have to be a video encoding total noob to believe it.
These video standards have various "profiles" that define the encoding "tools" that can be used, and the characteristics of the target decoders. These can vastly change the required bitrate to acheive a given quality. The quality of the encoder design makes a vast different too. Finally, moreso than anything, the characteristics of the input video affect the required bitrate for a given quality. A football game may need 3x the rate of a sitcom to look good.
If you want a real measure of the quality of an image, you might come _close_ if you use some well established metrics, but the most common do have weaknesses when compared against the human eye. They also require the source material as an input.
If you want a good guess, look at the quantizer value in the bitstream. This is an indication of how accurately the encoder stored the picture data for each new frame. A lower value means it discarded less of the signal, a higher value means it discarded more. This will be a primary driver of changes in the output bitrate.
There are various other things to consider, such as the frame/block types, but quantizer should get you close.
The app no longer reflects whether transit is on time, early, or late (which is reported by our MTS), so now even if I know the route it's harder to make my connections.
Does this allow someone to actually distribute a tool to enable breaking DRM for these purposes? Because it's all very well that you can break DRM, but it's totally toothless if each individual must do so themselves, as very few actually have the skills at time to do so.
Why respect copyright, when nothing will ever enter the public domain any more? There was supposed to be a balance where copyright would be enforced until a work became old enough where upon it would enter the public domain. It now stands that upon your grave, works you enjoyed as a child and possibly paid for many times over throughout your life will still not be free when you die.
What is really bizarre is that Apple seems to see no end to humiliating DST/time-based bugs. You would think they would have standard libraries/development guides/mandatory test cases related to this stuff by now.
Every time I log into a new box, the checkbox to remember this computer (and thus bypass 2FA in future) is pre-checked when inserting my hardware token.
Yes, signing into a machine means that to a certain degree I believe it's not already compromised. However, if I was wrong, and it was compromised, at least the hardware token should prevent password replays after 20 seconds had elapsed. Not with Google's defaults though! AFAIK there isn't even an option to change the default to unchecked if I wanted to.
Opus, except at _extremely_ low bitrates, has similar or better quality than the most commonly used modern codecs: http://opus-codec.org/comparis...
Flac is fast to encode and decode. Opus decodes slower than MP3 but on par with AAC LC, and encodes slightly faster than AAC LC and on par with MP3. Performance will vary a bit by encoder: http://fmedia.firmdev.com/audi...
Beating x264 (the encoder) is a very big accomplishment, because:
- It is very well recognized as the leading H264 encoder
- An incredible amount of time has been spent optimizing it
- It has been done while avoiding patent encumbered, which takes many well established algorithms/techniques off the table
Claiming that it's "not an accomplishment at all" tells me that you're extremely ignorant of the level of work involved here.
T-Mo have had problems with number hijacking/SIM-re-issue, malicious porting out of numbers to other networks, and now I find that they're storing passwords partially in plain text?
None of this matters. Google can document their new features to their heart's content. The Android update model ensures that the vast majority of people won't have these features on their phones for years.
* Nexus 5X: Notorious for just dying by going into a cycle of endless reboots one day, totally out of the blue. Refurbed replacements do the exact same thing. * Nexus 6P: Notorious for battery issues where after 1-1.5 years of use it will just start shutting down with 25-30% battery remaining * Pixel: Notorious for microphones breaking
The bizarre thing is that it seems rare for manufacturing rev's to happen, and with the Pixel's prices are high and price drops are rare (Play store still sells Pixel 1 for $549 base even today). They are trying to hold Apple-like prices on devices that have questionable quality issues. Fortunately Pixel 2 seems to be faring better, although Pixel 2 XL has been noted for LG's quality variance regarding the display viewing angle and burn-in. As an owner of some of these (mainly due to desiring a phone that gets regular security updates), Google appears very arrogant in their pricing.
Slashdot Mirror
... when I can just install Chrome? ;)
"It is made by Israel-based company Cellebrite, which says the technology does not access or store personal content."
The same company that sells devices to access personal content.
This is basically just a push by Cellebrite to standardize their expensive licenses because they specialize in opening locked phones/forensics.
People can't be trusted to be responsible. This has been clearly demonstrated with widespread harm caused by previously patched security bugs being none the less exploited.
Microsoft can't be trusted to be responsible. This has been clearly demonstrated with tricky/forced migration from older OS versions, data loss, and dead PCs.
You force updates on people seemingly non-stop, several of them cause huge problems, including data loss, and now you're building functionality to remove botched updates?
Here is a radical idea for you: Give us back control of when to apply updates.
Not defer them for a few days. Not select a slower update track. Put a damn setting that makes it our own responsibility to go click the update button again.
It's the same frequencies as 4G LTE, plus millimeter wave, which is also non-ionizing.
https://en.wikipedia.org/wiki/...
Think of all the new RF we've had in the past couple of decades with WiFi and cell towers absolutely everywhere.
What's happened to the rates of incidence of new cancer cases over that time? They're flat/down.
https://progressreport.cancer....
I call BS.
Seriously,
You are going to start in the middle of nowhere and end in the middle of nowhere. If this is the plan, just nix the entire thing.
All phones shipping with Android 8.0+ are required to support Treble's platform abstraction layer
Yeah? Call me when old phones actually start getting updates.
There should be significant tax penalties for:
- Non replaceable batteries OR OEM refuses to make available replacement batteries
- Devices that can't be reasonably easily opened (e.g. require hot air gun to pry away glued-down screen to get into case)
- Vendor applies warranty void stickers or attempts to void warranty for effecting a repair via replacement of a battery or modular part
And smaller penalties for:
- Devices that are not modular (e.g. things like cameras, speakers, etc. soldered to mainboard)
- Vendor commits to OS security updates and/or critical fixes for less than 3 years
IDA's pricing scheme is ridiculous.
I would like to educate myself with IDA for non-commercial use, but Starter is nearly $1000 and doesn't even handle 64-bit binaries. That is ridiculous.
Hex-Rays deprived themselves of corporate licensing last year when, having been unable to familiarize myself with anything but the old free 5.0 edition due to the cost, I could not confidently tell the person who approves the PO that yes, I am fairly confident I can use this tool to solve our problem.
I am very glad to see this competitor come along even if only for the fact it might make someone at Hex Rays re-evaluate their model.
That is total bollocks. You'd have to be a video encoding total noob to believe it.
These video standards have various "profiles" that define the encoding "tools" that can be used, and the characteristics of the target decoders. These can vastly change the required bitrate to acheive a given quality. The quality of the encoder design makes a vast different too. Finally, moreso than anything, the characteristics of the input video affect the required bitrate for a given quality. A football game may need 3x the rate of a sitcom to look good.
If you want a real measure of the quality of an image, you might come _close_ if you use some well established metrics, but the most common do have weaknesses when compared against the human eye. They also require the source material as an input.
If you want a good guess, look at the quantizer value in the bitstream. This is an indication of how accurately the encoder stored the picture data for each new frame. A lower value means it discarded less of the signal, a higher value means it discarded more. This will be a primary driver of changes in the output bitrate.
There are various other things to consider, such as the frame/block types, but quantizer should get you close.
The app no longer reflects whether transit is on time, early, or late (which is reported by our MTS), so now even if I know the route it's harder to make my connections.
Does this allow someone to actually distribute a tool to enable breaking DRM for these purposes? Because it's all very well that you can break DRM, but it's totally toothless if each individual must do so themselves, as very few actually have the skills at time to do so.
Apparently STILL the only phone OEM STILL looking out for the USER'S Privacy...
Is that true?
Does anyone know how Pixel stands up against like tools?
Why respect copyright, when nothing will ever enter the public domain any more? There was supposed to be a balance where copyright would be enforced until a work became old enough where upon it would enter the public domain. It now stands that upon your grave, works you enjoyed as a child and possibly paid for many times over throughout your life will still not be free when you die.
What I find really annoying about the Home Hub is the lack of a camera. It's a device that begs to be sued for video calls but can't be.
They say they did this for privacy reasons, but it's nothing a flip or slide cover wouldn't have solved equally well.
So many of Google's design decisions just leave you thinking, "ugh... why?!?" these days.
What is really bizarre is that Apple seems to see no end to humiliating DST/time-based bugs. You would think they would have standard libraries/development guides/mandatory test cases related to this stuff by now.
> DoH keeps third-party observers from knowing what websites a user is trying to access.
But isn't this information normally exposed by the TLS SNI extension anyway? You'd probably need to run a VPN to escape this particular risk.
Every time I log into a new box, the checkbox to remember this computer (and thus bypass 2FA in future) is pre-checked when inserting my hardware token.
Yes, signing into a machine means that to a certain degree I believe it's not already compromised. However, if I was wrong, and it was compromised, at least the hardware token should prevent password replays after 20 seconds had elapsed. Not with Google's defaults though! AFAIK there isn't even an option to change the default to unchecked if I wanted to.
Flac is lossless, it's full quality.
Opus, except at _extremely_ low bitrates, has similar or better quality than the most commonly used modern codecs:
http://opus-codec.org/comparis...
Flac is fast to encode and decode. Opus decodes slower than MP3 but on par with AAC LC, and encodes slightly faster than AAC LC and on par with MP3. Performance will vary a bit by encoder:
http://fmedia.firmdev.com/audi...
Beating x264 (the encoder) is a very big accomplishment, because:
- It is very well recognized as the leading H264 encoder
- An incredible amount of time has been spent optimizing it
- It has been done while avoiding patent encumbered, which takes many well established algorithms/techniques off the table
Claiming that it's "not an accomplishment at all" tells me that you're extremely ignorant of the level of work involved here.
Update: T-Mobile reps are denying storing them in plain text on Twitter so this may be a miscommunication gone out of hand.
T-Mo have had problems with number hijacking/SIM-re-issue, malicious porting out of numbers to other networks, and now I find that they're storing passwords partially in plain text?
What the actual F, T-Mobile?!
None of this matters. Google can document their new features to their heart's content. The Android update model ensures that the vast majority of people won't have these features on their phones for years.
Google's recent phones have all had problems:
* Nexus 5X: Notorious for just dying by going into a cycle of endless reboots one day, totally out of the blue. Refurbed replacements do the exact same thing.
* Nexus 6P: Notorious for battery issues where after 1-1.5 years of use it will just start shutting down with 25-30% battery remaining
* Pixel: Notorious for microphones breaking
The bizarre thing is that it seems rare for manufacturing rev's to happen, and with the Pixel's prices are high and price drops are rare (Play store still sells Pixel 1 for $549 base even today). They are trying to hold Apple-like prices on devices that have questionable quality issues. Fortunately Pixel 2 seems to be faring better, although Pixel 2 XL has been noted for LG's quality variance regarding the display viewing angle and burn-in. As an owner of some of these (mainly due to desiring a phone that gets regular security updates), Google appears very arrogant in their pricing.