Also be wary when using apps and especially when enabling push notifications. Lemmy API currently lacks any kind of support for partial access to an account (unless this has changed recently). So, apps cannot, for example, get read only access to your account's inbox. Apps can get either no access or full access. When you sign up for push notifications, an authentication token is stored to the push notification server which gives full access to your account to who ever happens to get their hand on that token. If there, for example, happens to be a security vulnerability on the push notification server, it might leak those tokens.

If you have enabled push notifications on some Lemmy app, and want to invalidate the token, you can just change your password.

Here's a post by Memmy for Lemmy's developer about push notifications: https://lemmy.ml/post/1534493

The issue with this is that Lemmy doesn't allow accounts with duplicate emails. So If I want three accounts, I need three email addresses. As Lemmy doesn't currently support push notifications, email is the only way to get notified about anything. Checking three different addresses is impractical.

I agree that this is best practice, but until Lemmy allows admins to remove the uniqueness requirement for email addresses, or sets up a decent push notifications API, it's not going to happen over most instances.

Fortunately, we were in no danger around the recent issues. Not only did we not use the feature in question, we have cross-site scripting policies set up correctly so scripts from other domains won't run.