«
Expand/Collapse
50 items tagged "lot"
Related tags:
chaos communication congress [+],
arduino [+],
tonnerre [+],
the rise [+],
project [+],
opensource project [+],
opensource [+],
mail readers [+],
web [+],
trust metrics [+],
trust [+],
seth hardy [+],
robots [+],
crypto applications [+],
cnc [+],
classic [+],
hacks [+],
week [+],
wearable [+],
unexpected corners [+],
time [+],
tags [+],
security [+],
new orleans [+],
misc [+],
miles [+],
hackers [+],
hackaday [+],
hack [+],
frequent flyer miles [+],
display [+],
bit [+],
ARM [+],
zelda [+],
zachariah perry [+],
xbox [+],
wristwatch [+],
work [+],
words of encouragement [+],
with [+],
wire [+],
whole lot [+],
water [+],
vinod [+],
vince cappellano [+],
video [+],
vendicator [+],
valentine [+],
vacuum fluorescent display [+],
type joke [+],
twinkle [+],
transportation [+],
toy cars [+],
toy [+],
tool [+],
todd [+],
tiny components [+],
tinkerer [+],
time saver [+],
than [+],
tattoo [+],
tait [+],
taco bell [+],
subtracting numbers [+],
stop sign [+],
still image [+],
stereo [+],
stephanie [+],
sql [+],
spoofers [+],
space experiments [+],
space [+],
sound [+],
smd [+],
skycam like [+],
skycam [+],
shop [+],
segment displays [+],
segment [+],
sculpture [+],
scart [+],
rover [+],
robot [+],
rfid readers [+],
rfid [+],
reprap [+],
replica props [+],
replica [+],
repair [+],
remote control [+],
reflow ovens [+],
reflow [+],
red light [+],
read [+],
prosthetic finger [+],
processing power [+],
printing [+],
printer [+],
presence [+],
prague [+],
pipboy [+],
pinky [+],
ping pong balls [+],
pick and place machine [+],
physical key [+],
physical feedback [+],
pedal [+],
parking lot attendant [+],
parking [+],
pal [+],
overhead view [+],
oven [+],
openpnp [+],
ocd [+],
occurrence [+],
nuclear reactor [+],
nova scotia canada [+],
nova scotia [+],
news [+],
new features [+],
mr.al [+],
mouse [+],
mount [+],
mode [+],
microcontrollers [+],
microcontroller [+],
megaupload [+],
mech eng [+],
machine [+],
love [+],
locomotion [+],
little chance [+],
linux [+],
light controllers [+],
light controller [+],
lifespan [+],
lifehacks [+],
lego bricks [+],
lego [+],
legal [+],
leds [+],
leapfrog [+],
laptop [+],
knowledge gap [+],
knack [+],
keyless [+],
juggler [+],
john powell [+],
james [+],
jaguar cd [+],
jaguar [+],
jack [+],
industrial processes [+],
indian motorcycle [+],
hydrofoil [+],
home [+],
holiday [+],
hobbyist [+],
heritage [+],
heating water [+],
heart container [+],
hdd [+],
handhelds [+],
guilty [+],
grey wall [+],
google [+],
gate [+],
full adder [+],
frank zhao [+],
fobs [+],
financial times [+],
festival [+],
experimenting [+],
excuse [+],
electroluminescence [+],
drive shaft [+],
domain redirection [+],
displaying graphics [+],
dip switches [+],
digital junk [+],
digital [+],
different styles [+],
didj [+],
dev boards [+],
dev [+],
designer [+],
decisions [+],
debugging [+],
debugger [+],
dave [+],
darknet [+],
dan royer [+],
crossover cable [+],
coordination [+],
cooking [+],
controller [+],
control engineering [+],
compatible boards [+],
combo [+],
cockpit [+],
clock source [+],
christmas light [+],
christmas [+],
chip debugging [+],
chip debugger [+],
china [+],
child [+],
charting [+],
certain [+],
cellphones [+],
carl [+],
car stereo [+],
car [+],
captain america shield [+],
captain america [+],
canon ae 1 [+],
canon [+],
canada [+],
cameras [+],
camera shots [+],
camera [+],
burning man [+],
bullduino [+],
bracer [+],
bottle of wine [+],
board [+],
bmw cars [+],
bmw [+],
bluetooth handset [+],
biped [+],
better [+],
beginner [+],
beagleboard [+],
aurora [+],
audio [+],
atmega8 [+],
atmega32 [+],
atari jaguar [+],
atari [+],
arm devices [+],
archers [+],
amper [+],
alpha numeric [+],
aloha state [+],
adder [+],
Issues [+],
Hardware [+],
Hackerspaces [+],
Ask [+],
555 timers [+],
3d printer [+]
-
-
12:12
»
Hack a Day
[Zachariah Perry] builds a lot of replica props, and judging from the first few offerings on his blog he’s quite good at it. We enjoyed looking in on the Captain America shield and Zelda treasure chest (complete with music, lights, and floating heart container). But his most recent offering is the wearable and (kind of) [...]
-
-
8:35
»
Hack a Day
We see a lot of microcontroller dev boards here at Hackaday, so much that we’re jokingly considering changing our name to Board a Day. These devices – from Arduinos to Arduino-compatible boards, very, very small boards, to extremely powerful ARM devices – are a great way to learn about the wonders of controlling electricity with code. [...]
-
-
13:01
»
Hack a Day
Here’s an automatic parking gate for toy cars. There’s no need to press a button, the electronics detect the presence of a vehicle on either side of the gate, raising it after verifying that the lot is not already full. It’s the same idea as counting how many people enter a room in order to [...]
-
-
5:01
»
Hack a Day
As your embedded applications get more complicated an On-Chip Debugger will save you a lot of time when things don’t run quite right. On-Chip Debugging (OCD) is just what it sounds like — a way to run your program on the target chip that lets you pause execution to examine values and change them if [...]
-
-
12:01
»
Hack a Day
We love seeing repairs and always marvel at the ability to track down the problem. [Todd] seems to have a knack for this. He was met with a lot of adversity when trying to get the Vacuum Fluorescent Display working on his car stereo. A lot of persistence, and a little bit of taking the [...]
-
-
14:07
»
SecDocs
Authors:
Seth Hardy Tags:
cryptography Event:
Chaos Communication Congress 22th (22C3) 2005 Abstract: Even with tutorials on the WoT and good trust policies the concept of "trust" can still be hard to grasp. Here we'll look at trust metrics, ways of using current trust systems better, and some non-crypto applications of trust. The web of trust best known for its use in PGP is now used in a number of other applications and is established as a good method for doing non-centralized PKI. But how good is it? How does one define a metric for trusting a trust metric? We have keysigning parties and extensive tutorials on good trust policies, but a lot of people still don't understand the basic concept of "trust," especially when it is superimposed on the world of graph theory. We'll take a look at the web of trust as it is currently used, including statistics on the PGP WoT and what that means in practical terms. And from there on, it's all about trust, including the trust metrics involved (and why they could be a lot better), and current "correct" practices for establishing trust (and why they could be a lot better). To wrap up, we'll look at the possibilities for doing other interesting (but non-cryptographic) applications involving trust.
-
14:07
»
SecDocs
Authors:
Seth Hardy Tags:
cryptography Event:
Chaos Communication Congress 22th (22C3) 2005 Abstract: Even with tutorials on the WoT and good trust policies the concept of "trust" can still be hard to grasp. Here we'll look at trust metrics, ways of using current trust systems better, and some non-crypto applications of trust. The web of trust best known for its use in PGP is now used in a number of other applications and is established as a good method for doing non-centralized PKI. But how good is it? How does one define a metric for trusting a trust metric? We have keysigning parties and extensive tutorials on good trust policies, but a lot of people still don't understand the basic concept of "trust," especially when it is superimposed on the world of graph theory. We'll take a look at the web of trust as it is currently used, including statistics on the PGP WoT and what that means in practical terms. And from there on, it's all about trust, including the trust metrics involved (and why they could be a lot better), and current "correct" practices for establishing trust (and why they could be a lot better). To wrap up, we'll look at the possibilities for doing other interesting (but non-cryptographic) applications involving trust.
-
13:01
»
Hack a Day
One look at this display and you know there’s a whole lot of pins that need to be wired up. Now look at what those display modules are mounted on. That’s right, [Kemley] is using point-to-point soldering to rig up this big display. It sports four sixteen segment modules on top for alpha-numeric information, and [...]
-
7:45
»
SecDocs
Authors:
Seth Hardy Tags:
cryptography Event:
Chaos Communication Congress 22th (22C3) 2005 Abstract: Even with tutorials on the WoT and good trust policies the concept of "trust" can still be hard to grasp. Here we'll look at trust metrics, ways of using current trust systems better, and some non-crypto applications of trust. The web of trust best known for its use in PGP is now used in a number of other applications and is established as a good method for doing non-centralized PKI. But how good is it? How does one define a metric for trusting a trust metric? We have keysigning parties and extensive tutorials on good trust policies, but a lot of people still don't understand the basic concept of "trust," especially when it is superimposed on the world of graph theory. We'll take a look at the web of trust as it is currently used, including statistics on the PGP WoT and what that means in practical terms. And from there on, it's all about trust, including the trust metrics involved (and why they could be a lot better), and current "correct" practices for establishing trust (and why they could be a lot better). To wrap up, we'll look at the possibilities for doing other interesting (but non-cryptographic) applications involving trust.
-
-
14:01
»
Hack a Day
With the Olympics on there are a lot of really great camera shots shown during the events. One of the best is the overhead view, which is provided by a camera suspended between cables. It’s not new for the Olympics, SkyCam has been around for over twenty years. What is new is [Dan Royer's] attempts [...]
-
-
17:04
»
Hack a Day
We had a lot of fun with that title. Of course when you’re talking about launching a thousand ping pong balls into space there’s no end to the puns which can be made. But this is actually a fantastic initiative to get people of all ages excited about science and near-space experiments. [John Powell] offers [...]
-
14:29
»
SecDocs
Authors:
Tonnerre Lombard Tags:
social Event:
Chaos Communication Congress 23th (23C3) 2006 Abstract: This lecture outlines a possible future retrospective on OpenSource built from a simple continuation of current trends. It's now been quite a while that OpenSource projects started to die out due to lack of developers, while on the other hand the number of similar projects in the same area is astonishing. 2006 then turned out to be the year when the first major OpenSource projects started to run into a similar crisis. In almost every area of computer science, there is an awful lot of similar projects which basically have the same goal but try to achieve it in only slightly different ways. There are, for example, gazillions of different Wiki projects, web fora, mail readers, editors, Linux distributions or window managers. This diversity does of course have a lot of advantages, but the amount of people working in the area of OpenSource in their free time is limited. Also, the amount of people who work in the area and are able to contribute quality code is quite low. The usual life cycle of an OpenSource project nowadays starts with its creation, of course. Then, it is usually maintained to the point where it is about half finished in terms of features. Then, there is usually a clash over some subject (Specific features that go/don't go in, the use of specific version control systems, the attitude of the maintainer), followed by a fork. Usually, this fork results in 3 or more different projects. The parent project usually dies off due to a lack of resources, which have been drained to the child projects. Normally, most of the child projects also lack a security practitioner, which usually leads to vulnerabilities, and consequently to a high load of security incidents which slow down the progress of the child project even further. Also, a lot of people think that in a fork project, they can now finally get rid of the scourge of good coding habits. This usually leads to the project wasting away due to a load of bugs that nobody can manage. There are various reasons for this. Of course, a prime reason lies in the evangelism that a lot of OpenSource developers just bear inside them. Projects get forked because they don't use the Only Beatific Technology, but some Inferior Technology from The Past. The original maintainer usually refuses to adapt to the new technology because he prefers to have a stable and well-known base to build on. Another big reason for this is the ego of some developers. A lot of people can't stand it if somebody tells them to bugger off with their patch because it doesn't meet the quality standards of the project. They fprk off a new project with the old code plus their patch, and either a number of developers from the original project fork off as well, or the child project quickly falls behind. Of course, there is also a problem on the maintainer side. A lot of maintainers don't like the fact at all that there are people who write better code or adapt new features that really are required for the project. This usually leads to one successful child project forking off while the parent project continues to float into space for a while with barely any maintainers left. This is of course one of the better ways to fork, but it still means a significant resource drain. Also, today's source control systems make it incredibly easy to fork off a project. It usually only requires a fork of the current repository, which is an usually action because today's source control systems just use project forks and push/pull technologies for concurrent development. Also, there are usually tools which convert an entire repository from source control system A to source control system B without even losing the metadata. This means that there is less hassle involved in forking off a project than there used to be, so it's easier to overcome one's inhibitions because the technical bar is lower. Another drain of resources isn't specific to an OpenSource project. An inherent problem of OpenSource resources lies in the fact that nowadays there is a new technology of the day out every other month, which means that most of the developers just try to learn a new Latest Thing (and start off projects with it, trying to solve problems that have been solved years before). This means that a lot of precious time is spent on learning Your Favorite Programming Language on Rails rather than writing code. On the other hand, the new technologies usually introduce new security problems that were previously unheard of, and that have to be taken into account as well. The .NET hype for example totally forgot to address that buffer overflow vulnerabilities aren't the only security problems in the world, and that .NET itself may also be a security problem. Finally, there will also be some positivism and a couple of suggestions (or maybe even guidelines) on how to get along a lot better in our projects than we used to.
-
14:25
»
SecDocs
Authors:
Tonnerre Lombard Tags:
social Event:
Chaos Communication Congress 23th (23C3) 2006 Abstract: This lecture outlines a possible future retrospective on OpenSource built from a simple continuation of current trends. It's now been quite a while that OpenSource projects started to die out due to lack of developers, while on the other hand the number of similar projects in the same area is astonishing. 2006 then turned out to be the year when the first major OpenSource projects started to run into a similar crisis. In almost every area of computer science, there is an awful lot of similar projects which basically have the same goal but try to achieve it in only slightly different ways. There are, for example, gazillions of different Wiki projects, web fora, mail readers, editors, Linux distributions or window managers. This diversity does of course have a lot of advantages, but the amount of people working in the area of OpenSource in their free time is limited. Also, the amount of people who work in the area and are able to contribute quality code is quite low. The usual life cycle of an OpenSource project nowadays starts with its creation, of course. Then, it is usually maintained to the point where it is about half finished in terms of features. Then, there is usually a clash over some subject (Specific features that go/don't go in, the use of specific version control systems, the attitude of the maintainer), followed by a fork. Usually, this fork results in 3 or more different projects. The parent project usually dies off due to a lack of resources, which have been drained to the child projects. Normally, most of the child projects also lack a security practitioner, which usually leads to vulnerabilities, and consequently to a high load of security incidents which slow down the progress of the child project even further. Also, a lot of people think that in a fork project, they can now finally get rid of the scourge of good coding habits. This usually leads to the project wasting away due to a load of bugs that nobody can manage. There are various reasons for this. Of course, a prime reason lies in the evangelism that a lot of OpenSource developers just bear inside them. Projects get forked because they don't use the Only Beatific Technology, but some Inferior Technology from The Past. The original maintainer usually refuses to adapt to the new technology because he prefers to have a stable and well-known base to build on. Another big reason for this is the ego of some developers. A lot of people can't stand it if somebody tells them to bugger off with their patch because it doesn't meet the quality standards of the project. They fprk off a new project with the old code plus their patch, and either a number of developers from the original project fork off as well, or the child project quickly falls behind. Of course, there is also a problem on the maintainer side. A lot of maintainers don't like the fact at all that there are people who write better code or adapt new features that really are required for the project. This usually leads to one successful child project forking off while the parent project continues to float into space for a while with barely any maintainers left. This is of course one of the better ways to fork, but it still means a significant resource drain. Also, today's source control systems make it incredibly easy to fork off a project. It usually only requires a fork of the current repository, which is an usually action because today's source control systems just use project forks and push/pull technologies for concurrent development. Also, there are usually tools which convert an entire repository from source control system A to source control system B without even losing the metadata. This means that there is less hassle involved in forking off a project than there used to be, so it's easier to overcome one's inhibitions because the technical bar is lower. Another drain of resources isn't specific to an OpenSource project. An inherent problem of OpenSource resources lies in the fact that nowadays there is a new technology of the day out every other month, which means that most of the developers just try to learn a new Latest Thing (and start off projects with it, trying to solve problems that have been solved years before). This means that a lot of precious time is spent on learning Your Favorite Programming Language on Rails rather than writing code. On the other hand, the new technologies usually introduce new security problems that were previously unheard of, and that have to be taken into account as well. The .NET hype for example totally forgot to address that buffer overflow vulnerabilities aren't the only security problems in the world, and that .NET itself may also be a security problem. Finally, there will also be some positivism and a couple of suggestions (or maybe even guidelines) on how to get along a lot better in our projects than we used to.
-
14:25
»
SecDocs
Authors:
Tonnerre Lombard Tags:
social Event:
Chaos Communication Congress 23th (23C3) 2006 Abstract: This lecture outlines a possible future retrospective on OpenSource built from a simple continuation of current trends. It's now been quite a while that OpenSource projects started to die out due to lack of developers, while on the other hand the number of similar projects in the same area is astonishing. 2006 then turned out to be the year when the first major OpenSource projects started to run into a similar crisis. In almost every area of computer science, there is an awful lot of similar projects which basically have the same goal but try to achieve it in only slightly different ways. There are, for example, gazillions of different Wiki projects, web fora, mail readers, editors, Linux distributions or window managers. This diversity does of course have a lot of advantages, but the amount of people working in the area of OpenSource in their free time is limited. Also, the amount of people who work in the area and are able to contribute quality code is quite low. The usual life cycle of an OpenSource project nowadays starts with its creation, of course. Then, it is usually maintained to the point where it is about half finished in terms of features. Then, there is usually a clash over some subject (Specific features that go/don't go in, the use of specific version control systems, the attitude of the maintainer), followed by a fork. Usually, this fork results in 3 or more different projects. The parent project usually dies off due to a lack of resources, which have been drained to the child projects. Normally, most of the child projects also lack a security practitioner, which usually leads to vulnerabilities, and consequently to a high load of security incidents which slow down the progress of the child project even further. Also, a lot of people think that in a fork project, they can now finally get rid of the scourge of good coding habits. This usually leads to the project wasting away due to a load of bugs that nobody can manage. There are various reasons for this. Of course, a prime reason lies in the evangelism that a lot of OpenSource developers just bear inside them. Projects get forked because they don't use the Only Beatific Technology, but some Inferior Technology from The Past. The original maintainer usually refuses to adapt to the new technology because he prefers to have a stable and well-known base to build on. Another big reason for this is the ego of some developers. A lot of people can't stand it if somebody tells them to bugger off with their patch because it doesn't meet the quality standards of the project. They fprk off a new project with the old code plus their patch, and either a number of developers from the original project fork off as well, or the child project quickly falls behind. Of course, there is also a problem on the maintainer side. A lot of maintainers don't like the fact at all that there are people who write better code or adapt new features that really are required for the project. This usually leads to one successful child project forking off while the parent project continues to float into space for a while with barely any maintainers left. This is of course one of the better ways to fork, but it still means a significant resource drain. Also, today's source control systems make it incredibly easy to fork off a project. It usually only requires a fork of the current repository, which is an usually action because today's source control systems just use project forks and push/pull technologies for concurrent development. Also, there are usually tools which convert an entire repository from source control system A to source control system B without even losing the metadata. This means that there is less hassle involved in forking off a project than there used to be, so it's easier to overcome one's inhibitions because the technical bar is lower. Another drain of resources isn't specific to an OpenSource project. An inherent problem of OpenSource resources lies in the fact that nowadays there is a new technology of the day out every other month, which means that most of the developers just try to learn a new Latest Thing (and start off projects with it, trying to solve problems that have been solved years before). This means that a lot of precious time is spent on learning Your Favorite Programming Language on Rails rather than writing code. On the other hand, the new technologies usually introduce new security problems that were previously unheard of, and that have to be taken into account as well. The .NET hype for example totally forgot to address that buffer overflow vulnerabilities aren't the only security problems in the world, and that .NET itself may also be a security problem. Finally, there will also be some positivism and a couple of suggestions (or maybe even guidelines) on how to get along a lot better in our projects than we used to.
-
14:21
»
SecDocs
Authors:
Tonnerre Lombard Tags:
social Event:
Chaos Communication Congress 23th (23C3) 2006 Abstract: This lecture outlines a possible future retrospective on OpenSource built from a simple continuation of current trends. It's now been quite a while that OpenSource projects started to die out due to lack of developers, while on the other hand the number of similar projects in the same area is astonishing. 2006 then turned out to be the year when the first major OpenSource projects started to run into a similar crisis. In almost every area of computer science, there is an awful lot of similar projects which basically have the same goal but try to achieve it in only slightly different ways. There are, for example, gazillions of different Wiki projects, web fora, mail readers, editors, Linux distributions or window managers. This diversity does of course have a lot of advantages, but the amount of people working in the area of OpenSource in their free time is limited. Also, the amount of people who work in the area and are able to contribute quality code is quite low. The usual life cycle of an OpenSource project nowadays starts with its creation, of course. Then, it is usually maintained to the point where it is about half finished in terms of features. Then, there is usually a clash over some subject (Specific features that go/don't go in, the use of specific version control systems, the attitude of the maintainer), followed by a fork. Usually, this fork results in 3 or more different projects. The parent project usually dies off due to a lack of resources, which have been drained to the child projects. Normally, most of the child projects also lack a security practitioner, which usually leads to vulnerabilities, and consequently to a high load of security incidents which slow down the progress of the child project even further. Also, a lot of people think that in a fork project, they can now finally get rid of the scourge of good coding habits. This usually leads to the project wasting away due to a load of bugs that nobody can manage. There are various reasons for this. Of course, a prime reason lies in the evangelism that a lot of OpenSource developers just bear inside them. Projects get forked because they don't use the Only Beatific Technology, but some Inferior Technology from The Past. The original maintainer usually refuses to adapt to the new technology because he prefers to have a stable and well-known base to build on. Another big reason for this is the ego of some developers. A lot of people can't stand it if somebody tells them to bugger off with their patch because it doesn't meet the quality standards of the project. They fprk off a new project with the old code plus their patch, and either a number of developers from the original project fork off as well, or the child project quickly falls behind. Of course, there is also a problem on the maintainer side. A lot of maintainers don't like the fact at all that there are people who write better code or adapt new features that really are required for the project. This usually leads to one successful child project forking off while the parent project continues to float into space for a while with barely any maintainers left. This is of course one of the better ways to fork, but it still means a significant resource drain. Also, today's source control systems make it incredibly easy to fork off a project. It usually only requires a fork of the current repository, which is an usually action because today's source control systems just use project forks and push/pull technologies for concurrent development. Also, there are usually tools which convert an entire repository from source control system A to source control system B without even losing the metadata. This means that there is less hassle involved in forking off a project than there used to be, so it's easier to overcome one's inhibitions because the technical bar is lower. Another drain of resources isn't specific to an OpenSource project. An inherent problem of OpenSource resources lies in the fact that nowadays there is a new technology of the day out every other month, which means that most of the developers just try to learn a new Latest Thing (and start off projects with it, trying to solve problems that have been solved years before). This means that a lot of precious time is spent on learning Your Favorite Programming Language on Rails rather than writing code. On the other hand, the new technologies usually introduce new security problems that were previously unheard of, and that have to be taken into account as well. The .NET hype for example totally forgot to address that buffer overflow vulnerabilities aren't the only security problems in the world, and that .NET itself may also be a security problem. Finally, there will also be some positivism and a couple of suggestions (or maybe even guidelines) on how to get along a lot better in our projects than we used to.
-
-
8:01
»
Hack a Day
A lot of higher end cars are now coming out with RF fobs that unlock and start the car. There is no longer a physical key that is inserted in the ignition. It turns out that for BMW this means stealing the cars is extremely easy for a sophisticated criminal. We always liked the idea of [...]
-
-
10:01
»
Hack a Day
Despite what you may have heard from the kids hanging out in the parking lot of Taco Bell, there’s a lot to be said about driving conservatively. Not peeling out after ever red light and stop sign does wonders for the life of your engine, and not slamming on the brakes 50 feet away from [...]
-
-
9:00
»
Hack a Day
Water takes a lot of energy to heat up. If you’d like evidence of this, simply jump into a 50° F swimming pool on Memorial Day. Despite the difficulty of heating water, that simple act accounts for a lot of industrial processes. From cooking a steak to running a nuclear reactor, there isn’t much that [...]
-
-
10:01
»
Hack a Day
[Stephanie] just finished up her wearable project which puts a lot of information where a wristwatch would normally be found. She calls it the Integrated Sensors Electronic Bracer. We had to look up what a bracer is; the name originates with archers and it was a leather wrap used to protect the wrist. This does that, but [...]
-
-
11:01
»
Hack a Day
We’ve seen a lot of builds using electroluminescent wire, usually in the realm of costumes and props. Unfortunately, most electrical engineers don’t deal with blinking and dimming EL wire and panels and any tinkerer trying to control electroluminescence doesn’t have a lot of resources on how to control EL stuff. [ch00f] wanted to fill this knowledge gap, [...]
-
-
4:35
»
Hack a Day
As a retired industrial designer, [Dave] has a lot of time to do what we’d all like to do: sit around in a workshop and make stuff. His latest project, an acrylic light display of an Indian motorcycle looks fantastic and betrays his designer heritage. The base of the light display is made up of a [...]
-
-
5:01
»
Hack a Day
After reading a bicycle-powered hydrofoil build we posted a few days ago, [James] sent in the project that earned him an iron ring from Dalhousie University in Nova Scotia, Canada. It’s a pedal-powered hydrofoil made of carbon fiber and a Titanium drive shaft [James] and five other students in a mech eng senior design class [...]
-
-
10:02
»
Hack a Day
[Vinod] has done a lot of work with microcontrollers, but this is his first try at displaying graphics using composite video. He had a small PAL television on hand, and an ATmega32 which just needs a stable clock source and a few resistors to get things going. There are a lot of other hacks around [...]
-
-
22:38
»
SecDocs
Tags:
social Event:
Chaos Communication Congress 28th (28C3) 2011 Abstract: In 2004 I started a weekly podcast on international under-reported news based on a feeling that this was something I enjoy doing and I could be good at. More than 7 years and 400 episodes later, with the help of listeners and friends, I have travelled almost nonstop to some of the most interesting and unexpected corners of the world. These travels have led me to some unconventional guests, topics, and life choices. Through it all, week after week, I have kept the program going. The lessons I've learned and continue to learn going forward, tell a story that answers alot of today's most popular questions about the future of the internet and independent journalism. From crowd source funding to the streets of New Orleans, from itunes politics to the mountains of Afghanistan, I will share these stories and whatever wisdom they have brought me.
-
22:38
»
SecDocs
Tags:
social Event:
Chaos Communication Congress 28th (28C3) 2011 Abstract: In 2004 I started a weekly podcast on international under-reported news based on a feeling that this was something I enjoy doing and I could be good at. More than 7 years and 400 episodes later, with the help of listeners and friends, I have travelled almost nonstop to some of the most interesting and unexpected corners of the world. These travels have led me to some unconventional guests, topics, and life choices. Through it all, week after week, I have kept the program going. The lessons I've learned and continue to learn going forward, tell a story that answers alot of today's most popular questions about the future of the internet and independent journalism. From crowd source funding to the streets of New Orleans, from itunes politics to the mountains of Afghanistan, I will share these stories and whatever wisdom they have brought me.
-
-
10:01
»
Hack a Day
Blinky lights have a way of attracting attention and that’s exactly what the members of the Maui Makers hackerspace were shooting for. The sculpture above is the logo for the Source festival, a Burning Man inspired music gathering in the Aloha state. For this year’s festival they went crazy, installing twelve meters of RGB LED [...]
-
-
15:02
»
Hack a Day
[Will] didn’t pick up a card, rose, and bottle of wine for Valentine’s Day like most guys. Nope, he planned way ahead and built this color-selectable glowing Valentine. When we first saw it, we figured he threw some LEDs together with a microcontroller and edge-lit a piece of acrylic. While that is technically what happened, [...]
-
-
10:07
»
Hack a Day
If you do a lot of SMD soldering, a reflow oven is the fastest and most efficient way to get all those tiny components attached to your PCB. [Frank Zhao] saw the reflow ovens we featured here over the last few weeks and figured he might as well show off his rig as well. We’re [...]
-
-
9:00
»
Hack a Day
We don’t know why, but the Atari Jaguar is getting a lot of attention this week. [10P6] just came up with this Jaguar/CD combo that reminds us what Atari could have come up with in 1993. The build itself is relatively simple once you get past [kevincal]‘s ‘April Fools’ type joke he played on the Atari [...]
-
-
8:01
»
Hack a Day
If you happen to do a lot of SMD work, a pick and place machine is an incredible time saver. The problem is that most automated pick and place solutions are well outside of the “small outfit” price range, let alone the budget of a hobbyist. We have seen some great DIY pick and place [...]
-
-
12:01
»
Hack a Day
That black box is hiding all kinds of goodies that make this rover a hacking playground. [Andrey] built the device around a BeagleBoard, which offers the processing power and modules that he needed to make the rest of it work. The control unit shrinks the pilot down to the rover’s size, using a cockpit that [...]
-
-
4:05
»
Hack a Day
This bar code tattoo was sent into us by [Lifespan]. Before going under the needle, [Lifespan] didn’t care much for tattoos. After seeing this video he realized that a tattoo could have dynamic content through domain redirection. [Lifespan] spent a lot of time going over the different styles of 2D bar codes. QR codes were [...]
-
-
13:01
»
Hack a Day
Hey everybody, [Nbitwonder] is building his own RepRap 3D printer. What’s special about that? Well, not much and and lot all at the same time. The art of building a self-replicating 3d printer still has a lot to do with luck and forum-crawling to make all of the decisions that go into this complicated project. [...]
-
-
9:35
»
Hack a Day
So we know you’ve got a lot of porn on your computer, but just how much is a lot? This concept mouse and hard drive combo aims to show you just how much digital junk you have acquired through physical feedback. The DataBot mouse looks like a typical run of the mill scroll mouse that [...]
-
-
10:00
»
Hack a Day
This robot juggler, pictured above during its appearance at Amper 2010, can keep five balls in the air at once. It was designed by the Department of Control Engineering at the Czech Technical Institute in Prague. We know it doesn’t look like much in that still image, but the two videos embedded after the break are pure [...]
-
-
8:42
»
Hack a Day
We’re sure there’s still a lot of folks using their original Xbox either for gaming or as an XBMC device. If you ever owned one yourself you’ll remember that you can’t turn it on with a remote control. If you have to get up and push a button on the front of the black box, [...]
-
-
6:00
»
Hack a Day
This 2-bit adder was a lot of work to build. It uses a total of thirty-six 555 timers and it does have the option of adding or subtracting numbers. It’s a rather unorthodox use of the part, depending more on the chip as an inverter and taking advantage of the fact that there’s an NPN [...]
-
-
12:00
»
Hack a Day
We see Arduino boards used in a lot of projects but we’ve never thought of using one as a USB crossover cable. That’s basically what [Jack the Vendicator] did to get his broken laptop running. When his video card stopped working he found himself unable to access the laptop. Newer machines don’t have a serial [...]
-
-
13:00
»
Hack a Day
We get a lot of tips about Christmas light controllers but rarely do they contain the kind of juicy detail that [Vince Cappellano] included with his setup. His video explaining the controller he built is embedded after the break and it’s not to be missed. We think there’s a lot of good design invovled in this porject. [...]
-
-
12:00
»
Hack a Day
We get a lot of email challenging us to hack things. Sometimes we ignore them, other times we send some words of encouragement. But this time around we thought [Tait] had really come up with a great hack; to build a Bluetooth handset into his prosthetic finger. He hasn’t done much hacking in the past [...]
-
-
12:00
»
Hack a Day
With 2400 LEGO bricks and a lot of patience, [Will Gorman] built a LEGO 3D printer. It’s similar to a RepRap or a Makerbot, but instead of extruding plastic, it uses pre-extruded building blocks (aka LEGO bricks). The grey wall extending far above the unit itself is a feed magazine which holds the raw material. [...]
-
-
12:00
»
Hack a Day
[Carl] has done a lot of work developing a collection of RFID hardware. The two cards you see above are spoofers that can be programmed in the field using the keypad on the left, or the rather intimidating banks of DIP switches on the right. We also enjoyed his look at the Atmel T5557 and [...]
-
-
11:00
»
Hack a Day
Shots of this Canon AE-1 camera-gone-digital have a lot of people scratching their heads. Originally there were a lot of “that’s been photoshopped” cries but the video after the break shows that it physically exists. This particular model of camera hasn’t been manufactured since 1984 so there’s little chance that the company’s bringing it back [...]
-
-
22:00
»
Hack a Day
Since we first mentioned the Leapfrog DIDJ, a lot has happened. A number of avid readers of Hack a Day teamed up with a couple hackers experienced with the DIDJ, and have managed to make some huge progress into making a linux based game console on the cheap. For all the readers who missed out [...]
-
-
11:00
»
Hack a Day
A while back, we announced that we would be bringing new features to Hackaday. One in particular that garnished a lot of interest was our question answer type thingy. Well, in case you hadn’t noticed, that has not happened yet. Without divulging too much into the secret machinery that lies underneath Hackaday, I’ll just say [...]
-
-
6:37
»
Hack a Day
This tiny biped shows a lot of coordination in its movements. As you can see, eight servo motors account for the locomotion with an ATmega8 as the brains of the operation. Posts for the first and second generation of this little guy feature several videos. We gather that a spreadsheet is being used to tweak [...]
-
-
9:00
»
darkc0de
lot of infected sql shop admin By Mr.Al3FrItE
0day.today (was: 1337day, Inj3ct0r, 1337db)
OSVDB Vulnerabilities
Exploit-DB
SecurityFocus Vulnerabilities
Bugtraq
XSSed
Packet Storm Security Headlines (2 unread)
Sophos security news
Penetration Testing
SecuriTeam
BackTrack Linux Forums
Threatpost
carnal0wnage.attackresearch.com
Carnal0wnage
Darknet
The Exploitant
Wirevolution