Neddick

e it a try, basically create a postgres database named neddick_dev, clone the repo, install Grails 3.3.6, and then run the runneddick.sh script from in the repo directory. You'd also want to tweak the neddick.home property defined in runneddick.sh to point somewhere meaningful. We don't currently have any built-in support for leveraging a site's built in search mechanism, but I could see it being a useful addition. If somebody wanted to contribute that kind of functionality, I'd be happy to include it. When we would get around to building it ourself is hard to say. [1]: https://github.com/fogbeam/Neddick

could say the idea here is to bring the Linked Data approach inside the enterprise. I can't promise anything definite, but as with any commercially backed open source project, the possibility is always open that if somebody contributes to the project and kicks ass, that we may be able to find (or create) a spot for that person at Fogbeam at some point. All commercial notions aside, we are working on some wicked cool stuff, especially the semantic web stuff, and would welcome anybody who wants to get involved. At worst, we'll all learn some stuff and have some fun together.

mantic query support. Coming down the pipe will be some rad visualizations and just generally more support for different ways to navigate the "knowledge space" that is entailed by related content, people, events and tasks. For me, this is a classic "win win" because I get to have fun working with cool tech: machine learning / big data (Mahout, Hadoop, etc.), Event Stream Processing, Semantic Web stuff (Stanbol, Jena, Fuseki, etc.) and because we're building some stuff that I think we're going to be able to monetize. Build awesome tools AND make money from it? That sounds like my idea of fun. :-)

re threshold, or is tagged with a certain tag. We'll also be implementing "channel filters" soon, which let you filter a given channel (sorta like a sub-reddit) down to just the entries that match your criteria. And we've got some mondo gnarly semantic content enhancement / analysis stuff coming down the pipe in the next few months... Unfortunately there aren't proper installers yet and the documentation is pretty weak, but if anyone is interested in giving it a spin, feel free to ping me for assistance. And we'll get the doco squared away at some point and get some tooling but to make installation / configuration easier (yeah, this stuff is an "on premises" play for now). [1]: https://github.com/fogbeam/Quoddy [2]: https://github.com/fogbeam/Neddick

