HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jwcrawley
uwho
HISTORICAL RECORD2015–2016
jwcrawley / uwho · Not publicly available

uwho

Discover this repository through its Hacker News conversations.

3Distinct people
10Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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 month10 dated mentions

Observed mentions: 2015-03-04 15:03:20 UTC to 2016-12-28 16:38:18 UTC.

01232015-03-01 00:00:00 UTC to 2015-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 20152015-04-01 00:00:00 UTC to 2015-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-01 00:00:00 UTC to 2015-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-01 00:00:00 UTC to 2015-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-07-01 00:00:00 UTC to 2015-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-08-01 00:00:00 UTC to 2015-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-01 00:00:00 UTC to 2015-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-01 00:00:00 UTC to 2015-11-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-11-01 00:00:00 UTC to 2015-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2016-02-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsJan 20162016-02-01 00:00:00 UTC to 2016-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-01 00:00:00 UTC to 2016-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-01 00:00:00 UTC to 2016-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-01 00:00:00 UTC to 2016-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-01 00:00:00 UTC to 2016-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-01 00:00:00 UTC to 2016-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-01 00:00:00 UTC to 2016-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-09-01 00:00:00 UTC to 2016-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-01 00:00:00 UTC to 2016-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-11-01 00:00:00 UTC to 2016-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-12-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsDec 2016

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
Mar 20152015-03-01 00:00:00 UTC2015-04-01 00:00:00 UTC101
Apr 20152015-04-01 00:00:00 UTC2015-05-01 00:00:00 UTC000
May 20152015-05-01 00:00:00 UTC2015-06-01 00:00:00 UTC000
Jun 20152015-06-01 00:00:00 UTC2015-07-01 00:00:00 UTC101
Jul 20152015-07-01 00:00:00 UTC2015-08-01 00:00:00 UTC101
Aug 20152015-08-01 00:00:00 UTC2015-09-01 00:00:00 UTC000
Sep 20152015-09-01 00:00:00 UTC2015-10-01 00:00:00 UTC000
Oct 20152015-10-01 00:00:00 UTC2015-11-01 00:00:00 UTC202
Nov 20152015-11-01 00:00:00 UTC2015-12-01 00:00:00 UTC000
Dec 20152015-12-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
Jan 20162016-01-01 00:00:00 UTC2016-02-01 00:00:00 UTC303
Feb 20162016-02-01 00:00:00 UTC2016-03-01 00:00:00 UTC000
Mar 20162016-03-01 00:00:00 UTC2016-04-01 00:00:00 UTC000
Apr 20162016-04-01 00:00:00 UTC2016-05-01 00:00:00 UTC000
May 20162016-05-01 00:00:00 UTC2016-06-01 00:00:00 UTC000
Jun 20162016-06-01 00:00:00 UTC2016-07-01 00:00:00 UTC000
Jul 20162016-07-01 00:00:00 UTC2016-08-01 00:00:00 UTC000
Aug 20162016-08-01 00:00:00 UTC2016-09-01 00:00:00 UTC000
Sep 20162016-09-01 00:00:00 UTC2016-10-01 00:00:00 UTC000
Oct 20162016-10-01 00:00:00 UTC2016-11-01 00:00:00 UTC000
Nov 20162016-11-01 00:00:00 UTC2016-12-01 00:00:00 UTC000
Dec 20162016-12-01 00:00:00 UTC2017-01-01 00:00:00 UTC202

What Hacker News says

