Reaction diffusion equations - there are hundreds in the human body doing things from handling the immune system, to regulating heart beats and the activation/inhibition of neuron activity. Every cortical unit in the brain has a particular purpose; remembering routes in 3D space or recognizing objects, shapes, colors and sounds.
If it's possible to make Gorilla glass for smartphones, wouldn't that work for solar panels? Perhaps someday, it will be possible to make solar panels as thin as plastic.
Wow. Perhaps someone could invent special flaps of metal that cover the solar panels and could automatically come down when there is heavy rain or hail. Maybe we could call them "shutters" or "grills".
For the record, they had university lecture notes that were no different from any other university (undergraduate courses are usually taught from the textbooks that every other university uses). The theory was that if a student didn't attend lectures and get the handouts that were provided, they would fail that course, and then fail to get a pass to go to the next year. So if the university could prove that the student had attended the lecture and got the handouts, then if the student failed, then that was entirely up to the student not reading the recommended textbooks, reading the handouts or handing in the coursework assignments.
It happened to all versions of MSDOS as well (Windows 3.1 days). Hardware like dot-matrix printers, VGA, SVGA graphics boards would all depend on their own 16-bit DOS drivers. Those became useless once everything moved to 32-bit Windows 95. And again when everything moved to 64-bit Windows. Even moves from Windows XP to Windows 7/8/10 usually involved new drivers. Then there's being able to boot a PC from USB. Old PC's can't do that. Modern PC's can. Even UEFI has problems booting from CD/DVD unless the magic options are set in the BIOS.
One of the old tricks of testing network software was to send randomly sized packets to the target system. Eventually something would crack. Sometimes they used function look-up tables to handle different packet types.
You can have encryption that is unbreakable for the masses, but can be cracked by brute-force by those with supercomputing systems with hundreds of thousands of CPU nodes.
If someone is using Tor, VPN's or some other IP address obfuscation system, then then odds are that one person is going to be using multiple proxy servers which will themselves be randomized due to machines being switched on or off depending on the time of day. Those users might have multiple systems; (desktops, laptops, tablets, smartphones).
So 20000 visits might be 1300 systems making 16 visits/week. Each of those systems is through a different proxy/Tor path which is reduced down to 100 users.
It wasn't a honeypot trap. The site existed before the Fed's took over. They got around the Tor encryption by getting some JavaScript/Java/PHP code to run on the host PC and extract the IP address that way. Stack Overflow and a hundred other blogs will all explain how to do this within a standard webpage. No illegal downloading of executables, DLL's, shared object files or modification of kernel permissions. Just plain web page design:
Some weapons already require two triggers to be pulled at the same time. Some smart gun systems use fingerprint or voice recognition. Others use a RFID ring that only activates the weapon when it is close to the wearer. But what if you have a cold, have been injured in the hands?
For legal reasons, my university took a register of every student who attended a lecture. That way they had a legal defence if anyone claimed the course notes were hopeless. They actually had one student who actually turned his lecture notes into a book back home.
The OpenGL bits that "sucked" at the time were lighting (8 or 16 light sources max, built in to the pipeline). This was great for CAD companies who just needed stuff to look like plastic, but it was awful for game developers. Also, OpenGL back then only used the begin/end model with display lists. The main vendors only optimized the paths that ID software used (various combinations of vertex, normal color and texcoords). Programmers had to speed test all the different paths to find out why there were speed differences. Some hardware vendors optimized their drivers for the application being run.
It has taken a lot of extensions to add vertex array/buffer objects, high level shaders, off-screen framebuffers, transform feedback and compute shaders. Even then the ARB commitee couldn't really agree on what features should be provided. If you look at the extension specifications from back then, hardware vendors couldn't even agree on what instructions should be provided for shaders.
From a Microsoft perspective, they are always the middle-man between hardware and applications (like shopping malls and actual plots of land). Thus they needed a device driver which they could modify and update in real-time according to the demands of the 3D industry, rather than at the speed of a committee. If anyone remembers the first attempts at building a standard for gaming (MSX consoles), each hardware vendor would provide a system that conformed to the base standard, and then add their own "special sauce" that tied players into their platform. This fell apart when games for one system wouldn't run on another. Microsoft wanted to avoid this and just be able to state what the minimum standard was (even this wasn't enough, so they moved into consoles with the XBox).
In 1995. when Quake made use of the floating-point and integer units of the Pentium CPU to do software texture-mapping in a custom engine, SGI realized that they had to bring out a software version of OpenGL that would run on desktop PC's. Back then some bits of OpenGL would be implemented in hardware (the "fast path"), and other bits in software (the "slow path"). It was a pain-in-the-ass for developers to try and divine which were slow and which were fast. Some combinations of vertex/color/normal attributes were fast and others were slow. Microsoft bought out a 3D game engine developer, pulled out the lower layers and created DirectX.
The 3Dfx brought out a piggy-back board, that worked with desktop PC's. Then SGI engineers left to form Nvidia, and a great race began. First texture-mapping was hardware accelerated, then both companies try to outdo each other every quarter with new extensions. That led to a legal battle, with Nvidia winning. Eventually by 2001, they reached having the first true full hardware accelerated consumer 3D graphics acceleration for a PC. That's continued.
Heat from an electric blanket would raise body temperature. Body temperature raises heart pressure to provide extra cooling. Extra blood pressure = migraine. The extra heat might also have some effect on the digestive system, heating up dissolved gases like CO2, CH4 and putting them through the blood stream.
To keep all your cortical units and neural units in sync, it was known that "slow waves" traveled through the brain tissue. That's particularly important for vision and audio processing given that over 30% of brain mass is dedicated to these inputs. The presence or absence of an electric field is known to speed up and slow down cell activity.
Various types of knowledge are also known to be stored in specific. Route-planning and map based knowledge are stored in the hypothalamus. I don't think this could instantly download lots of information but it might help boost brain activity.
To have a device connect to the Internet, you need a network chip (NIC), and that requires a TCP/IP stack. In turn that requires some basic OS, like Linux (embedded, no GUI, printers or any other drivers except a network driver). It's more cost effective writing a driver in C/C++ on a Linux system than it is to hire a microcode/firmware engineer. A webcam does live JPG/MPG compression and streaming as well as received commands, so that requires multithreading. Try to optimize and write that in assembler/microcode would take years. It's cheaper just to buy an embedded CPU and high-level toolchain.
It's easy enough to find out. I had an old desktop PC running Windows XP, and which hadn't been dejunkified for years. When it came to replacing the OS, it was time to have an OS demolishing party. Start by saving and transferring away all the files that needed to be saved. That left a user account with several gigabytes of data unaccounted for, as well as loads of system logs (uptime, applications used, driver loading) that were choking the defragmenter. Turns out all those "locked and unmovable files" were these log files. Delete them and suddenly the system was faster, and the defragmenter could work properly.
Once all your personal files are removed, it's only configuration files, web browser cache histories and application settings that are left.
Slashdot Mirror
Reaction diffusion equations - there are hundreds in the human body doing things from handling the immune system, to regulating heart beats and the activation/inhibition of neuron activity. Every cortical unit in the brain has a particular purpose; remembering routes in 3D space or recognizing objects, shapes, colors and sounds.
If it's possible to make Gorilla glass for smartphones, wouldn't that work for solar panels? Perhaps someday, it will be possible to make solar panels as thin as plastic.
You could always point a webcam at a TV tuned to a telesales channel
These systems already exist - used for protecting rugs, carpets and furniture on sundecks. Just needs a water/wind sensor and an electric motor:
http://mil.ufl.edu/4924/projec...
Wow. Perhaps someone could invent special flaps of metal that cover the solar panels and could automatically come down when there is heavy rain or hail. Maybe we could call them "shutters" or "grills".
For the record, they had university lecture notes that were no different from any other university (undergraduate courses are usually taught from the textbooks that every other university uses). The theory was that if a student didn't attend lectures and get the handouts that were provided, they would fail that course, and then fail to get a pass to go to the next year. So if the university could prove that the student had attended the lecture and got the handouts, then if the student failed, then that was entirely up to the student not reading the recommended textbooks, reading the handouts or handing in the coursework assignments.
It happened to all versions of MSDOS as well (Windows 3.1 days). Hardware like dot-matrix printers, VGA, SVGA graphics boards would all depend on their own 16-bit DOS drivers. Those became useless once everything moved to 32-bit Windows 95. And again when everything moved to 64-bit Windows. Even moves from Windows XP to Windows 7/8/10 usually involved new drivers. Then there's being able to boot a PC from USB. Old PC's can't do that. Modern PC's can. Even UEFI has problems booting from CD/DVD unless the magic options are set in the BIOS.
One of the old tricks of testing network software was to send randomly sized packets to the target system. Eventually something would crack. Sometimes they used function look-up tables to handle different packet types.
You can have encryption that is unbreakable for the masses, but can be cracked by brute-force by those with supercomputing systems with hundreds of thousands of CPU nodes.
If someone is using Tor, VPN's or some other IP address obfuscation system, then then odds are that one person is going to be using multiple proxy servers which will themselves be randomized due to machines being switched on or off depending on the time of day. Those users might have multiple systems; (desktops, laptops, tablets, smartphones).
So 20000 visits might be 1300 systems making 16 visits/week. Each of those systems is through a different proxy/Tor path which is reduced down to 100 users.
It wasn't a honeypot trap. The site existed before the Fed's took over. They got around the Tor encryption by getting some JavaScript/Java/PHP code to run on the host PC and extract the IP address that way. Stack Overflow and a hundred other blogs will all explain how to do this within a standard webpage. No illegal downloading of executables, DLL's, shared object files or modification of kernel permissions. Just plain web page design:
http://javascript.about.com/li...
Some weapons already require two triggers to be pulled at the same time. Some smart gun systems use fingerprint or voice recognition. Others use a RFID ring that only activates the weapon when it is close to the wearer. But what if you have a cold, have been injured in the hands?
If cows sense a threat to their calves they will approach the threat, knock it over and jump on it until that threat has gone.
http://www.independent.co.uk/n...
The next time you see them grazing peacefully in a sunny green field, just remember they are probably plotting to take over the world.
For legal reasons, my university took a register of every student who attended a lecture. That way they had a legal defence if anyone claimed the course notes were hopeless. They actually had one student who actually turned his lecture notes into a book back home.
The OpenGL bits that "sucked" at the time were lighting (8 or 16 light sources max, built in to the pipeline). This was great for CAD companies who just needed stuff to look like plastic, but it was awful for game developers. Also, OpenGL back then only used the begin/end model with display lists. The main vendors only optimized the paths that ID software used (various combinations of vertex, normal color and texcoords). Programmers had to speed test all the different paths to find out why there were speed differences. Some hardware vendors optimized their drivers for the application being run.
It has taken a lot of extensions to add vertex array/buffer objects, high level shaders, off-screen framebuffers, transform feedback and compute shaders. Even then the ARB commitee couldn't really agree on what features should be provided. If you look at the extension specifications from back then, hardware vendors couldn't even agree on what instructions should be provided for shaders.
From a Microsoft perspective, they are always the middle-man between hardware and applications (like shopping malls and actual plots of land). Thus they needed a device driver which they could modify and update in real-time according to the demands of the 3D industry, rather than at the speed of a committee.
If anyone remembers the first attempts at building a standard for gaming (MSX consoles), each hardware vendor would provide a system that conformed to the base standard, and then add their own "special sauce" that tied players into their platform. This fell apart when games for one system wouldn't run on another. Microsoft wanted to avoid this and just be able to state what the minimum standard was (even this wasn't enough, so they moved into consoles with the XBox).
In 1995. when Quake made use of the floating-point and integer units of the Pentium CPU to do software texture-mapping in a custom engine, SGI realized that they had to bring out a software version of OpenGL that would run on desktop PC's. Back then some bits of OpenGL would be implemented in hardware (the "fast path"), and other bits in software (the "slow path"). It was a pain-in-the-ass for developers to try and divine which were slow and which were fast. Some combinations of vertex/color/normal attributes were fast and others were slow. Microsoft bought out a 3D game engine developer, pulled out the lower layers and created DirectX.
The 3Dfx brought out a piggy-back board, that worked with desktop PC's. Then SGI engineers left to form Nvidia, and a great race began. First texture-mapping was hardware accelerated, then both companies try to outdo each other every quarter with new extensions. That led to a legal battle, with Nvidia winning.
Eventually by 2001, they reached having the first true full hardware accelerated consumer 3D graphics acceleration for a PC. That's continued.
Heat from an electric blanket would raise body temperature. Body temperature raises heart pressure to provide extra cooling. Extra blood pressure = migraine.
The extra heat might also have some effect on the digestive system, heating up dissolved gases like CO2, CH4 and putting them through the blood stream.
To keep all your cortical units and neural units in sync, it was known that "slow waves" traveled through the brain tissue. That's particularly important for vision and audio processing given that over 30% of brain mass is dedicated to these inputs. The presence or absence of an electric field is known to speed up and slow down cell activity.
Various types of knowledge are also known to be stored in specific. Route-planning and map based knowledge are stored in the hypothalamus. I don't think this could instantly download lots of information but it might help boost brain activity.
Inches, feet, yards, furlongs, rods, hands and hogsheads are Imperial units of measurement. Everything else is in rebel units of measurement.
You can split it up into several parts: task decomposition, actual coding, testing and refinement.
Here is what they are teaching in primary schools in the UK:
http://www.bbc.co.uk/education...
To have a device connect to the Internet, you need a network chip (NIC), and that requires a TCP/IP stack. In turn that requires some basic OS, like Linux (embedded, no GUI, printers or any other drivers except a network driver). It's more cost effective writing a driver in C/C++ on a Linux system than it is to hire a microcode/firmware engineer. A webcam does live JPG/MPG compression and streaming as well as received commands, so that requires multithreading. Try to optimize and write that in assembler/microcode would take years. It's cheaper just to buy an embedded CPU and high-level toolchain.
But how do you install the firmware? That's usually requires that you connect the device to a PC first.
They are definitely in Edinburgh. Both my college campus and home apartment complex had them. And I thought they were just in California.
"Beautiful sunny surburbia,
where the squirrels play, the magpies fly,
and dawn breaks with the sound of
rotating garden machinery."
It's easy enough to find out. I had an old desktop PC running Windows XP, and which hadn't been dejunkified for years. When it came to replacing the OS, it was time to have an OS demolishing party. Start by saving and transferring away all the files that needed to be saved. That left a user account with several gigabytes of data unaccounted for, as well as loads of system logs (uptime, applications used, driver loading) that were choking the defragmenter. Turns out all those "locked and unmovable files" were these log files. Delete them and suddenly the system was faster, and the defragmenter could work properly.
Once all your personal files are removed, it's only configuration files, web browser cache histories and application settings that are left.