<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jeremy Dickey on Medium]]></title>
        <description><![CDATA[Stories by Jeremy Dickey on Medium]]></description>
        <link>https://medium.com/@jeremydickey?source=rss-65d3f35804d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TNsDdiVUDHZhipp9PpN6zg.png</url>
            <title>Stories by Jeremy Dickey on Medium</title>
            <link>https://medium.com/@jeremydickey?source=rss-65d3f35804d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 04:53:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeremydickey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How is your customer service?]]></title>
            <link>https://medium.com/@jeremydickey/how-is-your-customer-service-53c93f191d63?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/53c93f191d63</guid>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sat, 25 Apr 2026 19:17:03 GMT</pubDate>
            <atom:updated>2026-04-25T19:20:31.255Z</atom:updated>
            <content:encoded><![CDATA[<p>How is your customer service?</p><p>That’s what I was asked in my last interview.</p><p>The job was described as a cloud cyber security engineer role that also dealt with on premises issues for government departments.</p><p>I was told I’d be handling the day to day troubleshooting of Splunks siem.</p><p>The job description itself was more focused on development, networking and cloud computing.</p><p>So I really had no idea what to expect.</p><p>In the interview I covered my more recent experience and left out much of my more tenured or more technical roles.</p><p>After answering several questions about my experience and how i’d resolve different things.</p><p>The interviewer seemed satisfied with my answers and to my surprise asked me about my customer service.</p><p>In the past decade I had worked largely with customers as I handled development, support, repairs, sales and more. However, as technical as I was I wouldn’t say I was great at customer service.</p><p>Infact, my entire life I have focused on the technical, on learning how to fix things , how to build things, so much so that you could have even called me eccentric!</p><p>I wasn’t even aware of how bad my customer service skills were.</p><p>Now years later, after being on numerous video calls, phone calls, emails, slack calls, WebEx calls and just communicating with people smarter than me, and from different backgrounds I can answer this question;</p><p>“How is your customer service&quot; without feeling robotic or like I’m just saying what I think folks want to hear.</p><p>I now understand customer service and I’ve even honed my networking knowledge even further than before.</p><p>My customer service is excellent, I think about what the end user needs, why they need it, and I answer with well thought out, accurate responses curated to be as helpful and polite as possible to the customer asking the question. I put myself in the customers shoes and think about if what I’m saying will be perceived well and how I can be perceived even better by the customer to really show that I value their time and efforts.</p><p>I ask you now, How is your customer service?</p><p>How can you improve your customer service?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53c93f191d63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Comprehensive Guide to Splunk on Linux: Installation, Data Ingestion, and Searching]]></title>
            <link>https://medium.com/@jeremydickey/comprehensive-guide-to-splunk-on-linux-installation-data-ingestion-and-searching-6c93db96a31c?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c93db96a31c</guid>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[splunk-enterprise]]></category>
            <category><![CDATA[splunk-administration]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sun, 30 Nov 2025 14:10:41 GMT</pubDate>
            <atom:updated>2025-11-30T14:10:41.356Z</atom:updated>
            <content:encoded><![CDATA[<p>Splunk is a powerful platform for searching, monitoring, and analyzing machine-generated data from any source. In Linux environments, it serves as a critical tool for operational intelligence, security monitoring, and troubleshooting by aggregating logs from applications, servers, and network devices.</p><p>This report provides a comprehensive guide for Linux users on installing and configuring Splunk Enterprise, managing data ingestion with Splunk Forwarders, and performing analysis using the Splunk Search Processing Language (SPL). It covers foundational topics from system prerequisites and installation procedures to advanced concepts like security hardening, performance tuning, and centralized forwarder management. The information is structured to guide users through the entire lifecycle of a Splunk deployment on major Linux distributions such as RHEL, Ubuntu, and SLES.</p><h3>Key Points</h3><ul><li><strong>System Prerequisites are Crucial:</strong> Successful Splunk Enterprise installation on Linux requires adherence to specific hardware (12+ CPU cores, 12+ GB RAM), software (supported OS versions, Kernel 3.x+), and user account configurations, including a dedicated non-root user.</li><li><strong>Installation is Package-Based:</strong> Splunk is installed using standard Linux packages (.rpm, .deb, .tgz), with consistent post-install steps involving changing ownership to a splunk user, accepting the license on first start, and enabling the service to start on boot.</li><li><strong>Forwarders are Key to Data Ingestion:</strong> The lightweight Splunk Universal Forwarder (UF) is the recommended method for collecting data from Linux endpoints. It offers a minimal footprint and can be managed centrally by a Splunk Deployment Server for scalable configuration.</li><li><strong>SPL is the Foundation of Analysis:</strong> The Search Processing Language (SPL) is used to search, filter, and analyze data. Queries are constructed by piping commands together, such as stats, timechart, and table, to transform raw log data into actionable insights.</li><li><strong>Security and Performance are Paramount:</strong> Hardening a Splunk installation involves enabling HTTPS, using signed certificates, restricting firewall ports, and implementing Role-Based Access Control (RBAC). Performance is optimized through efficient search queries, summary indexing, and proper hardware scaling.</li><li><strong>Configuration is File-Based:</strong> Splunk’s behavior is primarily controlled through configuration files (.conf) located in $SPLUNK_HOME/etc/. Best practice is to place custom configurations in local directories to override default settings without modifying them directly.</li></ul><h3>Part 1: Splunk Enterprise Installation and Initial Configuration</h3><p>Successful deployment begins with proper setup and configuration. This section details the requirements and steps for installing Splunk Enterprise on a Linux system.</p><p><strong>Hardware and Software Prerequisites</strong> Before installation, ensure the system meets the minimum requirements. High-performance environments, particularly for indexers, should significantly exceed these minimums.</p><p>Prerequisite Minimum Requirement Recommended for Performance <strong>CPU</strong> 12 cores 24–48 cores (Indexers) <strong>RAM</strong> 12 GB 64–128 GB (Indexers) <strong>Disk</strong> 250 GB (separate from OS) Fast SSD/NVMe for hot/warm data <strong>Network</strong> 1 GbE NIC Second 1 GbE NIC for management <strong>Supported OS</strong> RHEL 7/8/9, CentOS 7/8, Ubuntu ≥16.04, SLES 12/15 Latest supported versions <strong>Kernel</strong> Linux kernel 3.x or higher Information not provided <strong>Systemd</strong> Version 219 or higher Information not provided</p><p><strong>Note:</strong> AlmaLinux and Rocky Linux are considered compatible as RHEL derivatives.</p><p><strong>Installation Procedures</strong> Installation should always be performed as a dedicated non-root user for security. The default installation path is /opt/splunk.</p><p>Package Type Target Distributions Key Commands <strong>RPM (</strong><strong>.rpm)</strong> RHEL, CentOS, AlmaLinux, Rocky sudo useradd splunk&lt;br&gt;sudo rpm -i splunk_package.rpm&lt;br&gt;sudo chown -R splunk:splunk /opt/splunk <strong>DEB (</strong><strong>.deb)</strong> Debian, Ubuntu sudo useradd splunk&lt;br&gt;sudo dpkg -i splunk_package.deb&lt;br&gt;sudo chown -R splunk:splunk /opt/splunk <strong>TGZ (</strong><strong>.tgz)</strong> SLES, Generic, Custom Paths tar xvzf splunk_package.tgz -C /path/for/install&lt;br&gt;sudo chown -R splunk:splunk /path/for/install/splunk</p><p>After installation, Splunk must be started for the first time by the splunk user, accepting the license agreement: sudo -u splunk /opt/splunk/bin/splunk start --accept-license</p><p>To enable Splunk to start on boot using systemd: sudo /opt/splunk/bin/splunk enable boot-start -systemd-managed 1 -user splunk</p><p><strong>First-Time Setup and Directory Structure</strong> On the first launch, you will be prompted to create an administrator account and password. Splunk Web is accessible by default at http://&lt;your_server_ip&gt;:8000. Key configuration files reside within $SPLUNK_HOME (e.g., /opt/splunk).</p><p>Directory / File Purpose etc/system/default/ Default configuration files. <strong>Never edit these directly.</strong> etc/system/local/ Site-wide configuration overrides. Place custom .conf files here. etc/apps/ Contains installed applications and their configurations. etc/passwd Stores encrypted user credentials managed by Splunk. etc/auth/ Stores SSL certificates, keys, and the splunk.secret file.</p><p><strong>Security Hardening</strong> Securing a Splunk instance is critical.</p><ul><li><strong>Credentials:</strong> Immediately change default credentials.</li><li><strong>HTTPS:</strong> Enable HTTPS for Splunk Web (web.conf) and for communication between Splunk components (inputs.conf, outputs.conf). Replace default self-signed certificates with ones from a trusted Certificate Authority (CA).</li><li><strong>Firewall:</strong> Restrict access using iptables, firewalld, or ufw to only necessary ports, such as Splunk Web (8000), Management (8089), Indexer Receiving (9997), and Syslog (514).</li><li><strong>RBAC:</strong> Use Role-Based Access Control to limit user capabilities. Integrate with LDAP or SAML for centralized authentication.</li><li><strong>SELinux/AppArmor:</strong> Splunk does not fully support SELinux out of the box; running in “permissive” mode is recommended unless a custom policy is created. Similarly, custom AppArmor profiles may be needed.</li></ul><h4>Part 2: Data Ingestion and Forwarder Management</h4><p>Data is sent to Splunk indexers primarily through Splunk Forwarders.</p><p><strong>Forwarder Types: Universal vs. Heavy</strong> Choosing the right forwarder type depends on the data source and processing needs.</p><p>Feature Universal Forwarder (UF) Heavy Forwarder (HF) <strong>Resource Usage</strong> Minimal (CPU, memory, disk) High (full Splunk instance) <strong>Functionality</strong> Forwards raw data with minimal processing Can parse, filter, and route data <strong>Use Case</strong> Large-scale deployment on endpoints to collect logs Intermediate data processing, complex routing, running heavy add-ons <strong>Licensing</strong> No license cost Requires a Forwarder license</p><p><strong>Universal Forwarder Installation and Configuration</strong> The UF installation process mirrors that of Splunk Enterprise, using a dedicated package (splunkforwarder). After installation, the UF must be configured to send data to an indexer and, optionally, to be managed by a Deployment Server.</p><ul><li><strong>Add a forwarding target (indexer):</strong>&lt;br&gt;/opt/splunkforwarder/bin/splunk add forward-server &lt;host&gt;:9997</li><li><strong>Point to a Deployment Server:</strong>&lt;br&gt;/opt/splunkforwarder/bin/splunk set deploy-poll &lt;deploy_host&gt;:8089</li></ul><p><strong>Configuring Data Inputs and Outputs</strong></p><ul><li><strong>inputs.conf:</strong> Defines what data to collect. Common inputs include monitoring files ([monitor://...]), receiving syslog data, or running scripts. Best practice is to use a Universal Forwarder to monitor log files written to disk by services like rsyslog or syslog-ng.</li><li><strong>outputs.conf:</strong> Defines where to send the collected data. This can be a single indexer or a load-balanced group of indexers in a cluster. SSL should be enabled to secure data in transit.</li></ul><p><strong>Centralized Management with a Deployment Server</strong> A Deployment Server allows administrators to distribute and manage configurations (apps) for a fleet of Universal Forwarders.</p><ol><li><strong>App Packaging:</strong> Configurations (inputs.conf, outputs.conf, etc.) are packaged into &quot;deployment apps&quot; and placed in $SPLUNK_HOME/etc/deployment-apps on the Deployment Server.</li><li><strong>Server Classes:</strong> serverclass.conf is used to group forwarder clients based on hostname, IP address, or other criteria using whitelists and blacklists.</li><li><strong>Client Configuration:</strong> Each forwarder’s deploymentclient.conf points it to the Deployment Server to receive its designated apps.</li></ol><h4>Part 3: Searching and Reporting</h4><p>The primary interface for data analysis is the Search &amp; Reporting app in Splunk Web.</p><p><strong>The Splunk Search Interface</strong></p><ul><li><strong>Search Bar:</strong> Where you write SPL queries.</li><li><strong>Time Range Picker:</strong> Crucial for scoping searches to a specific timeframe to improve performance.</li><li><strong>Search Modes:</strong></li><li><strong>Fast:</strong> Fastest mode; only extracts fields necessary for the search.</li><li><strong>Smart:</strong> Default mode; balances speed and field discovery.</li><li><strong>Verbose:</strong> Slowest mode; discovers all possible fields in the event data.</li><li><strong>Job Inspector:</strong> A diagnostic tool that provides details on search execution costs, helping to identify performance bottlenecks.</li></ul><p><strong>SPL (Search Processing Language) Fundamentals</strong> SPL queries are built by chaining commands with a pipe (|) character.</p><ul><li><strong>Syntax:</strong> search &lt;keywords&gt; | command1 [options] | command2 [options] ...</li><li><strong>Filtering:</strong> Use keywords, boolean operators (AND, OR, NOT), and field-value pairs (e.g., status=404).</li><li><strong>Wildcards:</strong> Use the asterisk (*) to match multiple characters (e.g., event_code=5*).</li></ul><p><strong>Practical Linux-Oriented Search Scenarios</strong></p><ul><li><strong>Find system log errors:</strong> sourcetype=&quot;linux_messages&quot; (error OR failed OR warn)</li><li><strong>Analyze SSH login failures:</strong> source=&quot;/var/log/auth.log&quot; &quot;Failed password&quot; | rex &quot;for (?&lt;user&gt;\S+) from (?&lt;src_ip&gt;\S+)&quot; | top user, src_ip</li><li><strong>Monitor top denied IPs from </strong><strong>iptables logs:</strong> sourcetype=&quot;linux:netfilter&quot; action=&quot;DENY&quot; | top 10 src_ip</li></ul><p><strong>Creating Reports, Dashboards, and Alerts</strong></p><ul><li><strong>Reports:</strong> Any search can be saved as a report to be run again later.</li><li><strong>Dashboards:</strong> Reports can be added as panels to dashboards to create high-level views of key metrics.</li><li><strong>Alerts:</strong> Searches can be saved as alerts that trigger actions when certain conditions are met (e.g., more than 5 login failures in a minute). Actions can include sending an email or running a script.</li></ul><h3>Survey Note</h3><p>This section provides a more detailed breakdown of key components for advanced users and administrators.</p><p><strong>Advanced Configuration and Management</strong></p><p>Component Detailed Considerations <strong>Data Inputs</strong> <strong>File Monitoring (</strong><strong>monitor://):</strong> Use whitelists/blacklists to be specific. Avoid monitoring directories with thousands of frequently changing files. &lt;br&gt; <strong>Syslog:</strong> The best practice is to have rsyslog or syslog-ng write to a file, which the UF then monitors. This prevents data loss associated with direct UDP inputs. &lt;br&gt; <strong>HTTP Event Collector (HEC):</strong> Ideal for modern applications and serverless functions to send JSON-formatted data directly to Splunk via HTTP/S, bypassing the need for a forwarder. &lt;br&gt; <strong>Scripted Inputs:</strong> Use for collecting data from sources without log files (e.g., APIs, command-line tools). Scripts are placed in an app&#39;s bin directory and scheduled via inputs.conf. <strong>Forwarder Outputs</strong> <strong>Load Balancing:</strong> When forwarding to multiple indexers, outputs.conf can be configured to automatically load balance data. The autoLBFrequency setting controls how often the forwarder switches indexers. &lt;br&gt; <strong>Indexer Acknowledgment (</strong><strong>useACK=true):</strong> Guarantees data delivery by requiring the indexer to acknowledge receipt of each data block. This introduces a performance overhead and should be used only when data loss is unacceptable. &lt;br&gt; <strong>Persistent Queues:</strong> Newer Splunk versions can write queues to disk, preventing data loss if the forwarder is restarted. <strong>Security</strong> <strong>SSL/TLS for Forwarding:</strong> Securing the connection between forwarders and indexers is critical. This involves generating certificates, configuring outputs.conf on the forwarder (useSSL=true, sslRootCAPath, etc.), and inputs.conf on the indexer to handle splunktcp-ssl traffic. &lt;br&gt; <strong>Secret Rotation:</strong> The splunk.secret file encrypts sensitive data in configuration files. It should be rotated periodically according to your organization&#39;s security policy.</p><p><strong>Search Performance Optimization</strong></p><p>Optimizing searches is essential for a responsive Splunk environment, especially with large data volumes.</p><p>Technique Description <strong>Time Range</strong> The most effective optimization. Always narrow the time range as much as possible. <strong>Index and Source</strong> Always specify the index, source, and sourcetype to limit the data Splunk must search through. <strong>Streaming vs. Transforming</strong> Use streaming commands (e.g., search, where, rex, fields) early in your search pipeline. These run on the indexers. Transforming commands (e.g., stats, timechart, top, rare) run on the search head and should be used after data is filtered. <strong>tstats Command</strong> Use tstats instead of stats for extremely fast queries on indexed fields, metadata, or accelerated data models. It does not search raw data. <strong>Summary Indexing</strong> Create scheduled searches that pre-calculate results and save them to a separate, smaller &quot;summary&quot; index. Dashboards can then query this smaller index for near-instant results. <strong>Macros</strong> Encapsulate long or complex sections of SPL into reusable macros. This improves readability and maintainability.</p><p><strong>Comprehensive Troubleshooting</strong></p><p>Issue Area Diagnostic Steps &amp; Solutions <strong>Installation Fails</strong> Installation Check for missing library dependencies (libaio, libncurses5). Ensure user limits (ulimit) for nofile and nproc are set high enough for the splunk user. Verify sufficient disk space and correct permissions on /opt/splunk. <strong>Forwarder Not Connecting</strong> Forwarder Use netstat or telnet to verify connectivity to the indexer on port 9997 and to the deployment server on port 8089. Check firewalls on all hosts. Review $SPLUNK_HOME/var/log/splunk/splunkd.log for connection errors. Use splunk list forward-server to check status. <strong>Data Not Appearing</strong> Data Ingestion On the forwarder, use splunk btool inputs list --debug to verify the configuration is correct and not overridden. Check file permissions to ensure the splunk user can read the monitored files. On the indexer, search the _internal index for ingestion errors. <strong>Search is Slow</strong> Searching Use the <strong>Job Inspector</strong> to identify which part of the search is taking the most time. Refine the query to be more specific (index, time range). Avoid leading wildcards (*foo). Convert transforming searches on popular dashboards to use summary indexing or acceleration. <strong>License Violations</strong> Licensing Use the monitoring console or run a search on the _internal index to identify which sources are consuming the most license volume: `index=_internal source=<em>license_usage.log</em> type=RolloverSummary</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c93db96a31c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I started my first bug bounty today.]]></title>
            <link>https://medium.com/@jeremydickey/i-started-my-first-bug-bounty-today-0496d7d05828?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/0496d7d05828</guid>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sat, 31 Aug 2024 04:25:43 GMT</pubDate>
            <atom:updated>2024-08-31T04:25:43.815Z</atom:updated>
            <content:encoded><![CDATA[<p>I started my first bug bounty today.</p><p>I was stopped by the companies IDS/IPS!</p><p>It was actually pretty fun and I’m pretty happy the company stopped my xss so fast by blocking my ip and disallowing my vpn traffic.</p><p>I’ll set up a virtual attack box later and come back for more!</p><p>I’ve been bitten by the bug bounty bug and there’s no going back!</p><p>Thanks for reading.</p><p>If you need a website developed or want me to test your security please reach out.</p><p>You can schedule a call on my site <a href="https://www.jeremypdickey.com/">jeremypdickey.com</a></p><p>Or find me on Twitter</p><p>@jeremypdickey</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0496d7d05828" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to post to medium automatically with React app]]></title>
            <link>https://medium.com/@jeremydickey/how-to-post-to-medium-automatically-with-react-app-2b88115e6b8e?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b88115e6b8e</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 06:38:26 GMT</pubDate>
            <atom:updated>2024-04-27T06:38:26.252Z</atom:updated>
            <content:encoded><![CDATA[<h3>Step 1: Set Up a Claude Account and Get API Key</h3><p>1. Sign up for a Claude account on their website.<br>2. Once signed up, navigate to your account settings to obtain your API key.</p><h3>Step 2: Create a React App</h3><p>1. Set up a new React app using Create React App or any other method of your choice.</p><h3>Step 3: Frontend Development</h3><p>1. Design a user interface where users can input the article content and schedule posting time.<br>2. Utilize form components to capture article content and schedule time.</p><h3>Step 4: Backend Development with Python</h3><p>1. Develop a Python script that interacts with Claude API to post articles to Medium.</p><p>2. Use the requests library to make HTTP requests to Claude API.</p><h3>Step 5: Integration</h3><p>1. Connect your React frontend with the Python backend.</p><p>2. Use Axios or Fetch API to send data from the React app to the Python script.</p><p>3. Ensure proper error handling and validation in both frontend and backend.</p><h3>Step 6: Automation</h3><p>1. Use a scheduler library like APScheduler in Python to schedule the script to run daily at 12 PM CST.</p><p>2. Deploy your Python script to a server or use a cloud service like AWS Lambda to run it.</p><h3>Step 7: Testing and Deployment</h3><p>1. Test your application thoroughly to ensure it works as expected.</p><p>2. Deploy your React app to a hosting service like Vercel or Netlify.</p><p>3. Deploy your Python script to a server or a cloud service.</p><h3>Example Workflow:</h3><p>1. User fills out the article content and schedules the posting time in the React app.</p><p>2. React app sends the data to the Python backend.</p><p>3. Python backend receives the data, formats it, and sends a request to Claude API to post the article to Medium.</p><p>4. The Python script runs daily at 12 PM CST using a scheduler library.</p><p>5. Articles are automatically posted to Medium daily at the scheduled time.</p><h3>Considerations:</h3><p>- Ensure proper error handling and validation to handle any issues that may arise during the posting process.</p><p>- Respect Medium&#39;s terms of service and posting guidelines to avoid any issues with your account.</p><p>- Securely store API keys and sensitive information to prevent unauthorized access.</p><p>By following these steps and considerations, you can build a small React app that allows users to automatically post articles to Medium daily using Python and Claude API.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b88115e6b8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scraping Emails from Websites Using Python Based on Keywords: A Comprehensive Guide]]></title>
            <link>https://medium.com/@jeremydickey/scraping-emails-from-websites-using-python-based-on-keywords-a-comprehensive-guide-89f219c5bfdb?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/89f219c5bfdb</guid>
            <category><![CDATA[beautifulsoup]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[python-programming]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 06:27:49 GMT</pubDate>
            <atom:updated>2024-04-27T06:27:49.536Z</atom:updated>
            <content:encoded><![CDATA[<p>In today&#39;s digital world, email remains a powerful tool for communication and marketing.</p><p>However, building an email list can be time-consuming and challenging.</p><p>Fortunately, Python provides powerful tools for web scraping, allowing you to automate the process of extracting emails from websites based on specific keywords.</p><p>In this article, we&#39;ll explore how to scrape emails from websites using Python, focusing on intervals based on keywords.</p><h3>Prerequisites</h3><p>Before we get started, ensure you have the following prerequisites:</p><p>1. Python:</p><p>Make sure Python is installed on your system.</p><p>2. Beautiful Soup:</p><p>Install the Beautiful Soup library, which is a Python library for pulling data out of HTML and XML files.</p><p>You can install it using pip:</p><p>```bash<br>pip install beautifulsoup4<br>```</p><p>3. Requests:</p><p>Install the Requests library, which is an elegant and simple HTTP library for Python. You can install it using pip:</p><p>```bash<br>pip install requests<br>```</p><h3>Step 1: Identify Target Websites</h3><p>First, identify the websites from which you want to scrape emails. These could be business directories, forums, or any other sources relevant to your target audience.</p><h3>Step 2: Define Keywords</h3><p>Next, define the keywords that are relevant to the type of emails you&#39;re looking to scrape. These keywords will be used to filter the content of the web pages and extract emails that match the criteria.</p><h3>Step 3: Write the Python Script</h3><p>Now, let&#39;s write the Python script to scrape emails from websites based on the defined keywords. Here&#39;s a basic example using Beautiful Soup and Requests libraries:</p><p>```python<br>import requests<br>from bs4 import BeautifulSoup<br>import re</p><p>def scrape_emails(url, keywords):<br> response = requests.get(url)<br> soup = BeautifulSoup(response.text, &#39;html.parser&#39;)<br> emails = set()</p><p>for keyword in keywords:<br> matches = soup.find_all(string=re.compile(keyword, flags=re.IGNORECASE))<br> for match in matches:<br> email = re.findall(r&#39;\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b&#39;, match)<br> if email:<br> emails.update(email)</p><p>return emails</p><p>url = &#39;https://example.com&#39;<br>keywords = [&#39;contact&#39;, &#39;info&#39;, &#39;email&#39;]</p><p>emails = scrape_emails(url, keywords)<br>for email in emails:<br> print(email)<br>```</p><h3>Step 4: Set Interval and Automate</h3><p>To scrape emails at regular intervals based on keywords, you can integrate the script into a loop with a delay using Python&#39;s `time.sleep()` function. Here&#39;s a modified version of the script to scrape emails at intervals:</p><p>```python<br>import time</p><p>while True:<br> emails = scrape_emails(url, keywords)<br> for email in emails:<br> print(email)<br> <br> # Set the interval (in seconds)<br> time.sleep(3600) # Scrapes emails every hour<br>```</p><h3>Recap</h3><p>Scraping emails from websites using Python based on keywords can be a powerful way to build an email list for marketing or research purposes.</p><p>However, it&#39;s essential to respect the website&#39;s terms of service and ensure compliance with relevant laws and regulations, such as GDPR.</p><p>With the right approach and tools, you can automate the process of gathering valuable email contacts efficiently.</p><p>Happy scraping!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89f219c5bfdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating Zoom Meetings with Python: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@jeremydickey/automating-zoom-meetings-with-python-a-step-by-step-guide-7816b7a23466?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7816b7a23466</guid>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 06:22:47 GMT</pubDate>
            <atom:updated>2024-04-27T06:22:47.665Z</atom:updated>
            <content:encoded><![CDATA[<p>In today&#39;s digital age, automation is becoming increasingly essential to streamline tasks and save time.</p><p>One area where automation can greatly benefit is in managing Zoom meetings.</p><p>By leveraging the power of Python programming language and Zoom’s API, you can automate various aspects of scheduling, managing participants, and sending reminders for your Zoom meetings.</p><p>In this article, we’ll explore how to automate Zoom meetings using Python.</p><h3>Step 1: Install Required Libraries</h3><p>Start by installing the `requests` library, which will be used to make HTTP requests to the Zoom API. You can install it using pip:</p><p>```bash<br>pip install requests<br>```</p><h3>Step 2: Authenticate with Zoom API</h3><p>To authenticate with the Zoom API, you&#39;ll need your API key and API secret. Once you have these credentials, you can make requests to the Zoom API endpoints. Here&#39;s a basic example of how to authenticate:</p><p>```python<br>import requests</p><p>api_key = &#39;YOUR_API_KEY&#39;<br>api_secret = &#39;YOUR_API_SECRET&#39;</p><p>def generate_token(api_key, api_secret):<br> url = f&#39;https://api.zoom.us/v2/users/{api_key}/token?type=zak&#39;<br> response = requests.post(url, headers={&#39;Authorization&#39;: f&#39;Bearer {api_secret}&#39;})<br> return response.json()[&#39;token&#39;]</p><p>token = generate_token(api_key, api_secret)<br>```</p><h3>Step 3: Schedule a Zoom Meeting</h3><p>Now that you&#39;re authenticated, you can start scheduling meetings using the Zoom API. Here&#39;s how you can create a new meeting:</p><p>```python<br>def schedule_meeting(token, topic, start_time, duration):<br> url = &#39;https://api.zoom.us/v2/users/me/meetings&#39;<br> headers = {<br> &#39;Authorization&#39;: f&#39;Bearer {token}&#39;,<br> &#39;Content-Type&#39;: &#39;application/json&#39;<br> }<br> data = {<br> &#39;topic&#39;: topic,<br> &#39;type&#39;: 2,<br> &#39;start_time&#39;: start_time,<br> &#39;duration&#39;: duration<br> }<br> response = requests.post(url, json=data, headers=headers)<br> return response.json()</p><p>meeting_info = schedule_meeting(token, &#39;Python Automation Meeting&#39;, &#39;2024-04-28T10:00:00Z&#39;, 60)<br>print(&quot;Meeting ID:&quot;, meeting_info[&#39;id&#39;])<br>```</p><h3>Step 4: Automate Meeting Invitations and Reminders</h3><p>You can also automate sending meeting invitations and reminders to participants using Python&#39;s `smtplib` module for email sending. Here&#39;s a basic example:</p><p>```python<br>import smtplib<br>from email.mime.text import MIMEText</p><p>def send_email(sender_email, sender_password, recipient_email, subject, message):<br> msg = MIMEText(message)<br> msg[&#39;Subject&#39;] = subject<br> msg[&#39;From&#39;] = sender_email<br> msg[&#39;To&#39;] = recipient_email</p><p>server = smtplib.SMTP(&#39;smtp.gmail.com&#39;, 587)<br> server.starttls()<br> server.login(sender_email, sender_password)<br> server.sendmail(sender_email, recipient_email, msg.as_string())<br> server.quit()</p><p>sender_email = &#39;your_email@gmail.com&#39;<br>sender_password = &#39;your_password&#39;<br>recipient_email = &#39;recipient_email@example.com&#39;<br>subject = &#39;Zoom Meeting Reminder&#39;<br>message = &#39;Don&#39;t forget about our Zoom meeting tomorrow at 10:00 AM.&#39;</p><p>send_email(sender_email, sender_password, recipient_email, subject, message)<br>```</p><p>That’s all!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7816b7a23466" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automate daily email reports in Python]]></title>
            <link>https://medium.com/@jeremydickey/automate-daily-email-reports-in-python-dbd3d9dc5842?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbd3d9dc5842</guid>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 06:18:14 GMT</pubDate>
            <atom:updated>2024-04-27T06:18:14.398Z</atom:updated>
            <content:encoded><![CDATA[<p>You can easily automate sending daily email reports in Python using the `smtplib` and `email` libraries:</p><p>```python<br>import smtplib<br>from email.mime.text import MIMEText<br>from email.mime.multipart import MIMEMultipart<br>import datetime</p><p>def send_email(subject, message, from_email, to_email, smtp_server, smtp_port, smtp_username, smtp_password):<br> msg = MIMEMultipart()<br> msg[&#39;From&#39;] = from_email<br> msg[&#39;To&#39;] = to_email<br> msg[&#39;Subject&#39;] = subject</p><p>msg.attach(MIMEText(message, &#39;plain&#39;))</p><p>server = smtplib.SMTP(smtp_server, smtp_port)<br> server.starttls()<br> server.login(smtp_username, smtp_password)<br> server.sendmail(from_email, to_email, msg.as_string())<br> server.quit()</p><p># Example usage:<br>subject = &quot;Daily Report - &quot; + datetime.datetime.now().strftime(&quot;%Y-%m-%d&quot;)<br>message = &quot;This is your daily report.&quot;<br>from_email = &quot;your_email@example.com&quot;<br>to_email = &quot;recipient@example.com&quot;<br>smtp_server = &quot;smtp.example.com&quot;<br>smtp_port = 587<br>smtp_username = &quot;your_username&quot;<br>smtp_password = &quot;your_password&quot;</p><p>send_email(subject, message, from_email, to_email, smtp_server, smtp_port, smtp_username, smtp_password)<br>```</p><p>Setup is super simple.</p><h3>Install necessary libraries</h3><p>First, you need to install the `smtplib` and `email` libraries if you haven’t already. You can do this using pip:</p><p>```<br> pip install secure-smtplib<br> ```</p><h3>Configure email parameters</h3><p>Fill in the `subject`, `message`, `from_email`, `to_email`, `smtp_server`, `smtp_port`, `smtp_username`, and `smtp_password` variables with your email details.</p><h3>Set up email server</h3><p>Make sure you have access to an SMTP server. If you’re using Gmail, you might need to allow less secure apps or set up an app-specific password.</p><h3>Run the script daily</h3><p>You can use a task scheduler like cron (on Unix-based systems) or Task Scheduler (on Windows) to run the script daily at a specific time.</p><p>For example, on Unix systems, you can open your crontab file by running:</p><p>```<br> crontab -e<br> ```</p><p>Then add a line like this to run the script every day at 8:00 AM:</p><p>```<br> 0 8 * * * /usr/bin/python3 /path/to/your/script.py<br> ```</p><p>Make sure to replace `/usr/bin/python3` and `/path/to/your/script.py` with the correct path to your Python interpreter and script file, respectively.</p><h3>Testing</h3><p>Before setting up the scheduler, make sure to test the script to ensure it sends emails correctly.</p><p>Once everything is set up, your daily email reports will be sent automatically!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbd3d9dc5842" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Claude API Versions]]></title>
            <link>https://medium.com/@jeremydickey/understanding-claude-api-versions-c5b45f947ad8?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5b45f947ad8</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[anthropics]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 05:55:42 GMT</pubDate>
            <atom:updated>2024-04-27T05:55:42.371Z</atom:updated>
            <content:encoded><![CDATA[<p>Claude API serves as a bridge between React applications and external data sources, enabling developers to fetch, manipulate, and display data seamlessly.</p><p>As Claude API evolves, new versions are released with updated features, improvements, and sometimes breaking changes.</p><p>Understanding the differences between these versions is crucial for developers to leverage the full potential of Claude API in their React applications.</p><h3>Integrating Claude API v1 in React</h3><p>To integrate Claude API v1 into a React application, developers need to first obtain an API key from the Claude API website.</p><p>Once authenticated, they can make HTTP requests to retrieve data from the API endpoints.</p><p>Here’s a basic example of fetching data using Claude API v1 in a React component:</p><p>import React, { useState, useEffect } from &#39;react’;<br>import axios from &#39;axios’;</p><p>const MyComponent = () =&gt; {<br> const [data, setData] = useState([]);</p><p>useEffect(() =&gt; {<br> const fetchData = async () =&gt; {<br> try {<br> const response = await axios.get(&#39;https://api.claudeapi.com/v1/data&#39;);<br> setData(response.data);<br> } catch (error) {<br> console.error(&#39;Error fetching data:&#39;, error);<br> }<br> };</p><p>fetchData();<br> }, []);</p><p>return (<br> &lt;div&gt;<br> {data.map(item =&gt; (<br> &lt;div key={item.id}&gt;{item.name}&lt;/div&gt;<br> ))}<br> &lt;/div&gt;<br> );<br>};</p><p>export default MyComponent;</p><p>This example demonstrates fetching data from the Claude API v1 endpoint and rendering it in a React component.</p><h3>Upgrading to Claude API v2Claude</h3><p>API v2 introduces several improvements over v1, including enhanced performance, additional endpoints, and better error handling.</p><p>To upgrade from v1 to v2, developers need to modify their API requests and adapt to any breaking changes.</p><p>Here’s an example of migrating the previous code to use Claude API v2:// Update the API endpoint to v2<br>const response = await axios.get(’https://api.claudeapi.com/v2/data’);</p><p>Additionally, developers can take advantage of new features introduced in v2, such as pagination or filtering, to further optimize their data fetching process.</p><h3>Leveraging Claude API v3 for Advanced Functionality</h3><p>With Claude API v3, developers can unlock advanced functionality and customization options to tailor their API requests to specific requirements.</p><p>This version may introduce significant changes or additions, so developers should carefully review the documentation and update their code accordingly.</p><p>Here’s an example of integrating Claude API v3 into a React application:</p><p>// Update the API endpoint to v3<br>const response = await axios.get(’https://api.claudeapi.com/v3/data’, {<br> params: {<br> // Add custom query parameters if needed<br> sortBy: &#39;date’,<br> limit: 10<br> }<br>});</p><p>Developers can explore new features like real-time updates or GraphQL support to enhance their React applications further.Section</p><h3>Best Practices for Optimizing Claude API Usage in React</h3><p>Optimizing Claude API usage in React involves several best practices to ensure efficient data fetching, minimal latency, and robust error handling.</p><p>Developers should implement strategies such as caching frequently accessed data, minimizing unnecessary API calls, and implementing proper error handling mechanisms.</p><p>Additionally, considering factors like authentication, security, and data validation are essential for building reliable React applications with Claude API integration.</p><p>For more info refer to Claude documentation and stack overflow for bugs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5b45f947ad8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating Connection Requests to Recruiters on LinkedIn Using Python: A Practical Guide]]></title>
            <link>https://medium.com/@jeremydickey/automating-connection-requests-to-recruiters-on-linkedin-using-python-a-practical-guide-5d625b80576b?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d625b80576b</guid>
            <category><![CDATA[python-automation]]></category>
            <category><![CDATA[linkedin-auto-connect]]></category>
            <category><![CDATA[linkedin-automation-tool]]></category>
            <category><![CDATA[linkedin-automation]]></category>
            <category><![CDATA[linkedintips]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Fri, 12 Apr 2024 13:36:51 GMT</pubDate>
            <atom:updated>2024-04-27T05:59:15.927Z</atom:updated>
            <content:encoded><![CDATA[<p>LinkedIn has emerged as a powerful platform for professionals to connect, network, and explore career opportunities.</p><p>For job seekers, establishing connections with recruiters can be instrumental in accessing job openings and advancing their careers.</p><p>However, manually sending connection requests to recruiters can be time-consuming and inefficient.</p><p>In this article, we’ll explore how to automate the process of connecting with recruiters on LinkedIn using Python.</p><h3>Prerequisites:</h3><p>Before we begin, ensure you have the following prerequisites:<br>- Python installed on your system<br>- Basic understanding of Python programming<br>- LinkedIn account</p><h3>Install Required Libraries</h3><p>We’ll be using the `Selenium` library to automate interactions with the LinkedIn website. Install it along with the `webdriver_manager` library, which helps manage browser drivers.</p><p>```bash<br>pip install selenium webdriver_manager<br>```</p><h3>Setting Up Selenium WebDriver</h3><p>We’ll use the Chrome WebDriver for this tutorial. Ensure you have Google Chrome installed on your system.</p><p>Then, initialize the WebDriver in your Python script.</p><p>```python<br>from selenium import webdriver<br>from webdriver_manager.chrome import ChromeDriverManager</p><p>driver = webdriver.Chrome(ChromeDriverManager().install())<br>```</p><h3>Automating LinkedIn Login</h3><p>Use Selenium to automate the login process to your LinkedIn account.</p><p>```python<br>driver.get(‘<a href="https://www.linkedin.com/login&#39;">https://www.linkedin.com/login&#39;</a>)<br>username = driver.find_element_by_id(‘username’)<br>password = driver.find_element_by_id(‘password’)</p><p>username.send_keys(‘YourEmailAddress’)<br>password.send_keys(‘YourPassword’)</p><p>driver.find_element_by_xpath(“//button[<a href="http://twitter.com/type">@type</a>=’submit’]”).click()<br>```</p><h3>Searching for Recruiters</h3><p>Define a search query to find recruiters based on location, industry, or specific keywords.</p><p>```python<br>search_query = “Recruiter at [YourTargetCompany]”</p><p>search_box = driver.find_element_by_xpath(“//input[<a href="http://twitter.com/aria">@aria</a>-label=’Search’]”)<br>search_box.clear()<br>search_box.send_keys(search_query)<br>search_box.send_keys(Keys.RETURN)<br>```</p><h3>Sending Connection Requests</h3><p>Loop through the search results and send connection requests to recruiters.</p><p>```python<br>time.sleep(5) # Wait for search results to load<br>connect_buttons = driver.find_elements_by_xpath(“//button[<a href="http://twitter.com/aria">@aria</a>-label=’Connect’]”)<br>for button in connect_buttons:<br> button.click()<br> time.sleep(2) # Wait before sending next request<br>```</p><h3>Handling Captcha</h3><p>LinkedIn may prompt for a captcha verification. You can handle it manually or use third-party captcha solving services.</p><h3>Close the WebDriver</h3><p>Once the process is complete, close the WebDriver instance.</p><p>```python<br>driver.quit()<br>```</p><p>Follow me on LinkedIn: <a href="https://www.linkedin.com/in/jeremy-dickey/">https://www.linkedin.com/in/jeremy-dickey/</a><br>Contact me for projects: <a href="https://www.jeremypdickey.com/">https://www.jeremypdickey.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d625b80576b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring the Best AI Extensions for Visual Studio Code]]></title>
            <link>https://medium.com/@jeremydickey/exploring-the-best-ai-extensions-for-visual-studio-code-3adb65861408?source=rss-65d3f35804d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3adb65861408</guid>
            <category><![CDATA[vs-code-editor]]></category>
            <category><![CDATA[ai-extensions]]></category>
            <category><![CDATA[vs-code-extensions]]></category>
            <category><![CDATA[open-ai-api]]></category>
            <category><![CDATA[ai-experts]]></category>
            <dc:creator><![CDATA[Jeremy Dickey]]></dc:creator>
            <pubDate>Wed, 10 Apr 2024 13:32:02 GMT</pubDate>
            <atom:updated>2024-04-27T06:01:40.937Z</atom:updated>
            <content:encoded><![CDATA[<p>**Introduction:**<br>In today’s fast-paced world, developers are constantly seeking ways to enhance their productivity and streamline their workflows. With the rise of artificial intelligence (AI) technologies, integrating AI into development tools has become increasingly prevalent. Visual Studio Code (VS Code), a popular code editor, offers a vast array of extensions, including those leveraging AI capabilities. In this article, we’ll delve into some of the best AI extensions for VS Code that can supercharge your development experience.</p><h3>1. TabNine:</h3><p>TabNine is an AI-powered code completion extension for VS Code that uses machine learning models to provide highly accurate code suggestions.</p><p>It learns from your coding patterns and context to offer intelligent completions, significantly speeding up your coding process.</p><p>With support for multiple programming languages, TabNine can boost your productivity regardless of the technology stack you’re working with.</p><h3>Kite</h3><p>Kite takes AI-powered code completion to the next level by offering not just completions but also contextually relevant documentation and examples directly within your editor.</p><p>It provides real-time code snippets, function signatures, and documentation for Python, JavaScript, TypeScript, Go, and more.</p><p>Kite’s deep learning models analyze code from millions of open-source projects to deliver precise and helpful suggestions, making it an invaluable tool for developers.</p><h3>IntelliCode</h3><p>IntelliCode, developed by Microsoft, enhances the built-in IntelliSense feature of VS Code with AI capabilities.</p><p>It leverages machine learning to prioritize and suggest code completions based on your coding patterns and the specific context of your project.</p><p>IntelliCode supports various programming languages and frameworks, helping you write code faster and with fewer errors. It adapts to your coding style over time, becoming more accurate as you use it.</p><h3>Codota</h3><p>Codota is an AI-powered autocomplete extension that offers intelligent code suggestions and real-time error detection for Java and JavaScript.</p><p>It analyzes millions of code repositories to provide contextually relevant completions, saving you time and reducing coding errors.</p><p>Codota also provides inline documentation, helping you understand APIs and libraries more effectively as you code.</p><h3>DeepCode</h3><p>DeepCode uses AI to perform static code analysis and offer intelligent suggestions to improve your code quality and security.</p><p>It detects bugs, vulnerabilities, and anti-patterns in your code, providing actionable insights to help you write cleaner and more secure code.</p><p>DeepCode supports multiple programming languages, including JavaScript, Python, Java, and TypeScript, making it suitable for a wide range of projects.</p><p>Follow me on LinkedIn: <a href="https://www.linkedin.com/in/jeremy-dickey/">https://www.linkedin.com/in/jeremy-dickey/</a><br>Contact me for projects: <a href="https://www.jeremypdickey.com/">https://www.jeremypdickey.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3adb65861408" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>