One would have to compromise a large percentage of the nodes on the network to directly "mess with" the data.
Last time we discussed Bitcoin scalability, two Chinese miners controlled the majority of hashing power. And they have a vested interest in seeing transaction costs skyrocket as more network users try to fit their transactions into a single block.
Then how do I get support for severe slowdowns on my Nexus 7 (2012) 8 GB tablet purchased from the Google store, which started after I installed Lollipop?
Slash deliberately has broken Unicode support because of past abuses by vandals, such as bidirectional overrides to spoof moderation scores and characters more useful in obscene "ASCII art" (really Unicode art) than in English prose. Rehash, the fork of Slash used on SoylentNews, fixes Unicode support.
Atari Jaguar had three CPUs: a Motorola MC68000 used as an I/O processor, a proprietary 32-bit RISC CPU called "Tom" on the GPU die, and a proprietary 32-bit RISC CPU called "Jerry" designed for audio signal processing. Some games ran game logic on Tom, others on the 68000, but graphics rendering was all Tom. The 64-bit part of the Jaguar was the data bus to the GPU.
But is it 64-bit like the Atari Jaguar video game console and the AMD Jaguar processor (used in PlayStation 4 and Xbox One video game consoles)?
The article repeatedly says "x86", not "x86-64", "x64", "AMD64", or "EM64T", yet it mentions "Intel Atom Z3735G (Bay Trail)" which Intel says is 64-bit. But does its firmware support 64-bit mode?
The broader finding in MAI v. Peak was that the rights in 17 USC 117 apply only to the owner of a copy, not the lessee. The exception carved out in 1998 applies only if the alleged infringing lessee can prove that the use was for "maintenance or repair". Please see my reply to Rakarra.
Nintendo's patent on Dr. Mario (U.S. Patent 5,265,888, now expired), Sega's patent on Crazy Taxi (used to sue the developer of The Simpsons: Road Rage), and Konami's patent on Dance Dance Revolution (cf. Konami v. Roxor) would beg to differ.
So what do you and your lawyer plan to do if some songwriter sees your spare time music, finds it too similar to his own work, and sues you for $150,000?
Let me further clarify where the national boundaries would lie: A, B, and C in a "rich" country would sue company D in the same "rich" country for having sent their private information to E in an India-class country, which misused it.
I thought an iOS app developer had to be at least 18. Yet the photo at the top of the featured article clearly shows children under 13. How would that work? Would minor children develop and publish apps through their parents' developer account, and then Apple provide some way to hand responsibility for the app down to the child once the child comes of age?
Maybe a poor analogy but the idea is that Naples is full of shit or at least it was a few years ago. And by full of shit I mean it literally : it had a major waste problem with piles of garbage littering the streets.
When reading a general statement about a technology such as caching, it is up to you to consider all of the reasonably applicable implementations.
Likewise, when writing a general statement about a technology such as caching, it is up to you to suggest one or more implementations that you might consider reasonably applicable.
That is on you.
When you make a claim that "add[ing] a cache" will solve the bandwidth problem of unicast video on demand and then show unwillingness to complete your claim by specifying where in the path from cable HQ to the end user's display this cache would be located, you are shifting the burden of proof. Your use of "consider all of the reasonably applicable implementations" sounds like you're asking me to enumerate all places a cache could be and disprove each. That resembles another fallacious debating technique, the Gish Gallop. But I will do so anyway, as a favor to you:
By trichotomy, if the CMTS is between the cable company and the viewer, a cache is either before the CMTS, in the CMTS, or after the CMTS.
Before the CMTS
A cache before the CMTS requires the program to be sent through the CMTS separately for each viewer whose position in the program differs.
In the CMTS
A cache in the CMTS requires the program to be sent by the CMTS separately for each viewer whose position in the program differs.
After the CMTS
A cache after the CMTS would be on customer premises, making it a "digital video recorder" in a broad sense. A customer premises cache could receive the whole program in-order, like a traditional DVR, or snoop on pieces of the program that other viewers happen to be requesting, like a BitTorrent client. But given how the studios don't let Netflix pre-cache an entire film in advance on the user's device before the user begins to watch it, I doubt that the studios would be willing to license programs to cable companies that implement BitTorrent-style VOD.
Of all these possibilities, which do you "consider [...] reasonably applicable"? Or what specific possibility that I failed to imagine do you "consider [...] reasonably applicable"?
The key with dealing with long passwords? Muscle memory!
Good luck getting muscle memory to work on a flat sheet of glass. It's the same reason that a lot of video game genres are less viable on iPhone and Android than they would be on PlayStation Vita or Nintendo 3DS: you can't feel where the buttons are.
That'd fail because md5sum does not produce mixed-case or punctuation, which some sites require. Another site requires passwords to be no longer than 12 (!) characters.
Slashdot Mirror
One would have to compromise a large percentage of the nodes on the network to directly "mess with" the data.
Last time we discussed Bitcoin scalability, two Chinese miners controlled the majority of hashing power. And they have a vested interest in seeing transaction costs skyrocket as more network users try to fit their transactions into a single block.
Then how do I get support for severe slowdowns on my Nexus 7 (2012) 8 GB tablet purchased from the Google store, which started after I installed Lollipop?
They get mad when I point out that school is pronouned sk.
Unless it's run by a Jewish synagogue. Then it is pronounced as if it were "shool".
Slashdot still doesn't support Unicode?
Slash deliberately has broken Unicode support because of past abuses by vandals, such as bidirectional overrides to spoof moderation scores and characters more useful in obscene "ASCII art" (really Unicode art) than in English prose. Rehash, the fork of Slash used on SoylentNews, fixes Unicode support.
...by the author of Linux? That's a clone of an operating system developed by American Telephone and Telegraph. Mobilizing your world.
We can probably get down to 20 letters if we try hard
Irish got it down to 18 (abcdefghilmnoprstu, with h replaceable by a combining dot), but Irish spelling is as messed up as French.
Atari Jaguar had three CPUs: a Motorola MC68000 used as an I/O processor, a proprietary 32-bit RISC CPU called "Tom" on the GPU die, and a proprietary 32-bit RISC CPU called "Jerry" designed for audio signal processing. Some games ran game logic on Tom, others on the 68000, but graphics rendering was all Tom. The 64-bit part of the Jaguar was the data bus to the GPU.
Those are melons.
Not to be confused with the password to the doors of Durin.
But is it 64-bit like the Atari Jaguar video game console and the AMD Jaguar processor (used in PlayStation 4 and Xbox One video game consoles)?
The article repeatedly says "x86", not "x86-64", "x64", "AMD64", or "EM64T", yet it mentions "Intel Atom Z3735G (Bay Trail)" which Intel says is 64-bit. But does its firmware support 64-bit mode?
The broader finding in MAI v. Peak was that the rights in 17 USC 117 apply only to the owner of a copy, not the lessee. The exception carved out in 1998 applies only if the alleged infringing lessee can prove that the use was for "maintenance or repair". Please see my reply to Rakarra.
A news site in India already called "First!" on that idea.
Since you can't copyright game mechanics
A court found the opposite with respect to Tetris .
You can't patent game mechanics
Nintendo's patent on Dr. Mario (U.S. Patent 5,265,888, now expired), Sega's patent on Crazy Taxi (used to sue the developer of The Simpsons: Road Rage), and Konami's patent on Dance Dance Revolution (cf. Konami v. Roxor) would beg to differ.
So what do you and your lawyer plan to do if some songwriter sees your spare time music, finds it too similar to his own work, and sues you for $150,000?
This song is Copyrighted in U.S., under Seal of Copyright # 154085, for a period of 28 years
Explicitly disclaiming all subsequent renewals and extensions, I see. That was tried again later under the name Founders Copyright
Let me further clarify where the national boundaries would lie: A, B, and C in a "rich" country would sue company D in the same "rich" country for having sent their private information to E in an India-class country, which misused it.
I thought an iOS app developer had to be at least 18. Yet the photo at the top of the featured article clearly shows children under 13. How would that work? Would minor children develop and publish apps through their parents' developer account, and then Apple provide some way to hand responsibility for the app down to the child once the child comes of age?
Maybe a poor analogy but the idea is that Naples is full of shit or at least it was a few years ago.
And by full of shit I mean it literally : it had a major waste problem with piles of garbage littering the streets.
Does it have anything like the "designated shitting streets" in India?
As for the economy, it was all governed by the mafia. Businesses had to pay money to them for "protection".
Not so different from the U.S., where businesses have to pay money to the Music And Film Industry Associations for "license" to stay in business.
Which I assume doesn't stand for "Italian music and film industry associations".
When reading a general statement about a technology such as caching, it is up to you to consider all of the reasonably applicable implementations.
Likewise, when writing a general statement about a technology such as caching, it is up to you to suggest one or more implementations that you might consider reasonably applicable.
That is on you.
When you make a claim that "add[ing] a cache" will solve the bandwidth problem of unicast video on demand and then show unwillingness to complete your claim by specifying where in the path from cable HQ to the end user's display this cache would be located, you are shifting the burden of proof. Your use of "consider all of the reasonably applicable implementations" sounds like you're asking me to enumerate all places a cache could be and disprove each. That resembles another fallacious debating technique, the Gish Gallop. But I will do so anyway, as a favor to you:
By trichotomy, if the CMTS is between the cable company and the viewer, a cache is either before the CMTS, in the CMTS, or after the CMTS.
Before the CMTS A cache before the CMTS requires the program to be sent through the CMTS separately for each viewer whose position in the program differs. In the CMTS A cache in the CMTS requires the program to be sent by the CMTS separately for each viewer whose position in the program differs. After the CMTS A cache after the CMTS would be on customer premises, making it a "digital video recorder" in a broad sense. A customer premises cache could receive the whole program in-order, like a traditional DVR, or snoop on pieces of the program that other viewers happen to be requesting, like a BitTorrent client. But given how the studios don't let Netflix pre-cache an entire film in advance on the user's device before the user begins to watch it, I doubt that the studios would be willing to license programs to cable companies that implement BitTorrent-style VOD.Of all these possibilities, which do you "consider [...] reasonably applicable"? Or what specific possibility that I failed to imagine do you "consider [...] reasonably applicable"?
Treat others' PCs as if they're keylogged.
Probably because synchronizing the password manager across all devices that one uses is an extra-cost feature.
The key with dealing with long passwords? Muscle memory!
Good luck getting muscle memory to work on a flat sheet of glass. It's the same reason that a lot of video game genres are less viable on iPhone and Android than they would be on PlayStation Vita or Nintendo 3DS: you can't feel where the buttons are.
That'd fail because md5sum does not produce mixed-case or punctuation, which some sites require. Another site requires passwords to be no longer than 12 (!) characters.
How can login scripts run if /home is noexec?