├── .github
├── ISSUE_TEMPLATE.md
└── PULL_REQUEST_TEMPLATE.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── glitch.json
├── requirements.txt
├── server.py
└── templates
├── base.html
├── index.html
└── thank-you.html
/.github/ISSUE_TEMPLATE.md:
--------------------------------------------------------------------------------
1 | One line summary of the issue here.
2 |
3 | ### Expected behavior
4 |
5 | As concisely as possible, describe the expected behavior.
6 |
7 | ### Actual behavior
8 |
9 | As concisely as possible, describe the observed behavior.
10 |
11 | ### Steps to reproduce the behavior
12 |
13 | Please list all relevant steps to reproduce the observed behavior.
14 |
--------------------------------------------------------------------------------
/.github/PULL_REQUEST_TEMPLATE.md:
--------------------------------------------------------------------------------
1 | ### Problem
2 |
3 | Explain the context and why you're making that change. What is the
4 | problem you're trying to solve? In some cases there is not a problem
5 | and this can be thought of being the motivation for your change.
6 |
7 | ### Solution
8 |
9 | Describe the modifications you've done.
10 |
11 | ### Result
12 |
13 | What will change as a result of your pull request? Note that sometimes
14 | this section is unnecessary because it is self-explanatory based on
15 | the solution.
16 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # How to Contribute
2 |
3 | We'd love to get patches from you!
4 |
5 | ## Getting Started
6 |
7 | We follow the [GitHub Flow Workflow](https://guides.github.com/introduction/flow/)
8 |
9 | 1. Fork the project
10 | 1. Check out the `main` branch
11 | 1. Create a feature branch
12 | 1. Write code and tests for your change
13 | 1. From your branch, make a pull request against `twitterdev/twitterdev-template/main`
14 | 1. Work with repo maintainers to get your change reviewed
15 | 1. Wait for your change to be pulled into `twitterdev/twitterdev-template/main`
16 | 1. Delete your feature branch
17 |
18 | ## License
19 |
20 | By contributing your code, you agree to license your contribution under the terms of the APLv2: https://github.com/twitter/repo-scaffolding/blob/master/LICENSE
21 |
22 | ## Code of Conduct
23 |
24 | We believe that a welcoming community is important and we ask that you follow Twitter's [Open Source Code of Conduct](https://github.com/twitter/.github/blob/main/code-of-conduct.md) in all interactions with the community.
25 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
202 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Tweet a dog fact
2 |
3 | Allows you to Tweet a fact about dogs once! Try it out at [tweet-a-dog-fact.glitch.me](https://tweet-a-dog-fact.glitch.me).
4 |
5 | This site walks you through the OAuth 2.0 Authorization Code Flow with PKCE for authentication and makes a call to the Twitter API's manage Tweets endpoint.
6 |
7 | ## A framework
8 |
9 | This code sample can be a starting point to make a bot similar to [@Factual\_\_Dog](https://twitter.com/Factual__Dog), a bot that Tweets dogs facts twice daily. This can be remixed to make your own bot, if you do you will need to add in your own logic to determine how often your bot will Tweet.
10 |
11 | ## Prerequisites
12 |
13 | In order to remix this code sample you will need the following:
14 |
15 | - A developer account.
16 | - If you don’t already have access to the Twitter API, [you can sign up for a developer account.](http://t.co/signup)
17 | - A Project in the [developer portal](https://developer.twitter.com/en/portal/dashboard)
18 | - An App containing the credentials required to use the Twitter API
19 | - OAuth 2.0 turned on in your App’s authentication settings
20 | - You will also need to update your `.env` file to include your client ID, client secret and redirect URI. You can obtain your client ID and secret from your App's authentication settings and your redirect URI should be `your-glitch-project.glitch.me/oauth/callback`. This must match the redirect URI in your App's authentication settings.
21 |
--------------------------------------------------------------------------------
/glitch.json:
--------------------------------------------------------------------------------
1 | {
2 | "install": "pip3 install --user -r requirements.txt",
3 | "start": "PYTHONUNBUFFERED=true python3 server.py",
4 | "watch": {
5 | "ignore": [
6 | "\\.pyc$"
7 | ],
8 | "install": {
9 | "include": [
10 | "^requirements\\.txt$"
11 | ]
12 | },
13 | "restart": {
14 | "include": [
15 | "\\.py$",
16 | "^start\\.sh"
17 | ]
18 | },
19 | "throttle": 1000
20 | }
21 | }
22 |
--------------------------------------------------------------------------------
/requirements.txt:
--------------------------------------------------------------------------------
1 | Flask
2 | APScheduler==3.9.1
3 | backports.zoneinfo==0.2.1
4 | certifi==2022.5.18.1
5 | charset-normalizer==2.0.12
6 | click==8.1.3
7 | Flask-APScheduler==1.12.3
8 | idna==3.3
9 | importlib-metadata==4.11.4
10 | itsdangerous==2.1.2
11 | Jinja2==3.1.2
12 | MarkupSafe==2.1.1
13 | oauthlib==3.2.0
14 | python-dateutil==2.8.2
15 | pytz==2022.1
16 | pytz-deprecation-shim==0.1.0.post0
17 | requests==2.28.0
18 | requests-oauthlib==1.3.1
19 | six==1.16.0
20 | tzdata==2022.1
21 | tzlocal==4.2
22 | urllib3==1.26.9
23 | Werkzeug==2.1.2
24 | zipp==3.8.0
25 | Gunicorn
26 | redis==4.3.
--------------------------------------------------------------------------------
/server.py:
--------------------------------------------------------------------------------
1 | import base64
2 | import hashlib
3 | import os
4 | import re
5 | import json
6 | import requests
7 | from requests.auth import AuthBase, HTTPBasicAuth
8 | from requests_oauthlib import OAuth2Session, TokenUpdated
9 | from flask import Flask, request, redirect, session, url_for, render_template
10 |
11 |
12 | app = Flask(__name__)
13 | app.secret_key = os.urandom(50)
14 |
15 |
16 | client_id = os.environ.get("CLIENT_ID")
17 | client_secret = os.environ.get("CLIENT_SECRET")
18 | auth_url = "https://twitter.com/i/oauth2/authorize"
19 | token_url = "https://api.twitter.com/2/oauth2/token"
20 | redirect_uri = os.environ.get("REDIRECT_URI")
21 |
22 | # Set the scopes
23 | scopes = ["tweet.read", "users.read", "tweet.write", "offline.access"]
24 |
25 | # Create a code verifier
26 | code_verifier = base64.urlsafe_b64encode(os.urandom(30)).decode("utf-8")
27 | code_verifier = re.sub("[^a-zA-Z0-9]+", "", code_verifier)
28 |
29 | # Create a code challenge
30 | code_challenge = hashlib.sha256(code_verifier.encode("utf-8")).digest()
31 | code_challenge = base64.urlsafe_b64encode(code_challenge).decode("utf-8")
32 | code_challenge = code_challenge.replace("=", "")
33 |
34 |
35 |
36 | def make_token():
37 | return OAuth2Session(client_id, redirect_uri=redirect_uri, scope=scopes)
38 |
39 |
40 | def parse_dog_fact():
41 | url = "http://dog-api.kinduff.com/api/facts"
42 | dog_fact = requests.request("GET", url).json()
43 | return dog_fact["facts"][0]
44 |
45 |
46 |
47 | def post_tweet(payload, token):
48 | print("Tweeting!")
49 | return requests.request(
50 | "POST",
51 | "https://api.twitter.com/2/tweets",
52 | json=payload,
53 | headers={
54 | "Authorization": "Bearer {}".format(token["access_token"]),
55 | "Content-Type": "application/json",
56 | },
57 | )
58 |
59 |
60 | @app.route("/")
61 | def hello():
62 | return render_template("index.html")
63 |
64 |
65 | @app.route("/start")
66 | def demo():
67 | global twitter
68 | twitter = make_token()
69 | authorization_url, state = twitter.authorization_url(
70 | auth_url, code_challenge=code_challenge, code_challenge_method="S256"
71 | )
72 | session["oauth_state"] = state
73 | return redirect(authorization_url)
74 |
75 |
76 | @app.route("/oauth/callback", methods=["GET"])
77 | def callback():
78 | code = request.args.get("code")
79 | token = twitter.fetch_token(
80 | token_url=token_url,
81 | client_secret=client_secret,
82 | code_verifier=code_verifier,
83 | code=code,
84 | )
85 | doggie_fact = parse_dog_fact()
86 | payload = {"text": "{}".format(doggie_fact)}
87 | response = post_tweet(payload, token).json()
88 | posted_fact = response['data']['text']
89 | return render_template("thank-you.html", value=posted_fact)
90 |
91 |
92 | if __name__ == "__main__":
93 | app.run()
--------------------------------------------------------------------------------
/templates/base.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | Tweet a dog fact!{% block title %}{% endblock %}
5 |
9 |
10 |
11 |
12 |
Welcome! This app will Tweet one dog fact once from your account.
4 |
5 |
To get started, we'll need you to authorize Hello world twitter bot app to Tweet on your behalf using OAuth 2.0. Learn more information about OAuth 2.0.
6 |
Here's how it works:
7 |
8 |
We will redirect you to Twitter.com for you to authorize our app.
9 |
While at Twitter.com, you will authorize our Twitter App to post on your behalf.