doesnm/ligh7hau5
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A Matrix (https://matrix.org/docs/spec/) to Fediverse / ActivityPub client / bridge. Also, some media proxying.
8 commits 4 branches 11 tags 326 KiB
JavaScript 100%
Find a file
dependabot[bot] c8853eb273
chore(deps): bump eslint-utils from 1.3.1 to 1.4.2 
Bumps [eslint-utils](https://github.com/mysticatea/eslint-utils) from 1.3.1 to 1.4.2.
- [Release notes](https://github.com/mysticatea/eslint-utils/releases)
- [Commits](https://github.com/mysticatea/eslint-utils/compare/v1.3.1...v1.4.2)

Signed-off-by: dependabot[bot] <support@github.com>
2019-09-04 13:23:42 +00:00
commands fix(cmd): typo in response 2019-07-07 17:36:51 -04:00
.gitignore Initial commit 2019-07-03 13:35:09 -04:00
config.js release 0.1.0 2019-07-03 17:27:39 -04:00
LICENSE Initial commit 2019-07-03 13:35:09 -04:00
main.js fix(cmd): missing param 2019-07-06 13:46:28 -04:00
notification.json release 0.1.0 2019-07-03 17:27:39 -04:00
package.json release 0.1.0 2019-07-03 17:27:39 -04:00
README.md refactor: readme styling 2019-07-04 19:59:08 -04:00
registrar.js release 0.1.0 2019-07-03 17:27:39 -04:00
timeline.json release 0.1.0 2019-07-03 17:27:39 -04:00
yarn.lock chore(deps): bump eslint-utils from 1.3.1 to 1.4.2 2019-09-04 13:23:42 +00:00

README.md

Plemara

Plemara acts as a Matrix bridge to the Fediverse. This application should allow you to do most actions on the Fediverse including livefeed, posting, subscribing, etc. via Matrix. Configuration for the app can be found in config.js. You will need to provide a Matrix username and password for the bridge to work, this can be done through an account made on @matrix.org, or your own homeserver. For the Fediverse side, you will need an access_token, this can be created through the CURL steps below. You would replace fediverse.site with where you would like to run the bridge from.

Installation

  1. git clone https://github.com/vulet/plemara
  2. cd plemara && yarn install
  3. node main.js

Generating an access_token

  1. curl -X POST -d "client_name=<NAME HERE>&redirect_uris=urn:ietf:wg:oauth:2.0:oob&scopes=write follow read&website=http://fediverse.site" https://fediverse.site/api/v1/apps

Result:

{"client_id":"result",
"client_secret":"result",
"id":"result",
"name":"result",
"redirect_uri":"urn:ietf:wg:oauth:2.0:oob",
"website":"http://fediverse.site",
"vapid_key":"vapid_key"}
  1. curl -X POST -d "client_id=sekret&client_secret=sekret&scope=write follow read&grant_type=password&username=sekret@email.com&password=sekret" https://fediverse.site/oauth/token

Result:

{"token_type":"Bearer",
"scope":"write read",
"me":"https://fediverse.site/users/<your username>",
"access_token":"result"}

The access_token from the above command is then stored in the config.js file.

Images

Bridge