@floopfloop @shpuld It works like this: GS is the base, qvitter is both a new frontend and a backend extension that adds some more api endpoints for stuff like notifications. Pleroma is just a frontend, but it uses some of the API endpoints that qvitter adds.

The only reason we don't use the notifications endpoint is because it has a bug in it that makes it only usable with cookie-based auth, which pleroma doesn't do (yet). I'll fix this in qvitter some day and try to get it merged. We already got a similar mute-related bug fixed this way.

There's also Pleroma BE, which is an experimental new backend that also implements the GS/Qvitter API, but is a complete rewrite. That's still in development, though.