Federated identities work [out of the box](/help/#wordpress) with Wordpress. You just need to enter your Muut API keys on WP admin area. A SMALL subscription is required.
Good article 😀
We are having so many problems with Muut that we're looking into switching to Disqus. In addition to the terrible glitches within Muut's Shopify App, we are really disapointed that Muut still hasn't come up with a mobile app in spite of the fact that all those "stale" platforms like Disqus and Discourse have had them out for a long time.
Retraction: I'm learning quickly that the glitches aren't on Muut's end. Shopify makes such customizations very difficult. Had I known then what I know now, I would have setup my channel independently of my Shopify store. But not to fear -- Monika and team are solving the problem and coding the customizations we need into a Shopify walkthrough for customers like me. Great team you guys have at Muut!!
> @clitesbr > mobile app in spite of the fact that all those “stale” platforms like Disqus and Discourse have had them out for a long time. Just thought I'd mention that neither Disqus nor Discourse have a mobile app! Anyway Brian glad we've been able to help you get the customized Muut setup on your Shopify site!
I stand corrected again. I had used the Discourse app as a user, but see that its since been pulled from the iOS App Store. And if I understand correctly, Disqus is coded into extant mobile apps but that extensibility is done by the big companies using their platform, not by a dedicated Disqus app. At any rate, Courtney, I'll be looking forward to working with you guys for the forseable future. You've gotten my chief concerns straightened out and then some. Hopefully we can figure out a way for mobile users to stay logged into sites like mine for an extended period of time -- right now its that login inconvenience factor that had me most concerned about this forum on mobile. Until I figure out where the problem lies on Shopify, I'll be directing our mobile users to the full forum view on muut.com You guys rock.
Glad things are working out well for you!
Will be trying Muut with github pages. Hope it goes well. Any advices?
This page causes Chrome v45.0.2454.93 to consume 167 532KB of Private Memory, making it one of the larger memory-gobbling tabs now running for me, according to Chrome Task Manager—chrome://memory-redirect/ and chrome://memory-internals/ report different but similar numbers which don't change rankings of tabs—long-running Twitter and Facebook tabs also eat lots of memory. In everyday use, memory demand and demand paging slow my machine and my work more than load times. It slows not only this page itself, but my entire computer and my work, opening and reopening tabs/pages too, if i cannot leave them open. What plans has Muut for reducing memory usage and it deleterious effect on user experience?
John, in our tests Muut does not leak memory in the tab. In fact the memory that Muut uses should slightly decrease after a while being open (10-15%) and will not expand from there. If you look at a typical tab with nothing on it for me, chrome tabs start at around 70mb. That's for a empty server response. Basic HTML with no scripting for me ends up around mid 70s. Even basic scripting pushes that up quite a bit. If you add Muut to that page you will see it bump up to 110 or so then after a while of being inactive will drop to the 90s. So to go from nothing on the page to Muut we're not talking about a major. Things like Twitter and Facebook on initial load approach 300mb. On this page in particular there's more going on than just Muut contributing to the usage you are seeing, Muut itself contributes very little and does not leak when it's long running. I actually leave Muut tabs running pretty much indefinitely and I do not see any ballooning memory usage. A good test would be to have two pages, one with Muut and one without Muut, let both tabs run in the background and compare memory utilization. I think you'll find that Muut performs well in long running situations and it's resource usage compared to the same page without Muut is rather low (especially compared to anything with anywhere remotely close to the level of interactivity and realtime behavior Muut has).
Thanks, Courtney. Indeed, this Muut tab dropped to 132MB for me after loading and expanding all the comments while awaiting your reply—but jumped to 264MB upon hitting Reload. Right, i see a few other scripts using memory, but my browser reports [about:blank](about:blank) uses 22MB and [New Tab](chrome://newtab) uses 28MB, while [blank.org](blank.org) uses 43MB all in separate Incognito tabs. Blog pages i see typically use well less than 100MB, but ballooning memory wasn't my original comment nor question. In daily use, managing work, pages, and concomitant memory take more effort and planning, while load-times pale in significance. I often haven't much choice except to close (and reload later) pages eating lots of memory. That said, if you have experiments charting memory use across browsers with and without Muut, that would make a good article about memory use.
Just for fun I just ran the profiler to find out memory usage taken up by JS both here and on a page with only Muut on it. This page it's about 25MB of memory used by all JS according to the profiler Muut plus other scripts running on this page. On a page with Muut and nothing else I get about 9.5MB. Also just for reference blank.org used 96mb on my browser on initial load. Of course this would definitely drop after a while if I left it open. Sorry I misinterpreted your initial post. Since you were referring to long running tabs, I assumed you were concerned about memory leakage. Regarding Muut's memory footprint in general, one of the benefits of having incredibly concise code for the client library, focusing on text only posts with fewer formatting options, hiding images behind links rather than rendering them, is that Muut will add very little memory overhead in general to a page. Of course if you have a very graphically heavy page like this blog post, it'll use more memory than a mostly text page whether Muut is on it or not. In any case it's always nice to see others concerned about performance (whether it's memory, cpu, or bandwidth impacting it). Far to few people are concerned at all, they benchmark on powerful computers with great connections, hardly indicative of a typical user. We obsess over these things. We even went so far as to build [riot](http://riotjs.com/) which was more in line with this obsession than other tools available. We do have some performance focused blog posts that we've been tossing around, eventually we'll get them out. We need more hours in the day...
Thank you again for your thoughts, Courtney. Yes, performance in general matters but also specifically to me, since i have an older machine running with only 3GB memory. Restoring this page from Closed Tabs and via the back button now consistently uses only 77MB, before i started typing, for what it's worth. I'll keep Muut and its capabilities in mind for strategic communications, and have begun sharing word with friends.
[Testi](//muut.com/u/moot/s1/:moot:rmC9:testi.jpg.jpg) Testing Muut
Is there no way to reply to an individual comment or @someone so they know you're responding to them?
> @Chase Buckner > Is there no way to reply to an individual comment or @someone so they know you're responding to them? Your best bet—in order to both keep the discussion linear, and thus more understandable, as well as to make the post itself clearer, especially taken out of context—is to quote the portion you want to comment. You do that by selecting and clicking "Quote" icon. We are also working on "@someone" mentions feature, though no ETA at the moment.
Hey, I'm in the process of updating my blog. Would it be possible to import all the comments on my Drupal site into your system that I would embed on my new platform?
I'd like to see it in action more
Would be great to have a comparison chart between muut, disqus, googleplus, livefyre, isso, etc.