Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Track HN: Survival Rate of Show HN Stories

nami.land

Post reply on HN
Print view View original

51–60 of 75 posts

Re: Track HN: Survival Rate of Show HN Stories

#51

Post by gkoberger »

codetrotter wrote: post #36
gkoberger wrote: post #13

I'm happy to say that the reports of my death here are greatly exaggerated :) I'm the owner of both #4 and #140 on the Top-scoring Show HN Stories that Didn’t Survive... but both are very much alive! #4 StackSort was a Github.com page, but on 2021 they made it so only Github.io wroks. If dang sees this, I'd really appreciate if you could change the URL for https://news.ycombinator.com/item?id=5395463 to use github.io…

The main page https://gkoberger.github.io/ that the https://gkoberger.github.com/ link suggests going to gives a 404 as well. Could be a good idea to add a main page for https://gkoberger.github.io/ that links the StackSort page and anything else

Good call! I'll fix that up today.

Re: Track HN: Survival Rate of Show HN Stories

#53

Post by rahimnathwani »

hawski wrote: post #7

Regarding database hosting, if you would consider giving the data away, I would suggest converting it to an SQLite database and sharing it over Torrent.

I'm guessing OP wants to share a database that's always up to date.

A torrent containing a single sqlite file would be good for a snapshot in time, but each update would require a new torrent, even if it only contains the updates since the base or last release.

IIRC IPFS can be used to distribute files that change over time, with only the changes being transferred, although of course there would need to be a place where OP publishes the hash of the most recent file.

In either case, someone would need to seed the file to guarantee it's always available.

Re: Track HN: Survival Rate of Show HN Stories

#54

Post by echelon »

gkoberger wrote: post #13

I'm happy to say that the reports of my death here are greatly exaggerated :) I'm the owner of both #4 and #140 on the Top-scoring Show HN Stories that Didn’t Survive... but both are very much alive! #4 StackSort was a Github.com page, but on 2021 they made it so only Github.io wroks. If dang sees this, I'd really appreciate if you could change the URL for https://news.ycombinator.com/item?id=5395463 to use github.io…

If we're going by vote count, my "show HN" should be #30, but it's not on the list at all.

Re: Track HN: Survival Rate of Show HN Stories

#55

Post by actuallyalys »

Semaphor wrote: post #8

The top 250 has 8 dead projects from 2023. Of those 8, 5 are not dead at all, 1 is alive but has an expired certificate and only 2 (the lowest ranked) are dead. This does not seem like useful data.

That's definitely a red flag, although I'd expect the 2023 data to have a disproportionate number of false negatives relative to true negatives (since the vast majority of 2023 projects are still alive).

Re: Track HN: Survival Rate of Show HN Stories

#56

Post by 12907835202 »

gkoberger wrote: post #50
12907835202 wrote: post #40

Earlier quoted context omitted.

How on earth did you get readme.com? I'm assuming someone else owned it, whenever I see that and all the "make an offer" links I move on and ignore it. Was the process easy?

It wasn't called ReadMe originally... I happened to be browsing HN, and came across a post with someone offering readme.io for free, and I was like "oh that's a great name!" (I ultimately paid $3k as a thank you) https://news.ycombinator.com/item?id=6397526 For the first few years, we used readme.io as our domain. When we did our Series A, I finally bought the .com for $170k. By that point I knew we were successful,…

Wow I can't fathom the .com being worth that much. Did you manage to do any sort of math on whether the .com has helped bring in $170k of sales? Or how many years it would take to break even.

Re: Track HN: Survival Rate of Show HN Stories

#57

Post by vnchr »

12907835202 wrote: post #56
gkoberger wrote: post #50

Earlier quoted context omitted.

It wasn't called ReadMe originally... I happened to be browsing HN, and came across a post with someone offering readme.io for free, and I was like "oh that's a great name!" (I ultimately paid $3k as a thank you) https://news.ycombinator.com/item?id=6397526 For the first few years, we used readme.io as our domain. When we did our Series A, I finally bought the .com for $170k. By that point I knew we were successful,…

Wow I can't fathom the .com being worth that much. Did you manage to do any sort of math on whether the .com has helped bring in $170k of sales? Or how many years it would take to break even.

It’s an asset they can resell, and he validated the $170k price himself by paying that much.

Re: Track HN: Survival Rate of Show HN Stories

#58

Post by gnicholas »

> Send me your interesting queries

I'd be interested to see what the top Show HN posts were, after adjusting for the growing size of the HN community. That is, posts from 10 years ago would not have garnered as many upvotes simply because the community was smaller, and presumably posts were upvoted less back then, in general.

I don't know the best way to measure this; it could be normed based on the median number of upvotes for the top story each week, bucketed by month. Probably someone has a better idea for this.

Re: Track HN: Survival Rate of Show HN Stories

#60

Post by noncoml »

folli wrote: post #24

Nice work! I'd actually be interested in factors that make a Show HN a success vs failure. Objectively, there's an obvious one your dataset: time of submission. Tuesday afternoon (which timezone? I assume US west coast?) seems to be key. No way this correlates with the quality of submissions. Subjectively: it seems to become much harder recently. I managed once a couple of years ago for a short time to reach the fron…

> which timezone?

I’m wondering the same. Earlier in the article he mentions UTC.

So it’s either afternoon or early in the morning Pacific time.

Post reply on HN