HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
zolagonano
a-ninjas-handbook
JavaScript2024–2024
zolagonano / a-ninjas-handbook

a-ninjas-handbook

A Ninja's Handbook: A book on privacy, security, and anonymity online.

2Distinct people
2Mentions
0Explicit recommenders
94GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A Ninja's Handbook: A book on privacy, security, and anonymity online.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval2 dated mentions

Observed mentions: 2024-08-16 07:12:23 UTC to 2024-08-18 21:42:12 UTC.

012024-08-16 06:00:00 UTC to 2024-08-16 09:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 16, 06:002024-08-16 09:00:00 UTC to 2024-08-16 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-16 12:00:00 UTC to 2024-08-16 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-16 15:00:00 UTC to 2024-08-16 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-16 18:00:00 UTC to 2024-08-16 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-16 21:00:00 UTC to 2024-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-17 00:00:00 UTC to 2024-08-17 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-17 03:00:00 UTC to 2024-08-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-17 06:00:00 UTC to 2024-08-17 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-17 09:00:00 UTC to 2024-08-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-17 12:00:00 UTC to 2024-08-17 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 17, 12:002024-08-17 15:00:00 UTC to 2024-08-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-17 18:00:00 UTC to 2024-08-17 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-17 21:00:00 UTC to 2024-08-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 00:00:00 UTC to 2024-08-18 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 03:00:00 UTC to 2024-08-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 06:00:00 UTC to 2024-08-18 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 09:00:00 UTC to 2024-08-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 12:00:00 UTC to 2024-08-18 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 15:00:00 UTC to 2024-08-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 18:00:00 UTC to 2024-08-18 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-18 21:00:00 UTC to 2024-08-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 18, 21:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 16, 06:002024-08-16 06:00:00 UTC2024-08-16 09:00:00 UTC110
Aug 16, 09:002024-08-16 09:00:00 UTC2024-08-16 12:00:00 UTC000
Aug 16, 12:002024-08-16 12:00:00 UTC2024-08-16 15:00:00 UTC000
Aug 16, 15:002024-08-16 15:00:00 UTC2024-08-16 18:00:00 UTC000
Aug 16, 18:002024-08-16 18:00:00 UTC2024-08-16 21:00:00 UTC000
Aug 16, 21:002024-08-16 21:00:00 UTC2024-08-17 00:00:00 UTC000
Aug 17, 00:002024-08-17 00:00:00 UTC2024-08-17 03:00:00 UTC000
Aug 17, 03:002024-08-17 03:00:00 UTC2024-08-17 06:00:00 UTC000
Aug 17, 06:002024-08-17 06:00:00 UTC2024-08-17 09:00:00 UTC000
Aug 17, 09:002024-08-17 09:00:00 UTC2024-08-17 12:00:00 UTC000
Aug 17, 12:002024-08-17 12:00:00 UTC2024-08-17 15:00:00 UTC000
Aug 17, 15:002024-08-17 15:00:00 UTC2024-08-17 18:00:00 UTC000
Aug 17, 18:002024-08-17 18:00:00 UTC2024-08-17 21:00:00 UTC000
Aug 17, 21:002024-08-17 21:00:00 UTC2024-08-18 00:00:00 UTC000
Aug 18, 00:002024-08-18 00:00:00 UTC2024-08-18 03:00:00 UTC000
Aug 18, 03:002024-08-18 03:00:00 UTC2024-08-18 06:00:00 UTC000
Aug 18, 06:002024-08-18 06:00:00 UTC2024-08-18 09:00:00 UTC000
Aug 18, 09:002024-08-18 09:00:00 UTC2024-08-18 12:00:00 UTC000
Aug 18, 12:002024-08-18 12:00:00 UTC2024-08-18 15:00:00 UTC000
Aug 18, 15:002024-08-18 15:00:00 UTC2024-08-18 18:00:00 UTC000
Aug 18, 18:002024-08-18 18:00:00 UTC2024-08-18 21:00:00 UTC000
Aug 18, 21:002024-08-18 21:00:00 UTC2024-08-19 00:00:00 UTC101

What Hacker News says

2 sources
Well, I think a Tor hidden service is probably the ideal for hosting it. Making it so users have to go through that system rather than accessing it via the clearnet makes it less likely your adversary can easily figure out where it's hosted and who the hosting company is. I'd also recommend using a secure/disposal operating system like Tails, using the Tor browser with the default settings at all times, changing your writing style as much as possible and using an identity that's only used for the blog in question, and never used to access the clearnet/on any other service you can think of. Also, try and make sure the identity used is as plausible as possible. Maybe create a fake photo with AI and a fake but realistic sounding name and description to go with it, then use those to create a fake online footprint. An obvious pseudonym makes p
Read the rest
eople want to find out who it is, while a realistic name and identity makes them think they've identified the person behind it. But of course, it really all depends on who exactly your enemies are. Normal people and companies have a lot less in the way of resources for tracking someone down than government agencies. It takes a lot less opsec work to fool say, Burger King than it does the NSA. Funny enough, this guide that was posted a few days ago on Hacker News might be exactly what you need: https://github.com/zolagonano/a-ninjas-handbook
In Best way to set up a risky blog?
znano·Aug 16, 2024Submission

Show HN: A ninja's Handbook: A book on privacy, security, and anonymity online

This book was a project that I started after two years of constant paranoia and anxiety, trying to achieve a decent level of privacy and anonymity. From the things I learned during that time, I decided to write a book to help jump-start the privacy and anonymity journey of those who might be in the same situation. I know this book is not a complete guide on how to harden your devices and operating systems, and it wasn't meant to be. It was supposed to cover the very fundamentals of privacy, security, and anonymity rather than the highly technical stuff that might exhaust and frustrate normies. Repo: https://github.com/zolagonano/a-ninjas-handbook
127 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.