Re: PDF in a Browser?
I thought foxit was now wrapped in spyware installer crap. Haven't touched it for years now.
2545 publicly visible posts • joined 7 May 2012
> if the Oz Revenue Dept. felt they were owed something by Plutus it would follow this same pecking order
I guess it depends on whether the government feels the political heat enough to try and leave some scraps on the table for the state coffers in lieu of having no palatable alternative gst carve up.
I recently upgraded from a nexus 5. It's power button had broken and got stuck in a reboot loop (yes, known issue). So I installed an app to wake up the phone with the volume button instead so I could still use it. Then the microphone stopped working (yes, also known issue). So I got myself a cheap Bluetooth headset so I could still use it. Then the battery dropped so low that I couldn't be more than an hour or so without a charge. It finally died after replacing the battery.
I didn't buy a Google phone because I don't need a 1300AUD telephone.
Your comment may be correct for the nexus but I'm afraid it is not with the pixel. Unless by fraction you are considering numbers greater than one.
It has to be from date of purchase, not first release. If you are selling these things still in 2016 then you should be still patching them to 2019, even if a particular phone was purchased in 2013.
Windows Vista (released 2006) only ended security patch support a few weeks ago. (And even then you can still wave about a large wad of cash and get updates). Why can't phone makers do the same? If it's a cost thing, I would have paid an additional $100 for "guaranteed monthly security patches for 5 years".
> a device that is essentially a glorified microscope optics attachment for a smartphone is not exactly a new idea and has not been for the better part of a decade probably.
Absolutely correct. Such an attachable microscope lens is definitely covered under prior art. There is, however, one novel part of this invention which you have missed but any of the highly trained USPTO officers could have recognised. This is not just any attachable microscope lens, but rather an attachable microscope lens on a mobile device. Don't beat yourself up though. Sometimes the novelty of an invention is hard for a lay person to recognise.
Hydrogen is not a fuel in the same sense as petroleum or diesel. There aren't any special rocks you can whack a drill into and slurp it out. Instead you find the atoms attached in other molecules. You then need to apply some energy to those molecules to break the bonds. When you burn that hydrogen in a fuel cell, you get some of that energy back. In other words, it is closer to a battery. You consume some energy to charge it up (create the H2) then consume it in your motor.
And whilst you can do it from water, it is probably cheaper at scale to start with natural gas. There are two big problems with using natural gas for that. Firstly, it is far more energy efficient to just burn the gas itself. Secondly the waste CO2 kind of misses the point of replacing the internal combustion engine. That plus the fact it isn't renewable, that hydrogen is very hard to store, that it's energy density is rubbish and so requires liquefication (hugely energy intensive) and is way more expensive means it will never be a better fit in cars than batteries. It's only advantage over batteries is that you can get 300-500km range in a few minutes. There are other use cases where fuel cells do make sense, but not here.
Good point. Out of curiosity, shouldn't 911 have some sort of redundancy to redirect calls to another call centre somewhere else in the country when the local emergency service isn't able to answer within a couple of rings? At least that's how it works with 000 down under. (Or is that just an unusual over preparedness by us to better handle the risk of a drop bear infestation?)
No need to do that. If you had read the article byline, you would have noticed that although authorities switched them off, they switched them on again. I'm still unclear after reading the article as to why after going around and switching them off, they turned them back on.
We've seen this movie before somewhere...
The difference that i can see here is that PCs were never set and forget concepts. They had service packs, antivirus definitions and the like. But who, when purchasing their next light bulb, is thinking "how do I apply security patches? Whilst i don't condone vigilante hacking, it's hard to feel sympathy for an industry that has produced so much crap security with bad practices even at a 101 level (hard coded passwords, missing even basic user permissions, running unnecessary daemons with root access, the list goes on). Maybe some bricked returns will score some pretty rubbish eBay/Amazon reviews and will ward off bricks and mortar retailers from stocking such products. The iot industry (and I include car manufacturers here) need to understand that software isn't an engineer and forget enterprise, and if they can't learn the lessons of that industry then pull back and sell regular light bulbs/door locks/cameras/cars/whatever until they do learn those lessons.
I'm not hopeful though. Best security practice starts with collect as little data as you need to function, run as few services as is needed to accomplish that task, and run those services with as few rights as possible. This is the very antithesis of iot.
Warranty just means that the manufacturer must fix any issues at their cost (or refund or substitute where that isn't possible) for that period. It doesn't mean that your device is suddenly not protected under consumer law the day after warranty expires. It just means that you might have to pay for the repairs where those costs are reasonable.
For example, many cars come with 3 year warranties. If after 4 years a major component like the gearbox fails and you have had it regularly serviced and you didn't use it for motor sport then that would be considered a major failure well within the typical lifespan of such components and they are legally obliged to fix it. If the same happened after 10 years or if it hadn't been maintained according to the service schedule or if you had made modifications then they wouldn't.
Whether the manufacturer would comply with the law is entirely another matter. They would most likely push you around on the marginal cases and throw an NDA your way for the open and shut cases.
It's actually not bad if you ignore the marketing. Simple configuration on your servers to monitor your log4Xyz logs, Windows event logs, etc from disparate machines out there and you can do big data-esq mining on it all, find out which software/OS versions are being impacted by some specific exception (in pretty close to real time).
If I'm reading the JavaScript right, the attacker needs to know the hostname of the splunk server. In public facing servers that might be an issue, but it looks like it needs to be a targeted attack or mitm to be practical.
Wireless is shared bandwidth. So whilst you may get 100Mbps standing under the tower at 3am, you can forget anything approaching that on Saturday night when everyone presses play on their Netflix HD streams. The only way to ease congestion is to pop up more towers and reduce the broadcast strength of each and thereby reducing contention.
The low hanging fruit are incredibly important to connect as the project involves cross subsidies. If they wait for tpg to fibre up all the unit blocks in Sydney and Melbourne then those users won't be contributing to the network build into less commercially interesting regions. It's in essence just a usage based tax.
It doesn't cost anywhere near a dollar for Aus Post to deliver an envelope to my house, yet there are other houses where the effective cost could be hundreds of dollars. Yet we all benefit from being able to send mail to nearly everyone. In the same way, we all benefit from internet availability across the whole community.
Fttn and fttdp are effectively stop gap measures. They might scale for the next 5-10 years but at some point they will need to be replaced with fttp. By all means do a cost benefit comparison. Maybe fttn with a 5 year life allied faster rollout and ROI, and maybe we won't utilise the capacity of fttp before then, but the problem as i see it is a lack of forward thinking. They are only interested in costs and returns over budget estimates. If they built the harbour bridge today they would have made it 2 lanes each way and not bothered with the train line either.
And the counter example of Windows Mobile where they forgot aboutbackwards compatibility between generations. Developers became disinterested in doing yet another port to a platform with nearly zero user base, then the available apps became a factor with the consumers in a death spiral.
Apologies for the buzzfeed link but you get the gist.
Agreed with FIA. You can't retrospectively add some requirement to check your email within period x.
Perhaps licenses could be written to authorise proxies in the event that you can't be contacted for an extended period or if you are known to have died. You could even stipulate the default proxy as the unanimous decision of the project foundation board to handle those who were never interested beyond the feature/fix they needed 5 years back. You just don't get to move the goal posts. Most open source licenses are written deliberately to make these sorts of changes really difficult.
> How about a blanket OS rule that shit apps can't grab focus unless the last user command was to launch that app?
I've written software that needs to grab focus (yeah we all claim that). In my case, it is in response to a biometric hardware events, so you need the "interruptions" and you are pretty forgetful if you don't remember presenting yourself for authentication under a second earlier.
Just here to point out that Microsoft have made this harder to achieve over the years. Back in win 9x, there was a pretty simple call. It got abused. They then changed what it did in XP to flash the window orange and introduced some other method to do it. That got abused too. So i think they just dropped support for that. There is an always on top mode that the OS these days basically ignores too.
I'm not going to share publicly how it gets achieved, but it's a big waste of everyone's time but at least bofh would get a snigger. All they needed from the get go was a control panel applet where users could whitelist applications they want to do this and ignore the request from anything else.
> Nest deliberately designs its cameras to use internet-hosted storage for video, not local storage
Wait, a *security* camera that is flummoxed by a lack of internet connection? Using cloud storage doesn't stop you including a cheap sd card as a rolling buffer.
Oh and Google, October would be 90 days ago Shirley.
Another way would be to have a collection of DNS servers configured locally that get round robin'd for each request, since profiling requires combining the pattern of DNS lookups from specific pages.
That, or if you're feeling like a real crazy cat, use an ad blocker and VPN.
> "it's no longer possible to prove that (for example) a hashed document is unique"
Agreed with OP. This is not the goal. It relies on the fact that the amount of hardware, CPU/GPU time, electricity and opportunity cost involved in "reversing" the hash back to the original bytestream means that a suitably resourced attacker wouldn't bother.
Whilst source code is much harder than a PDF file to hide junk bytes of your discretion so they remain unnoticed, it wouldn't be impossible to use comment blocks or constants.
Fair enough and I'm sure she feels terrible, BUT...
There is a limit to the scope of contract you as an IT Pro would be willing to sign before bringing lawyers at 12 paces. IANAL, but i have seen clauses in contacts that aren't worth the paper they are written on because the thing they try to claim indemnity for (as an example) can not be indemnified against due to legislative protections.
I would expect a barrister to understand their liability for breaking client privilege or publishing information with various suppression orders active. And knowing that, it would be incredibly surprising to think it's ok for the data to be downloaded onto a shared computer where the husband alone might accidentally stumble upon confidential documents whilst searching for something he needs. And i would expect such computers used to handle that data to be maintained by people who have signed both confidentiality agreements and agreements that state that the data will be handled in accordance with best security practices. So again, she either failed to obtain those assurances or her husband should be rather nervous about his breach of contract.
And finally £1000?? Did she park in a bus zone or compromise the private documents of hundreds of people through at best carelessness?