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


Forgot your password?

Comment Re:This is insane (Score 1) 764

And black-to-black crime is bad, agreed, but a police officer who shots a black innocent is another category. In every job accidents happen, and the accidents in jobs where there is a gun involved might be lethal, but the public cases aren't accidents. I don't think that black-to-white or white-to-black crime should get more attention than black-to-black.

The common cold isn't as harmful for the people's lives who get it, as the AIDS syndrome.

But I do say that we should focus more on security on the streets than in the air, because there are much more deaths per kilometer on the streets than in the air.

Comment This is insane (Score 3, Insightful) 764

Centuries ago, you got into serious problems if you ran around claiming you have a mission to fulfil the devil gave you. Now, this gets replaced by feminism, and everybody who doesn't join in the holy movement is an infidel who should be punished. The level of intolerance towards people who aren't "feminists" is raising and raising.

If they really wanted to help women, they should go to india, help solving its rape problem, or to saudi arabia, where women get stoned when they sleep with men who aren't their husband.

Comment Re:what about git? (Score 2) 85

No, the difference between 2nd preimage and collision is that for your hash function HASH, you have for 2nd preimage sth, and HASH(sth) given, and want to get sth2 so that HASH(sth) == HASH(sth2). sth2 is choseable by you, either completely, or only in parts. Sometimes you only have HASH(sth), but you never can modify sth.

Now for collision, you only have HASH given, as function, but you can chose both sth and sth2, either completely, or in parts.

This means you never can rewrite history with git, if you only can do collision attacks. You can however have two "histories": first an "official" one, then an inofficial one. So if you can do collision attacks, and you publish releases as signed email, together with the git sha ID, then you are vulnerable to NSA NSLs where they ask you to create a backdoored version of your software with the same hash as the public non-backdoored one for the next release. They can't require that for previous releases, as that would be 2nd preimage.

Comment Re:The nine steps to raise and fall as browser (Score 1) 317

Ignore how Chrome is still rising steadily despite already doing all of the things you dislike

In some points, mozilla are so idealistic, they hurt themselves. They didn't chose to implement h.264 for HTML5, because to win the codec war. This just led to users switch to chrome. I know, google also did something very mean, they agreed to allow any video to be possible to be played back with ogv and remove h.264, both promises they didn't keep, at least the youtube promise hasn't been kept for a long time. But mozilla could have reacted earlier.

If mozilla really wanted to develop the best browser, they should implement more web APIs. Just think of the still largely missing MSE, or the U2F (which isn't that of a priority, but is a good example of yet another API not implemented). They also could have implemented apple's HLS, in order to beat iphones on this. But rather they chose "no", and said "once we have MSE, this is all doable by js". This is vaporware speak, not how to make a browser that wants to be the most used one.

Comment Re:The nine steps to raise and fall as browser (Score 1) 317

Firefox being locked out of major mobile OSes

Then they should do things only for those operating systems, but not for all of them.

shitty addons are more important than letting them fix things

They aren't. Fixing things is important, but why do they announce to lock down their Add-on API _after_ they have implemented and 99% completed e10s support? I know, there is servo, and probably its right when they say that many of the functionalities of the old APIs are now possible with HTML5. But WebRTC simply doesn't replace an API to send raw udp data.

Firefox surely just had to stay the course, and it would have been just fine

They should be open to change, but they shouldn't abandon their old principles.

Comment The nine steps to raise and fall as browser (Score 2, Insightful) 317

1. Publish a product that's better than competitors'.

2. Open source it.

3. Earn the cheers from the free software crowd, and get the advantage from external contributors, as only large browser vendor.

4. Your users will love the freedom they have, and your product will be famous for its extendibility. They'll love ad-blockers as the web gets more and more annoying ads.

5. Get more and more market share by staying better than your shitty competitors.

6. Let other browser vendors copy your success by open-sourcing their browser as well, or giving up to EEE the WWW.

7. Start your downfall:
a) Require add-ons to be signed because we live now in a world of apps and every app is is signed.
b) Publish ads in your product's start page. Enjoy the annoyment of your users.
c) Integrate an useless closed source product. (Pocket). Enjoy the annoyment of your users.
d) Announce that your addon API will be locked down.
e) Publish your "principles for content blocking". <====== We are here
f) Enforce them. This is the point of no return.

8. Gently shove a Yoda Doll up your user's asses. Be careful, its larger than the dicks the other browser vendors ram up their ass as well. That's also the only reason your browser is still used.

9. Enjoy your 2% market share.

Comment Re:Why not just lock down the radio portion? (Score 5, Informative) 143

WiFi routers aren't like mobile phones with separate application processor and baseband. Instead, they only have one chip, mostly due to more cost involved in having two chips. Thats why this new rule is so bad: it doesn't mandate that there is a part that has to remain free, so the vendors do what companies always do, take the cheapest solution (this isn't wrong by itself), and lock down the only processor which does both application and baseband.

The FCC should either mandate that there is a second, fully flashable part of the chip, or simply solve the problem itself, and this is installing proper tracking down hardware at airports where WiFi devices could interfere the wheather radar. Then they could find, stop, and make accountable for, those who abuse the freedom of their WiFi devices. As this costs money, they rather chose to limit freedom, and still remain vulnerable like before. Those who want to attack airports still can get illegal devices.

Comment Re:Translation ... (Score 1) 145

Github does not charge to host projects. Github therefore must use one of these three methods to make a profit if they don't start charging for use.


It does: https://github.com/pricing

Only public projects are free. And this is IMO a fair model. If you want to hide your code from the public, it means in most cases that your software is closed source. And that usually means you make money with it, where its just fair to give github a small part of it, these are basic economic "supply chain" rules. Conversely, if your code is public, it most likely is open source as well. There is some public content on github which is not open source licensed, but most of it is.

And about learning git, it has a steep learning curve, but once you know it, its real fun. CVS isn't distributed, I really like git for its speed and features like git blame. Sadly many people think git == github.

Submission + - How The Car Industry Has Hidden Its Software Behind The DMCA (computerworld.com)

Lucas123 writes: The DCMA has allowed carmakers to keep third parties from looking at the code in their electronic control modules. The effect has been that independent researchers are wary of probing vehicle code, which may have lead companies like Volkswagen to get away with cheating emissions tests far longer than necessary. In a July letter to the U.S. Copyright Office, the Environmental Protection Agency expressed its own concern of the protection provided by the DMCA to carmakers, saying it's "difficult for anyone other than the vehicle manufacturer to obtain access to the software." Kit Walsh, an attorney with the Electronic Frontier Foundation, said the legal uncertainly created by the DMCA "makes it easier for manufacturers to conceal intentional wrongdoing. The EFF has petitioned the U.S. Copyright Office for an exemption to the DMCA for embedded vehicle code so that independent research can be performed on electronic control modules (ECMs), which run a myriad of systems, including emissions.

FORTRAN is not a flower but a weed -- it is hardy, occasionally blooms, and grows in every computer. -- A.J. Perlis