This WeeChat script fetches YouTube video information from URLs shared in a channel and posts the extracted details back to the channel. It utilizes the YouTube Data API to retrieve video information, ensuring accurate and reliable data extraction.
This project is intended to be a continuation of my deprecated repository, weechat.youtube-info.
- Python (2.7+ or 3.x)
- WeeChat
requestslibrary (pip install requests)- YouTube Data API key (obtainable from Google Cloud Console)
- Install WeeChat if you haven't already. Refer to the official WeeChat documentation for installation instructions.
- Install the
requestslibrary by running the following command:
pip install requests- Obtain a YouTube Data API key from the Google Cloud Console.
- Download the
youtube_info.pyscript file to your local machine. - Open the
youtube_info.pyscript file and replace"YOUR_API_KEY"with your actual YouTube Data API key. - Open WeeChat and load the script by running the following command:
/script load /path/to/youtube_info.pyReplace /path/to/youtube_info.py with the actual path to the script file on your machine.
- Join a channel where users share YouTube URLs.
- When a YouTube URL is posted in the channel, the script will automatically retrieve the video information using the YouTube Data API.
- The extracted information includes the video's title, author, and duration, presented in a clean format.
- The script will post the extracted information back to the channel for everyone to see and discuss.
┌─ Start Program
│
├─ Join a channel
│
├─ Listen for messages
│ ├─ Is it a YouTube URL?
│ │ ├─ Yes
│ │ │ ├─ Fetch YouTube video details
│ │ │ │ ├─ Call YouTube API
│ │ │ │ │ ├─ Construct API request
│ │ │ │ │ ├─ Send API request
│ │ │ │ │ └─ Receive API response
│ │ │ │ │
│ │ │ │ └─ Extract video information from response
│ │ │ │
│ │ │ └─ Post video information to the channel
│ │ │
│ │ └─ No
│ │
│ └─ Continue listening for messages
│
└─ End Program
You can customize the script behavior by modifying the following variables in the script:
API_KEY: Replace"YOUR_API_KEY"with your actual YouTube Data API key obtained from the Google Cloud Console.
- The script requires a valid YouTube Data API key to access the API. Make sure to obtain a key from the Google Cloud Console and replace
"YOUR_API_KEY"in the script with your actual key. - The YouTube Data API has rate limits and usage quotas. Ensure your API key and usage comply with the API's terms and restrictions to avoid service interruptions.
Contributions to the script are welcome! If you have any suggestions, improvements, or bug fixes, please submit a pull request or open an issue on the GitHub repository.
@apple-fritter's IRC Repositories:
- driftwood: A unified IRC log format definition. (Rust)
- flotsam: Aggregate a per-user metric of flagged contributions to any given user. (Rust)
- jetsam: Flag lines of driftwood formatted IRC logs for sanitization, moderation, or further review. (Rust)
- scrimshaw: Create a quoteslist of any given user, from your driftwood formatted logs. (Rust)
- weechat.driftwood: Natively log WeeChat messages in the driftwood standard. (Python)
- xchat.channel-moderation: Moderate an IRC channel. (Python)
- doppelganger: X-Chat mIRC imposter. Fingerprint subversion. (Python bundle)
- irccloud-to-weechat: Convert IRC logs from IRCcloud format to Weechat format. (Rust)
- irccloud-to-xchat: Convert IRC logs from IRCcloud format to XChat format. (Rust)
- weechat.driftwood: Natively log WeeChat messages in the driftwood standard. (Python)
- weechat.ban-evasion-detection: Detect and prevent ban evasion. (Python)
- weechat.typo-aggregator: Record misspelled words in a TSV (tab-separated values) file. (Python)
- weechat.whois-aggregator: Aggregate whois data in a rolling CSV file. (Python)
- weechat.youtube-info: Deprecated. Extract video information from a YouTube URL and post it back to the channel. (Python)
- weechat.youtube-api: Extract video information from a YouTube URL and post it back to the channel. (Python)
When working with any project involving IRC (Internet Relay Chat), it's important to keep the following considerations in mind to ensure a positive and respectful environment for all participants.
Tailor your project's behavior and responses to align with the expected norms and conventions of IRC. Take into account the preferences and expectations of IRC users, ensuring that your project provides a seamless and familiar experience within the IRC ecosystem.
Respect and adhere to the guidelines and policies of the IRC platform you are using. Familiarize yourself with the platform's rules regarding script usage, automation, and acceptable behavior. Comply with the platform's Terms of Service, and be mindful of any limitations or restrictions imposed by the platform. Strive to create an inclusive and welcoming environment where all users can engage respectfully and comfortably.
Maintain a polite and courteous demeanor in all interactions. Uphold the fundamental principles of respect, avoiding engagement in illegal, inappropriate, or offensive behavior. This includes refraining from using derogatory or inflammatory language, sharing explicit, triggering, or offensive content, engaging in harassment, or launching personal attacks. Obtain explicit consent before interacting with other users or sending automated responses. Respect the privacy of other users and avoid invading their personal space without their permission.
Avoid disrupting the normal flow of conversation within IRC channels. Ensure that your project's actions and responses do not cause unnecessary disruptions or inconvenience to other users. Implement mechanisms to prevent spamming or flooding the channel with excessive or irrelevant messages. Handle errors gracefully, preventing unintended behavior or disruptions to the IRC platform or the experiences of other users.
Consider the potential variations in behavior across different IRC platforms and clients. While aiming for compatibility, be aware that certain functionalities may not be available or consistent across all platforms. Test your project on multiple IRC platforms and clients to ensure compatibility and provide the best possible experience for users.
Contributions are welcome! If you'd like to contribute, please follow these steps:
- Fork the repository.
- Create a new branch for your feature or bug fix.
- Make your changes and commit them.
- Push your changes to your forked repository.
- Submit a pull request to the main repository.
This software is provided "as is" and without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.
The authors do not endorse or support any harmful or malicious activities that may be carried out with the software. It is the user's responsibility to ensure that their use of the software complies with all applicable laws and regulations.
This project is licensed under the MIT License.