Manuel Stahl
Manuel Stahl
Which permissions are required for this action? If the repo is configures the GITHUB_TOKEN to be restrictive, you need to elevate the required permissions in the workflow. See also https://docs.github.com/en/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token
And what kind of URL would that be?
Please fix the checks. Try `yarn fix` and run `yarn test` yourself.
Privacy is not an issue. We assume that anyone using `synapse-admin` could as well access the synapse database.
@PC-Admin can you update what you are still missing?
Nice example for a unit test...
With "fully delete" you mean delete from the database? This is generally a bad idea, since a user can simply register this user ID again.
Would be nice if LineageOS and others could establish their own standard for push notifications. Should be based on web push IMHO. https://datatracker.ietf.org/doc/html/draft-ietf-webpush-protocol https://web.dev/push-notifications-overview/
@jcgruenhage @minecraftchest1 you're right, but that means something like sygnal (or any other service that want's to support push) has to implement Firebase, Apple APNs, Web Push, Openpush and Unified...
The main issues to be resolved are environment variables. Especially `REACT_APP_VERSION` and `REACT_APP_SERVER`. Draft is here: [vitejs](https://github.com/Awesome-Technologies/synapse-admin/tree/vitejs)