No description
c927c30567
Misskey's code does the same, but our groups behave differently enough that this may be not the best choice for example, let's say we have: - notifications 1-5 for reaction to note A - notifications 6-8 for reaction to note B - notifications 9-12 for reaction to note A - notification 13-19 for non-groupable events - notification 20 for reaction to note A and that events happened one every minute (so the last notification is from 20 minutes ago) client requests the most recent 10 notifications; we fetch notifications 1-10, and reply: - grouped id 6 for reactions 6-8 to note B - grouped id 10 for reactions 1-5, 9-10 to note A then the client requests 10 more notifications, untilId=10; we fetch notifications 11-20, and reply: - non-grouped notifications 13-19 - grouped id 20 for reactions 11,12,20 to note A because we sort by id, and also the `createdAt` marks the _newest_ event in each group, the client will then show: 6 reactions to note B, 6 minutes ago 4 reactions to note A, 1 minute ago notifications 13-19, 13 minutes to 19 minutes ago 3 reactions to note A, 11 minutes ago I don't know how to make this work better ☹ |
||
|---|---|---|
| .config | ||
| .devcontainer | ||
| .gitlab | ||
| .okteto | ||
| .vscode | ||
| assets | ||
| chart | ||
| cypress | ||
| eslint | ||
| fluent-emojis@cae981eb4c | ||
| idea | ||
| locales | ||
| packages | ||
| scripts | ||
| sharkey-locales | ||
| tossface-emojis@3c0ac3f7bd | ||
| .dockerignore | ||
| .dockleignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .node-version | ||
| .npmrc | ||
| .vsls.json | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| compose.local-db.yml | ||
| compose_example.yml | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| crowdin.yml | ||
| cypress.config.ts | ||
| Dockerfile | ||
| healthcheck.sh | ||
| IMPORTANT_NOTES.md | ||
| LICENSE | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| Procfile | ||
| README.md | ||
| renovate.json5 | ||
| ROADMAP.md | ||
| SECURITY.md | ||
| UPGRADE_NOTES.md | ||
✨ 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 to - 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