Who Should We Blame For Friday’s DDOS Attack?

“Wondering which IoT device types are part of the Mirai botnet causing trouble today? Brian Krebs has the list, tweeted Trend Micro’s Eric Skinner Friday, sharing an early October link which identifies Panasonic, Samsung and Xerox printers, and lesser known makers of routers and cameras. An anonymous reader quotes Fortune:
Part of the responsibility should also lie with lawmakers and regulators, who have failed to create a safety system to account for the Internet-of-Things era we are now living in. Finally, it’s time for consumers to acknowledge they have a role in the attack too. By failing to secure the internet-connected devices, they are endangering not just themselves but the rest of the Internet as well.
If you’re worried, Motherboard is pointing people to an online scanning tool from BullGuard (a U.K. anti-virus firm) which checks whether devices on your home network are listed in the Shodan search engine for unsecured

Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/E6YM92S0WZg/who-should-we-blame-for-fridays-ddos-attack

Original article

Build a Talking Radio That Reads Incoming Notifications With a Raspberry Pi

The idea of a machine that talks to you intelligently might be a ways off still, but Instructables user MisterM wanted to make a radio that’d announce general details throughout the day. To do this, he wired up a Raspberry Pi Zero to a text-to-speech engine, then tossed in a dose of If This Then That.Read more…

Original URL: http://feeds.gawker.com/~r/lifehacker/full/~3/6SFYm1LSB6s/build-a-talking-radio-that-reads-incoming-notifications-1788071610

Original article

NPM v4.0.0

Welcome to npm@4, friends!

This is our first semver major release since the release of npm@3 just over a year ago. Back then, @3 turned out to be a bit of a ground-shaking release, with a brand-new installer with significant structural changes to how npm set up your tree. This is the end of an era, in a way. npm@4 also marks the release when we move both npm@2 and npm@3 into maintenance: We will no longer be updating those release branches with anything except critical bugfixes and security patches.

While its predecessor had some pretty serious impact, npm@4 is expected to have a much smaller effect on your day-to-day use of npm. Over the past year, we’ve collected a handful of breaking changes that we wanted to get in which are only breaking under a strict semver interpretation (which we follow). Some of these are simple usability improvements, while others fix

Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/LX82ZGB_waY/v4.0.0

Original article

Kaldi Speech Recognition Toolkit


To build the toolkit: see ./INSTALL. These instructions are valid for UNIX
systems including various flavors of Linux; Darwin; and Cygwin (has not been
tested on more “exotic” varieties of UNIX). For Windows installation
instructions (excluding Cygwin), see windows/INSTALL.

To run the example system builds, see egs/README.txt

If you encounter problems (and you probably will), please do not hesitate to
contact the developers (see below). In addition to specific questions, please
let us know if there are specific aspects of the project that you feel could be
improved, that you find confusing, etc., and which missing features you most
wish it had.

Kaldi information channels

For HOT news about Kaldi see the project site.

Documentation of Kaldi:

Info about the project, description of techniques, tutorial for C++ coding.
Doxygen reference of the C++ code.
Kaldi forums and mailing lists:

We have two different lists

User list kaldi-help
Developer list kaldi-developers:
To sign up to any of those mailing lists, go to

Development pattern for contributors

Create a

Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/cYHYmFkYjoE/kaldi

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: