http://www.who.int/mediacentre...
http://wwwnc.cdc.gov/eid/artic...
https://simple.wikipedia.org/w...
Seems to indicate that the bat species can be a host, but doesn't show the symptoms. Studies have also shown antibodies to previous strains of ebola in the areas where the matching outbreaks occurred.
It's worse than that though -- many of these areas mistrust the doctors and also believe that the only way for a person's soul to be safe after death is with a ritual burial that involves physical contact with the dead. That's why they're hiding many of the dead, and why they have the "worst case" scenario in the first place.
The interesting thing about ebola is that it is aggressive enough that it generally DOES burn itself out, counting on other carriers (appears to be fruit bats from latest studies) to incubate the disease until the next outbreak in primates.
How is Netflix wrong here? They're an American company operating in the US, they have licenses to allow people to request streams from Canada, but the Canadians have no jurisdiction over what an American firm operating out of America does.
This is a regulatory overreach the way that that asinine media tax to pay for piracy is. If the customers lose out, it's because their regulators are incompetent.
Netflix doesn't allow Canadians to access Netflix USA -- they instead have a service called Netflix Canada that is only available to Canadians. Where this crosses the border is that they bank through a Canadian bank to process orders, therefore they are operating out of Canada.
Regulatory overreach would be the CRTC going after Netflix USA for something they're doing in the US; this is trade happening in Canada, so that's why they're involved.
That said, the CRTC likely doesn't have the right to step in here in the first place, even though they can, and have not been slapped down by the government in the past for doing similar things. That's because they're supposed to regulate broadcasting; the rest of their remit is on very shaky ground/legislation.
The interesting thing here is that while the CRTC clarified the definition of broadcasting here, they've also expanded their role beyond broadcasting. What Netflix is challenging here (rightly) is whether they actually have the right to do so. I'd say they don't, but the government has given them a LOT of leeway over the years.
They're not legislating anyone; they don't have that power. What they're trying to do is assert commecial control over Netflix Canada who isn't backing up their claims with actual numbers.
CRTC is very much involved in the Canadian part of the Internet, just like they are in Canadian imports of other things such as optical media and digital storage in general.
In case you didn't get it yet...
This is about Canadian companies (not Netflix USA, who Netflix doesn't let Canadians use) fighting for control over who gets to decide how/how much Canadian content is made available in Canada, and how.
When it's American broadcasters going after Canada's icravetv, American courts had no problem getting a US court order that basically ended the service, because it was a rebroadcaster.
Can anyone seriously argue that Netflix isn't also rebroadcasting TV content?
Two weights, two measures. What a mess! And really, whatever solution will be a mess.
The difference is that NetFlix gets permission for rebroadcasting -- they have a license. That's why they don't have the same selection that other rebroadcasters do -- because they're licensing content on a show-by-show basis, not taking the OTA stream and routing it over the Internet.
This case is kind of unfortunate, as both the CRTC and Netflix are in the wrong, and both sides are unwilling to back down and come to a reasonable compromise, as that would threaten their power base.
The problem here is that the CRTC can stop all payment via Canadian credit cards to Netflix, and Netflix can support customers paying via alternate methods who are willing to stream over a VPN -- so the result of this conflict is that both sides lose, and the citizen (not consumer, although them too) loses even more.
But this whole thing is really about Rogers and Shaw lobbying the CRTC to block foreign competition for their new Shome project. CRTC is probably quite happy to be flexing their "muscle" in this situation after continually taking a beating from US lobbying interests on allowing US content onto Canadian networks.
So yeah; it's a huge mess to sort out.
Think of it this way... design a blueprint of your building in something like sketchup, and tag all the different surfaces according to type. Then put antennas in strategic places in the structure (could do 3 in each room, or surround the entire building) and turn on the multiband antennas.
The RF interference should be able to be mapped in this way fairly easily; especially if you set state and then open/close doors, turn WiFi on/off, turn on lights/heaters, etc.
Record all this state information, and then with minimal training, the system should be able to identify all mobile objects and when they moved.
If you toss in the RFID chips here, you could serialize each major mobile item, and actively track them anywhere in the structure.
This isn't new, and doesn't need all that much knowledge of RF, just a good AI that can learn.
See: http://www.extremetech.com/ext... for one way it's been done.
I presume you read this?
http://idle.slashdot.org/story...
I've got a solution that will make everyone happy:
Have NetFlix partner with the NFB to distribute NFB content... globally. Nothing like providing global access to Canadian content. NetFlix could even provide it for free to everyone in Canada with an account but no current subscription. Under this setup, the CRTC wouldn't have a leg to stand on, as at that point, they will get their Canadian Content on NetFlix (not sure about the French/English ratio though).
HOWEVER
I'm pretty sure this really has nothing to do with NetFlix and EVERYTHING to do with the new consortium raising a Canadian NetFlix "competitor" (Shomi) whispering nasty things in the CRTC's ear. Yes, blame Rogers/Shaw for this fracas, as they're likely where the blame really lies.
Hmm... scratch that; it's not a re-branding, as the Dreamer uses more filament types, is heated, and has a few other goodies missing in the Builder. And it's only $200 more.
Oh, and it appears to be a re-branded one of these http://www.flashforge-usa.com/... which say they support Linux. I'm guessing that FlashForge Dreamer drivers for Linux would drive the Idea Builder without much modification.
If it works with OS X and Vista, that means you should be able to reverse engineer the protocol and make it work with Linux without too many issues. The drivers seem to work with AutoCAD tools, so my guess is the drivers aren't proprietary either but use a common protocol.
Have you ever used a dremel tool?
For the most part they're crap. Perhaps before the '80s thay had good stuff but it's been downhill for a long time.
I'll bite. I've used a Dremel-brand dremel tool in the late 90's, and found it solid (if made of a lot of plastic), dependable, and accurate. The accessories were way too expensive, but Black & Decker accessories are of the same quality and fit in the Dremel opening.
B&D, Ryobi, Makita and similar manufacturer's dremel tools though -- I've found to be underpowered, made of cheap components, and have a shaft locking mechanism that is abysmal, not holding the shaft in a centred manner at all. DeWalt is also pretty good.
Likewise, I've had hit-and-miss experience with Dremel's other offerings -- some are good, some aren't. But their original tool still works as well as it ever did.
True... which is why talking about large-bit encryption isn't really the issue; it's the implementations that are the issue. I was mostly rebutting the part about exponential difficulty with bitsize making your encryption more secure. I'd give *properly implemented* AES-256 another decade at least before it has any security issues whatsoever. By the time AES-256 can be cracked via brute force, the entire algorithm will be out of date, so increasing bitsize won't be much of a gain.
But it doesn't matter how many bits are used or what algorithm, or even what implementation, if even one password at, or above your level on the system being protected is in the Adobe password file, people.
Always draw your curves, then plot your reading.
