Got an IndieWeb site? Want to interact with federated social networks like Mastodon, Hubzilla, and more? Bridgy Fed is for you.
 
 
 
 
Go to file
Ryan Barrett 76686af538
cache lots of GET requests
this helps with requests that make external HTTP fetches, eg indieweb home pages/posts and federated profiles/posts, which change rarely.

in particular, outbound AP requests that get federated widely (eg Mastodon) result in all of those federated instances making the same bridgy fed requests at the same time, often within just a few seconds. more background: tootsuite/mastodon#4486
2019-04-16 11:05:18 -07:00
.circleci
static convert AP mentions to home page webmentions 2019-04-16 10:46:40 -07:00
templates
tests convert AP mentions to home page webmentions 2019-04-16 10:46:40 -07:00
.gitignore
README.md
activitypub.py cache lots of GET requests 2019-04-16 11:05:18 -07:00
add_webmention.py cache lots of GET requests 2019-04-16 11:05:18 -07:00
app.yaml
appengine_config.py
common.py convert AP mentions to home page webmentions 2019-04-16 10:46:40 -07:00
logs.py
models.py
redirect.py cache lots of GET requests 2019-04-16 11:05:18 -07:00
render.py cache lots of GET requests 2019-04-16 11:05:18 -07:00
requirements.freeze.txt
requirements.txt
salmon.py
superfeedr.py
webfinger.py cache lots of GET requests 2019-04-16 11:05:18 -07:00
webmention.py

README.md

Bridgy Fed Circle CI Coverage Status

Got an IndieWeb site? Want to interact with federated social networks like Mastodon, Hubzilla, and more? Bridgy Fed is for you.

https://fed.brid.gy/

Bridgy Fed connects the IndieWeb with federated social networks using ActivityPub and OStatus. Original design docs:

License: This project is placed in the public domain.

Development

First, install the Google Cloud SDK (aka gcloud) with the gcloud-appengine-python and gcloud-appengine-python-extras components.

Once you've done that, run this to find the App Engine libraries directory:

STATE instead use Installation Root: [/usr/local/Caskroom/google-cloud-sdk/latest/google-cloud-sdk]
gcloud info | grep -o -E '/[^:]+google_appengine'

(If that doesn't output anything, try just gcloud info, look in the Python PATH section, and try to find the App Engine directory.)

Add that directory to your $PYTHONPATH, e.g. export PYTHONPATH=$PYTHONPATH:/opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/platform/google_appengine. Then, run:

virtualenv local
source local/bin/activate
pip install -r requirements.txt
python -m unittest discover

The last command runs the unit tests. If you send a pull request, please include (or update) a test for the new functionality!

If you hit an error during setup, check out the oauth-dropins Troubleshooting/FAQ section. For searchability, here are a handful of error messages that have solutions there:

bash: ./bin/easy_install: ...bad interpreter: No such file or directory

ImportError: cannot import name certs

ImportError: No module named dev_appserver

ImportError: cannot import name tweepy

File ".../site-packages/tweepy/auth.py", line 68, in _get_request_token
  raise TweepError(e)
TweepError: must be _socket.socket, not socket

error: option --home not recognized

You may need to change granary, oauth-dropins, webmention-tools, mf2util, or other dependencies as well as as Bridgy Fed. To do that, clone their repo locally, then install them in "source" mode with e.g.:

pip uninstall -y granary
pip install -e <path to granary>
ln -s <path to granary>/granary \
  local/lib/python2.7/site-packages/granary

The symlinks are necessary because App Engine's vendor module evidently doesn't follow .egg-link or .pth files. :/

To deploy to the production instance on App Engine - if @snarfed has added you as an owner - run:

gcloud -q app deploy --project bridgy-federated *.yaml

Compatibility

Here are in progress notes on how I'm testing interoperability with various federated social networks.

ActivityPub

Salmon