The best way - he had already identified the need and wrote it a while ago ![]()
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.
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.
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.
But I’m using your team’s wonderful app all the time, and all it’s missing is a feed 
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.
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.
我最初想找一个稍微不那么宏大的方案:只是聚合几个由我完全控制的 Discourse 实例。虽然独立的站点可以让每个站点专注于不同的主题或受众,但也存在一些缺点。如果能实现以下功能就太好了:
- 跨站点共享用户管理权限
- 能够移动帖子和话题
- 拥有共享的通知系统
这一项可以通过将其中一个论坛设置为其他论坛的 SSO 服务器来实现。
我认为其他功能实现起来会相当困难——我猜可以通过插件和 API 来实现,但这听起来需要数千美元的开发成本,并且后续维护也需要不少投入。
事实证明“不行”。我通过惨痛的教训发现,在 SSO 端禁用用户的 SSO 账户并不会阻止其登录后的发帖行为。
没错,他们会保持登录状态。你需要通过某种方式添加一个 webhook,将他们从关联论坛中注销。我认为这在插件中实现起来相当容易,对于有才华的开发者来说大概需要一两个小时(对我来说可能要多一点!)
Fig 符合需求吗?
有人知道有能在 Windows 或网页浏览器上运行的吗?
您能澄清一下您在问什么吗?我不明白您的意思。