dakkar
421f8d49e5
Since notifications are stored in Redis, we can't expect relational integrity: deleting a user will *not* delete notifications that mention it. But if we return notifications with missing bits (a `follow` without a `user`, for example), the frontend will get very confused and throw an exception while trying to render them. This change makes sure we never expose those broken notifications. For uniformity, I've applied the same logic to notes and roles mentioned in notifications, even if nobody reported breakage in those cases. Tested by creating a few types of notifications with a `notifierId`, then deleting their user.
✨ Features
- ActivityPub support
Not on Sharkey? No problem! Not only can Sharkey instances talk to each other, but you can make friends with people on other networks like Mastodon and Pixelfed! - Federated Backgrounds and Music status
You can add a background to your profile as well as a music status via ListenBrainz, show everyone what music you are currently listening too - Mastodon API
Sharkey implements the Mastodon API unlike normal Misskey - UI/UX Improvements
Sharkey makes some UI/UX improvements to make it easier to navigate - Sign-Up Approval
With Sharkey, you can enable sign-ups, subject to manual moderator approval and mandatory user-provided reasons for joining. - Rich Web UI
Sharkey has a rich and easy to use Web UI! It is highly customizable, from changing the layout and adding widgets to making custom themes. Furthermore, plugins can be created using AiScript, an original programming language. - And much more...
Documentation
Sharkey Documentation can be found at Sharkey Documentation