cinnamon seems the better approach, because much of gnome3 is still what it was in gnome2. so just replace the sucking parts. And this is what cinnamon does... replacing the shell, but not the rest.
firewall which allows outgoing traffic and denies incoming connections. and privacy-extensions, which obfuscate how many hosts are there, and which one is communicating at the moment.
just because IPv6 includes the mac in the address, when you follow the stateless autoconfiguration procedure without privacy extensions, it does not mean, your ethernet/wifi will not use MAC addresses anymore. This remains unchanged.
and the MAC in the ip has one big advantage: if you know your hardware, you know the ip the computer will get. prefix:computed-suffix.
of course, the reasonable default is, be reachable via:mac-suffix, but surf via:PE-suffix. And use another pe-suffix with a much longer validity for long connections like instant-messaging and such stuff.
My information was, that nvidia said when asked some time ago, they do not have plans to support wayland at the moment. Which is quite logical, as there are too little users of wayland to encourage anyone to update his drivers for wayland. When wayland is THE graphics system on every distribution, i bet there will be nvidia drivers.
they don't plan to support it, yet. When wayland is the way to go, they will adapt their driver. But they will not create a driver for beta versions of a maybe successor of X.
instead of stuffing more and more into the browser itself, put more of the stuff in plugins.
but not the old nsplugins, limited to their square area, but plugins which can for example improve the javascript engine, define new html-tags, and such stuff. okay, much of this is done via javascript already nowadays, but everthing which would run faster with native code, should go to plugins. so what about and video? They could be plugins, just with a reasonable api, not the limited api which nsplugins use.
tl;dr: Plugins could mean, just make your code modular and load only when needed. Much like firefox-addons, but the concept should be cross-browser. At least stop putting more and more into firefox, when only a part of the users really use it.
Slashdot Mirror
the amount of fuel is constant in my solar power plant, you insensitive clod!
> serve more of the internet than google ......
implies google serves less than 50% of the internet
Or why is it such a small number?
Of some person with a Macbook, holding a defective GPU in his hands and beating an apple with it.
if Mark Zuckerberg ... ... or Chuck Norris!
http://www.h-online.com/security/news/item/Windows-8-will-be-available-in-four-editions-1541216.html
cinnamon seems the better approach, because much of gnome3 is still what it was in gnome2. so just replace the sucking parts. And this is what cinnamon does ... replacing the shell, but not the rest.
firewall which allows outgoing traffic and denies incoming connections. and privacy-extensions, which obfuscate how many hosts are there, and which one is communicating at the moment.
i do not think you know, how privacy extensions work.
just because IPv6 includes the mac in the address, when you follow the stateless autoconfiguration procedure without privacy extensions, it does not mean, your ethernet/wifi will not use MAC addresses anymore. This remains unchanged.
and the MAC in the ip has one big advantage: if you know your hardware, you know the ip the computer will get. prefix:computed-suffix.
of course, the reasonable default is, be reachable via :mac-suffix, but surf via :PE-suffix. And use another pe-suffix with a much longer validity for long connections like instant-messaging and such stuff.
then firewall it. not on the host itself, but at your router.
NAT (66) may be useful, PAT will not be useful anymore.
computing the question.
works fine, firefox 11. dunno if any other settings are relevant. but flashblock additional is fine, too.
And this is the problem. when you're foot is moving 0.0 km/h, then you cannot be braking.
i do not know about this problem.
My information was, that nvidia said when asked some time ago, they do not have plans to support wayland at the moment.
Which is quite logical, as there are too little users of wayland to encourage anyone to update his drivers for wayland. When wayland is THE graphics system on every distribution, i bet there will be nvidia drivers.
[x] block adobe flash
[x] use on trusted websites, too
[x] show placeholder symbol
(not the exact text, as my system does not have an english locale)
same interface in noscript. i do not speak of the script blocking part,but of the click-to-start-plugin part.
they don't plan to support it, yet.
When wayland is the way to go, they will adapt their driver. But they will not create a driver for beta versions of a maybe successor of X.
like personas. put more stuff into the core, which works better as an extension.
even native code could be run in a way, which cannot break your browser.
instead of stuffing more and more into the browser itself, put more of the stuff in plugins.
but not the old nsplugins, limited to their square area, but plugins which can for example improve the javascript engine, define new html-tags, and such stuff.
okay, much of this is done via javascript already nowadays, but everthing which would run faster with native code, should go to plugins. so what about and video? They could be plugins, just with a reasonable api, not the limited api which nsplugins use.
tl;dr: Plugins could mean, just make your code modular and load only when needed. Much like firefox-addons, but the concept should be cross-browser. At least stop putting more and more into firefox, when only a part of the users really use it.
flash html canvas svg with chromium.
with firefox, flash is the fastest and the rest is sucking.
good argument for using more chromium.
i really need to evaluate, how much of my data (history, bookmarks, etc.) can be imported and which extensions i would really be missing.
yeah, and you can configure noscript to block plugins even when scripts are allowed.
you need to enable "block plugins even on whitelisted sites" or something like this. Then you have exactly the flashblock behaviour.
> vector animation
> canvas
you're doing it wrong.
you need to test scripted svg.