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

Proof of concept twitterbot for talks announcments. #103

Closed

Conversation

sentientmonkey
Copy link

Also some refactoring for the client builder. This is functional but
might need some tweaking on verbage and timezone testing (wee).

Also some refactoring for the client builder. This is functional but
might need some tweaking on verbage and timezone testing (wee).
@phiggins
Copy link
Member

Thanks for taking a stab at this Scott, but this won't help with reminding me to do it. ;)

The biggest problem with automating this is that it requires everything to follow a rigid process which it doesn't now. I love the idea, but doing something like this requires:

  • All of the presenters to have accounts on our site. This means either forcing everyone to sign up or me creating accounts for them.
  • Everyone to always add their talk on the site (or have me do it).
  • All the sessions to be a single speaker giving a talk with a title. The perfect counterexample of this is Ryan and Aaron's ping-pong demo, but there's also TBA talks, etc.

Then you run into problems like the speaker name + talk title making the tweet longer than 140 characters, etc.

I think the best solution, unfortunately, is for me to set a calendar reminder and keep doing it manually. :(

@sentientmonkey
Copy link
Author

Yup, we still have human problems here 😉

I didn't take a stab at the tweet truncation logic... that might take a bit to get right.

I like the idea of making sure that upcoming talks are added to the site so everyone can see, but understand the issues around users without accounts, multiple user talks, TBA talks. Maybe there needs to be more features around what admins can do, or maybe it's trying to over engineer a process that already works well enough. 😀

@zenspider
Copy link
Member

Where does this stand?

@sentientmonkey
Copy link
Author

Not sure this ends up providing value based on feedback from Pete. Will close out issue.

@seattlerb seattlerb locked and limited conversation to collaborators Jan 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants