# Discourse の Federation サポート
**URL:** https://meta.discourse.org/t/federation-support-for-discourse/90921
**Category:** Feature
**Tags:** completed
**Created:** [2018 年 6 月 28 日午前 5:32 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921 "2018-06-28T05:32:10Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@buoyantair](https://meta.discourse.org/u/buoyantair)
#### Post date: [2018 年 6 月 28 日午前 5:32 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/1 "2018-06-28T05:32:10Z")
この機能の主な目的は、Mastodon がグローバルフィードとローカルフィードを活用して健全で分散化された Mastodon インスタンスのネットワークを維持しているように、すべての Discourse コミュニティを相互接続することです。これにより、あるインスタンスのユーザーが別のインスタンスの話題に接続し、フォローし、議論できるようになります。この機能は、Discourse に多くの新たな可能性をもたらす我认为でしょう。
# メリット
- 自分のローカルコミュニティに接続するだけで、他でフォローしている他の Discourse コミュニティの話題に関するニュースを受け取れることを想像してみてください！
- 他の Discourse コミュニティのトピックを購読し、コメントするために、各コミュニティでアカウントを作成する必要がなくなります。
- 構造的にすべてのコミュニティを分散化しながら、同時にすべての人を接続します！
## 留意点
- インスタンス所有者は、他のコミュニティからの特定のユーザーが自コミュニティと相互作用することをブロックする権限を持っています。
- また、コミュニティを非公開にするか、コミュニティのコンテンツを特定のコミュニティグループとのみ共有することを決定する権利も有しています。
この機能のデメリットについてはまだ十分に検討していませんが、皆様のご意見を聞かせてください！
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [2018 年 6 月 28 日午前 5:39 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/2 "2018-06-28T05:39:41Z")
> [@buoyantair](#):
>
> - An instance owner has the ability to block certain people from other communities from interacting with their community.
> - They also have the right to choose the community to be private or that the content of the community can only be shared to a particular group of communities.
> - It structurally decentralizes all the communities while at the same time connecting everyone!
These three aren’t actually a benefit over what Discourse already has today. In fact, it makes the first two harder to do – there’s a lot of trust in the account server operators involved with private sites.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018 年 6 月 28 日午前 6:20 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/3 "2018-06-28T06:20:23Z")
Is there any web-federated system at scale that has actually worked, become popular, and is actively in use? I think this is an inordinately hard problem.
I’m unclear how viable Mastodon is in terms of it being a real competitor to a massively centralized service like Twitter – as I understand it, Mastodon is a Twitter clone, but decentralized?
---
### Author:  [@buoyantair](https://meta.discourse.org/u/buoyantair)
#### Post date: [2018 年 6 月 28 日午前 6:42 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/4 "2018-06-28T06:42:36Z")
> [@codinghorror](#):
>
> I’m unclear how viable Mastodon is in terms of it being a real competitor to a massively centralized service like Twitter – as I understand it, Mastodon is a Twitter clone, but decentralized?
From what I have seen, there are a couple of federated systems like Mastodon and Matrix. These are pretty active places and also have bridges to other platforms (IRC, twitter etc). Mastodon is not really a competitor, it’s main purpose was to provide a decentralized twitter where every community is governed by it’s own rules.
Matrix implements it’s own protocol to make federation system possible, I think Mastodon does the same.
There is a protocol that’s still actively being developed by W3C called “Activity Pub”
> **[ActivityPub](https://www.w3.org/TR/activitypub/)**
>
> The ActivityPub protocol is a decentralized social networking protocol
> based upon the \[ActivityStreams\] 2.0 data format.
> It provides a client to server API for creating, updating and deleting
> content, as well as a federated...
---
### Author:  [@buoyantair](https://meta.discourse.org/u/buoyantair)
#### Post date: [2018 年 6 月 28 日午前 6:54 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/5 "2018-06-28T06:54:34Z")
> [@buoyantair](#):
>
> An instance owner has the ability to block certain people from other communities from interacting with their community.
Oh well this is not a benefit, sorry. I meant that if I owned a discourse instance and other people from other discourse communities are also able to discuss about topics in my community, I am able to define rules on how others interact with my community’s topics. It should be as simple as blocking or banning a user on my instance. But that doesn’t mean that the user is not able to participate in other discourse forums.
> [@buoyantair](#):
>
> They also have the right to choose the community to be private or that the content of the community can only be shared to a particular group of communities.
It’s not a benefit, I agree, this feature is already partially implemented in Discourse (to make it private etc) I guess what can be implemented if a federation exists is the ability to give the owner to choose which communities are allowed and which are not. I haven’t really thought of it.
Hold on let me make some edits 😂
---
### Author:  [@Cameron\_D](https://meta.discourse.org/u/Cameron_D)
#### Post date: [2018 年 6 月 28 日午前 7:08 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/6 "2018-06-28T07:08:17Z")
> [@codinghorror](#):
>
> Is there any web-federated system at scale that has actually worked, become popular, and is actively in use? I think this is an inordinately hard problem.
IRC and email are, I’m pretty sure, the only two that are used outside of an ideological niche.
IRC _was_ properly decentralised very early on, but due to spam, attacks, takeovers, etc. it evolved into a handful of seperate, closed, networks (efnet, freenode, etc.). These days it’s been mostly replaced with fully centralised services.
Likewise, email was completely decentralised but over time (and for similar reasons) it has become very centralised to just a few large providers (i.e. Gmail, Outlook, Yahoo, and sending services like Mailgun and MailChimp). And while running your own mail server is still possible it requires frequent upkeep and configuration to ensure all those large providers keep accepting your mail.
I suppose you could also include BitTorrent and DHT as well, they are decentralised and seem to work fairly well, though it can and has been flooded with fake peers and requests in the past.
As far as I know, new decentralised services like Mastodon and Matrix are yet to run into and deal with those problems (I’m happy to be shown otherwise).
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [2018 年 6 月 28 日午前 7:20 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/7 "2018-06-28T07:20:42Z")
Discussed at length before, allow me (and note these have embedded related topics too, enjoy 🙂 )
> [@Revitalizing the Discourse Hub](https://meta.discourse.org/t/revitalizing-the-discourse-hub/15029):
>
> The original basic idea of the Discourse Hub have a reserved @username across all Discourse instances, so when someone sees @username on any Discourse forum, they’ll know it is (probably) you! … seems like kind of a bad idea in retrospect. Why? Well, if you run your own Discourse, and your name is @david, you probably want to be called @david, even if some other David reserved the name in Feburary 2013 here on meta. It is your community, after all, who are we to tell you that you can’t use y…
> [@What would it take to replace Facebook with Discourse?](https://meta.discourse.org/t/what-would-it-take-to-replace-facebook-with-discourse/84060):
>
> I’m genuinely looking to dump Facebook and I’m sure I’m not alone (!!!) Discourse is clearly a great much better alternative to Facebook & Yahoo Groups. (and others) But how about modifying it to support befriending and personal feeds with associated privacy control? Would this be a total rewrite? Am I totally off here? I guess this might not scale as sign-ups iterated recursively? You could quickly chew up server capacity and have to migrate to bigger and bigger machines? If not Discours…
> [@Tools to "aggregate" many Discourse forums?](https://meta.discourse.org/t/tools-to-aggregate-many-discourse-forums/81899):
>
> The good news: Discourse is popular, perhaps the [fastest-growing](https://trends.builtwith.com/cms/forum-software) forum software out there. The bad news: I now have a ton of Discourse forums that I need to keep tabs on, on a most-daily basis. Does anyone else struggle with this information management challenge? At one point there was a working [Chrome extension called “Discourse Forum Notifications”](https://chrome.google.com/webstore/detail/discourse-forum-notificat/okmkhbdimfnmdhpclfbamachjcpcgcmi) that helped (a little bit), but it was last updated 13 months ago, and doesn’t seem to work any more. And the “official” Android app allo…
[http://opensym.lero.ie/wp-content/uploads/2017/08/a8-silva.pdf](http://opensym.lero.ie/wp-content/uploads/2017/08/a8-silva.pdf)
> **[ActivityPub - one protocol to rule them all? - Sky Schubert](https://overengineer.dev/blog/2018/02/01/activitypub-one-protocol-to-rule-them-all/)**
>
> Random thoughts, articles and projects by a chronic overengineer.
---
### Author:  [@buoyantair](https://meta.discourse.org/u/buoyantair)
#### Post date: [2018 年 6 月 28 日午前 7:36 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/8 "2018-06-28T07:36:35Z")
Awesome! Great addition! I did not even think about Email and IRC! ha! and yes, even torrents are mostly decentralized and peer to peer.
Another good example is the Onion network. It is also pretty much a peer to peer decentralized platform!
---
### Author:  [@thwright](https://meta.discourse.org/u/thwright)
#### Post date: [2018 年 6 月 29 日午後 12:45 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/9 "2018-06-29T12:45:13Z")
Another federation example in the wild is a Nextcloud-style federation for file shares. I’m sure the software’s support could be extended further as well.
> **[Nextcloud Federation - Nextcloud features that put you in control](https://nextcloud.com/features/#federation)**
>
> Collaboration, Security | Discover all of the Nextcloud features for quick reference: AI, online collaboration tools, smart picker, and more!
---
### Author:  [@buoyantair](https://meta.discourse.org/u/buoyantair)
#### Post date: [2018 年 7 月 1 日午後 3:32 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/10 "2018-07-01T15:32:46Z")
I never knew that was actually around! 😮 Seems great!
---
### Author:  [@kephas](https://meta.discourse.org/u/kephas)
#### Post date: [2018 年 7 月 4 日午後 12:14 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/11 "2018-07-04T12:14:50Z")
Email is still self-hosted by tens or hundreds of thousands of companies around the world. Most ISPs provide their own mail server to their users too. So maybe email is less decentralized than before, but it’s in no way become centralized.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018 年 8 月 6 日午前 4:36 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/12 "2018-08-06T04:36:48Z")
> [@codinghorror](#):
>
> I’m unclear how viable Mastodon is in terms of it being a real competitor to a massively centralized service like Twitter – as I understand it, Mastodon is a Twitter clone, but decentralized?
Here is a nice explainer
> **[How Does Mastodon Work? - Kev Quirk](https://kevq.uk/how-does-mastodon-work/)**
>
> I’ve spoken about Mastodon numerous times on this blog. It is the social media platform I use more than any other, but for a new user it can be confusing because it doesn’t work like other social media sites.
I still think this is so intrinsically hard and so difficult to get working at scale that I feel anyone taking this on is falling into [a kind of Xanadu trap](https://blog.codinghorror.com/the-xanadu-dream/) — the more effort you spend traveling toward it, the farther away the goal gets.
---
### Author:  [@Muiren](https://meta.discourse.org/u/Muiren)
#### Post date: [2018 年 10 月 1 日午後 11:59 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/13 "2018-10-01T23:59:03Z")
I beat this drum a long time ago. The point made regarding a plurality of identical names across disparate CDCK Forum instances could be possibly be addressed with an Alias Table. Not a literal SQL Alias Table but a Reference Table of Alias. My actual concern about that is in creating a central repository that just shouts “Come, hack me!” Hence my curiosity about the creation of an Open Source ie FSF Blockchain SSO that possibly works in conjunction with Let’s Encrypt. I’m researching this for use within an envisioned Discourse-based Fediverse exclusive to constituents of the [**APFU|CC** ™](https://apfu.cc), a Federation Union of Worker-Owned Cooperatives.
I am trying to discern the feasibility of creating a [HIPAA](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html)/[NOPP](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/model-notices-privacy-practices/index.html) Compliant Personal Roaming Profile Registry that can eventually pass regulatory muster.
Initial trial use within the aforementioned federated network of [Discourse](https://meta.discourse.org/) forum communities, with a curated suite of like platform applications introduced beginning with [Rocket Chat](https://forums.rocket.chat/), for Slack-like Real-Time Communications complementary to the long-form format of Discourse.
The goal is to use a variant of [participatory action research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2566051/) and [design thinking](https://dschool.stanford.edu/resources-collections/a-virtual-crash-course-in-design-thinking) with stakeholders to programmatically develop this proposed ecosystem, specifically addressing the needs of agnostic portability across a broad spectrum of transactional contexts requiring Authentication, Authorization, and Accounting, with Secure Transport [vis-à-vis](https://www.merriam-webster.com/dictionary/vis-%C3%A0-vis) Diameter-based Protocol, [de rigueur](https://dictionary.cambridge.org/us/dictionary/english/de-rigueur).
On several occasions, the concept of a Blockchain SSO would creep into my thoughts.
That was so long ago that I was certain someone already was doing it, and was proved entirely correct in that assumption on discovering [Civic has a Blockchain SSO](https://www.civic.com/products/secure-identity-platform/) product.
This proposal would require a time-series variant of Postgres DB SQL, [TimescaleDB](https://www.timescale.com/) for example because everything I am doing revolves around mobility in real time.
I would appreciate commentary by any DB Engineers in the Meta-Discourse family about installing Discourse on the TimescaleDB.
Hope that makes sense to you. If not, ask me.
---
### Author:  [@strypey](https://meta.discourse.org/u/strypey)
#### Post date: [2019 年 5 月 11 日午後 4:23 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/14 "2019-05-11T16:23:35Z")
I’d like to +1 the idea of implementing ActivityPub in Discourse. Initially, it could be a plug-in, like the Pterotype plug-in for WordPress, so those Discourse communities who want to experiment with it can do that. The results of those experiments could inform discussions about whether to make it a core feature.
In order to post this comment, I had to set up a new account here and use email or a datafarm (GH, gOgle, Titter etc) to confirm my email address. Even though I’ve been a good citizen on many Discourse forums over the years, I’m treated by this system as a first-time Discourse user (handholding UI, limits on links in comments etc).
Some of the potential benefits of federated Discourse:
- once I have an account on one Discourse forum, that could be my posting identity on any other (unless I want a separation of concerns). I don’t need to create a new account (and profile etc) for every forum I want to post in.
- my posting reputation can be aggregated across all the federated Discourse instances I post in. This is useful information for locals when I start posting on a new instance, whether I’m a good citizen, and bad one, or a vanilla one. It also means each new forum can recognize my Discourse experience level, and If I’m a good lad, I don’t have to start from scratch with posting permissions every time.
- Discourse can use other Discourse instances in the federation as third-party identity providers, instead of advertising corporate datafarms on the login page
@codinghorror
> Is there any web-federated system at scale that has actually worked, become popular, and is actively in use?
There’s a growing number of federated web apps, see the curated lists at fediverse.party. One instance monitoring site has data for nearly 3 million user accounts across all the federated web apps, of which about half were used to post something in the last 6 months, and about 500,000 in the last month. Many others may be lurkers who are reading but not posting.
> **[The Federation - a statistics hub](https://the-federation.info/)**
>
> Node list and statistics for The Federation and Fediverse
So far, most are micro-blogging apps like Mastodon. But there are also apps for video-sharing (PeerTube), photo-sharing (PixelFed), blogs (write.as, Plume, and the Pterotype plug-in for WordPress), events (Mobilizon), pastebin (Distbin), and more. Thanks to standards like ActivityPub (also the Diaspora protocols and Zot), not only do they all federate within instances of their own software, but they can also federate with instances of other software using the same federation standards.
If anyone is interested in working on an AP plug-in for Discourse and looking for guidance, there is a Discourse forum at socialhub.network where developers from different projects compare notes about implementations, discuss ways to improve inter-operation and UX across instances and apps, and share related news.
---
### Author:  [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [2019 年 5 月 15 日午後 7:14 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/15 "2019-05-15T19:14:20Z")
It must be noted that Discourse ActivityPub development is going to be supported by the NGI0 EU funding scheme. There’s a related topic at [ActivityPub Implementation for Discourse](https://meta.discourse.org/t/activitypub-implementation-for-discourse/107263) that should be reopened for interested people since nothing is sure yet about how this will play.
I would be very glad to open a dedicated space to discuss this plugin development on [https://socialhub.network](https://socialhub.network).
---
### Author:  [@simevo](https://meta.discourse.org/u/simevo)
#### Post date: [2019 年 8 月 5 日午後 3:24 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/16 "2019-08-05T15:24:48Z")
Discourseでのフェデレーション有効化に+1。最初のステップは、以下の通りWebFingerプロトコルのサポートです：
> **[How to implement a basic ActivityPub server](https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/)**
>
> Today we’ll be looking at how to connect the protocols powering Mastodon in the simplest way possible to enter the federated network. We will use static files, standard command-line tools, and some simple Ruby scripting, although the functionality...
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [2019 年 8 月 6 日午後 2:11 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/17 "2019-08-06T14:11:12Z")
非常に興味深いですね。どこまで進んでいるのでしょうか？
機能仕様書はありますか？私には、これはユーザーエクスペリエンスから始まり、そこから技術へと掘り下げる必要があるように思えます。
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [2019 年 8 月 6 日午後 2:16 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/18 "2019-08-06T14:16:57Z")
Discourse アプリによってこの問題の一部が解決されていると言えないでしょうか？
これは通知レベルでのアグリゲーターであり、複数の Discourse サイトへの接続や認証情報を保持します。
実際の解決策は、Discourse アプリを強化してフィードを表示できるようにすることではないかと考えられます。
もう一つ注目すべき点は、スマートなメールフォルダが同様のフィードを提供する可能性があるということです。
もしかすると、私は全く的外れなのかもしれませんが…
---
### Author:  [@frandavid100](https://meta.discourse.org/u/frandavid100)
#### Post date: [2019 年 8 月 25 日午後 5:49 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/20 "2019-08-25T17:49:52Z")
Discourse でフェデレーションのサポートを導入していただければとても嬉しいです。特に、@angus 氏が作成した以下のプラグインを見た後ではなおさらです。
> [@Discourse Follow](https://meta.discourse.org/t/follow-plugin/110579):
>
> IMPORTANT WARNING: This plugin may affect whether laws that regulate social media apply to your forum. Consult legal for advice. discourse2Summary Discourse Follow allows users to follow other users, list the latest topics involving them, and receive notifications when they post.hammer_and_wrenchRepository Link [https://github.com/discourse/discourse-follow](https://github.com/discourse/discourse-follow)open_bookInstall Guide [How to install plugins in Discourse](https://meta.discourse.org/t/install-plugins-in-discourse/19157)Screenshots Followed users posts feed:
[meta.discourse.org](http://meta.discourse.org) にアクセスして Socialhub の通知を確認したり、フォローしている Socialhub ユーザーの新しい投稿一覧を取得したり、ブックマークした Socialhub カテゴリをここで直接表示したりできるようになったら素晴らしいでしょう。
---
### Author:  [@rishabh](https://meta.discourse.org/u/rishabh)
#### Post date: [2019 年 8 月 26 日午前 10:11 UTC](https://meta.discourse.org/t/federation-support-for-discourse/90921/21 "2019-08-26T10:11:42Z")
> [@hellekin](#):
>
> 関連トピックに [Discourse 向け ActivityPub 実装](https://meta.discourse.org/t/activitypub-implementation-for-discourse/107263) があります。今後の展開がまだ不確かなため、興味のある人のためにこのトピックを再オープンすべきでしょう。
そのトピックを再オープンする前に、コミュニティで誰かが着手できる機能的な仕様をここで決定すべきだと考えます。
「Discourse 向け ActivityPub 実装」という用語は非常に広範であるため、チームはこの取り組みをシンプルに保ち、小さく始めるべきだと強く考えています。
* * *
@Falco 氏がこの方向性について興味深い提案をされていました。ご意見はいかがでしょうか？
> [@Falco](#):
>
> ### 提案
>
> Discourse における ActivityPub の実装に関する私の提案は、Feediverse と複数の Discourse インスタンスを活用して、Facebook のフィードを再現する方法を構築することです。
>
> 基本的な Facebook フィードは以下の要素で構成されます：
>
> 1. 友人が自分の壁に投稿すること
> 2. 見知らぬ人々が自分のグループに投稿すること
>
> 現在、Mastodon（または他の OStatus/ActivityPub 対応のマイクロブログプラットフォーム）では 1 のみに対応しています。では、2 を非常にうまく行うのは何でしょうか？:discourse: です！
>
> そこで私の提案は、ユーザーが利用している Discourse インスタンスから複数の ActivityPub フィードを追加できるようにすることです。例えば私自身の場合：
>
> - Meta
> - PiHole
> - Age of Empires Forums
> - Overwatch Forums
>
> これらのフィードから投稿（最新または人気順）を Mastodon のソーシャルフィードに **交互に** 表示させるものです。
>
> 高解像度のモックアップをご覧ください：
>
> 
>
> 投稿やトピックを追加する場合、長さやコンテキストの扱いについては読者にお任せする課題とします。
[次のページ](https://meta.discourse.org/t/federation-support-for-discourse/90921.md?page=2)