It did the patching for me during the night (I told it to do so for security updates), so I woke up to already patched systems.
Full disclaimer: I work for Canonical.
1,105 karma · joined January 3, 2012
[ my public key: https://keybase.io/tribaal; my proof: https://keybase.io/tribaal/sigs/Qt8qTIwlH51g_5rp4GSqKaPFvwKhfAoZT-Pmbh0ZPM4 ]
It did the patching for me during the night (I told it to do so for security updates), so I woke up to already patched systems.
Full disclaimer: I work for Canonical.
The headline is sensationalist, what they are doing it paying for the government not to issue more logging licenses (easy to verify) and putting forests on "protected" status (as well as other concrete, targeted projects).
It's not like they are handing out cash to the government against a promise.
It's not like they just ask to stop and give them cash, like the headline suggests.
Most affordable android phones here are "tecno" (chinese samsung knockoffs), but it's notably hard to flash since not many people with the know-how own any.
By the way, if you do have the know-how to port i.e. cyanogenmod to a new device please get in touch - I'll be glad to send you a few handsets, and you'd make loads of people in developing countries a solid :)
What exactly is hard about it?
USSD codes are critical.
I'm an Atheist, but I leave people alone and don't try to press my view on the rest of mankind, just like I like to be treated by religious people. I feel there is a strong "anti-religion" movement that calls itself Atheist, and I feel it's giving the rest of us a bad rap.
tl;dr: I don't believe in god but don't care if you do.
Pretty please, somebody confirm my reading comprehension skills are complete garbage? :)
http://ntrs.nasa.gov/search.jsp?R=20140006052
> Thrust was observed on both test articles, even though one of the test articles was designed with the expectation that it would not produce thrust. Specifically, one test article contained internal physical modifications that were designed to produce thrust, while the other did not (with the latter being referred to as the "null" test article).
Sorry, but I don't think any interviewer in the history of job interviews would give a guy a job if he showed up late without warning - how is your "testing for reliability" any different?
Let's hope the bugs found are published in a timely and open fashion. Yes they say it will, but the proof is in the pudding :)
It would be great to re-hash the information to the general public, however.
You should assume any computer you don't own is keylogged, period.
- If it proves to be actually good, they might actually sell some of those chips, too (it's developing their local high-tech sector. Even a tiny piece of the market is better than none at all, especially if their own agencies kickstart it).
- It highers the cost for foreign intelligence to write software for that platform: their arsenal of viruses and trojans are completely useless. Unless you acquire detailed specifications of the platform, find some test chips, develop new software and finally infect your target... Takes time and money.
- They get some (positive, for once) international press.
- They can parade how awesome mother Russia is to their own nationalist ego.
Russia wants to be independent from the US for computers, because they fear (rightfully) American chips to be bugged.
Having slow, expensive chips made in Russia is probably more interesting to certain agencies than fast and cheap American chips - or relying on typewriters :)
I always thought most biometrics vendors were fishy, and this is no exception.
Sure, I can't think of all applications that would benefit from websockets, but so far, none of the ones I've seen do. I'm certain you can find at least a few exceptions, but my point is that it is only this: exceptions.
Setting an alias like "alias sssh='mosh'" greatly helps with muscle memory, too (of course, don't override "ssh", you might still need it).
Funny anecdote: I live in a city called "Moshi"
You start with a longpoll and get some data, then negotiate websockets (hey, my network and browsers are websockets capable!). Then the connection drops. And then you go through another round of everything again when you get back online (http + longpoll + websockets, instead of just http + longpoll).
Odds are, your website doesn't need websockets anyway, and 99% of your users are just fine with waiting a couple of seconds more to get their notification (and in the process, people with unreliable connections can still use your site).
Of course, if you're doing online stock trading notifications or something like that, you might actually need these two seconds. But then I'll strongly question your choice of using a browser for that :)
EDIT: fixed stray "*"
Websockets suck here. BGP routers here flap very often, nuking TCP connections because hey, power cuts. Guess what happens?
Tip: If you're "out to change the world", make sure you can turn your wifi card every 30 seconds and still get a decent-ish experience (yes, long-polling HTTP works, so does good old timer-based polling).
Why not just add @param annotations in your docstrings instead?
- Bare except: statements (that catches everything, even Ctrl-C)
- Mutables as default function/method arguments
- Wildcard imports!
(different paper formats, two columns, two pages per one landscape paper, four pages per one portrait paper... all with the same content)
The more bandwidth you share for TOR, the more free wifi you get. If you only "sell" wifi to torcoin owners, you simply trade internet access time, but running a tor relay would be like "mining" in the traditional bitcoin world.
EDIT: The point I'm trying to make is that instead of "just" the way to create torcoins, this would also create a way to spend it (and provide value to people by spending it).
It's still going to be a challenge, but that makes a more manageable one :)