Close
0%
0%

Headless Bluesky OSINT Radar

Collecting public Bluesky posts for select keywords, storing metadata in SQLite and generating daily reports for analysis on Linux Mint.

Similar projects worth following
0 followers
A project for collecting, storing and analyzing public Bluesky activity around selected keywords. The goal is to build a small, reliable, always-on backend appliance which quietly gathers social signals over time. The Linux Mint machine acts as a headless collection node for polling the ATProto API for chosen topics, normalizing the results, storing useful metadata in SQLite and generating regular reports for later analysis. Each collector run will also be logged so the project can track uptime, failures, duplicates and collection volume over time.

A Linux Mint-based backend appliance for collecting, storing and analyzing Bluesky activity around selected keywords. The project is designed to run continuously as a headless collection node, gathering activity over time from the ATProto ecosystem and preserving them in a local SQLite database for later analysis.

At its core, the system polls the ATProto API for chosen topics, processes the returned posts and stores useful information such as text content, handles, engagement, keywords and response data. Each run is logged so the appliance can track not only what it collected, but also how reliably the device operated. This includes timestamps, success or failure states, duplicates, inserted records, total volume and errors.

The goal is to build a small, reliable social signal collection appliance operating independently on a local network. Rather than depending on an external analytics platform, the project emphasizes simplicity and transparency; a Linux Mint machine, Flask API, SQLite database and scheduled collection.

This project is especially useful for long-term observation of public conversation patterns. By collecting posts containing particular keywords over months, the system can support later analysis of topics, authors, engagement, trends, health and changes in public interest. The stored data will eventually be exported into reports and frontend D3.js graphics.

The project is intentionally built in phases. The first phase focuses on data collection and storage. The second phase adds automation, uptime tracking and regular report generation. Later phases include dashboards, trend detection, comparisons, frequency analysis and data exports.

  • Removed Original Project Files From Raspberry Pi 5 Computer

    Bret Bernhoft4 days ago 0 comments

    Today’s progress focused on removing my first attempt at developing this application on a Raspberry Pi 5, while confirming the existing Pi-hole installation remained healthy and unaffected.

    The first step was to verify whether any application databases still existed on the RPi 5 system. A search was run for common SQLite database file types. The results showed several databases including Pi-hole databases, Mesa graphics cache files, Linux system databases and Docker metadata. None of these were related to the deleted project, so no unnecessary database files were removed.

    Next, systemd services were reviewed to identify anything running from the old application. This revealed the Headless Bluesky OSINT Radar service was still installed and active. The service definition was inspected, indicating the presence of the original project directory, a related Python virtual environment, a loaded .env file and app.py script. This confirmed the exact project path and service file needing to be removed.

    The cleanup plan included stopping and disabling the systemd service, deleting the service file, reloading systemd and removing the remaining project directory. Additional commands were used to check for any leftover files, running processes, Docker containers and Docker volumes from the old project.

    After completely removing the old application, Pi-hole was checked to ensure the Raspberry Pi’s DNS filtering service was still functioning correctly. The service was confirmed to be active and running. A DNS test also returned a successful response, confirming the local DNS resolution through Pi-hole was working properly.

    Moving forward, instead of using a Raspberry Pi 5 computer, this project is utilizing a Linux Mint machine. Which will be documented in future log entries and project details.

View project log

Enjoy this project?

Share

Discussions

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates