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.
Ich wäre zunächst an etwas weniger Umfangreichem interessiert: einfach mehrere Discourse-Instanzen zu aggregieren, die alle unter meiner eigenen Kontrolle stehen. Unterschiedliche Sites ermöglichen es, jede auf ein anderes Thema oder eine andere Zielgruppe auszurichten, bringt jedoch einige Nachteile mit sich. Es wäre schön:
- die Benutzermoderation über alle Sites hinweg zu teilen
- Beiträge und Threads verschieben zu können
- gemeinsame Benachrichtigungen zu haben
Das könnte man erreichen, indem man eines der Foren als SSO-Server für die anderen einrichtet.
Ich denke, dass die anderen Punkte ziemlich schwierig umzusetzen wären – ich vermute, es ließe sich zwar über ein Plugin und die API realisieren, aber das würde wahrscheinlich Tausende an Entwicklungskosten verursachen und einen erheblichen Wartungsaufwand bedeuten.
Es stellt sich heraus: „Nein leider nicht.
Ja, sie bleiben eingeloggt. Man müsste irgendwie einen Webhook hinzufügen, um sie aus den verbundenen Foren auszuloggen. Ich denke, das wäre in einem Plugin ziemlich einfach umzusetzen, etwa eine oder zwei Stunden für einen talentierten Entwickler (und etwas länger für mich!)
Passt Fig?
Kennt jemand eine, die unter Windows oder im Webbrowser läuft?
Können Sie bitte präzisieren, was Sie genau benötigen? Ich verstehe Ihre Frage nicht.