Is it really that big of a deal? Any text will need to be scaled up. I'm typing this on a 13" Sony Vaio (Z12) with "Full HD" (Best Buy speak for 1920x1080) and I wouldn't be able to see anything if I hadn't scaled up the fonts.
Our eyes can only make out so much detail, and I think this new screen might be a bit beyond what most people will need for a quality small-screen experience.
The paper was preliminary to begin with. It is currently withdrawn in order to fix minor typos and because currently "enough unresolved issues with the paper exist to foster a healthy sense of skepticism". This is a good thing for now.
The original discussion was in a Google Doc but has since moved to a wiki.
People might think it's funny when their AI friend has a funny accent, but it's cheaper to outsource these things to India! I assure you people will be amazed and perplexed by how wonderful this AI is, but maybe curious why it has an hourly cost....
the join removal. But what about the partitioning features that have been on the table for quite some time now? The scaffolding is already there, but implementing partitioning is still quite a chore. I just want to be able to gracefully create/manage partitions as in Oracle. There are also a few papers floating around out there with proof-of-concept parallelization/optimization schemes that can be applied with partitioning knowledge.
Google probably wants to use the data for their own analysis. So, I suggest all of Slashdot team together and forge a large volume of the most bullshit data that will convince Google that, without a doubt, they need to make every first search result named "Frosty P1ss!" linked to goatse in order to make their customers happy.
And their only reason for making it is so THEY can specify the required DRM compliance for high-bandwidth devices. It was the foremost issue during development.
It's the only reason they've re-branded and protocol-ized existing technology. HDCP 3.0 anyone?
I use pfSense seriously and it's great; however, all it does in regard's to OPs concerns is make the manual configuration easier/prettier. Although you'd be able to use SSH & shell scripts to change config files, that might make a lot of sysadmins (like me) nervous.
xxdinkxx makes some good points, and also I've learned from experience that OpenCV is too slow for mobile devices in its generic form. You'd end up needing to write optimized assembler code specific to the camera's processor anyway.
It can sometimes be the backbones but it's more often that the Last Mile is the source of bandwidth/latency issues. You can thank our telecoms for not doing The Right Thing(TM) with all of the government subsidization that many telecoms in other countries used to fix the obviously expensive problems.
In the cases where we do pay through the nose for reasonably fast connections, the problem becomes centered around load on servers. You can't stream HD content to 100,000 users from one machine, so there's a point when you need to build out your services to meet the capacity of the network.
It's not a matter of what is on the website as much as it is this: many of us see a bleak future when law dictates what sites we can and cannot visit on the internet.
This ruling means that rather than only taking down websites that cause direct harm to a person or a group of people, access to sites can be removed even if they fall within copyright gray areas, where laws and ideas are different all over the world, or where they possibly threaten financial harm (no matter how [un]justified) to large organizations.
It's like taking a magazine off the stands in just one country because it says anti-patriotic things about its leader. or, if you want to go into the realm of content legality, a magazine that tells you how to exploit DNS vulnerabilites (3 cheers for the 2600 periodical).
Ok, I did RTFA, and also some public court documents.
Well, Mr. Steven Marks, representing the "Executive Vice President & General Counsel" of the RIAA has decided to share his email with us, so please everyone, please feel free to send him your thoughts, feeling, etc on the subject of music copyrights, which may include but mot be limited to pictures of feces if you deem it to be appropriate.
Several readers sent in an update on DTN, the interplanetary Internet protocol...
Please stop screwing up the meaning of DTN. Not just/., but everyone writing article about Vint Cerf and "his" interplanetary internet. The acronym stands for Delay Tolerant Network, and is a type of network in which connectivity is ephemeral and a contemporaneous path between two points often doesn't exist at any point in time, necessitating any communication to be tolerant to delay (and/or disruption).
ADTN protocol is one that takes advantage of the ephemeral connectivity of DTNs, usually along the lines of employing the store, carry, and forward approach to getting data from A to B via a time-varying path; e.g. a path exists, just not at any point in time.
What Cerf has done has create a bundle forwarding protocol stack for the Android. It's not as "out there" as you'd think- someone send you data, you carry it, then forward it later. Lots of questions/issues in between as you might imagine.
I think some people like Kevin Fall need to get more credit for their contribution to this area of research.
Disclaimer: I am NOT Kevin Fall but I am a network researcher, specifically in the area of DTNs. No, not the algorithm.
It's the actual release date of Duke Nukem Forever. This news will be huge... earth-shattering even.
I imagine:
Lawyers: $7,999,999.
Privacy Policy Education Fund: $1.
It's the end of the lime for them alright, and it's sad to see such a historic piece of software going out on a such a sour note.
Is it really that big of a deal? Any text will need to be scaled up. I'm typing this on a 13" Sony Vaio (Z12) with "Full HD" (Best Buy speak for 1920x1080) and I wouldn't be able to see anything if I hadn't scaled up the fonts. Our eyes can only make out so much detail, and I think this new screen might be a bit beyond what most people will need for a quality small-screen experience.
But my Chrome updated silently... I thought it was supposed to either ask me or let me know an update is available. Surprising.
The paper was preliminary to begin with. It is currently withdrawn in order to fix minor typos and because currently "enough unresolved issues with the paper exist to foster a healthy sense of skepticism". This is a good thing for now.
The original discussion was in a Google Doc but has since moved to a wiki.
Info: Previous post explaining the proof more clearly
Paper (not wort reading for most of us)
Actually they stole the Coast Guard's initialism, which is even worse because it's obvious that all the letters are the same when repeated out loud!
I think this is cool, but.... how fast is it in a more practical situation?
source
People might think it's funny when their AI friend has a funny accent, but it's cheaper to outsource these things to India! I assure you people will be amazed and perplexed by how wonderful this AI is, but maybe curious why it has an hourly cost....
Sorry a bit hasty there. The port 6363 is a backdoor for a Westel modem. HTTP Server header is Server: WSTL CPE 1.0 .
50940 is unresponsive.
Just ran it on all ports overnight, here ya go. Omitted all but the 3 useful lines,
PORT STATE SERVICE VERSION
6363/tcp open tcpwrapped
50940/tcp closed unknown
the join removal. But what about the partitioning features that have been on the table for quite some time now? The scaffolding is already there, but implementing partitioning is still quite a chore. I just want to be able to gracefully create/manage partitions as in Oracle. There are also a few papers floating around out there with proof-of-concept parallelization/optimization schemes that can be applied with partitioning knowledge.
Google probably wants to use the data for their own analysis. So, I suggest all of Slashdot team together and forge a large volume of the most bullshit data that will convince Google that, without a doubt, they need to make every first search result named "Frosty P1ss!" linked to goatse in order to make their customers happy.
Finn and Norman filmed and photographed live animals in the act of trapping their air bubbles, solving a mystery that has been debated for millennia.
Somehow I am starting to think that exaggeration in the media goes too far sometimes....
And their only reason for making it is so THEY can specify the required DRM compliance for high-bandwidth devices. It was the foremost issue during development. It's the only reason they've re-branded and protocol-ized existing technology. HDCP 3.0 anyone?
I use pfSense seriously and it's great; however, all it does in regard's to OPs concerns is make the manual configuration easier/prettier. Although you'd be able to use SSH & shell scripts to change config files, that might make a lot of sysadmins (like me) nervous.
xxdinkxx makes some good points, and also I've learned from experience that OpenCV is too slow for mobile devices in its generic form. You'd end up needing to write optimized assembler code specific to the camera's processor anyway.
It can sometimes be the backbones but it's more often that the Last Mile is the source of bandwidth/latency issues. You can thank our telecoms for not doing The Right Thing(TM) with all of the government subsidization that many telecoms in other countries used to fix the obviously expensive problems.
In the cases where we do pay through the nose for reasonably fast connections, the problem becomes centered around load on servers. You can't stream HD content to 100,000 users from one machine, so there's a point when you need to build out your services to meet the capacity of the network.
It's not a matter of what is on the website as much as it is this: many of us see a bleak future when law dictates what sites we can and cannot visit on the internet.
This ruling means that rather than only taking down websites that cause direct harm to a person or a group of people, access to sites can be removed even if they fall within copyright gray areas, where laws and ideas are different all over the world, or where they possibly threaten financial harm (no matter how [un]justified) to large organizations.
It's like taking a magazine off the stands in just one country because it says anti-patriotic things about its leader. or, if you want to go into the realm of content legality, a magazine that tells you how to exploit DNS vulnerabilites (3 cheers for the 2600 periodical).
No, but they'll be able to dance to Thriller in a very synchronized and entertaining fashion.
I'm an academic and I actually have to sift through bullshit like this to get to the real research, and it's quite frustrating.
As usual, they choose to address things readers will find interesting and leave out important details. Here's a few pseudo-equations for you:
PowerRequired(802.11) < Power(3G).
PowerRequired(3G x N phones) >> PowerRequired(One 802.11 AP).
SpeedAndReliability(One 802.11 AP) > SpeedAndReliability(3G x N phones (N < 20 probably)).
And most importantly:
Cost(N tethered phones) >>>>> Any reasonable price.
Here's a tip to Microsoft Research: try doing some research first.
* IAAANR. (I am an annoyed network researcher.)
He never even visits the local university. There's thousands of computer science undergrads here that could learn a thing or two from him!
Ok, I did RTFA, and also some public court documents.
Well, Mr. Steven Marks, representing the "Executive Vice President & General Counsel" of the RIAA has decided to share his email with us, so please everyone, please feel free to send him your thoughts, feeling, etc on the subject of music copyrights, which may include but mot be limited to pictures of feces if you deem it to be appropriate.
SMarks@riaa.com
Several readers sent in an update on DTN, the interplanetary Internet protocol ...
Please stop screwing up the meaning of DTN. Not just /., but everyone writing article about Vint Cerf and "his" interplanetary internet. The acronym stands for Delay Tolerant Network, and is a type of network in which connectivity is ephemeral and a contemporaneous path between two points often doesn't exist at any point in time, necessitating any communication to be tolerant to delay (and/or disruption).
A DTN protocol is one that takes advantage of the ephemeral connectivity of DTNs, usually along the lines of employing the store, carry, and forward approach to getting data from A to B via a time-varying path; e.g. a path exists, just not at any point in time.
What Cerf has done has create a bundle forwarding protocol stack for the Android. It's not as "out there" as you'd think- someone send you data, you carry it, then forward it later. Lots of questions/issues in between as you might imagine.
I think some people like Kevin Fall need to get more credit for their contribution to this area of research.
Disclaimer: I am NOT Kevin Fall but I am a network researcher, specifically in the area of DTNs. No, not the algorithm.
As a concerned legitimate user of /. I must offer these words...
FREE V1AGRA!!
FREE MOVIE DOWNLOADS!
UNLIMITED P0RN FREE!!
(pdxp is no longer with you. the spambots are now infesting his brain, and you are all next)