> Most prominently, we used it during our Olympics coverage to monitor the results of the API we built and let us know if the data ingestion pipeline ever grew stale. To do that, we set up a pipeline
I always liked the Yahoo Pipes concept... but it didn' seem take off... and I personally found it too limited for everything I tried to do with it. Perhaps it's just another case of the old "visual programming language" is harder than it looks.
I hope Huginn does better. I like their copywriting "You always know who has your data. You do."
Agreed. I did a multipart Yahoo Pipes project to find my current apartment. It grabbed info from two sites, tossed out the uninteresting ones, filtered it a bit, then texted me if a new apartment in my price/location range appeared.
Very useful, if a little awkward. The Huginn project sounds like a great alternative!
I don't know, the documentation is excellent. That is certainly one of the best READMEs I have ever seen. The organization of the setup sction of the README is superb. The author of the README clearly thought about the needs of new users as well as seasoned veterans. More projects need to adopt this general format:
# Getting Started
## Quick Start
If you are unsure of our project and just want to play around, you can
get things set up quickly by:
1. Clone this repository and…
2. Do something
3. Do the other thing
If you need more detailed instructions, have no fear. We are not going
to look down on you if you are not an expert. We took the time to write
a setup guide for newcomers: [Novice setup guide][novice-setup-guide].
Everybody has to start somewhere.
## Real Start
Follow these instructions if you wish to deploy your own version or
contribute back to the project. There is nothing we hate more than
README’s that ignore all of the practical concerns related to setting up
a long term installation. Follow these steps and it will be easy for you
to keep up with updates to the project and still retain the all tweaks
you made to suit your idiosyncrasies.
## Odds and Ends
### Optional features
Not everybody needs a XYZ plugin or wants to share their every action
with PQR. You can enable these features by…
### Rare Corner cases
In certain rare circumstances you made need to prevent X or implement Y.
Prevent X by…
If you need to implement Y…
This looks really awesome for managing an office. We're currently automating things using Google scripts and other custom glue to do things like order food, get feedback on lunch and mail people weekly digests activities. Sounds like this could be a great solution for this.
Zapier is also good with lots of integrations, but it's a little pricey. Yet if you calculate what your time is worth and include the amount spent on making this work plus customizations, it's probably less. Depends on if Zapier can do what you want.
I'm not sure about the etymology of Hugin, but Huginn is more than likely a reference to Norse mythology (for Anchorman fans, you'd recognize it as "Great Odin's raven!"):
I am working on a similar project called Taskflow.io that is aimed at more backend business oriented tasks. It can do similar things through an interface flowchart editors where you make the actual flowchart that gets executed. I would still consider it a public beta. I would love your feedback.
Will this be provided As-A-Service, or will it be a downloadable product that can be deployed in-house? This is exactly what I have been looking for for a while, but there's absolutely zero chance we're going to send any of our business information to a remote service.
Anyone know why this project encourages using a private fork to do contributing development?
> "Make a public fork of Huginn. [...] Make a private, empty GitHub repository called huginn-private. Duplicate your public fork into your new private repository[. ...] Checkout your new private repository. Add your Huginn public fork as a remote to your new private repository[. ...] When you want to contribute patches, do a remote push from your private repository to your public fork of the relevant commits, then make a pull request to this repository."
It will run, but the default Procfile spins up 4 processes, so Heroku might be expensive. If someone wants to figure out how to get everything to run easily in one process, that would make free Heroku hosting possible. I run it on a small VPS.
Exciting stuff, it would be amazing to build an AI layer on top of this that mines your browsing habits (depending on your paranoia settings) and automatically generates agents based on your interests.
Storm is a framework for coordinating computation. It's not really designed to "perform automated tasks for you online" - although of course you could make it do that.
If you want to run a machine learning algorithm on 100 machines then Storm is what you want. Want a service to check the weather for your location? Huginn looks good.
Storm doesn't naturally support dynamic topologies and is rather resource hungry, which needs a bit advanced planning. I was looking @ Storm for my own pipelining product (bip.io) very early on and shied away as too high an opportunity cost for self-hosting users/devs to be bothered with. On a Rasberry Pi for example, forget about it. Without being able to create dynamic graphs it otherwise just ends up being a simple message bus (anti-pattern).
You are right that Storm is certainly more robust for large amounts of data. But Storm just provides underlying infrastructure. Huginn builds on top of something like that to add different agents for twitter, weather etc. So afaict, Huginn is an app built on top of something like Storm.
I extended a Find My iDevice API lib about a year ago with the intention of creating a Huginn agent for exactly this, but life got in the way. I also wanted to add a geofencing agent, too.
[+] [-] danso|12 years ago|reply
https://source.opennews.org/en-US/articles/open-source-bot-f...
> Most prominently, we used it during our Olympics coverage to monitor the results of the API we built and let us know if the data ingestion pipeline ever grew stale. To do that, we set up a pipeline
[+] [-] hyp0|12 years ago|reply
I hope Huginn does better. I like their copywriting "You always know who has your data. You do."
[+] [-] shavenwarthog2|12 years ago|reply
Very useful, if a little awkward. The Huginn project sounds like a great alternative!
[+] [-] albertsun|12 years ago|reply
[+] [-] dfc|12 years ago|reply
[+] [-] platz|12 years ago|reply
[+] [-] malanj|12 years ago|reply
[+] [-] toomuchtodo|12 years ago|reply
[+] [-] anentropic|12 years ago|reply
[+] [-] yukichan|12 years ago|reply
[+] [-] c0nsumer|12 years ago|reply
This just has another N bolted on to the end and does something completely different.
[+] [-] jmduke|12 years ago|reply
http://en.wikipedia.org/wiki/Huginn_and_Muninn
[+] [-] FroshKiller|12 years ago|reply
[+] [-] jschulenklopper|12 years ago|reply
BTW, a great idea and an impressive side project!
[+] [-] fasteddie31003|12 years ago|reply
[+] [-] zorbo|12 years ago|reply
[+] [-] bkyan|12 years ago|reply
http://shadowcatcher.mindcast.com/clips/1397535410d5p7t6ut3s...
[+] [-] johnobrien1010|12 years ago|reply
[+] [-] alxndr|12 years ago|reply
> "Make a public fork of Huginn. [...] Make a private, empty GitHub repository called huginn-private. Duplicate your public fork into your new private repository[. ...] Checkout your new private repository. Add your Huginn public fork as a remote to your new private repository[. ...] When you want to contribute patches, do a remote push from your private repository to your public fork of the relevant commits, then make a pull request to this repository."
[+] [-] tectonic|12 years ago|reply
[+] [-] rcyeager|12 years ago|reply
[+] [-] finnn|12 years ago|reply
[+] [-] thomasfl|12 years ago|reply
[+] [-] tectonic|12 years ago|reply
[+] [-] jayxie|12 years ago|reply
[+] [-] platz|12 years ago|reply
[+] [-] nl|12 years ago|reply
If you want to run a machine learning algorithm on 100 machines then Storm is what you want. Want a service to check the weather for your location? Huginn looks good.
[+] [-] feralmoan|12 years ago|reply
[+] [-] egonschiele|12 years ago|reply
[+] [-] weavie|12 years ago|reply
[+] [-] okhan|12 years ago|reply
[+] [-] zwentz|12 years ago|reply
[+] [-] kzahel|12 years ago|reply
[+] [-] crawfordcomeaux|12 years ago|reply
Unsure if there's a better lib out there, but here's what I worked on...warning: needs lots of love, eg. tests: https://github.com/rickyc/find-my-ios-device
[+] [-] gibbsnich|12 years ago|reply
[+] [-] platz|12 years ago|reply
[+] [-] N0RMAN|12 years ago|reply
[+] [-] kirk21|12 years ago|reply
[+] [-] tectonic|12 years ago|reply
[+] [-] SloughFeg|12 years ago|reply
[+] [-] sundip|12 years ago|reply
[+] [-] fujipadam|12 years ago|reply