2c15820ef6
fixes #65. thanks again for reporting, @nekr0z! |
||
---|---|---|
.circleci | ||
static | ||
templates | ||
tests | ||
.gcloudignore | ||
.gitignore | ||
README.md | ||
activitypub.py | ||
add_webmention.py | ||
app.py | ||
app.yaml | ||
appengine_config.py | ||
common.py | ||
index.yaml | ||
logs.py | ||
models.py | ||
oauth_dropins | ||
redirect.py | ||
render.py | ||
requirements.txt | ||
salmon.py | ||
superfeedr.py | ||
webfinger.py | ||
webmention.py |
README.md
Bridgy Fed
Got an IndieWeb site? Want to interact with federated social networks like Mastodon, Hubzilla, and more? Bridgy Fed is for you.
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
You'll need Python 3. Install the Google Cloud SDK (aka gcloud
) with the gcloud-appengine-python
and gcloud-appengine-python-extras
components. Then, run:
python3 -m venv local3
source local3/bin/activate
pip install -r requirements.txt
Now, run the tests to check that everything is set up ok:
gcloud beta emulators datastore start --no-store-on-disk --consistency=1.0 --host-port=localhost:8089 < /dev/null >& /dev/null &
python3 -m unittest discover
kill %1
Finally, run this in the repo root directory to start the web app locally:
dev_appserver.py --log_level debug --enable_host_checking false --support_datastore_emulator --datastore_emulator_port=8089 --application=bridgy-federated app.yaml
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>
To deploy to the production instance on App Engine - if @snarfed has added you as an owner - run:
gcloud -q beta app deploy --no-cache --project bridgy-federated *.yaml
Compatibility
Here are in progress notes on how I'm testing interoperability with various federated social networks.
ActivityPub
- Mastodon (issue) works! They shipped support in 1.6.
- Hubzilla is getting close!
- Old since lastauth.com is down now:
snarfed@lastauth.com, example post
- Old since lastauth.com is down now:
- distbin
- No explicit accounts, can post anything as anyone
- pump.io
- snarfed@datamost.com
- Tried posting a bunch of ways, couldn't get any to work :/
- Kroeg
- Not open to other users yet. Seems to be running at puckipedia.com/social.
Salmon
- Friendica
- snarfed@libranet.de
- Example post: HTML (alternate link), Atom
- Atom has Salmon link rel,
author.dfrn:handle
is user URI (dfrn is http://purl.org/macgirvin/dfrn/1.0))
- GNU Social (née StatusNet)
- snarfed@quitter.se
- Example post: HTML, Atom
- Atom has no Salmon link rels!
author.name
is username (snarfed)
- Hubzilla
- snarfed@lastauth.com
- Example post: HTML
- Only has Atom
link rel="alternate"
for full feed, not individual post :/ - Atom feed has Salmon link rels inside top level
feed
, not in individualentry
s - Atom entries have
author.name
as username (snarfed)
- Mastodon
- snarfed@mastodon.technology
- Example post: HTML, Atom
- Profile HTML/Atom have Salmon link rel. Individual post HTML/Atom don't.
author.email
is snarfed@mastodon.technology