HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
solokeys
solo1
C2018–2022
solokeys / solo1

solo1

Solo 1 firmware in C

10Distinct people
26Mentions
0Explicit recommenders
2.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Solo 1 firmware in C

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM 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 year26 dated mentions

Observed mentions: 2018-09-14 00:29:53 UTC to 2022-08-19 00:45:51 UTC.

024682018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC826
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC615
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303

What Hacker News says

6 sources
We sell open source security keys: https://solokeys.com Paid: Amazon, the thing I like is that their dashboard clearly shows marketing cost and revenues, so you can very easily say whether it's worth or not. Non-paid: - Github: http://github.com/solokeys/solo Last time I measured, we had 1% of our traffic coming from Github, and 1% of that traffic converting to a sale. This is pretty awesome I think, especially because having a baseline we can improve. We're not making any strong sale-pitch on Github, we simply put links to our store at the top and bottom of the readme. Right now we're running a crowd funding campaign, and because we knew Github was bringing high quality traffic we're advertising it there. - Twitter. This is our 2nd social in sales. We're not doing anything special, just clear profiles (personal and business) with links t
Read the rest
o the store, and clear call to actions when you tweet. - Pinterest. This is the social that bring us most clicks the the store. I know the platform very well, of course. For SoloKeys specifically the audience is not right, so there's little to zero conversions to sales, but it's good learning nevertheless. - Medium/Hackernoon. When we blog, we typically get spikes of traffic and sometimes sales. But it requires time to write posts, so it's not really as scalable as the other channels. (We're barely using Facebook, and zero Instagram, so I can't really talk about these).
In Ask HN: What marketing channels are working for you in 2019?
Blogging, but really marketing in general, thought me to ask "what do I want to say?" and "to whom am I talking?" To an extreme this is also important in the code, because you can get the most clever algorithm or implementation or optimizatiton, but if your code should be maintained by someone else, you'd better keep it clear over clever. In short, write code that others can understand and modify. More generally, with code we have comments, commit messages, readme and sometime even documentation. This is an example of how, at a certain point in time, we reviewed our README. From a confusing list of instructions, it's now a clear how to: https://github.com/solokeys/solo/commit/bbc61d5743b45d62f7e2... - What is this? A security key, with call to action (you can get one) - First FAQ: Security - First User / Use case: Hacker who wants to pers
Read the rest
onalize his key - Advanced User: Developer who wants to contribute - More docs - More bla bla - Call to action again (you can get one) As you can see this is the classical structure of any blog post / marketing page.
In Ask HN: As a software developer, why do you think blogging is necessary?
Fwiw I just received some solo keys after backing their kickstarter. Unfortunately the firmware doesn't yet support key storage, but it should be comming. I think it looks like an interesting alternative to nitrokey in the open source space. They have usba and usbc variants, and are working on nfc ("solo tap") variant: https://solokeys.com/ https://github.com/solokeys/solo https://www.amazon.com/Solo-Two-Factor-Authentication-USB-Tr... https://solokeys.com/en/start/faq/ "Can I use Solo for OpenGPG or Ssh? Not yet Can I use Solo to store passwords? Not yet."
In 773M Password ‘Megabreach’ Is Years Old

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.