Skip to content
Snippets Groups Projects

Don't depend on launcher.moe for status assets

What does this PR do? (Please give us a brief description of what this PR does.)

Every Sharkey instance that hasn't changed the status images to custom ones, depends on launcher.moe. That not only spams launcher.moe, but also creates a dependency to a centralized domain that can be easily avoided. If launcher.moe goes down, these instances won't be able to display a status image; if launcher.moe gets hijacked, these instances will serve the hijacked images etc. (Similarly Misskey depends on https://xn--931a.moe/)

Is there another reason for this that I'm missing? Otherwise this MR points the status images to local copies.

Contribution Guidelines By submitting this merge request, you agree to follow our Contribution Guidelines

  • I agree to follow this project's Contribution Guidelines
  • I have made sure to test this pull request
Edited by Evangelos Paterakis

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
Please register or sign in to reply
Loading