Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pleroma
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 156
    • Issues 156
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 23
    • Merge Requests 23
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Pleroma
  • pleroma
  • Merge Requests
  • !264

Merged
Opened Aug 06, 2018 by kaniini@kaniini2 of 2 tasks completed2/2 tasks
  • Report abuse
Report abuse

message relay

This branch introduces an instance-wide actor which boosts public posts. This is used for relaying public posts. The instance-wide actor may also consume other instance's posts, including those of Mastodon relays.

using the message relay

To use the message relay, one simply follows another instance. Pleroma instances will always have the relay at instance.tld/relay. This is done using a mix task:

# MIX_ENV=prod mix relay_follow https://instance.tld/relay

To unfollow another instance:

# MIX_ENV=prod mix relay_unfollow https://instance.tld/relay

You can also use a URI of a Mastodon relay, instead of a Pleroma relay.

disabling the message relay

If you wish for your instance to not act as a relay, you can turn it off by adjusting the :instance configuration context:

config :pleroma, :instance,
  allow_relay: false

testing

The following instances are known to have relay enabled:

  • pleroma.site
  • pleroma.dereferenced.org
  • rabbit.country
  • social.toromino.de

things left to do

  • notifications from the relay shouldn't be delivered to the user
  • boosts from the relay shouldn't be observable

Closes #144 (closed).

Edited Aug 16, 2018 by kaniini

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch https://git.pleroma.social/kaniini/pleroma.git feature/relay
git checkout -b kaniini/pleroma-feature/relay FETCH_HEAD

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout origin/develop
git merge --no-ff kaniini/pleroma-feature/relay

Step 4. Push the result of the merge to GitLab

git push origin develop

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 7
  • Commits 23
  • Pipelines 6
  • Changes 13
Assignee
No assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: pleroma/pleroma!264

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.