Blogger Describes Effort That Led to Removal of Over 300 Tor Exit Nodes

·1 views

A post on kaba.cx describes how the author got more than 300 Tor exit nodes removed. The article was shared on Hacker News, where it received 25 points and 5 comments. The source text provided is only metadata, so the specific methods, parties involved, and reasons for the removals cannot be confirmed from it. Readers would need to consult the original post for details on the process and its outcome.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer's self-scan finds own repo still on retiring macos-14 runner image

On October 19, GitHub began rolling the ubuntu-latest label to Ubuntu 26.04 and started a first brownout of the macos-14 image ahead of its November 2 retirement. The author ran their RunnerDriftAudit scanner on five repositories and found eleven high-severity floating or retired runner labels, including one iOS project still pinned to macos-14. Switching that workflow to macos-15 fixed it, with CI passing on the new image the same morning. The author deliberately left other floating labels in place where they serve as intentional tests, and noted that unpinned actions/checkout@v4 references remain unfixed. The scanner is a free, open-source, single-file Python tool.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Deleted Open Files Keep Disk Space Until the Writing Process Exits

A cleanup that removes camera clips can leave disk usage unchanged if a process still holds one of the files open. On Linux, removing a name does not release the space while a file descriptor remains open. In tests on ext4 using a stand-in recorder, a deleted 200 MiB file kept its space allocated until the writing process exited. The author found the process with lsof and /proc, and noted that truncating the file through /proc freed space but left the writer with a sparse file. The behavior matches the unlink(2) documentation, which keeps the file in existence until the last descriptor closes.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

SlothCommit uses a local 1B Gemma model to draft commit messages and weekly changelogs

A CS student built SlothCommit, a tool that uses Gemma 3 1B running locally through llama.cpp to write Conventional Commit messages from staged diffs. The sloth commit command asks for confirmation before committing, while sloth week compiles the past seven days of commits into a grouped changelog with a short summary. A git hook option fills in messages automatically and steps aside if the model is unavailable. The project requires no API key or account, and code never leaves the user's machine. The author notes the model's output is a first draft that can fall short, and the tool's own commit history was written with it.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Spreadsheet Method Groups Orders by Customer to Spot Repeat and Lapsed Buyers

A guide explains how to turn a raw order list into a one-row-per-customer summary using standard spreadsheet formulas instead of a pivot table. It covers totals, order counts, first and last order dates, and days since the last purchase, with classifications for one-time, repeat, and lapsed customers. The method includes a reconciliation check that flags orders from customers missing from the list, which would otherwise go unnoticed. MINIFS and MAXIFS require Excel 2019, Microsoft 365, or Google Sheets, while the other formulas work in any version. The author tested the formulas in LibreOffice Calc on sample data rather than in the other spreadsheet programs.

0 comments Read more at DEV Community