eternal-flame-ad/gotify-webhook-misskey — explained in plain English
Analysis updated 2026-07-27 · repo last pushed 2024-11-15
Get push notifications on your phone when someone mentions or follows you on Misskey.
Manage multiple Misskey accounts and funnel all alerts into one Gotify feed.
Set different urgency levels so notifications from one server appear more important than another.
| eternal-flame-ad/gotify-webhook-misskey | advayc/wrapped | aegrail/aegrail-engine | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Go | Go | Go |
| Last pushed | 2024-11-15 | — | — |
| Maintenance | Stale | — | — |
| Setup difficulty | moderate | easy | hard |
| Complexity | 2/5 | 2/5 | 5/5 |
| Audience | ops devops | general | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires a running Gotify server and manual webhook configuration in each Misskey account's settings.
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.
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.
Mainly Go. The stack also includes Go.
Stale — no commits in 1-2 years (last push 2024-11-15).
No license information was provided in the repository explanation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.