Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get alerts by email when someone else joins Mastodon #194

Open
devnoname120 opened this issue Dec 19, 2022 · 3 comments
Open

Get alerts by email when someone else joins Mastodon #194

devnoname120 opened this issue Dec 19, 2022 · 3 comments

Comments

@devnoname120
Copy link

No description provided.

@MurmeltierS
Copy link
Contributor

as this would require pretty heavy backend lifting and mail-sending infrastrucutre my guess would be that this is pretty much out of scope for this project :|

@devnoname120
Copy link
Author

Note that a service such as Mailgun or Sendgrid would solve the infrastructure part.

For example, Mailgun is free for 5000 emails a month and $1 for each extra 1000 emails.

I'm not sure how feasible it would be. You could probably reach out to them to ask for a special free plan or big discounts as an open-source non-commercial project.

@lucahammer
Copy link
Owner

As @MurmeltierS said, that would be a quite different project. I probably wouldn't use mail, but ActivityPub messages.

Fedifinder is designed to store as little user data as possible. To notify people, it would need to at least store access tokens of the Twitter and Fediverse account to retrieve follow lists and compare them to the results. But for a good experience that's not enough, because it would inform you about any found accounts that you don't follow already. And maybe there is a reason why you don't follow them. So it needs to store already identified accounts as well. When it uses mail instead of direct messages, it needs to store mail addresses. It needs a schedule to run, monitoring and more stability (users won't notice when it crashes and can try again with a simple reload). How to handle inactive users? Over time the database grows, accounts move, servers become unreachable. Those cases need to be handled. People probably want to be able to manage their settings: More data to store and at least some kind of settings page to build.

Sending mails would be the least of my concerns. Especially because I would use messages. But everything else is currently to much. If someone wants to build it, I would recommend to either fork fedifinder or just copy the parts that can be reused (twitter auth, nasty regex for handle identification and method to check if a domain is a fediverse instance).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants