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

Implement a timed event that broadcasts almost expiring CFPs etc. through Twitter #38

Open
jfversluis opened this issue Jun 20, 2018 · 6 comments
Labels
awesome enhancement New feature or request

Comments

@jfversluis
Copy link
Collaborator

Since the Twitter account is now in place, it might be nice to have it broadcast more than just "a new CFP was added". For instance, have it tweet each week what CFPs are about to expire or something. Or just random sometimes to advertise itself.

Maybe through an Azure Function?

@jfversluis jfversluis added enhancement New feature or request awesome labels Jun 20, 2018
@Jandev
Copy link
Collaborator

Jandev commented Aug 10, 2018

Great idea!

I guess we need to add a new column ReminderSent (DateTime). This can be used to send out the tweets for expiring CFP's.
Something I dislike about bots is them bombing my timeline with dozens of tweets. I'd hate to see this happen to CFP Exchange. Therefore, the Function should run like every X hours. If there are CFP's expiring in the next 7 days and the (DateTime.UtcNow - ReminderSent) < 7 days), it should send out a tweet, but only for 1 CFP!

If there are multiple CFP's expiring, in a couple of hours the next one will be picked up. And so on...

It's also possible to schedule a re-reminder. First reminder is 7 days before a CFP ends, the re-reminder is 3 days before the CFP ends.

This is a nice issue if you want to get started with Azure Functions and maybe ARM templates.

@jfversluis
Copy link
Collaborator Author

I totally agree, I don't want to numb the users by sending dozens of tweets every day. I was indeed thinking once a week or something so that you are reminded of that one CFP you wanted to submit.

@staal-it
Copy link
Contributor

staal-it commented Nov 3, 2018

What about Hangfire? --> https://www.hangfire.io/

@jfversluis
Copy link
Collaborator Author

I've heard of Hangfire! Never used it though... But seems my web app has to be always-on to be able to do this?

@staal-it
Copy link
Contributor

Yes, I believe you are correct. But that's not really a problem since there are no extra costs right?

Shall I create a simple pull-request to get started with just one use-case or would you rather take a different approach?

@jfversluis
Copy link
Collaborator Author

For always-on you need a higher pricing plan on Azure. But the way the Azure Function is set up now it requires always-on too, and costs are not too bad.

So, long story short: yes! Set something up! Then we can always decide to do things differently later on 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awesome enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants