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


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:It's pretty simple (Score 1) 272

i do not know about the US Energy Star rating, in europe we have this: https://en.wikipedia.org/wiki/...

This is required and very useful. Most people DO look at then, specially on more expensive or consuming appliances. It keeps being improved and allows one to see how much energy or water they use per year. IIRC, newest version even show how much that energy cost in euros, so one can compare several appliances and see how much money one safe by going with a better ratting. Even if more expensive, some pay themselves.

The end result was that junk, consuming appliances quickly disappeared from market, even a uneducated users would look to 2 similar priced appliances, one with rating B and another with rating D, they would choose the B. sometimes simple tune ups from a brand could upgrade the rating, without affecting the price.
Today energy efficiency are publicized by the brands and the even move those energy label to well visible areas, so people can compare

Comment Re: Firefox 57 could be the end of Firefox. (Score 2) 133

that is why they want to drop the old add-on support and use a model mostly compatible with chrome.
Current add-ons are too close to the firefox code and they can not mess with the code without breaking add-on or creating never-ending compatibility layers.

With the new add-ons api, this will get more stable and easier to port add-ons back and forward from/to chrome

Comment Re:They've compartmentalised the renderer? (Score 1) 133

yes, but firefox was build as monolitic, separate each layer required lot of changes as every layer calls were all over the code. That was one of the reasons google started with chrome, trying to break firefox modules would be slower than rebuild... the problem with rebuild is instability, breaks with existent code and requires a huge amount of resources (just look to the netscape 4.x to mozilla migration)

mozilla have done that slowly and they started with plugins and then pick the next problematic layer (javascript, render, video/audio, etc)... only now firefox is turning multi-process and can finally apply sandbox to those layers

Comment Re: Firefox dropping support for older hardware. (Score 1) 133

then update the OS!
local users without security updates, you are looking for trouble, no matter what browser you use...
better yet, install linux, run your app in wine, install freeNX, xpra, LTSP or even tightvnc (test to see what fits better your clients and app) and use it to run your app. Use native linux apps and only use wine for really support old apps

Comment Re:Is this a late April Fool's joke? (Score 2) 386

damn, out of moderation points... +5 for you!

gnome is largely ignored today, not being totally ignored just because of gtk ... that in turns forces you to use several gnome tools
i only know one person that used gnome3 and mostly because he uses fedora, not because he likes it, he just didn't care enough to change it.

Comment Re:Don't forget about open source projects. (Score 1) 286

For firefox, you can check, they describe very well what is sent and almost all the data is technical related, no identifiable info, no browsing history... and they inform you of that and you can opt-out

Now compare that with MS, where it is full of identifiable info, browsing history and even command line (great to catch passwords, "interesting" paths and programs)

Comment Re:IPv6 tunneling (Score 1) 56

i forgot the cons:

- 4 times bigger IPs make harder to memorize then, but IP is for computers, users use dns. Also, first half is netwkork and stay the same (just like 192.168.1.) and the second half is usually the machine mac address, but can also be manually assign hex "numbers" (like dead:beef) :)
- requires ipv6 support in all network layer. that is why it took so long to deploy, each layer was expecting for the other layer to deploy. Now most bigger sites have ipv6, almost all backbones have ipv6, all OS have ipv6 support, all routers in the last 3-4 years have ipv6, now many ISPs also have ipv6... even AWS added ipv6 recently.
so right now only smaller sites do not have ipv6 and lazy ISPs... that is why sixxs is doing this, so users pressure the lagging ISPs to move forward and stop postponing ipv6. If one ISP do not deploy ipv6, users can switch to another and report that they are leaving because of the lack of IPV6. a few users doing this may be enough to sound the alarm in some ISPs

Comment Re:IPv6 tunneling (Score 2) 56

-you get a rebuild protocol that tried to fixed many shortcomings of ipv4. you get encryption (ipsec) build in, dropped all the obsolete ICMP packets and now ICMP is useful to control the traffic (so no more drop all ICMP as you will lose features)
-you get million of address and enabled you to get public IPs for all your machines, even internal machines. so NAT is not needed anymore. Firewall is still needed, but your home router will mostly stop being a router+NAT+firewall and be router+firewall
-As no NAT, direct connect and p2p is a lot easier, no need for strange hacks and third party servers to punching holes in the firewall
-dhcp, manual ip assignment and similar are past, with ipv6 the setup for users is just plug and use, even without dhcpv6
-header rebuild make routing a lot simpler, so faster connections and also easier to grow
-you can get mobile IPs, that even on different locations, you still get your own IP

simply check this sites:

Comment Re:This is extortion: nope! (Score 1) 228

Nope, this is not extortion nor blackmail, it is really trying to get a fix quickly and not letting companies screw their costumers, either by being lazy or by security agencies pressure

If a company gets the bug report and then do not do anything for one year, what wikileaks can do ? release the info before the fix or wait more? either way, it is already too much time for a security bug that is being abused and in the end the info will be public with no one protected and in the end, it will always be wikileaks fault.

better way is to agree the terms of the disclosure, putting hard limits for the fixes timelines. This pressures the company to follow the agreed timeline and release a fix. If they fulfill, everyone wins, if they fail, wikileaks can pressure for the update and depending of the reason for the delay, they can release the info without patch and report that the company failed with the agreement. this proves that wikileaks tried to follow the rules and the fault for the problem is the company.

I think this is totally logic, MS, Oracle and many other companies do not care about security or take way too long to release fixes... as as the article hints, security agencies can pressure to keep the holes open. With a agreement, everyone knows what will happen and the end user will win. Without any agreement, just sending the info to the companies, those bugs could be open for months, being exploit by unknowns and everyone losed.

Just check the security reports, most of then are fixed in a few days, so asking for a date limit is a good thing... as you also find security fixes that took way to long to be fixed

Slashdot Top Deals

Possessions increase to fill the space available for their storage. -- Ryan