Anyways, if you look closely at those photo collages that were so hip a couple of years ago, it almost does appear that they choose pictures based on sub-picture resolution colors... I'll explain:
Say the pixel you're doing contains the edge between a dark and a light area (someone's chin typically). If you look closely at those montages, it seems like the program has chosen mostly pictures that have the bottom half darker than the top half -- in effect getting sub-pixel (in this context, a pixel is one of the small pictures) resolution. You might be able to steal some code from there.
The ascii character set offers very few characters like that, but it'd be easy enough to do some downsampling of the pixel and then edge enhancement. If that matches one of a small set of cases (/\-_|+@VA>) reasonably well, use that, else use your grey-level lookup table.
You're referring to the "must accept any interference recieved" clause, right? I always thought that just meant that the device couldn't bitch about other devices bothering it.
Well, its more of person B asking person A about site C. It is up to person B to use the response person A gives in any way it wants to.
Blocking software is pull technology, so as long as person B is happy with person A's opinions or views, I don't don't see that site C has any say in the matter.
It's not like B is being duped here -- they are asking for opinions -- buying opinions infact, so there is a contract between the two parties that matter: A and B.
I imagine that the best analogy is that of movie reviews -- how factually correct does a movie review have to be? Anyone? Anyone?
well, the Tera chip (which I constantly rant about -- I love that thing) and the MAJC do know about threads. However the IBM thingies, and indeed pretty much every other chip out there indeed do not know a thread from a twinned up piece of animal hair.
They need OS support to switch from one instruction stream to the other. Without that os support, it is up in the air what the IBM multichip would do (I guess I should read the link, eh?), but I imagine that one of cores is a master and is the only one which is activated on startup. It is up to it to run the OS code that initialises the other cores with the appropriate instruction streams.
I imagine that the secure storage of the hardware is due less to the price of the servers than it is to the fact that most system security is predicated on the machine remaining physically inviolate. I get root read privs on any machine I can rip the harddrive out of, for example.
Do you do any matching, to try to get edges represented by appropriate characters -- basically sacrificing local grey level correctness for better resolution. Basically, instead of a triagle looking like this:
The contribution is being able to locate the message in the DNA -that's where the primers come in. It's a simple pre/postprocessing step to make the hidden message conform to whatever statistics you want.
A more sagacious question is _do the primers_ conform to the relevant statistics? Well, punk, do they?
Hrm. Patents aren't necessarily evil. E2B didn't immediately strike me as obvious, although this may be due to a general lack of information -- this was after all a press release, so as little information as possible is included to avoid confusing the media.
Could you perhaps provide some links to, or details about, what E2B really is, so that I can evaluate your claim that this is obvious technology?
Something that breezes through nuclear calculation could probably brute-force crack most encryption methods in an afternoon...
That would be very bad crypto, in that case. The keyspace enumerable (ie, assume a key checked per cycle -- obviously a best case scenario) for a 1 TeraOPs machine is just shy of 40 bits per second. So in two seconds it does 41, in 4 seconds it does 42... in 24 hours, just over 51 bits. Since you on average only need to search the half the keyspace, the best this machine could hope to crack using brute force is a 52 bit key per day.
But they were talking about eventually scaling up to 100 odd TOPs. 128 == 2^7, which brings it up our searchable space to just under 60 bits.
At that rate, You'll need to search for 2^68 days to break a 128 bit key. That's a pretty long time. Go calculate it for yourself. Oh, I'll do it, it's 10^20 odd days.
TERA does have some killer tech. I love that multithreaded switch on each clock stuff. Given that multi-threading is a big thing these days (cf sun's MAJC chip) and SGI has their CC-NUMA with non-uniform memory latencies, it makes a lot of sense for SGI to aquire TERA.
TERA's chip would be the perfect complement for a CC-NUMA architecture. Perfect.
How does swapping to a RAMdisk make any sense. I'm sure I'm missing something, but that just feels kooky. Unless you're meaning ramdisks on other computers (basically distributed shared memory) which assumes that net is significantly faster than local disk. I'll buy that for advanced networking. Just.
My understanding and poor memory want to claim that hennesy and patterson's DLX architecture -- which (once again, from memory, so add salt) became concretised as the MIPS chip was the first RISC platform. Indeed, they could have patented (for once, something I conscider to be a patentable invention) the concept of constant complexity instructions, and prolly have made a bundle.
Personally I like SUN's java-multi-threaded CPU concept ( even if it never succeeds ). Basically, you have 4 parallel fully functional, non-related, non-pipelined, fully optimized functional units. There are no resource contention issues, no scheduling problems, a simplified logic design. And it's cheaper because you take away pipelining. The best part is that each of these extrememly simple components are just cookie cuts. You spend all your time tweaking the hell out of one tiny unit, then make 32 copies. Almost as easy as cache design.
Tera baby! 128 threads, hardware support for context switching, no L1 cache, no pipelining, no superscalar units.
Bascially, you context switch after each instruction. Since you have 128 threads, this hides all the memory latency. You gotta love that design.
Stability is paramount in any palmtop w/o external storage. If a crash will kill your saved work, you'll never be able to trust the machine with _any_ work.
I've actually been toying with completely unmounting my harddrive in my laptop -- it has enough ram to hold a decent sized ramdisk and still have enough memory to work out of. By completely spinning down the harddisk, I hope to be able to extend the battery life to almost an hour (So I was a cheapskate and bought the noname brand. Now I'm paying for it). The only reason I would be willing to do this is because I know that my system is stable enough never to crash.
From my laptop, I want a big screen, good keyboard, large harddrive, long batterylife. Notice how processor speed a was abstent from my requirements. I'm thinking a 486 or even a 386 (hell all I do is use emacs anyway) would do me just fine.
Hey laptop makers! lookie here! This is a market segment waiting for your attention.
Johan
Re:Telnet is the only solution.
on
SSH v. SRP
·
· Score: 1
Lovely,
apparently this post was is the same category as "PERL sucks! Python Rulez!".
Hillarious.
Re:Telnet is the only solution.
on
SSH v. SRP
·
· Score: 0
4, Insightful!?! That was the sound of the camel's back breaking.
Slashdot's moderation system's gotta change, 'cause it ain't working. Perhaps we should require all moderators to pass a humor identification, physics and math skills (yesterday, someone was comparing acceleration to velocity and was modded rediculously high), and perhaps even some rudimentary computer science tests.
Probably in the FAQ, which I would check before posting a question. However, this is an answer, so I don't feel the need for actually following directions (kindergarten didn't take). Anyway:
my Garbage Collection oriented friends tell me that His one biggest regret is making GC support optional. If it were required, then x% of all programming errors would go away, and library interfaces would be y times cleaner (no questions about who references or disposes of shared objects).
You sure? I assumed that the reason why they were able to make it seamless was that if you use a 2x2 grid, each panel still has two hidden edges, giving you somewhere to attach the input signal. If you use a 3x3 scheme, the middle panel has no obscured edge, so it has to be fed "from behind", which I'm assuming is harder to do.
Why rescan the whole screen; you really only need to update pixels whose color has changed. But you're right -- as resolutions increase, bandwidth to the display is going to become a bottleneck, so we'll have to start using some send-the-diff scheme. Perhaps mpeg compressed video signal all the way to the display? This also relates to previous discussions on encrypted signals too.
Slashdot Mirror
Now, that was real ugly:-)
Anyways, if you look closely at those photo collages that were so hip a couple of years ago, it almost does appear that they choose pictures based on sub-picture resolution colors... I'll explain:
Say the pixel you're doing contains the edge between a dark and a light area (someone's chin typically). If you look closely at those montages, it seems like the program has chosen mostly pictures that have the bottom half darker than the top half -- in effect getting sub-pixel (in this context, a pixel is one of the small pictures) resolution. You might be able to steal some code from there.
The ascii character set offers very few characters like that, but it'd be easy enough to do some downsampling of the pixel and then edge enhancement. If that matches one of a small set of cases (/\-_|+@VA>) reasonably well, use that, else use your grey-level lookup table.
D'ya got any movies to watch yet?
You're referring to the "must accept any interference recieved" clause, right? I always thought that just meant that the device couldn't bitch about other devices bothering it.
Johan
Well, its more of person B asking person A about site C. It is up to person B to use the response person A gives in any way it wants to.
Blocking software is pull technology, so as long as person B is happy with person A's opinions or views, I don't don't see that site C has any say in the matter.
It's not like B is being duped here -- they are asking for opinions -- buying opinions infact, so there is a contract between the two parties that matter: A and B.
I imagine that the best analogy is that of movie reviews -- how factually correct does a movie review have to be? Anyone? Anyone?
well, the Tera chip (which I constantly rant about -- I love that thing) and the MAJC do know about threads. However the IBM thingies, and indeed pretty much every other chip out there indeed do not know a thread from a twinned up piece of animal hair.
They need OS support to switch from one instruction stream to the other. Without that os support, it is up in the air what the IBM multichip would do (I guess I should read the link, eh?), but I imagine that one of cores is a master and is the only one which is activated on startup. It is up to it to run the OS code that initialises the other cores with the appropriate instruction streams.
I imagine that the secure storage of the hardware is due less to the price of the servers than it is to the fact that most system security is predicated on the machine remaining physically inviolate. I get root read privs on any machine I can rip the harddrive out of, for example.
Johan
nitpick:
negroponte, I thought, defined bits as the immaterial thingies, and atoms as the material ones.
So shouldn't that be atoms are atoms!?
Or perhaps you were referring to something else
Do you do any matching, to try to get edges represented by appropriate characters -- basically sacrificing local grey level correctness for better resolution. Basically, instead of a triagle looking like this:
######
#####
####
###
##
#
make it look like this:
------/
#####/
####/
###/
##/
#/
.
or something like that?
Or something like
I was bitching about the lack of a cypherpunks login @ the NYT, and some kind soul set up the same l+p there as well for me.
Johan
The contribution is being able to locate the message in the DNA -that's where the primers come in. It's a simple pre/postprocessing step to make the hidden message conform to whatever statistics you want.
A more sagacious question is _do the primers_ conform to the relevant statistics? Well, punk, do they?
c'mon people. that was funny. :-)
rapt / wrapped
That was one of the better puns I've seen in a long time.
Johan
Hrm. Patents aren't necessarily evil. E2B didn't immediately strike me as obvious, although this may be due to a general lack of information -- this was after all a press release, so as little information as possible is included to avoid confusing the media.
Could you perhaps provide some links to, or details about, what E2B really is, so that I can evaluate your claim that this is obvious technology?
TIA
Johan
Something that breezes through nuclear calculation could probably brute-force crack most encryption methods in an afternoon...
That would be very bad crypto, in that case. The keyspace enumerable (ie, assume a key checked per cycle -- obviously a best case scenario) for a 1 TeraOPs machine is just shy of 40 bits per second. So in two seconds it does 41, in 4 seconds it does 42... in 24 hours, just over 51 bits. Since you on average only need to search the half the keyspace, the best this machine could hope to crack using brute force is a 52 bit key per day.
But they were talking about eventually scaling up to 100 odd TOPs. 128 == 2^7, which brings it up our searchable space to just under 60 bits.
At that rate, You'll need to search for 2^68 days to break a 128 bit key. That's a pretty long time. Go calculate it for yourself. Oh, I'll do it, it's 10^20 odd days.
Johan
Good comment, that (#18). Upmod it, pls.
TERA does have some killer tech. I love that multithreaded switch on each clock stuff. Given that multi-threading is a big thing these days (cf sun's MAJC chip) and SGI has their CC-NUMA with non-uniform memory latencies, it makes a lot of sense for SGI to aquire TERA.
TERA's chip would be the perfect complement for a CC-NUMA architecture. Perfect.
Cool.
A technical aside:
How does swapping to a RAMdisk make any sense. I'm sure I'm missing something, but that just feels kooky. Unless you're meaning ramdisks on other computers (basically distributed shared memory) which assumes that net is significantly faster than local disk. I'll buy that for advanced networking. Just.
Johan
That's hillarious. They'd rather have the town change its name than add word delimiter recognition or an exception.
And these people actually stay in business!
My understanding and poor memory want to claim that hennesy and patterson's DLX architecture -- which (once again, from memory, so add salt) became concretised as the MIPS chip was the first RISC platform. Indeed, they could have patented (for once, something I conscider to be a patentable invention) the concept of constant complexity instructions, and prolly have made a bundle.
But I guess they still made out ok.
Personally I like SUN's java-multi-threaded CPU concept ( even if it never succeeds ). Basically,
you have 4 parallel fully functional, non-related, non-pipelined, fully optimized functional units.
There are no resource contention issues, no scheduling problems, a simplified logic design. And
it's cheaper because you take away pipelining. The best part is that each of these extrememly
simple components are just cookie cuts. You spend all your time tweaking the hell out of one tiny
unit, then make 32 copies. Almost as easy as cache design.
Tera baby! 128 threads, hardware support for context switching, no L1 cache, no pipelining, no superscalar units.
Bascially, you context switch after each instruction. Since you have 128 threads, this hides all the memory latency. You gotta love that design.
Stability is paramount in any palmtop w/o external storage. If a crash will kill your saved work, you'll never be able to trust the machine with _any_ work.
I've actually been toying with completely unmounting my harddrive in my laptop -- it has enough ram to hold a decent sized ramdisk and still have enough memory to work out of. By completely spinning down the harddisk, I hope to be able to extend the battery life to almost an hour (So I was a cheapskate and bought the noname brand. Now I'm paying for it). The only reason I would be willing to do this is because I know that my system is stable enough never to crash.
yes!
let me repeat that
yes!
From my laptop, I want a big screen, good keyboard, large harddrive, long batterylife. Notice how processor speed a was abstent from my requirements. I'm thinking a 486 or even a 386 (hell all I do is use emacs anyway) would do me just fine.
Hey laptop makers! lookie here! This is a market segment waiting for your attention.
Johan
Lovely,
apparently this post was is the same category as "PERL sucks! Python Rulez!".
Hillarious.
4, Insightful!?! That was the sound of the camel's back breaking.
Slashdot's moderation system's gotta change, 'cause it ain't working. Perhaps we should require all moderators to pass a humor identification, physics and math skills (yesterday, someone was comparing acceleration to velocity and was modded rediculously high), and perhaps even some rudimentary computer science tests.
This is getting silly.
Probably in the FAQ, which I would check before posting a question. However, this is an answer, so I don't feel the need for actually following directions (kindergarten didn't take). Anyway:
my Garbage Collection oriented friends tell me that His one biggest regret is making GC support optional. If it were required, then x% of all programming errors would go away, and library interfaces would be y times cleaner (no questions about who references or disposes of shared objects).
But they're biased of course.
Johan
The best part is that it scales beyond 2x2
You sure? I assumed that the reason why they were able to make it seamless was that if you use a 2x2 grid, each panel still has two hidden edges, giving you somewhere to attach the input signal. If you use a 3x3 scheme, the middle panel has no obscured edge, so it has to be fed "from behind", which I'm assuming is harder to do.
All this based on assumptions.
Why rescan the whole screen; you really only need to update pixels whose color has changed. But you're right -- as resolutions increase, bandwidth to the display is going to become a bottleneck, so we'll have to start using some send-the-diff scheme. Perhaps mpeg compressed video signal all the way to the display? This also relates to previous discussions on encrypted signals too.
Johan