diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 27c7716..69b14c1 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -24,6 +24,7 @@ jobs: - name: execute py script # run app.py env: + NODEMAVEN_PROXY: "${{ secrets.NODEMAVEN_PROXY }}" TWITTER_API_KEY: "${{ secrets.TWITTER_API_KEY }}" TWITTER_API_SECRET: "${{ secrets.TWITTER_API_SECRET }}" TWITTER_ACCESS_TOKEN: "${{ secrets.TWITTER_ACCESS_TOKEN }}" diff --git a/FUNDING.yml b/FUNDING.yml index ff57ceb..484b8d2 100644 --- a/FUNDING.yml +++ b/FUNDING.yml @@ -1,2 +1,2 @@ github: [dhohirpradana] -custom: ["https://mediasiana.id"] +custom: ["https://github.com/dhohirpradana"] diff --git a/README.md b/README.md index ddcf1df..ae00dd9 100644 --- a/README.md +++ b/README.md @@ -3,24 +3,26 @@ Automate change of name and Twitter profile banner using Python code and Github action. # Steps -1. *To get Twitter Keys* -Go to Twitter developer site [Twitter Developer](https://developer.twitter.com "Twitter Developer") and register twitter developer -> Create new project -> Create app -> Keys and token -|key name|description| -|--------|--------------| -|TWITTER\_API\_KEY|The Consumer Key for your Twitter App (this is the same for every user)| -|TWITTER\_API\_SECRET|The Consumer Secret for your Twitter App (this is the same for every user)| -|TWITTER\_ACCESS\_TOKEN|The Public part of an Access Token for your Twitter App (this is different for every user)| -|TWITTER\_ACCESS\_TOKEN\_SECRET|The Secret part of an Access Token for your Twitter App (this is different for every user)| +1. _To get Twitter Keys_ + Go to Twitter developer site [Twitter Developer](https://developer.twitter.com "Twitter Developer") and register twitter developer -> Create new project -> Create app -> Keys and token -2. *Use this template or Clone this repository and push to your Github* -https://github.com/dhohirpradana/Twitter-Automatically-Name-Banner.git +| key name | description | +| --------------------------- | ------------------------------------------------------------------------------------------ | +| TWITTER_API_KEY | The Consumer Key for your Twitter App (this is the same for every user) | +| TWITTER_API_SECRET | The Consumer Secret for your Twitter App (this is the same for every user) | +| TWITTER_ACCESS_TOKEN | The Public part of an Access Token for your Twitter App (this is different for every user) | +| TWITTER_ACCESS_TOKEN_SECRET | The Secret part of an Access Token for your Twitter App (this is different for every user) | +| NODEMAVEN_PROXY | The Secret part of an Access Token for your Twitter App (this is different for every user) | -3. *Set Github Secrets* -Go to your repository -> Settings -> Secrets -> Action -> Set TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_TOKEN_SECRET, TWITTER_API_KEY, TWITTER_API_SECRET with your Twitter keys +2. _Use this template or Clone this repository and push to your Github_ + https://github.com/dhohirpradana/Twitter-Automatically-Name-Banner.git -4. (*if .github/workflows/main.yml not exists)* *Create Workflow* -Go to your repository -> Actions -> New workflow -> Setup a workflow yourself -> whatever.yaml +3. _Set Github Secrets_ + Go to your repository -> Settings -> Secrets -> Action -> Set TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_TOKEN_SECRET, TWITTER_API_KEY, TWITTER_API_SECRET with your Twitter keys + +4. (_if .github/workflows/main.yml not exists)_ _Create Workflow_ + Go to your repository -> Actions -> New workflow -> Setup a workflow yourself -> whatever.yaml ```javascript name: twitter auto update banner and name @@ -46,7 +48,7 @@ jobs: run: | python -m pip install --upgrade pip pip install tweepy - + - name: execute py script # run app.py env: TWITTER_API_KEY: '${{ secrets.TWITTER_API_KEY }}' diff --git a/README1.md b/README1.md new file mode 100644 index 0000000..2af10d2 --- /dev/null +++ b/README1.md @@ -0,0 +1,274 @@ +## Overview + +
Approach | +Description | +Difficulty | +Speed | +
---|---|---|---|
Obtain Twitter API Keys and Tokens | +Create a Twitter Developer account. | +Medium | +Medium | +
Python Programming Language | +Programming language known for its readability and clear syntax. | +Hard | +Medium | +
Python Pip | +Package installer for Python. | +Easy | +Fast | +
Tweepy | +Python library that provides easy access to the Twitter API. | +Easy | +Fast | +
Technique | +Speed | +Cost | +Scale | +Anonymity | +Other Risks | +Additional Notes | +
---|---|---|---|---|---|---|
VPN Service ⭐⭐ ⭐⭐ |
+ Fast, offers a balance of anonymity and speed | +Usually paid | +- Good for small-scale operations. - May not be suitable for high-volume scraping due to potential IP blacklisting. |
+ - Provides good anonymity and can bypass geo-restriction. - Potential for IP blacklisting/blocks if the VPN's IP range is known to the target site. |
+ - Service reliability varies. - Possible activity logs. |
+ Choose a reputable provider to avoid security risks. | +
TOR Network ⭐⭐ |
+ Very slow due to onion routing | +Free | +- Fine for small-scale, impractical for time-sensitive/ high-volume scraping due to very slow speed. - Consider only for research purposes, not scalable data collection. |
+ - Offers excellent privacy. - Tor exit nodes can be blocked or malicious, like potential for eavesdropping. |
+ - | +Slowest choice | +
Public Wi-Fi ⭐ |
+ Vary | +Free | +Fine for small-scale. | +Potential for being banned by target sites if scraping is detected. | +Potential unsecured networks | +Long distance way solution. |
+
Mobile Network ⭐⭐ |
+ Relatively fast but slower speeds on some networks | +Paid, potential for additional costs. | +Using mobile IPs can be effective for small-scale scraping, impractical for large-scale. | +Mobile IPs can change but not an anonymous option since it's tied to your personal account. | +- | +Using own data | +
Private/ Dedicated Proxies ⭐⭐⭐ ⭐⭐ (Best) |
+ Fast | +Paid | +- Best for large-scale operations and professional scraping projects. | +Offer better performance and reliability with lower risk of blacklisting. | +Vary in quality | +- Rotating Proxies are popular choices for scraping as they can offer better speed and a variety of IPs. - You can use this proxy checker tool to assess your proxy quality |
+
Shared Proxies ⭐⭐⭐ (Free) ⭐⭐ ⭐⭐ (Paid) |
+ Slow to Moderate | +Usually Free or cost-effective for low-volume scraping. | +Good for basic, small-scale, or non-critical scraping tasks. | +Can be overloaded or blacklisted or, encountering already banned IPs. | +Potential unreliable/ insecure proxies, especially Free ones. | +
Technique | +Speed | +Cost | +Scale | +Anonymity | +Additional Notes | +
---|---|---|---|---|---|
Residential Rotating Proxies ⭐⭐⭐ ⭐⭐ (Best) |
+ Fast | +Paid | +Ideal for high-end, large-scale scraping tasks. | +- Mimics real user IPs and auto-rotate IPs when using proxy gateways, making detection harder. - Provides high anonymity and low risk of blacklisting/blocks due to legitimate residential IPs. |
+ Consider proxy quality, location targeting, and rotation speed. | +
Datacenter Rotating Proxies ⭐⭐ ⭐⭐ |
+ Faster than Residential Proxies | +More affordable than Residential Proxies | +Good for cost-effective, large-scale scraping. | +Less anonymous than Residential Proxies. - Higher risk of being blocked. - Easily detectable due to their datacenter IP ranges. |
+ Consider reputation of the provider and frequency of IP rotation. | +