So if you wanted to, for example, define a "marketing" channel and point it all the popular marketing blogs, you could do that. Or you could create a "techies" channel, point it at Hacker News, Techcrunch, GroovyBlogs.org, etc. Whatever makes sense. OK, so given a Reddit like thing, where we are starting to do some different stuff is here... we are implementing what we call "triggers" and "filters" to give a user more control over what happens with content in the system. Filters let you filter a channel down to only those entries that match certain criteria (title keyword, body keyword, score, submitter, etc.). Triggers are a similar notion, but they fire in reaction to events like "new entry posted", "entry tagged", "entry voted on", etc., and allow users to hook an action to the event. So you can arrange to, for example, have an entry emailed if it hits a certain score or receives a certain tag. We also have an explicit "share" button that we attach to entries that allows you to share the entry via email, XMPP, or via a RESTful POST (in ActivityStrea.ms format) to a URL. Right now we are focused on using that feature to allow users to "share" entries to our other product, Quoddy[2], which is an Enterprise Social Network. As an ESN, it lets you do all the kinds of things you might imagine an ESN doing, and we're working now on Semantic Web integration so we can do automatic content enrichment, etc. So yeah, I'm a big fan of technological tooling for sharing information and knowledge in an office setting. Now, the kinds of things we're building, I think, start to have the most value once an organization gets to a certain threshold of size/complexity (say, 500 employees or more). A 10 person company might be able to get by with just an email list or something a lot simpler than our thing. Honestly, we're building mainly for bigger companies, as our ESN has SOA/ESB integration, BPM integration and a lot of "enterprise" stuff (which stands to reason, seeing as it's an "enterprise" social network! :-) ) Obviously I think that information / knowledge sharing are important, or we wouldn't be working on this stuff. But here's where it gets more interesting in my opinion... if all you do is share links, blurbs, whatever, you gain some value from that, but you don't gain the maximum value from it. You can email your office a link to a great article about, say, a new programming technique that you think should be adopted, or a new marketing approach, and it's very easy for it to just disappear into the ether, for various reasons. We think this kind of information sharing should have deeper hooks into how people actually get work done, and should support tooling to help A. keep things from getting lost, B. route just the right information to just the right people, and C. provide context to help support decision making. That's why we thing things like BPM and ESB integration are important to an ESN.. imagine if somebody shares a link to a document, and when you view it, you get pointers to open workflow User Tasks which are related to that document, or to recent business events which have some connection to that document. Or, imagine if you have a button you can click that takes the link that got shared, and actually starts a workflow around it. One thing about this stuff though... culture is huge. Some companies are a good fit for this kind of stuff, and some aren't. Companies that are very "flat" organizationally, that promote empowered employees and widespread collaboration, will love this stuff. Companies that are heavy on top-down, command & control hierarchy, that are very divisive politically, where knowledge hoarding is practiced, etc., won't use this stuff even if you implement it. Anyway, if you ever want to bat some ideas around offline, feel free to shoot me an email. Information sharing / knowledge management / collaboration are kind of my passion, so I'm always interested in talking about this stuff. [1]: https://github.com/fogbeam/Neddick [2]: https://github.com/fogbeam/Quoddy

n model... this is based on a "install and host it yourself" model - because our real focus in on enterprise use, and we expect people to consume feeds from things like their CRM system, document management system, internal blogs, etc. as a primary use case. Also, as a side note, I think Dave Winer has some interesting thoughts here[2] for anybody considering building a new Reader. [1]: https://github.com/fogbeam/Neddick [2]: http://threads2.scripting.com/2013/march/theIdealRssReader

les innocently (There's a new visual theme coming that won't look so obviously inspired by Reddit, BTW) All of that said, we're not at a 1.0 release yet and while a LOT of stuff works, and someone could almost certainly get value from it, there are definitely bugs and things that don't yet work the way we want them to. In particular the recommendations engine is currently just the Lucene MoreLikeThis filter which is pretty naive. We have plans to roll some much more sophisticated analysis using Mahout[2] eventually, but haven't gotten there yet. Eventually we'll have persistent searches with alerts via email and XMPP, alerts based on vote thresholds, and a whole raft of other features. It's coming together, just more slowly than we'd like. If you want to take a look, there's a public demo server at http://demo.fogbeam.org:8080/neddick1 Sample logins are testuser0-testuser19 with password "secret". The front-page right now is actually being fed the RSS feed from here at HN, but you'll notice it's a few days out of date. That's one of the bugs I mentioned. There's a bad piece of content coming in on one of the feeds, and it's breaking the parsing, which is currently causing it to break out of the loop that consumes the feed. Fixing that is on my TODO list for Real Soon Now, so hopefully by this weekend. Edit: This channel is more up to date, and it is, indeed, being populated from a Google Alert. This is getting a bit meta circular now... :-) http://demo.fogbeam.org:8080/neddick1/r/Microsoft If you wanted to use this for a more general "entire web" alerting tool, you'd have to build (or acquire) a crawler to go out and get the data. I think there might be some useful stuff in Nutch[3], Droids[4], Manifold[5] and/or Heritrix[6], but I won't swear to it. That's the bit we're not really interested in, as we aren't trying to build a public, consumer facing app here, but a tool for use inside organizations. Still, if somebody wanted to use it that way, it could be done. Scalability would also be an issue, but I think that could be managed.. [1]: https://github.com/fogbeam/Neddick [2]: http://mahout.apache.org [3]: http://nutch.apache.org [4]: http://incubator.apache.org/droids/ [5]: http://manifoldcf.apache.org/ [6]: http://en.wikipedia.org/wiki/Heritrix