Live data from Hacker News

The realtime magic behind Moot and how we deliver all your instant notifications

moot.it

21–30 of 47 posts

Re: The realtime magic behind Moot and how we deliver all your instant notifications

#21
post #16

Ehm.. tens of millions of realtime events but no "www." alias?: 404 Not Found Code: NoSuchWebsiteConfiguration Message: The specified bucket does not have a website configuration BucketName: www.moot.it RequestId: xxxx HostId: xxxxx I didn't know what "Moot" was so I tried www.moot.it

Hmm I think you must have hit it while we were doing a deploy. Looks like the www alias points right to S3 instead of our CDN. The CDN would have hidden the bucket reconfiguration. Oops. Will be updating the alias to point to the CDN. Thanks for catching that.

You're welcome!

(less welcome whoever downvoted me :))

Re: The realtime magic behind Moot and how we deliver all your instant notifications

#22
On Moot: I registered my account because I wanted to integrate Moot on my new website I'm building and when trying to integrate it to a view in Rails:

    `a class="moot" href="#{request.original_url}"> Awesome Startup`
I'm getting an message on the page and no moot forums.

" (moot logo) startup does not exist."

Isn't this like Disqus where I can have commenting threads based on the page?

Re: The realtime magic behind Moot and how we deliver all your instant notifications

#23

On Moot: I registered my account because I wanted to integrate Moot on my new website I'm building and when trying to integrate it to a view in Rails: `a class="moot" href="#{request.original_url}"> Awesome Startup` I'm getting an message on the page and no moot forums. " (moot logo) startup does not exist." Isn't this like Disqus where I can have commenting threads based on the page?

Yes. You can have commenting threads based on the page. The value on the href attribute takes a form

https\://moot.it/i/[forumname]/[an_unique_path]

You'll get the [forumname] from the setup (https://moot.it/setup) and you need to pick an unique path for each of the commenting area. The paths can be designed to fit your site's structure. For example

/blog/2013/august:my-awesome-entry /blog/2013/june:another-blog-post

You can list all comments from any path such as

/blog/2013

The "/i/" part means SEO indexed content. Our servers automatically generate a search engine optimized version of all the comments that are structured according to the path structure. Here is the SEO content for our forums for example

https://moot.it/i/moot

And here are all comments from our release blog entries

https://moot.it/i/moot/blog/release

The way we handle SEO is one of the differences from Disqus.

Here is more information about the paths:

https://moot.it/docs/embedding.html#paths

Re: The realtime magic behind Moot and how we deliver all your instant notifications

#25
post #11

Earlier quoted context omitted.

Realistically, it sounds like the 2nd diagram should have the middle section of the first diagram. As in, a single message/circle, gets "split" (or more accurately dup'd) and somewhat simultaneously delivered to the start of every 'channel'. The way it is now makes the appearance that a message isn't sent down a channel where the logic gate will not eventually deliver it. But that doesn't seem to be the case.

Yeah, yeah, I know: I'm just a graphic designer without a deep knowledge of the technology... But what happens in the diagram is still pretty close to what you describe, to be fair: messages duped and delivered simultaneously. Absolute accuracy would have made for a pretty complex illustration. Point taken anyway, I'll try harder next time! Btw, did you notice it has blue heads? I thought those were cool.

Why are they blue do they not understand the diagram they are being used in either?

Re: The realtime magic behind Moot and how we deliver all your instant notifications

#26
post #10

Are you going to open-source your json-rpc library? If so, is there a specific timeframe you have in mind? I'd really love to use this technology in my own projects.

You may be interested in dnode[0] as well. Protocol documented here[1].

[0] https://github.com/substack/dnode

[1] https://github.com/substack/dnode-protocol/blob/master/doc/p...

Re: The realtime magic behind Moot and how we deliver all your instant notifications

#27
Do you have any plans to open source this for people who wants to install Moot on their own server? As a forum junkie, I'm excited about Moot, but I hope you do understand that to be successful as a platform you have to give the option to self-host :)

Re: The realtime magic behind Moot and how we deliver all your instant notifications

#28
post #9

If you want something similar to this and you're on the JVM, you can use open source Atmosphere[1] which handles this flow exactly (websocket with fallback, multiple 'tags', etc). [1] https://github.com/Atmosphere/atmosphere

I integrated Atmosphere into a Dropwizard-based project (not on GitHub yet, hoping to get it out there in a week or two -- look for Cyranix/mi5 if interested). Although I did get it to work, it wasn't a smooth experience. There seem to be many ways of accomplishing the same thing which are just different enough to trip you up in subtle ways (at least if you're only a moderately experienced dev like myself), and the documentation is a bit of a mess (scattered, not well translated from French, etc. -- not entirely, but enough to be a pain). Any JavaScript devs interested in this sort of tech could make a much-appreciated contribution to the project by making a client-side script that doesn't depend on jQuery.
Post reply on HN