May 12
May 07
K-I-S-S-I-N-G! Great news for both teams, Revision3 and Viddler have decided to team up — errr, Rev3 has decided to host all of their videos on Viddler’s system. See a tidbit from Colin’s latest post on the Viddler blog:
Each and every day more of your favorite videos, from vlogs to viral, are showing up here on Viddler. Today is no exception. Now more than ever, thanks to Revision3 and all of its shows joining Viddler, you can watch your favorite Web video shows in your favorite Web video player!
Please join me in welcoming DiggNation, The Digg Reel, Infected, The Revision3 Gazette, Tekzilla, my friend Om Malik’s GigaOm Show, PixelPerfect, iFanboy, SYSTM, Scam School, XLR8R, Web Drifter, and the Totally Rad Show to the Viddler community.
Not only is this great for Viddler (as any publicity is good publicity and this is surely great) but this also means a great new feature is rolled out (at least I think it’s new), Digg right in the Viddler videos. (Forgive me if it’s not but if it’s new to me, it’s new because it’s my blog and I said so.)
They’ve made it simple and easy to do. Just make sure you’ve submitted the link to Digg and then simply add a tag to your video that says “digg:URL-that-was-submitted-to-viddler” and you’re all set. Remember, make sure you have already posted it or you get something like this:
So go ahead, behold the beautiful new child that is Vidiggler and bask in its glory — or at least give it a whirl on your own videos.
What do you think of Viddler and Rev3 joining forces? Or better yet, what are your thoughts on Web2.0 companies joining forces in general?
Apr 21
I came across a very interesting read at Marcus Ranum’s blog about the 6 dumbest ideas in computer security. His number 1 idea was by far one of my biggest pet peeves:
#1) Default Permit
The most recognizable form in which the “Default Permit” dumb idea manifests itself is in firewall rules. Back in the very early days of computer security, network managers would set up an internet connection and decide to secure it by turning off incoming telnet, incoming rlogin, and incoming FTP. Everything else was allowed through, hence the name “Default Permit.” This put the security practitioner in an endless arms-race with the hackers. Suppose a new vulnerability is found in a service that is not blocked - now the administrators need to decide whether to deny it or not, hopefully, before they got hacked. A lot of organizations adopted “Default Permit” in the early 1990’s and convinced themselves it was OK because “hackers will never bother to come after us.” The 1990’s, with the advent of worms, should have killed off “Default Permit” forever but it didn’t. In fact, most networks today are still built around the notion of an open core with no segmentation. That’s “Default Permit.”
This could not be truer. I find every time I go into a meeting to discuss, setup, introduce or roll out the newest and greatest product, this comes into play. Most people want to roll it out without thinking about what it actually does. Take for example a new firewall system. The new product could be brought in, setup and configured exactly like the old one and everything will probably continue to function. But in the end, why bother spending $20,000 on the new box if you aren’t going to look at what you’re using it for.
Please keep this in mind while setting up your new software program, coding your new web application or simply plugging in the greatest computer you have ever owned. Keep it closed — open only what you need.