10 sources
Unfortunately, that assumes that "you" have that choice. Individually, I'm sure you can rip out, mutilate, deface, damage or what have you to devices that report fine-grained time-series data. But the moment you go anywhere else, you're being recorded, watched, monitored, measured, and recorded. It's already being done, and it's way past time that we do have that discussion. Because without string and stark dialogue, we'll end up with "We're not doing anything wrong, so why should we care?" kind of responses. Or worse yet, people won't understand what something like accurate TS data from power input can lead to.[0] And as an addition on the above comment, I also wrote a CPU-bound facial recognition app. I wrote it initially for a convention that we have for our hackerspace every year... But it took me a week to do in my spare time, using
Read the rest
open source libs (OpenCV, QT). This stuff is just getting more ubiquitous.[1] [0]: http://www.hennebert.org/download/publications/isspa-2012-ma... MACHINE LEARNING APPROACHES FOR ELECTRIC APPLIANCE CLASSIFICATION [1]: https://github.com/jwcrawley/uWho
In Amazon refuses to let police access US murder suspect’s Echo recordings
The argument isn't that you use OpenCV: OpenFace also uses OpenCV. However, I think you should target and present your program as being a program that uses face recognition, not as a face recognition program. You are using and not crediting here that your program uses existing, off-the-shelf face recognition functionality already in OpenCV: https://github.com/jwcrawley/uWho/blob/2823479d5abf9f8f2de21...
In OpenFace: Free and open source face recognition with deep neural networks
That's what my github.com/jwcrawley/uWho project does: Facial recognition on an old computer with no GPGPU processing. Now , any of the CVDazzle "exploits" screwing up a LBP cascade on face detection works to subvert my model, as does closing ones eyes. Aside those small details, it was in large a great success for my initial goal. Now, I'm looking at getting it into a client-server architecture, where I can recognize who lives here, and whom comes over regularly. The idea is that I can have an "aware front door" that can ring a doorbell or send a message (with who: text/picture) if we are away. Even crazier is to allow bidirectional voice to us over a VoIP connection. I see its purpose in a part of the home IoT infrastructure that isn't like a "internet toilet" kind of uselessness.
In OpenFace: Free and open source face recognition with deep neural networks
I also built an Open Source (GPL3) facial recognition program as well, called uWho (github.com/jwcrawley/uWho). Mine doesn't need anything like CUDA or OpenCL, and runs on a 6 year old laptop at 1280x720@15fps. I ran it at our free, ticketless convention called Makevention (bloomington, IN). Estimates were that 650-700 people showed up. My tracker counted 669 uniques, which I think is spot on. I also wrote mine for privacy in mind. The database was a KNN on a perceptual hash of the face. The data that was stored was only a hash and could only verify a face: it could not generate the face from the hash. Considering the application (Maker/Hacker con) I wanted to be sure that this was the case. (The data only resided on that machine, and it's wiped now.) I've halted work on the gui version of it. Now I want to make it into a client/server, w
Read the rest
here the clients are RasPis (or other cheap compute with camera) and the server is whatever good machine you have. Initially, I'll reimplement the same algo, but I know that KNN has exponential time/cpu requirements the more samples I get.
In OpenFace: Free and open source face recognition with deep neural networks
I think you're coming from this already feeling that privacy is very important. The people you're trying to explain it to probably don't really care. With that in mind, here's how I'd see you explain in that way to a lay person who doesn't get why it's important: > I wrote a program called uWho(https://github.com/jwcrawley/uWho) for our hacker You're a hacker? > With a permissive license (OpenCV) attached to a GPL3 (Qt) I have absolutely no idea what you're talking about already. > My version was nice, in that it saved a one-way hash of the person's face. It is a 2 liner to save the full face instead of the nice method I did. If I was following, the only thing so far is that you were taking pictures of people and recognised faces and it was really useful, and you're trying to convince me that we should be worried about others taking pictu
Read the rest
res of us and recognising faces? > Now, tell me this: what would happen if a company downloaded every face in a user's profile, checked the names of tagged faces, and ran all of them through a face recognizer like what I already made? What would happen? The company can recognise who people are, like facebook can and I already allow and don't care about / like?
In The Era of Automatic Facial Recognition and Surveillance Is Here
I have a great way to explain Facial Recognition and why it's important.... _________________________________ I wrote a program called uWho(https://github.com/jwcrawley/uWho) for our hacker/maker convention, Makevention. Our goal was to determine how many people showed up to the convention, as it was a free-to-attend with a suggested donation event. With a permissive license (OpenCV) attached to a GPL3 (Qt), I was able to make a real-time face scanner. My version was nice, in that it saved a one-way hash of the person's face. It is a 2 liner to save the full face instead of the nice method I did. I did this using software anyone can get. Now, imagine having this software, with mainframes combined with the ability to trawl through a user's facebook profile... Because a like allows that. And do you have a company's Facebook permission? Now
Read the rest
they can see your whole profile, as well as your friends. Now, tell me this: what would happen if a company downloaded every face in a user's profile, checked the names of tagged faces, and ran all of them through a face recognizer like what I already made? That's why it is important.
In The Era of Automatic Facial Recognition and Surveillance Is Here
Ok. So businesses already have cameras. Yeah, privacy, schmiravacy. That horse has done gone left the barn. So, the second problem with cameras/face tracking is cost? I wrote this: https://github.com/jwcrawley/uWho It does what your hardware does, but also does facial recognition. It's still early in the build process, but I'm working on a commercial (non-QT) version of this. But right now, it can accurately count unique people, as well as remember people. So when Jane walks in front of the camera, it remembers that her database number is 1234. Tomorrow, it will also remember that she's 1234. And tracking is all stored in few XML config files for easy calculation.
In Show HN: Density – Anonymous People Counter and API

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.