HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
fsgreco
go-bunny-sign
Go2025–2025
fsgreco / go-bunny-sign

go-bunny-sign

This Go package lets you display animated messages with an adorable bunny holding a sign. Because, why not?

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

What to know before exploring

What it is

This Go package lets you display animated messages with an adorable bunny holding a sign. Because, why not?

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: 2025-08-31 13:16:12 UTC to 2025-09-02 19:46:43 UTC.

012025-08-31 12:00:00 UTC to 2025-08-31 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 31, 12:002025-08-31 15:00:00 UTC to 2025-08-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-31 18:00:00 UTC to 2025-08-31 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-31 21:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-09-01 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 03:00:00 UTC to 2025-09-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 06:00:00 UTC to 2025-09-01 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 09:00:00 UTC to 2025-09-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 12:00:00 UTC to 2025-09-01 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 15:00:00 UTC to 2025-09-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 1, 15:002025-09-01 18:00:00 UTC to 2025-09-01 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 21:00:00 UTC to 2025-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-02 00:00:00 UTC to 2025-09-02 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-02 03:00:00 UTC to 2025-09-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-02 06:00:00 UTC to 2025-09-02 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-02 09:00:00 UTC to 2025-09-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-02 12:00:00 UTC to 2025-09-02 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-02 15:00:00 UTC to 2025-09-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-02 18:00:00 UTC to 2025-09-02 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 2, 18: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 31, 12:002025-08-31 12:00:00 UTC2025-08-31 15:00:00 UTC110
Aug 31, 15:002025-08-31 15:00:00 UTC2025-08-31 18:00:00 UTC000
Aug 31, 18:002025-08-31 18:00:00 UTC2025-08-31 21:00:00 UTC000
Aug 31, 21:002025-08-31 21:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 1, 00:002025-09-01 00:00:00 UTC2025-09-01 03:00:00 UTC000
Sep 1, 03:002025-09-01 03:00:00 UTC2025-09-01 06:00:00 UTC000
Sep 1, 06:002025-09-01 06:00:00 UTC2025-09-01 09:00:00 UTC000
Sep 1, 09:002025-09-01 09:00:00 UTC2025-09-01 12:00:00 UTC000
Sep 1, 12:002025-09-01 12:00:00 UTC2025-09-01 15:00:00 UTC000
Sep 1, 15:002025-09-01 15:00:00 UTC2025-09-01 18:00:00 UTC000
Sep 1, 18:002025-09-01 18:00:00 UTC2025-09-01 21:00:00 UTC000
Sep 1, 21:002025-09-01 21:00:00 UTC2025-09-02 00:00:00 UTC000
Sep 2, 00:002025-09-02 00:00:00 UTC2025-09-02 03:00:00 UTC000
Sep 2, 03:002025-09-02 03:00:00 UTC2025-09-02 06:00:00 UTC000
Sep 2, 06:002025-09-02 06:00:00 UTC2025-09-02 09:00:00 UTC000
Sep 2, 09:002025-09-02 09:00:00 UTC2025-09-02 12:00:00 UTC000
Sep 2, 12:002025-09-02 12:00:00 UTC2025-09-02 15:00:00 UTC000
Sep 2, 15:002025-09-02 15:00:00 UTC2025-09-02 18:00:00 UTC000
Sep 2, 18:002025-09-02 18:00:00 UTC2025-09-02 21:00:00 UTC101

What Hacker News says

2 sources

Show HN: My first Go project, a useless animated bunny sign for your terminal

Hi HN, I wanted to share my very first (insignificant) project written in Go: a little CLI tool that displays messages with an animated bunny holding a sign. I wanted to learn Go and needed a small, fun project to get my hands dirty with the language and the process of building and distributing a CLI. I've built a similar tool in JavaScript before so I thought porting it would be a great learning exercise. This was a dive into Go's basics for me, from package structure and CLI flag parsing to building binaries for different platforms (never did that on my JS projects). I'm starting to understand why Go is so praised: it's standard library is huge compared with other languages. One thing that really impressed me was the idea (at some point of this journey) to develop a functionality by myself (where in the javascript original project I cho
Read the rest
ose to use an external library), here with the opportunities that std lib was giving me I thought "why don't try to create the function by miself?" and it worked! In the Js version I used the nodejs "log-update", here I write a dedicated pkg. I know it's a bit silly, but I could see it being used to add some fun to build scripts or idk highlight important log messages, or just make a colleague smile. It's easy to install if you have Go set up: go install github.com/fsgreco/go-bunny-sign/cmd/bunnysign@latest Since I'm new to Go, I would genuinely appreciate any feedback on the code, project structure, or Go best practices. The README also lists my planned next steps, like adding tests and setting up CI better. Thanks for taking a look!
26 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.