HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
badger
frontend
HISTORICAL RECORD2011–2011
badger / frontend · Not publicly available

frontend

Discover this repository through its Hacker News conversations.

2Distinct people
3Mentions
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, 1:49:46 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 day3 dated mentions

Observed mentions: 2011-12-13 21:54:25 UTC to 2011-12-29 16:26:52 UTC.

012011-12-13 00:00:00 UTC to 2011-12-14 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 132011-12-14 00:00:00 UTC to 2011-12-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-15 00:00:00 UTC to 2011-12-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-16 00:00:00 UTC to 2011-12-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-17 00:00:00 UTC to 2011-12-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-18 00:00:00 UTC to 2011-12-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-19 00:00:00 UTC to 2011-12-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-20 00:00:00 UTC to 2011-12-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-21 00:00:00 UTC to 2011-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 212011-12-22 00:00:00 UTC to 2011-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-23 00:00:00 UTC to 2011-12-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-24 00:00:00 UTC to 2011-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-25 00:00:00 UTC to 2011-12-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-26 00:00:00 UTC to 2011-12-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-27 00:00:00 UTC to 2011-12-28 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2011-12-28 00:00:00 UTC to 2011-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-12-29 00:00:00 UTC to 2011-12-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 29

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
Dec 132011-12-13 00:00:00 UTC2011-12-14 00:00:00 UTC101
Dec 142011-12-14 00:00:00 UTC2011-12-15 00:00:00 UTC000
Dec 152011-12-15 00:00:00 UTC2011-12-16 00:00:00 UTC000
Dec 162011-12-16 00:00:00 UTC2011-12-17 00:00:00 UTC000
Dec 172011-12-17 00:00:00 UTC2011-12-18 00:00:00 UTC000
Dec 182011-12-18 00:00:00 UTC2011-12-19 00:00:00 UTC000
Dec 192011-12-19 00:00:00 UTC2011-12-20 00:00:00 UTC000
Dec 202011-12-20 00:00:00 UTC2011-12-21 00:00:00 UTC000
Dec 212011-12-21 00:00:00 UTC2011-12-22 00:00:00 UTC000
Dec 222011-12-22 00:00:00 UTC2011-12-23 00:00:00 UTC000
Dec 232011-12-23 00:00:00 UTC2011-12-24 00:00:00 UTC000
Dec 242011-12-24 00:00:00 UTC2011-12-25 00:00:00 UTC000
Dec 252011-12-25 00:00:00 UTC2011-12-26 00:00:00 UTC000
Dec 262011-12-26 00:00:00 UTC2011-12-27 00:00:00 UTC000
Dec 272011-12-27 00:00:00 UTC2011-12-28 00:00:00 UTC110
Dec 282011-12-28 00:00:00 UTC2011-12-29 00:00:00 UTC000
Dec 292011-12-29 00:00:00 UTC2011-12-30 00:00:00 UTC101

What Hacker News says

3 sources
We have been using the term "brand new" as a way to show that we're trying to approach the domain industry a bit differently than our 5-10 year old competitors. I think the biggest example is that we've open sourced our javascript frontend (http://github.com/badger/frontend) which exclusively uses our API (http://badger.github.com/). We think the domain industry is ripe for disruption and we think we have the right team and ideas to execute. As you pointed out though we don't have a proven track record. Unfortunately, there's not a lot we can do about that. Service guarantees and long-term contracts might seem nice on the surface but wouldn't really change much if we went out of business. I believe the quote goes something like: "The only two things guaranteed in life are death and taxes. (Benjamin Franklin)" That said, we're a star
Read the rest
tup in San Francisco with an office and employees and have been around for over a year. We previously were a domain reseller (rhinonames.com) but have spent the last six months becoming ICANN accredited and building badger.com. We think we can build the best registrar around and we're here to stay.
In Show HN: Badger.com is a brand new domain registrar (GoDaddy competitor)

Badger.com is a new Domain Registrar. We oppose SOPA and like elephants.

Hey HackerNews, six months ago we started building a brand new registrar because we were underwhelmed by all of the existing options. Here's what makes us different: - We won't try to upsell you with unnecessary add-ons. - We want registering and managing domains to be an enjoyable experience... not something you're forced to tolerate. - We've spent a lot of time making our interface fast, simple and easy to use. We've built our frontend website entirely in JavaScript to make the experience as fast as possible. - Our website is open source and is built on top of our API. The source code (JavaScript, CSS, etc) for our website can be found at https://github.com/badger/frontend and the documentation for our API can be found at http://badger.github.com/. If you'd like to make improvements, we welcome and encourage GitHub pull requests! - W
Read the rest
hois privacy is free and enabled by default. - DNS hosting is free and enabled by default. - For a limited time, we are offering domains for $8 (new registrations, transfers and renewals). Please be aware that our normal price is $15 per domain. If you are registering or transferring lots of domains, volume discounts will apply which can bring the price all the way down to $10 per domain. - We are an ICANN accredited registrar, not a reseller. We only support .com and .net at the moment but we will be adding support for many more TLDs in the next couple of weeks so please bear with us. - We're a startup in San Francisco. Although our team is small right now, we have really big ambitions and what we have so far is just the beginning. We thrive on feedback, so don't hold back! You can send questions and suggestions to us at support@badger.com and we will respond as soon as we can. First 100 people to signup get a free domain: https://www.badger.com/#register/hackernews
29 points · Open discussion
Thanks for noticing! We built badger.com a bit differently from most sites. Our backend is just a JSON api and the frontend uses this API and is implemented entirely in Javascript using an internal library we'll be releasing soon (code name: Hasher). API Docs - http://badger.github.com/ Frontend Source Code - http://github.com/badger/frontend Hasher JS Lib - https://github.com/badger/frontend/tree/master/javascripts/l... So for example, the Javascript behind our DNS manager can be found here -- https://github.com/badger/frontend/blob/master/javascripts/d...
In Show HN: Badger.com, a new domain registrar, needs beta testers (1 free domain)

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.