41–50 of 59 posts
Earlier quoted context omitted.
Have a look at this too - http://hn.premii.com/
There is also an Android app by this premii person, and it re-directs all links through its own domain. Very annoying and actually borderline malicious.
Maybe, YC is trying to teach you something about product building. Something like: "we don't make our site mobile friendly because the content is so good that people still use it on their phone even if they have to zoom in a little. The day when people stop coming to hacker news or apply to YC because it's not mobile friendly, then we might do something about it. Otherwise it's just a waste of time and money for us."…
In this particular case, I am bit more reserved : why not ask a (well-known) contractor ? I am pretty sure pg just have to ask to get tens of high caliber lisp hacker proposals.
Yes, it will happen. Yes, we're working on it. The reasons it's taking so long are: (1) the change required is not tiny; and (2) everyone working on it has many other things to do, most of which are more pressing. That doesn't make it a low priority (it's a high priority), but it means we have to do it as a background process.
Maybe the conflict is that you want to do everything in a big step; making vote buttons etc more accessible, but there are some quick changes (I mean maybe 2 lines added to the style sheet which surely is one file?) that would make a vast improvement at least to our ability to use HN on our phones.
If you guys are lacking time, I'm sure that there are some companies out there who would love the kudos of some pro bono work.
Older versions of android stock browser used to act this way, but latest chrome on android does not.
Yes, it will happen. Yes, we're working on it. The reasons it's taking so long are: (1) the change required is not tiny; and (2) everyone working on it has many other things to do, most of which are more pressing. That doesn't make it a low priority (it's a high priority), but it means we have to do it as a background process.
Even if you simply steal LWN.net's very basic comments CSS, it wouldn't take you more than a full working day, including testing on few iPhones and different-resolution Androids.
A passionate community whose quality of life needs aren't met is a big missed opportunity and I find it strange that I have to be telling you that.
Apples and oranges, but still -- don't forget what happened to SourceForge. Used to be the go-to place years ago. Now it employs malware technics to not go broke.
Everybody can have hubris when famous, busy and (somewhat) rich. Question is -- can you treat your community right even at the height of your pique in popularity and usage?
It's shameful and baffling that the community must take over with shady proxy sites and apps to fill a gap you've been avoiding to fill for years.
Earlier quoted context omitted.
Have a look at this too - http://hn.premii.com/
There is also an Android app by this premii person, and it re-directs all links through its own domain. Very annoying and actually borderline malicious.
https://play.google.com/store/apps/details?id=co.adrianblan....
I've found this site as one of the easier to use ones on mobile?
Exactly. As far as I'm concerned, HN IS (!!!) mobile friendly. I'm so sick of the garbage mobile formatting that is ubiquitous these days. Give me a clean desktop version any day. Pinch to zoom FTW. 2009 was way easier to browse on the iPhone than 2015, what happened? Granted, there is an occasional gem but they are the rare exception. Perhaps bump the frontsize up a bit, but I don't see how HN could really be mobile…
Problem is, that you're basically "forced" to produce a mobile site by Google, otherwise you'll be way down in the SERPs :(
I never understood the point of mobile sites - i'm perfectly capable of pinching my screen, in case something is unreadable (which isn't too much, given retina screens and all that...)
Yes, it will happen. Yes, we're working on it. The reasons it's taking so long are: (1) the change required is not tiny; and (2) everyone working on it has many other things to do, most of which are more pressing. That doesn't make it a low priority (it's a high priority), but it means we have to do it as a background process.
I know that you must be sick writing that response, and I'm sure I'm missing the complexity somewhere, but it's been put off for years now. Maybe the conflict is that you want to do everything in a big step; making vote buttons etc more accessible, but there are some quick changes (I mean maybe 2 lines added to the style sheet which surely is one file?) that would make a vast improvement at least to our ability to us…