gitwtfhub

wtf is gotify-webhook-misskey?

eternal-flame-ad/gotify-webhook-misskey — explained in plain English

Analysis updated 2026-07-27 · repo last pushed 2024-11-15

1GoAudience · ops devopsComplexity · 2/5StaleSetup · moderate

TL;DR

A bridge tool that listens for webhook notifications from Misskey social servers and forwards them to a self-hosted Gotify push notification server, letting you see all social alerts in one unified place.

Mindmap

mindmap
  root((repo))
    What it does
      Listens for Misskey webhooks
      Forwards to Gotify
      Formats notifications
      Includes click-through links
    Setup
      Short config file
      Add Misskey secrets
      Point webhooks at bridge
    Use cases
      Multi-account notifications
      Custom priority per instance
      Centralized alert feed
    Limitations
      Alpha stage project
      Upstream Misskey bugs
      Reaction patches needed
    Audience
      Self-hosters
      Misskey users
      Gotify owners

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Get push notifications on your phone when someone mentions or follows you on Misskey.

REASON 2

Manage multiple Misskey accounts and funnel all alerts into one Gotify feed.

REASON 3

Set different urgency levels so notifications from one server appear more important than another.

What's in the stack?

Go

How it stacks up

eternal-flame-ad/gotify-webhook-misskeyadvayc/wrappedaegrail/aegrail-engine
Stars111
LanguageGoGoGo
Last pushed2024-11-15
MaintenanceStale
Setup difficultymoderateeasyhard
Complexity2/52/55/5
Audienceops devopsgeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires a running Gotify server and manual webhook configuration in each Misskey account's settings.

No license information was provided in the repository explanation.

Wtf does this do

gotify-webhook-misskey is a small bridge tool that takes notifications from Misskey (a decentralized social network) and sends them to Gotify (a self-hosted push notification server). It's useful for people who want to see Misskey alerts in their regular notification stream instead of using a web app or keeping multiple browser tabs open for different accounts. Misskey can send webhooks when events happen, like when someone replies to you, mentions you, follows you, or shares your post. This tool acts as a listener for those webhooks, formats the information into Gotify-style notifications, and passes them along. You set up a short configuration file listing your Misskey instances with their secrets and priority levels, then point each Misskey account's webhook settings at this bridge. The click-through URLs in the notifications are also wired up so you can jump directly to the relevant post or user profile. This would appeal to someone running their own Gotify server who is active on one or more Misskey instances and wants all their social notifications funneled into one place. For example, if you manage accounts on two different servers, you could set different priority levels so notifications from one instance appear more urgent than the other in your Gotify feed. The project is described as alpha-stage, and the README notes some upstream bugs in Misskey related to reaction notifications that require a server-side patch to fix. There's also a mention of incorrect webhook payload formatting before a certain Misskey version. These are issues on the Misskey side rather than with this bridge itself, but they mean some features may not work perfectly until the upstream platform addresses them.

Yoink these prompts

Prompt 1
Help me write a config file for gotify-webhook-misskey with two Misskey instances, one with high priority and one with low priority.
Prompt 2
How do I configure a Misskey webhook to point at my gotify-webhook-misskey bridge so I get reply and follow notifications in Gotify?
Prompt 3
What Misskey server version do I need for gotify-webhook-misskey to work correctly, and how do I patch the reaction notification bug mentioned in the README?

Frequently asked questions

wtf is gotify-webhook-misskey?

A bridge tool that listens for webhook notifications from Misskey social servers and forwards them to a self-hosted Gotify push notification server, letting you see all social alerts in one unified place.

What language is gotify-webhook-misskey written in?

Mainly Go. The stack also includes Go.

Is gotify-webhook-misskey actively maintained?

Stale — no commits in 1-2 years (last push 2024-11-15).

What license does gotify-webhook-misskey use?

No license information was provided in the repository explanation.

How hard is gotify-webhook-misskey to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is gotify-webhook-misskey for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.