Forgot your password?
typodupeerror

Comment: Re:Wrong question (Score 2) 432

by Skuto (#45915129) Attached to: Why Do Projects Continue To Support Old Python Releases?

>He only said that he didn't want it to work with older versions, and that it was not a lot of work - i.e. it still took some amount of work - to make it not work with older versions

He doesn't say that at all. Really. It's not even remotely in the article. He talks about dropping support for Python 2.6. This isn't an action involving work! It means you no longer care if it doesn't work in Python 2.6.

Comment: Re:Wrong question (Score 1) 432

by Skuto (#45915119) Attached to: Why Do Projects Continue To Support Old Python Releases?

>What he appears to be complaining about is "Why do projects continue to require old Python releases?"

No, he doesn't. I re-read the article after reading your post and I have no idea where you get this.

He really is talking about dropping support, i.e. no longer caring if it doesn't work on old Python versions.

Comment: Re:Nice, impressive achievement (Score 5, Informative) 62

by Skuto (#45620039) Attached to: Opus 1.1 Released

Depends on what mobile device? The reference code has extensive ARM optimizations, that's in fact one of the main improvements in 1.1 And yes, it can be accelerated with a programmable DSP if present, IIRC there's some support for C55x in the same reference code.

Audio decoding is fast enough on modern ARM SoC that dedicated hardware isn't strictly needed to get good battery life.

+ - The Streisand Effect: A Florida journalist's smear and censor campaign backfires-> 2

Submitted by Anonymous Coward
An anonymous reader writes "A tragic death, freedom of speech, libel, defamation, legal threats, unethical journalism, reddit's /r/bicycling, and The Streisand effect. A South Florida "journalist" is called out for running a smear story, doubles down on his position, publicly attacks commenters and reddit, and threatens legal action when a disturbing conflict of interest is exposed."
Link to Original Source

Comment: Based on a study? (Score 1) 29

by Skuto (#44565949) Attached to: Google Multiplies Low-Tier Bug Bounties By Factor of Five

This might be due to the result of study showing that the insane bounties Google promises for top end bugs (especially for Chrome) draw many people in to look for Chrome security bugs, but that actually the expected payout for looking for Chrome bugs is exactly the same as it for for (for example) Firefox, because the latter pays more for the easier to find bugs.

Microsoft already changed their bug bounty program significantly days after the study was announced.

Comment: Re:Did I read that right? (Score 4, Informative) 583

by Skuto (#44471895) Attached to: Half of Tor Sites Compromised, Including TORMail

You should had to be running Firefox 17 on windows afaik (that was the version included by the Tor Bundle).

You had be running the specific, modified Firefox version that's shipped with Tor.

Mozilla's Firefox 17 (ESR) has been patched for this vulnerability. (i.e. it's not a real 0-day)

Comment: Re:And the winner is... Mozilla?!! (Score 1) 314

by Skuto (#42885359) Attached to: Opera Picks Up Webkit Engine

Who do you think the W3C is? It's the browser vendors. Who do you think benefits from smaller browsers not being interoperable with bigger ones? Not the smaller vendors, I tell you.

Now, do you think the vendors with the near-monopoly marketshare on Mobile care about making competition in their market easier?

Comment: Re:Good. (Score 1) 378

by Skuto (#40574289) Attached to: Mozilla Downshifting Development of Thunderbird E-Mail Client

I don't suppose the re-assigned devs are going to anything useful, like multi-process Firefox.

The conclusion was that multi-process Firefox isn't magically going to make the browser more responsive, and will make it use more memory instead. Actually fixing the bugs that make it less responsive does seem like a much more useful spending of developer time.

Comment: Re:Need a niche (Score 2) 91

by Skuto (#40566801) Attached to: Telefonica Shows Prototype Firefox OS Phone

accuracy of rendering pages

It's the same engine as desktop Firefox. What you're seeing is that a lot of websites send "Webkit-only" markup to Android devices. (Dolphin uses Android's rendering engine) This is something Firefox can never fix. There's an add-on that makes it pretend it's desktop Firefox, that generally stops misbehaving sites from sending broken markup. I suspect most sites will get their act together eventually.

I don't see the "slanted font" problem you talk about on my Galaxy S2, so that's rather strange. The "small font" problem can be solved by setting text size to "tiny" (yes, it's pretty retarded that you have to do the exact opposite of what you would expect, from what I understand it's because that option is completely misnamed).

Be sociable. Speak to the person next to you in the unemployment line tomorrow.

Working...