[solved] Ask HN: Is HN silently deleting/blocking too long comments?

4 points by dathinab ↗ HN
Wrt. the recent article about DST I posted a comment with two links to useful (but sadly German) youtube videos as well as something between a subscript/summery of this videos.

Only to notice that this comment never appears at all, it organically was there for a moment and then it was permanent gone and any try to post is just silently does nothing...

Well the comment was pretty long, so I guess HN might silently remove to long comments to prevent spam or similar?

EDIT: The solution was I'm stupid and there is a easy to overlook More button at the bottom of the page. Supper embarrassing. Thanks for the answers.

12 comments

[ 3.9 ms ] story [ 47.2 ms ] thread
Not sure about comments, but shadow ban this is what HN does not disdain.
Just to be clear the comment was _insanely_ long, like 68 lines and a total of >4000 characters.

So HN silently eating such a comment as a form of spam protections seems reasonable, I just wonder if that really is the case or some unlucky network error or similar got in the way.

I still see the comment, are you sure you didn't just get confused because it wasn't on the first page of the discussion?
Yes, how embarrassing.

Due to some non-hackernews related reasons the More button was basically non visible to me.

easy mistake to make :) I'd be curious how many people aren't even aware that threads can span multiple pages - dang even sometimes pins a comment to remind people at the top.
I think this is one of those areas where the desire for minimalism in the UI works against the site. This is the only forum I've been to where people have to be reminded that pagination exists because making it obvious would violate the site's design ethos.
Not just to you. The question comes up for others too. Hopefully before too long we'll be able to just go back to rendering entire pages without More links at the bottom.
It has links to something other than Wikipedia. That sets off a spam filter for many people right off the bat.
Thanks, I already found out what the problem was. It turns out there is a easy to overlook More button at the bottom of the comment section :-)