aaad
dbfafe25e3
previously, when adding items either at the beginnig (e.g. new notes coming in while we're not looking at the top of the timeline) or a the end (e.g. more items arriving from a background fetch) of a paginated view, the resulting list got truncated to `displayLimit`, potentially throwing data away and causing a new fetch. This, coupled with the async nature of scrolling & fetching, could cause weird results. Also, `offset` was always incremented by the size of the fetched results, even if not all of them were displayed, meant that it was possible for offset-based pagination to drop items. Finally, the "queue" of new items (usually, new notes) also got truncated to `displayLimit`, which again could drop items (this effect was usually masked by the first point: when scrolling to the top of the timeline, if the queue's length was equal to `displayLimit`, those notes displaced any existing ones, `unshiftItems` set `more.value=true`, you got scrolled to the top, and notes were fetched again, so you lost your position but at least all notes got shown, eventually) |
||
|---|---|---|
| .config | ||
| .devcontainer | ||
| .gitlab | ||
| .okteto | ||
| .old/workflows | ||
| .vscode | ||
| assets | ||
| chart | ||
| cypress | ||
| fluent-emojis@cae981eb4c | ||
| locales | ||
| misskey-assets@0179793ec8 | ||
| packages | ||
| scripts | ||
| 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 | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| crowdin.yml | ||
| cypress.config.ts | ||
| docker-compose_example.yml | ||
| docker-compose.local-db.yml | ||
| Dockerfile | ||
| healthcheck.sh | ||
| IMPORTANT_NOTES.md | ||
| LICENSE | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| Procfile | ||
| README.md | ||
| ROADMAP.md | ||
| SECURITY.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 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