federation

From IndieWeb
(Redirected from fediverse)

federation in the context of the IndieWeb refers to services and features that work directly between IndieWeb sites peer-to-peer, without having to setup or create accounts in both places, without a centralized service or silo bottleneck, with perhaps the exceptions of both DNS and Bridgy Fed, the latter an open source ActivityPub proxy many use to federate with Mastodon.

Related terms:

Why

You should support federation on your site so you can:

  • Use your site to mention people on other sites and respond to their posts
  • Show mentions and responses from other sites to your posts, on your site
  • Allow other sites to subscribe to (follow) your site, preferably in realtime
  • Subscribe to (follow) other sites from your site

How to

To support federation on the IndieWeb, support the following:

How to federate posts and responses

You (and your site) get federation benefits from implementing each of these smaller steps, so see the following for the specific how to instructions:

  1. h-entry markup on your posts
  2. Webmention sending
  3. Webmention receiving
  4. h-entry consuming

How to federate mentions

Federating mentions is a special somewhat simpler case of federating posts, except using home page URLs rather than post permalinks:

  1. To notify others when you mention them
  2. To receive notifications when others mention you

How to federate following

There are incremental following federation benefits to each of these smaller steps, and thus you should implement them as described:

  1. h-feed markup on your primary (composite) stream of updates (like on your homepage), and other streams
    • Allows people to find all the posts on your home page or other stream pages
    • Implement: How to publish h-feed
  2. Publish notifications with WebSub
  3. Follow and subscribe via WebSub
  4. h-feed consuming

Social Media

From a social media user perspective, federating across social media sites means two people can post, see each others posts, and respond to each other, each using a different site or service, each without having to use or setup the other site or service.

Contrast this with say two silos like Facebook and Twitter, where if you want to post something so that it is seen by users of the other service, you have to create an account on that other service, set it up to automatically receive your posts, and even then responses will not federate back to whichever service you posted on.

Discussion

DNS Exception

DNS Exception: In the context of the IndieWeb, and the web in general, the hierarchicial architecture of DNS is accepted as an exception to the abovementioned federation requirement of no centralized bottlenecks. That being said, there are ongoing efforts to figure out how to replace DNS with a peer-to-peer system.

IndieWeb Focus

Focus: for day-to-day practical purposes, the IndieWeb community is not working on addressing the DNS centralization issue/exception and is instead focusing on design (UI/UX) of how user-level features can and should federate.

Protocols and formats

A protocol or format can be said to support federation if it can be supported by multiple sites+ with multiple implementations++, to interact directly with each other without the use of any third party sites, or centralized bottlenecks.

  • +multiple sites because one site only is a silo
  • ++multiple implementations* because one implementation only is a monoculture, based on (evolving) code, not a dependable protocol or format (when in conflict, the single codebase wins over any spec).

Examples:

Additional protocols

Federation projects

Projects that implement one or more additional federation protocols:

History

There have been many attempts and limited deployments of various social web federated systems using various protocols and formats.

Pingback and h-entry

In the IndieWeb in particular, the first federated comment thread was built using:

See:

This first IndieWeb federation test demonstrated:

  • federated mentions in the original post to others's IndieWeb homepages
  • federated comments from the people mentioned and others's sites

Webmention itself had barely been started on a github repo and wiki page, these are the latest versions as of 2013-04-19:

OStatus

Main article: OStatus

(stub section)

Does anyone have any (Internet Archive) links to the first federated OStatus posts and a cross-site thread? Presumably from circa 2010 (or earlier?)

XMPP

Main article: XMPP

As a non-web attempt at Federation, XMPP is worth looking at to see how it addressed all the challenges with federating across disparate systems.

Email

Email is often held up historically as a successful federated system.

There are many barriers that are not only preventing more decentralization in email, but ironically incentivizing and causing more centralization in a handful of large servers/services such as Gmail.

There is so much server specific configuration / setup that is needed to get your message accepted by other servers that email in practice is becoming a less-than-fully-federated system. Like if you have to contact help@ some domain (Gmail, Yahoo, etc.) to get them to configure their mail servers to accept mail from your server, then it's become a step down from the full sense of "federation" that email launched and became popular with.

There has been some anecdotal reports of the increasing difficulty to setup any form of usable mail server. Peter Molnar runs his own server, and yet found difficulty (e.g. with messages making it to their destinations) just with switching it from its existing well established domain name to a new domain name.

Articles

Articles and blog posts about federation, federated social networks, and the fediverse.

Criticism

See Also

Retrieved from "https://indieweb.org/wiki/index.php?title=federation&oldid=89910"