Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:I ran it (Score 2) 54

I ran it too and what the app told me wasn't immediately useful. When I checked on Google Play, others had said the same. So I installed Lookout Security's Stagefright detector and it not only told me my devices were vulnerable, it also linked to helpful instructions to change my settings and avoid the problem.

You can install it from here: https://play.google.com/store/...

Lookout's blog page has details about the app and how to make sure your messaging apps are safe from the exploit: https://blog.lookout.com/blog/...

If you use a third-party messaging app you will have to follow the general instructions given on the blog page to find the settings specific to your particular app. I should point out that Textra has already fixed the problem from their end. Here's what the app showed me: http://i.imgur.com/36G7o0t.png

I don't know if it's possible for someone to remotely install the Stagelight vulnerability on your device and then use the device to send exploited messages to everyone on your Contacts list, but if I thought of that then you can bet someone else will.

Comment How many do you need?! (Score 1) 100

"None of the ~50 employees were able to identify reporter John Markoff, and only about 10 were able to identify video journalist Catherine Spangler."

So, a crime has been committed, there are ~50 witnesses, of which 'only about 10' are able to identify one person. Statistically significant? What would the police and the courts think?

Oh, and what exactly is 'about 10' people? Somewhere north of 9.75?

Comment And they'll be running Android Lollipop (Score 0) 201

According to what I read at BBC News, engineering chief, Hiroshi Lockheimer said, "We've made a concerted effort around focusing on the enterprise-use case. If you think about it most people only carry one device. The one device that they carry [should] work for various scenarios in their life -obviously for personal use, but also if they want to use it for corporate purposes." That must be why they named it Lollipop...

Comment It's right in front of me (Score 0) 199

"Do you know any complex software that succeeded in avoiding documentation by having significantly improved usability?"

Yes. Android.

"As a customer, how would you feel with a very simple product (much simpler than the competition but still a bit complex) that has no documentation?"

Fine, as long as it hand-holds the user right at the beginning with some simple (possibly animated) guides.

Comment The licences need more clarification (Score 0) 64

I'll mention right up front that most of the more than 10,000 photos I've published on Flickr were, and continue to be, under the Creative Commons Attribution Share-Alike licence. Most of the people who have used my photos have done so quietly, without any fuss. Now and again, someone asks politely if they can use a photo even though it is clearly marked as to which licence applies, and my Flickr Profile also makes this clear and goes so far as to say how I prefer to be attributed. If I think that anyone wanting to use my photos might have problems with the Share-Alike part (e.g. commercial enterprises who want to keep their own licences on the content) I just generally quietly change the licence to Attribution only and let them get on with it. I may be unusual in this way as my intent is to provide a service to the community - and that's what I see CC as being all about. And as a result, many hundreds of web pages feature my photos. And this probably saves them a dollar or two. It looks like a win-win situation from here.

I do, however, reserve the right to change the licence on any of my photos, no matter when they were first published. I'm trying to build up a small fine art portfolio and intend to continue changing some photos to All Rights Reserved. And I've stated as such in my Flickr Profile. But that in no way affects the rights of anyone who has used any of my photos beforehand. As far as I'm concerned, the date of publication should settle the issue of who has which rights. If someone used my photo under CC BY-SA on the 31st of March, say, and I change the licence to ARR on the 1st of April, then that person's rights don't change as regards their use of the photo up to and including 31st March. They don't have to take the photo down, and I won't charge them for its use. If they reuse the photo after that then it's likely to be because they don't know about the licence change. If I find out they've reused it, I'll let them know about the licence but won't insist that they find another photo. After all, I might not know they've reused it until months afterwards. So I'll always err on the generous side. So that I can continue providing a service. At some point in the near future, I'll convert most of my photos to CC BY to make this easier.

Having said all this, I know that some other photographers are far less easy-going, even to the point of being litigious. My opinion is that the Creative Commons (i.e. whoever 'officially' represents it) needs to look at the wording on the CC website and especially any legalese therein, and rewrite it to include information and guidelines as to what should happen when a contributor intends to change their licence. If, as I believe is the case legally, the date of publication is primary in deciding who has what rights, then the website should make this clear to both contributors and users of creative work. Users should be clear that, if the licence on a work changes, their use up to that date is lawful and cannot be challenged; and that reuse of the same work after the date of change of the licence comes under the provisions of the new licence exclusively. Likewise, contributors should also abide by this and not attempt to charge fees in retrospect for lawful use of a work prior to the date of change of the licence.

For me, the spirit of the CC movement is most important, but the letter needs to be nailed down a lot tighter than it currently is.

Comment Design Patterns (Score 1) 172

"Intermediate" means whatever you think it means, but I'm assuming you know language constructs and data structures. For me, "intermediate" means "knows enough to do some real damage". So at this point I recommend that you learn those things that are common to all programming languages: software design patterns.

Many people would point you at the book "Head First Design Patterns" and that would be a good choice. But there's also a Dummies book that's written by someone who is an expert in that area. I don't have the details to hand but if you're interested you'll find them easily.

Once you know the name of a few patterns you'll find that you can do a lot of learning/research on Wikipedia, because they're pretty much all up there. To start you off, you could take a look at the Model View Controller pattern, implemented in Java and other high-level languages, and think about how you might refactor one of your existing projects to incorporate it. And MVC can easily lead you into the parallel study of frameworks.

A good knowledge of patterns and frameworks will not only keep you out of trouble but also increase your employability, should that be your intention.

A bug in the hand is better than one as yet undetected.