Trucks often pay a significant fee for their use of highways. This is necessary because a truck causes over a thousand times more road damage than a car. So yeah, that particular example is not so great. They should definitely be paying much, much more than cars to use public roadways.
The declarativeNetRequest API only allows extensions to block or redirect requests. The webRequest api is more flexible as compared to the declarativeNetRequest API because it allows extensions to evaluate a request programmatically.
Local proxies are still allowed. And likely always will be if they want the corporate market share (this is the reason tls 1.3 got blocked for a year). Add your proxy's CA to your trusted certs and it can mogrify all the pages you send its way, regardless of security or origin. Granted, you can no longer see the original certificate from the origin webserver, but block ads it will.
At that time, the trick wasn't to get applications to run with their own permissions, it was to keep them running in ring 3 w/o overwriting your OS, libraries, page tables, or accessing any PIO registers that could crash the system in new and surprising ways. It was still the wild west of windows memory management and process isolation.
I have the same experience; the battery utility tells you which apps it wants to "optimize," but in no way does it (or can it) tell you what that will do to app functionality, so it's extremely easy to click through and "optimize all" without thinking about it. This list-based power management probably needs to be done at the Android platform level, not through separate OEM applications, so user applications can report what functionality they'll lose if you disable background operation.
But once I figured out what it was doing, I became extremely happy with how easy it was to work with.
This breaks the window to content relation, unless it goes away when unfocused. And if it goes away, why bother having it outside the content window? If the user can't figure out which web page/app generated the pop-out, this feature is only going to cause frustration.
EZpass already uses plate readers as a backup for the RF beacons. I don't know why it uses both, though I suspect visibility issues require it (snow, fog, etc).
With the upcoming prevalence of forward-looking mm-wave radar, we could potentially automatically map potholes -- something automakers might want to do to avoid small objects on the road (at autonomous level >=4) and provide a smoother ride. Ideally, they would require no user interaction to report it.
The existing data systems are awesome, and would totally fit the bill if they were available for use by the government. They even use GPS, which is almost exactly what I described. In fact, we could contract one of these folks to build the federal infrastructure for us; a ready made system built on government contract, owned and operated by the government. Unique infrastructure projects should be owned by the state/fed in any case where a most-preferred-customer clause doesn't make sense; viz. the service isn't being sold to anyone else. Because if the government (or any corporate entity) started using the interface a lot, you can bet that the data set owner will charge plenty of money for access fees, especially if the government wanted the interface/product to stay supported and to-specification over a long period of time.
The road tax should be monthly and incremental and paid to the region in which the vehicle is used and based on the weight of the vehicle. Thus GPS tracks (or just county-tagged mileage) + automatic reporting (over some wireless tech, possibly as simple as bluetooth+phone app) + minor enhancements to stored telemetry which is already in most all modern cars, including ICE. The EDR (blackbox) capability has been mandatory since 2014. Server side, legal side, and bureaucracy-side would be much more of a burden, but it could (and should) be implemented federally and paid to locality. Ideally, it would end toll booths and independent ezpass nonsense. Even better if it provided statistical information about which roads get used the most and the condition of those roads (potholes, roughness, etc) which would aid in repair/expansion planning.
If you're worried about privacy concerns, you should take public transport or a taxi. It's not like you turn your phone off in the car anyway; 80+% of you use your phone while driving. A phone bleeds the same location information and we've got no location/metadata protection laws here in the USA. We may as well put it to good use fairly taxing based on usage (eg equivalent single axle load) and better understanding the usage patterns of our roads.
Hi, what? Sales-weighted average MPG for passenger cars is >36 MPG as of 2014. The average went down 31% in 2 years? Do you have a reference? Here's mine:
https://www.rita.dot.gov/bts/s...
I started using 2FA recently, before that unique passwords & pw manager. I've never been bitten by security problems, but I'm relatively low profile.
Working with u2f (yubikey) and totp (google authenticator) has been a bit annoying. Most sites don't support u2f, or even 2FA in general. The ones I want to have 2FA, like my bank, do not or they implement it through sms/email. Some sites, like Facebook, have issues with multiple u2f tokens (ie. second and subsequent tokens do not work). It requires extra effort to get gmail working in external clients with saved device trust instead of 2FA as well.
Actually using u2f has been nice though, even with chrome on android via nfc. Once things are set up on a site, it's very reliable.
Regarding things that break over time in linux, at least these days, if I static link with musl I can guarantee my binaries will work on other distributions as opposed to being jacked by glibc. Granted nsswitch will be broken if you want to use anything but dns, but screw it!
Delphi's another language that lets you get shit done without really knowing or caring too much about what you're doing. The GUI editor is easy to use and you can basically drop in tiny code snippets without really thinking about your object model too much. Even FFI definitions are easy to do in Delphi. If I didn't have python-tkinter and ctypes, I'd probably be using Delphi or Lazarus/fpc for our in-house device testing UIs.
The worst problems I've run into with delphi/pascal is migrating projects from old versions of the IDE to new ones and having weird bugs creep in.
That and the guy who wrote a lot of it had a peculiar habit of misspelling variable names just slightly and using different variants for different things, but that's not a language fault.
The CPAN library system is mature, it has ports on a ridiculous number of platforms, and the syntax isn't even particularly awful. If anything, its curse is (anecdotally) that it's everywhere and new-to-perl developers run across old code all the time and struggle to figure out the system it backs. And the fact that perl hacks had (have?) a bad habit of becoming defacto production code.
Repeating what A.C.s 1 & 3 said, Chrome is all about forcing you to upgrade. The Goog has an administrative background service which prevents you from ever receiving the UAC prompt because they update that frequently and they don't want to train users to blindly click through UACs that were not initiated by user action. Mozilla Firefox does this too. All of which would be better handled through Microsoft Store, Chocolatey, or some other unified package update interface.
DAB is not HDFM. DAB uses MP2 @
DAB also transmits 9-12 channels in a single 1.5MHz transmission that must be simultaneously received (expensive), then the stream you want can be decoded from the digital data. HDFM uses normal 200kHz-wide channels or subchannels of normal radio transmissions. This guarantees battery life is always going to be worse for portables decoding DAB and DAB+ than HDFM, and both will be a lot worse than demodulating simple FM directly.
All that aside, I could care less about what they do to commercial radio as long as they leave AM weather and emergency radio alone. Were I Norwegian, it would bother me that the government is effectively forcing the use of a patented codec because the out-of-patent codec allowed by the DAB standard sounds like shit compared to FM.
I'd say it is warranted to credit MS with making serious effort to maintain backward compatibility. A win32 binary (not driver) which if implemented to spec on Windows XP w/ VC++6.0 probably still runs in Windows 10, at least until they kill off win32 in favor of UWP. Win32 and COM's fanatical (and much appreciated) adherence to ABI versioning means most software packages will run for a very long time via MS's compatibility shims. How many commercial or FOSS projects can you think of which provide those kinds of version compatibility shims? The only one I can think of is glibc and very few projects appear to target versioned symbols. Microsoft's backwards-compat-OCD exceeds what is possible with static linking.
Slashdot Mirror
Mission creep. Their original purpose and their present purpose appear to have a conflict of interest...
Trucks often pay a significant fee for their use of highways. This is necessary because a truck causes over a thousand times more road damage than a car. So yeah, that particular example is not so great. They should definitely be paying much, much more than cars to use public roadways.
The declarativeNetRequest API only allows extensions to block or redirect requests. The webRequest api is more flexible as compared to the declarativeNetRequest API because it allows extensions to evaluate a request programmatically.
Seems to say all that needs to be said.
Local proxies are still allowed. And likely always will be if they want the corporate market share (this is the reason tls 1.3 got blocked for a year). Add your proxy's CA to your trusted certs and it can mogrify all the pages you send its way, regardless of security or origin. Granted, you can no longer see the original certificate from the origin webserver, but block ads it will.
I wonder if Dropbox (not the article author) means encrypted ext4. ext4 itself supports file-level encryption since linux 4.1.
https://wiki.archlinux.org/ind...
That has its own ioctls and policy management.
At that time, the trick wasn't to get applications to run with their own permissions, it was to keep them running in ring 3 w/o overwriting your OS, libraries, page tables, or accessing any PIO registers that could crash the system in new and surprising ways. It was still the wild west of windows memory management and process isolation.
I have the same experience; the battery utility tells you which apps it wants to "optimize," but in no way does it (or can it) tell you what that will do to app functionality, so it's extremely easy to click through and "optimize all" without thinking about it. This list-based power management probably needs to be done at the Android platform level, not through separate OEM applications, so user applications can report what functionality they'll lose if you disable background operation.
But once I figured out what it was doing, I became extremely happy with how easy it was to work with.
That's a pretty common feature on receivers. It's usually labeled Dynamic Range Compression or Night Mode.
LED-lit PRNG sparkling? Sounds marketable to me.
This breaks the window to content relation, unless it goes away when unfocused. And if it goes away, why bother having it outside the content window? If the user can't figure out which web page/app generated the pop-out, this feature is only going to cause frustration.
EZpass already uses plate readers as a backup for the RF beacons. I don't know why it uses both, though I suspect visibility issues require it (snow, fog, etc).
With the upcoming prevalence of forward-looking mm-wave radar, we could potentially automatically map potholes -- something automakers might want to do to avoid small objects on the road (at autonomous level >=4) and provide a smoother ride. Ideally, they would require no user interaction to report it.
The existing data systems are awesome, and would totally fit the bill if they were available for use by the government. They even use GPS, which is almost exactly what I described. In fact, we could contract one of these folks to build the federal infrastructure for us; a ready made system built on government contract, owned and operated by the government. Unique infrastructure projects should be owned by the state/fed in any case where a most-preferred-customer clause doesn't make sense; viz. the service isn't being sold to anyone else. Because if the government (or any corporate entity) started using the interface a lot, you can bet that the data set owner will charge plenty of money for access fees, especially if the government wanted the interface/product to stay supported and to-specification over a long period of time.
The road tax should be monthly and incremental and paid to the region in which the vehicle is used and based on the weight of the vehicle. Thus GPS tracks (or just county-tagged mileage) + automatic reporting (over some wireless tech, possibly as simple as bluetooth+phone app) + minor enhancements to stored telemetry which is already in most all modern cars, including ICE. The EDR (blackbox) capability has been mandatory since 2014. Server side, legal side, and bureaucracy-side would be much more of a burden, but it could (and should) be implemented federally and paid to locality. Ideally, it would end toll booths and independent ezpass nonsense. Even better if it provided statistical information about which roads get used the most and the condition of those roads (potholes, roughness, etc) which would aid in repair/expansion planning.
If you're worried about privacy concerns, you should take public transport or a taxi. It's not like you turn your phone off in the car anyway; 80+% of you use your phone while driving. A phone bleeds the same location information and we've got no location/metadata protection laws here in the USA. We may as well put it to good use fairly taxing based on usage (eg equivalent single axle load) and better understanding the usage patterns of our roads.
Hi, what? Sales-weighted average MPG for passenger cars is >36 MPG as of 2014. The average went down 31% in 2 years? Do you have a reference? Here's mine: https://www.rita.dot.gov/bts/s...
I started using 2FA recently, before that unique passwords & pw manager. I've never been bitten by security problems, but I'm relatively low profile.
Working with u2f (yubikey) and totp (google authenticator) has been a bit annoying. Most sites don't support u2f, or even 2FA in general. The ones I want to have 2FA, like my bank, do not or they implement it through sms/email. Some sites, like Facebook, have issues with multiple u2f tokens (ie. second and subsequent tokens do not work). It requires extra effort to get gmail working in external clients with saved device trust instead of 2FA as well.
Actually using u2f has been nice though, even with chrome on android via nfc. Once things are set up on a site, it's very reliable.
Oh, it is. For reference, at the current estimated energy cost of BTC, 6 GWh is roughly power equivalent to mining 12.2 blocks (2 hours).
Regarding things that break over time in linux, at least these days, if I static link with musl I can guarantee my binaries will work on other distributions as opposed to being jacked by glibc. Granted nsswitch will be broken if you want to use anything but dns, but screw it!
Delphi's another language that lets you get shit done without really knowing or caring too much about what you're doing. The GUI editor is easy to use and you can basically drop in tiny code snippets without really thinking about your object model too much. Even FFI definitions are easy to do in Delphi. If I didn't have python-tkinter and ctypes, I'd probably be using Delphi or Lazarus/fpc for our in-house device testing UIs.
The worst problems I've run into with delphi/pascal is migrating projects from old versions of the IDE to new ones and having weird bugs creep in.
That and the guy who wrote a lot of it had a peculiar habit of misspelling variable names just slightly and using different variants for different things, but that's not a language fault.
The CPAN library system is mature, it has ports on a ridiculous number of platforms, and the syntax isn't even particularly awful. If anything, its curse is (anecdotally) that it's everywhere and new-to-perl developers run across old code all the time and struggle to figure out the system it backs. And the fact that perl hacks had (have?) a bad habit of becoming defacto production code.
It's too bad no major web service uses smartcards for client authentication except the DOD and they're trying to get rid of them.
Pretty sure this is the old meme. See reference npm left-pad fiasco.
Pretty much the power user's lament these days.
Repeating what A.C.s 1 & 3 said, Chrome is all about forcing you to upgrade. The Goog has an administrative background service which prevents you from ever receiving the UAC prompt because they update that frequently and they don't want to train users to blindly click through UACs that were not initiated by user action. Mozilla Firefox does this too. All of which would be better handled through Microsoft Store, Chocolatey, or some other unified package update interface.
Note to self, no < signs.
DAB is not HDFM. DAB uses MP2 @ ~128kbps; DAB+ is the same bitrate except HE-AAC (under patent); HDFM uses up to 300kbps, also HE-AAC.
DAB is not HDFM. DAB uses MP2 @
DAB also transmits 9-12 channels in a single 1.5MHz transmission that must be simultaneously received (expensive), then the stream you want can be decoded from the digital data. HDFM uses normal 200kHz-wide channels or subchannels of normal radio transmissions. This guarantees battery life is always going to be worse for portables decoding DAB and DAB+ than HDFM, and both will be a lot worse than demodulating simple FM directly.
All that aside, I could care less about what they do to commercial radio as long as they leave AM weather and emergency radio alone. Were I Norwegian, it would bother me that the government is effectively forcing the use of a patented codec because the out-of-patent codec allowed by the DAB standard sounds like shit compared to FM.
I'd say it is warranted to credit MS with making serious effort to maintain backward compatibility. A win32 binary (not driver) which if implemented to spec on Windows XP w/ VC++6.0 probably still runs in Windows 10, at least until they kill off win32 in favor of UWP. Win32 and COM's fanatical (and much appreciated) adherence to ABI versioning means most software packages will run for a very long time via MS's compatibility shims. How many commercial or FOSS projects can you think of which provide those kinds of version compatibility shims? The only one I can think of is glibc and very few projects appear to target versioned symbols. Microsoft's backwards-compat-OCD exceeds what is possible with static linking.