An official RSS/Atom feed would be great too.
Have you seen https://news.ycombinator.com/rss ?
Ugh no... No idea how I've missed that.
Thanks!
Hacker News Official API
91–100 of 138 posts
Re: Hacker News Official API
#92Earlier quoted context omitted.
By “showing comments led” do you mean showing comment points/votes? Also, if comment viewable comment points are gone forever, then the “popularity” filter should be removed from HN’s search and the old voting data removed from the public API. To me, if users have concerns about “unfair voting” to me the solution is not to hide them. Also, if comment points aren’t important, why even allow them? They are obviously im…
Like I said, this has been heavily litigated. So much so that I think you'd have difficulty coming up with an argument that hadn't been made already about it. Not making other people's comment scores available is, as I said, a part of the premise of the community. There are other communities that work differently. There isn't a single optimal set of policies.
You’re right, obviously the best way to secure the community was to obscure the votes of people that were upvoting toxic content instead of the mods/community just publicly tagging and flagging the related undesirable content and penalizing the voting weights of anyone upvoting that content.
If votes being public impacts voting patterns, listing top users, having usernames publicly associated with comments, being able to follow given user’s comments, etc — for sure does too. What’s the difference?
Re: Hacker News Official API
#93Earlier quoted context omitted.
Like I said, this has been heavily litigated. So much so that I think you'd have difficulty coming up with an argument that hadn't been made already about it. Not making other people's comment scores available is, as I said, a part of the premise of the community. There are other communities that work differently. There isn't a single optimal set of policies.
You’re right, obviously the best way to secure the community was to obscure the votes of people that were upvoting toxic content instead of the mods/community just publicly tagging and flagging the related undesirable content and penalizing the voting weights of anyone upvoting that content. If votes being public impacts voting patterns, listing top users, having usernames publicly associated with comments, being abl…
You're arguing here as if there is an argument to be had. I'm trying to help you understand that there is no such argument. Your claims have been considered and rejected hundreds of times over the last 10 years. It'd behoove you to consult the search bar below and read some of those old discussions. This isn't a case where the community made a rash decision and just doesn't realize how problematic it is; you're talking about what is probably the single most deliberate community management decision HN has ever made. It's not going to change.
A moment later
Maybe it'll help if you get your head around the goal of HN. There are a bunch of things you personally seem to want to accomplish with HN. But HN itself has just one goal: to nurture curious conversation. Other sites have other, equally valid goals: propagating the news as quickly as possible, or relentless focus on a particular topic, or getting the best Q&A pairs to the top of Google's search results. HN, though: curious conversation. That's the whole ballgame.
Anything that drags on curious conversation is a non-starter on HN, even if it might make a bunch of things better for you.
We don't have to guess about whether making comment scores available is a drag on curious conversations; it manifestly was, for years. People have an innate, visceral reaction to comment scores they feel are unjust, and they talk about them, and those conversations choke the landscape like kudzu.
A lot of things about HN make more sense when you accept the premise of the site, and understand that HN will make most sacrifices it can come up with to optimize for that premise.
Re: Hacker News Official API
#94Re: Hacker News Official API
#95In response to people's complaints about the usability of the HN Firebase API: yes. We're going to eventually have a new API that returns a simple JSON version of any HN URL. At that point we'll phase out the Firebase API, with a generous deprecation period. I'd be curious to hear people's thoughts about what a generous deprecation period might be.
How difficult would it be to host the same Firebase API on top of whatever will be driving the new JSON stuff?
Re: Hacker News Official API
#96In response to people's complaints about the usability of the HN Firebase API: yes. We're going to eventually have a new API that returns a simple JSON version of any HN URL. At that point we'll phase out the Firebase API, with a generous deprecation period. I'd be curious to hear people's thoughts about what a generous deprecation period might be.
I'd say it depends on how straightforward the new API will be. The app I use (Materialistic) is both free and ads-free. So I don't expect the developer to drop everything they are doing to update it if will require a lot of work. So 6 months minimum if everything is well documented, a year if it will be a hassle.
Re: Hacker News Official API
#97What is the use case? I can't imagine anything besides getting a real time view on the frontpage or likes of my own comments that a monthly static data dump wouldn't solve.
Re: Hacker News Official API
#98I'm currently writing an HN posts score tracker (basically it plots score variations over time since they were in new for each popular post) and it's really handy that you can just subscribe with eventsource [0] and get realtime update when something changes without having to manually poll each post wasting resources. Not yet sure about the latency though. [0] https://github.com/jpopesculian/reqwest-eventsource/
https://hnrankings.info/
Nice one, wish there was something similar for user rankings (with karma points).
Re: Hacker News Official API
#99What is the use case? I can't imagine anything besides getting a real time view on the frontpage or likes of my own comments that a monthly static data dump wouldn't solve.
Probably 3rd party clients that offer quality of life / usability improvements over the website.
E.g. I use Hackers [1][2] because it is much easier to read stories on mobile and supports dark mode. Unfortunately, it doesn't support commenting or downvoting (yet?)
[1] https://apps.apple.com/us/app/hackers-for-hacker-news/id6035... [2] https://github.com/weiran/Hackers
Re: Hacker News Official API
#100Earlier quoted context omitted.
You’re right, obviously the best way to secure the community was to obscure the votes of people that were upvoting toxic content instead of the mods/community just publicly tagging and flagging the related undesirable content and penalizing the voting weights of anyone upvoting that content. If votes being public impacts voting patterns, listing top users, having usernames publicly associated with comments, being abl…
You're arguing here as if there is an argument to be had. I'm trying to help you understand that there is no such argument. Your claims have been considered and rejected hundreds of times over the last 10 years. It'd behoove you to consult the search bar below and read some of those old discussions. This isn't a case where the community made a rash decision and just doesn't realize how problematic it is; you're talki…
Just to be clear, intentionally not responding, since you repeatedly in my opinion ignored my points and contrary to your claims, did not engage me out of intellectual curiosity.