Devices like tablets are in direct competition with notebooks and in some situations even PCs. Now lets assume the typical slashdot poster, who is a hobby programmer.
If he's sitting at his pc, and surfs on the web, he may interrupt it to do some coding. maybe he's annoyed by something on a website and writes a userscript to change it, or he just gets an idea for a cool script and can instantly switch to a terminal and write it.
If he's surfing on his mobile device, he does not have a keyboard, and not even a system which does good multitasking (in the human sense, not in the multithreading sense). So if he's annoyed by something on a website, its likely, he just ignores it. Or maybe he tries to search for a userscript for his mobile browser, but its unlikely he starts writing one. And starting to program something more advanced on a touchscreen is even more unlikely.
You do not need to be a programmer, to have this problem. Mobile devices, which lack proper input like mouse and keyboard are designed for consumption, they are not designed to create something.
kvm for example boots another kernel... okay, with virtio it reduces some overhead, but its another kernel. other virt stuff is more lightweight... but the first "virtualization" is just a multiprocess OS.
when you virtualize in unix system, then you create a virtual machine to run multiple applications seperated from each other on a OS, which was invented to run multiple applications seperated from each other. Many applications do not really need a VM, but just a shell account and some own ip, where they are allowed to use privileged ports.
other approaches are chroot/lxc/linux-vserver maybe openvz lightweight VMs.
for example, in german the word hangup "aufhängen" was displaces by "auflegen" (to lay sth. down), like you did with the old telecom telephones with keys on one big block and a receiver to hold at your ear. Of course, you could try to implement this by an app, which hangs up when you lay down the phone... but face it, you did not hang up or lay down your DECT mobile, as well.
> Which is why I hit the "like" button for EVERYTHING!!!!! thats exactly wrong. Then facebook knows, whats everything for you. So they know all of your environment, because you clicked like on everything YOU saw, but of course not on things, you did not see.
The other main difference: An API documentation is long and everthing seems as if it were of equal importance. Now read it, try to get started... At stackoverflow (and other online communites, why this advertisment here?), the documentation is weighted by importance. You will get a lot more answers to the questions, which are propably the right questions, which keeps you on track doing it the right way.
dells pages are just commercial, because you only can use them properly, when you have bought that machine, or when you want to.
opensource on the other hand... many people pay money to provide the hosting for free software. You would assume, when you do not get money for your software, you want at least some cheap hosting... but no, its worth it to the authors of the software. Another reason, why you should donate to your favourite projects.
let them go "pay-for-content". Then they will see, what they are actually worth to the user. Which means better sites, and the bad ones just die because nobody pays.
then the question is, why not doing it the other way round: allow 3rd-partys to access their own cookies, but do not allow them to set a cookie, if they are not the 1st party at the moment.
Think about it. If they call it a nuclear strike, they will start using some other technique. Flash-Cookies, DOM-Storage, E-Tags, whatever fits. And this is not so easy to block. So now, the default allowed their techniques and the advanced users could just uncheck it. then, we will need more advanced filters, because they use more advanced tracking.
Slashdot Mirror
> implying, there is the #ifdef line
Chrome can teleport many goats per second, firefox not even one.
a laptop is fine, you can code python on it. But coding python on a tablet is no fun.
Devices like tablets are in direct competition with notebooks and in some situations even PCs.
Now lets assume the typical slashdot poster, who is a hobby programmer.
If he's sitting at his pc, and surfs on the web, he may interrupt it to do some coding. maybe he's annoyed by something on a website and writes a userscript to change it, or he just gets an idea for a cool script and can instantly switch to a terminal and write it.
If he's surfing on his mobile device, he does not have a keyboard, and not even a system which does good multitasking (in the human sense, not in the multithreading sense). So if he's annoyed by something on a website, its likely, he just ignores it. Or maybe he tries to search for a userscript for his mobile browser, but its unlikely he starts writing one. And starting to program something more advanced on a touchscreen is even more unlikely.
You do not need to be a programmer, to have this problem. Mobile devices, which lack proper input like mouse and keyboard are designed for consumption, they are not designed to create something.
kvm for example boots another kernel ... okay, with virtio it reduces some overhead, but its another kernel. other virt stuff is more lightweight ... but the first "virtualization" is just a multiprocess OS.
and thats an argument, to boot a full kernel, just to seperate the access to gcc?
That just some "we have the ressources anyway" argument.
when you virtualize in unix system, then you create a virtual machine to run multiple applications seperated from each other on a OS, which was invented to run multiple applications seperated from each other. Many applications do not really need a VM, but just a shell account and some own ip, where they are allowed to use privileged ports.
other approaches are chroot/lxc/linux-vserver maybe openvz lightweight VMs.
Close the Browser.
for example, in german the word hangup "aufhängen" was displaces by "auflegen" (to lay sth. down), like you did with the old telecom telephones with keys on one big block and a receiver to hold at your ear. Of course, you could try to implement this by an app, which hangs up when you lay down the phone ... but face it, you did not hang up or lay down your DECT mobile, as well.
the covariance of these properties.
> Which is why I hit the "like" button for EVERYTHING!!!!!
thats exactly wrong. Then facebook knows, whats everything for you. So they know all of your environment, because you clicked like on everything YOU saw, but of course not on things, you did not see.
The other main difference: ...
An API documentation is long and everthing seems as if it were of equal importance. Now read it, try to get started
At stackoverflow (and other online communites, why this advertisment here?), the documentation is weighted by importance. You will get a lot more answers to the questions, which are propably the right questions, which keeps you on track doing it the right way.
and the lgpl-part is, why companies like apple can use it without opensourcing their browser.
Can Bettridges Law of Headlines ever be wrong?
dells pages are just commercial, because you only can use them properly, when you have bought that machine, or when you want to.
opensource on the other hand ... many people pay money to provide the hosting for free software. You would assume, when you do not get money for your software, you want at least some cheap hosting ... but no, its worth it to the authors of the software. Another reason, why you should donate to your favourite projects.
but i never visisted ad.d*bleclick.net directly.
with the user without these plugins as loser.
let them go "pay-for-content". Then they will see, what they are actually worth to the user. Which means better sites, and the bad ones just die because nobody pays.
then the question is, why not doing it the other way round: allow 3rd-partys to access their own cookies, but do not allow them to set a cookie, if they are not the 1st party at the moment.
Think about it. If they call it a nuclear strike, they will start using some other technique. Flash-Cookies, DOM-Storage, E-Tags, whatever fits. And this is not so easy to block. So now, the default allowed their techniques and the advanced users could just uncheck it. then, we will need more advanced filters, because they use more advanced tracking.
no, it is not, even if you may wish so.
he wanted to filter the MACs, which get an ip via DHCP. Thats no protection, because i just pick some unused ip by hand.
do not confuse his misleaded approach with MAC filtering on the accesspoint (a layer below IP)
as stuff like "a evil twin network" aren't really crimes ... why should they. Its a matter of perspective, if a twin-network is "evil".
why? Just pick a unused static ip from (or even not from) the dhcp-range.
between two facebook profiles.