Facebook Censored Me for Mentioning Open-Source Social Network Mastodon

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • PopRuby - Clothing and Accessories for Ruby Developers
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • Mastodon

    Your self-hosted, globally interconnected microblogging community

    They block https://joinmastodon.org but not, say, https://mastodon.social - so probably it's not a part of a strategy.

  • hometown

    A supported fork of Mastodon that provides local posting and a wider range of content types.

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

  • PopRuby

    PopRuby: Clothing and Accessories for Ruby Developers. Fashion meets Ruby! Shop our fun Ruby-inspired apparel and accessories designed to celebrate the joy and diversity of the Ruby community.

  • Socialhome

    A federated social home

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

  • Misskey

    🌎 An interplanetary microblogging platform 🚀

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

  • gotosocial

    Fast, fun, small ActivityPub server.

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

  • PixelFed

    Photo Sharing. For Everyone.

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

  • PeerTube

    ActivityPub-federated video streaming platform using P2P directly in your web browser

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  • Friendica

    Friendica Communications Platform

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

  • diaspora*

    A privacy-aware, distributed, open source social network.

    * in case of a mute, it could also be not wanting their federated timeline to be flooded with primarily mastodon.social posts

    Lack of federation between these instances and mastodon.social could be a reason not to pick mastodon.social. (Similar situation applies to mastodon.online btw, which is a spin-off server of m.s.)

    Another reason to pick a different instance could be not wanting to use mainline Mastodon software. For example because you want to run your own instance on limited hardware (Mastodon can get a bit resource intensive), don't like Ruby, miss certain features, don't like the front-end (though alternative external front-ends to Mastodon do exist), or some other reason.

    Personally I am on an instance that runs [Mastodon Glitch Edition, also known as Glitch-Soc](https://glitch-soc.github.io/docs/), which is a compatible fork of Mastodon which implements a bunch of nice features such as increased post character count (Mastodon defaults to 500 characters per post, Glitch-Soc supports increasing this in the server settings), Markdown support (though only instances that also support HTML-formatted posts will see your formatting; mainline Mastodon servers will serve a stripped down version of your post instead), and improved support for filters / content warnings / toot collapsing, optional warnings when posting uncaptioned media, and other additional features.

    Another alternative Mastodon fork is [Hometown](https://github.com/hometown-fork/hometown) which focuses more on the local timeline (showing posts only from your own instance) with the addition of local-only posts, to nurture a tighter knit community.

    Aside from Mastodon there are other implementations of ActivityPub which can still federate with Mastodon instances, such as [Misskey](https://github.com/misskey-dev/misskey), [diaspora*](https://diasporafoundation.org/) (which AFAIK inspired Google Plus back in the day), [Hubzilla](https://hubzilla.org//page/hubzilla/hubzilla-project), [Peertube](https://joinpeertube.org/) (focused on peer-to-peer video distribution), [Friendica](https://friendi.ca/), [Pleroma](https://pleroma.social/), [Socialhome](https://socialhome.network/), [GoToSocial](https://github.com/superseriousbusiness/gotosocial), [Pixelfed](https://pixelfed.org/) (which started as a sort of federated Instagram alternative) and more. [Fediverse.party](https://fediverse.party/) is a nice way to discover various protocols that make up the bigger Fediverse.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts