The best way - he had already identified the need and wrote it a while ago 
「いいね！」 5
HI @tobiaseigen, long time indeed. The response I got to offcourse suggested there wasn’t much demand for it and I abandoned it. I’ve also drifted away from discourse (and ember).
Might need to get back into it soon though. I’m working on a real estate project now called PropertyWebBuilder and I could do with having a forum for it.
Will send you a PM.
「いいね！」 3
I completely concur with your vision.
I’ve just killed a project that attempted to migrate users off of a Facebook Group.
I failed.
Despite offering them a superior set of Discourse functionality, including bespoke plugins I had written to provide really rich domain functionality that blew a hole in Zucks side the one feature I could not compete with was the ability to show an aggregation of all the interest groups they were subscribed to.
“We loved your website, Robert, but it was just more convenient to scroll down Facebook” 
If we had a single web page and web app that could show a feed of all your many Discourse site accounts now that would be just great.
Perhaps an RSS reader would suffice. Has anyone tried this? But ultimately you need a way to access with your individual accounts in the way the (excellent) iOS app does.
「いいね！」 4
This is conceptually great, but why was it written in React? If you build a tool for a big population of Discourse users, many of whom may be actively contributing plugins and Theme Components based on Ember, wouldn’t it be a good idea to write the app using Ember to help secure future support from the community?
It is a false dichotomy though, an alternate directory would still exist outside Facebook so nobody would go there. The only answer is incredibly compelling unique content, same as it ever was.
「いいね！」 2
But I’m using your team’s wonderful app all the time, and all it’s missing is a feed 
「いいね！」 2
I wrote a proposal to tackle this exact problem: mix in many different Discourse activity in a central and social user feed.
You can follow your peers in Mastodon and add your “groups” (Discourse instances that you care about, like one about a game you like, one about your ioio hobby, etc) to be interleaved in your forum.
We can also do the same by making a robust Facebook / Twitter integration, that periodically picks a random topic/post from /top and puts it on social media. This is all possible already, but not easy for non-technical people.
「いいね！」 9
I follow many Discourse forums with my feed reader.
What I do is scrap the HTML and convert it to a feed.
Got it nailed pretty well by now, not only for Discourse, but for any other site.
This way, no need for the blackbox algorithms, it is all under my control.
「いいね！」 2
まずは、少し範囲を絞ったものから始めたいですね：自分自身で管理している複数の Discourse インスタンスを単に集約することです。別々のサイトを持つことで、それぞれを異なるトピックや対象者に特化させることができますが、いくつかの欠点もあります。以下のような機能ができれば嬉しいです：
- サイト間でユーザーのモデレーションを共有する
- ポストやスレッドを移動できる
- 共通の通知を受け取る
「いいね！」 1
これは、他のフォーラムの SSO サーバーとして 1 つのフォーラムを設定することで実現できます。
他の機能については、かなり難しいと思います。プラグインと API を通じて実装できないこともないでしょうが、開発コストが数千ドル規模になり、維持にも相当な手間がかかるでしょう。
残念ながら「不可能」でした。SSO 側でユーザーの SSO アカウントを無効化しても、すでにログインしている場合は投稿を禁止できないことを、痛い目を見て学びました。
はい、ログイン状態は維持されます。関連するフォーラムからログアウトさせるには、何らかの方法でウェブフックを追加する必要があります。これはプラグインで比較的簡単に実装できると思います。有能な開発者なら 1〜2 時間、私ならもう少しかかるかもしれませんが！
「いいね！」 1
Figは条件に合致しますか？
Windows やウェブブラウザで動作するものをご存じの方はいらっしゃいますか？
何を求めているのか詳しく教えていただけますか？どのようなご質問か理解できません。
「いいね！」 4