From IndieWeb
(Redirected from GitHub Pages)
Jump to: navigation, search

GitHub is a specialized content hosting silo for code, issues, comments, and static content that has some aspects of a commons, and through free domain mapping, a content hosting service as well.

  • See github-pages for how to setup a static Github pages site!


  • star a repo: serves as a personal bookmark and ranking the popularity of the repo
  • watch a repo: receive notifications of updates to the repo
  • issue posts
  • . . .

POSSE to GitHub

For POSSEing source code to github, see git.

While git is inherently distributed, all the extra functionality (issues, pull requests, etc.) that GitHub adds on top is not. GitHub has a nice API for interacting with repositories, which makes it pretty easy to POSSE issues, comments on issues, stars, and maybe more.

POSSE note to GitHub

Plain text notes can be POSSEd to GitHub as a gist.

No known examples of anyone doing this yet.

Be the first and add your permalinks here!

POSSE an issue

An issue post that is in reply to a particular GitHub repo can (and should) be POSSEd to GitHub as a new issue on that GitHub repo.

See examples of POSSEing issues to GitHub:

POSSE reply to repo

A reply to a GitHub repo path, may make sense to be POSSEd as a comment on that path, e.g. if it is a gist. If the reply is an issue, see above POSSE an issue.

POSSE reply to issue

A reply to a specific GitHub issue can (and should) be POSSEd as a new comment on that issue.

POSSE star of repo

A star on a GitHub repo can (and should) be POSSEd as a like of the repo.


If you POSSE to GitHub in any of the above ways, you should backfeed any replies on your post's GitHub POSSE copy back to your own post so that you can:

  • keep a copy of people's comments on your post
  • view follow-ups to your post on your post, instead of having to visit GitHub's site
  • reply to follow-ups to your post, from your site, instead of using GitHub's UI

IndieWeb Examples

Aaron Parecki

Aaron Parecki is manually POSSEing comments on GitHub issues from his own site to GitHub. E.g.:

Colin Tedford

Colin Tedford manually POSSEs Github issues, and manually POSSEs and backfeeds comments on GitHub issues (it's just occasional bug reports, so not as onerous as it might be if he were a developer).

Chris Aldrich

Chris Aldrich is occasionally automatically POSSEing comments on GitHub issues from his Known site to GitHub. E.g.:

He does this with the Known plugin to POSSE to GitHub.

Bridgy Publish

Bridgy supports POSSEing issues, issue/PR comments, and stars to GitHub!

Bridgy Backfeed

There is no current support in Bridgy to backfeed responses to your GitHub POSSE copies back to your original posts. Feature request:


Known has a plugin for automatic POSSEing to GitHub:


  • supports creating issues, commenting on issues and pull requests, and starring repositories since 2016-04-22

Porting to the IndieWeb

Example github activity Atom feed whereby you can export or PESOS your activities from:

If you want a feed of activity by others on your repositories, it looks like you can get it through your "Personal News Feed". "Your personal News Feed shows activity—other than your own!—on repositories you watch. […] To subscribe to your personal News Feed in your favorite RSS reader, click Subscribe to News Feed under your list of repositories."

Self-hosted alternatives

Main article: git#Software

There are some self-hosted alternatives to GitHub. Gitlab and Gogs support issue tracking and project management as well.

  • GitLab: full-featured GitHub replacement
  • Gogs: full-featured GitHub replacement
  • Gitolite: web interface for managing repositories, with fine-grained access controls
  • Gitweb: simple web interface for browsing git repositories
  • Formerly Gitorious (acquired by GitLab in March 2015)
  • Formerly Gitosis (deprecated long ago in favor of gitolite)


Account reuse is potential security issue

2018-02-07 GitHub allows account deletion, recreation by another party, with library dependency:


DMCA harassment

You can lose your data due to unjustified DMCA takedowns:

DDoS collateral damage

Github is sometimes the target of DDoS attacks, apparently targeted at specific projects. While GitHub seems to be handling the attacks in such a way as to keep access working, this is a vulnerability of any centralized service, that it attracts attacks unrelated to your use of it, that jeopardize your use of it (collateral damage). Most recent first

  • 2015-03-26 DDoS attack [1] via unsuspecting browsers executing scripts from (MitM) faked Baidu requests[2].

March 2017 Terms of Service Update

In March 2017, GitHub updated their terms of service. Several people are upset about the change, which may affect GPL and similarly licensed software.


Occassionally GitHub fails to handle requests:


No server is currently available to service your request.

Sorry about that. Please try refreshing and contact us if the problem persists.

See Also