41–46 of 46 posts
Earlier quoted context omitted.
I'm not following... how is this broken? The headers return a 302 code, pointing to the proper HTTPS site. If you click the link you pasted, your browser should properly redirect (tested in FF, Chrome).
Those slashes are escaped with backslashes in the response
Earlier quoted context omitted.
I'm not following... how is this broken? The headers return a 302 code, pointing to the proper HTTPS site. If you click the link you pasted, your browser should properly redirect (tested in FF, Chrome).
Those slashes are escaped with backslashes in the response
Earlier quoted context omitted.
RSS format sucks because XML sucks. I agree that it would be awesome if it was opensource so you could mitigate any risks by having it run on your own hardware, but really it's a valuable service and they deserve to make some money, which will play into keeping the service alive.
Thanks! The stack which is required for the Streamified API is really quite large, too. Between node, mongo, elasticsearch, and a few other pieces of software... plus a few dozen node modules and even some custom linux configuration, it's really not feasible to expect devs to install it on their own machines ;)
If you want my opinion, I would recommend finding a small area of your tech stack that you wish was better and starting an opensource project to solve that specific problem. No one expects twitter to give away their source code for their core product, but they do appreciate bootstrap and bower.js a whole lot.
Earlier quoted context omitted.
RSS format sucks because XML sucks. I agree that it would be awesome if it was opensource so you could mitigate any risks by having it run on your own hardware, but really it's a valuable service and they deserve to make some money, which will play into keeping the service alive.
I would agree if we were talking about a SOAP protocol that could be restful or something. But RSS doesn't bother me at all. You can just pass it through a converter to suit your fancy, and the bloat for an average use case of 10 results can't be that much. It's a minor miracle anybody decided to publish their sites through RSS so I'm happy they used the format that was hot at the time and got adoption.
But I still want it to die and JSON to become the new king in data transfer. That could be due to my work being in the web development arena and using node.js, but I honestly think it's just a better solution.
Earlier quoted context omitted.
Sorry, but this is a developer portal -- not a news source or blog -- and really isn't meant to be used on a mobile device. I acknowledge that this may not be the answer you're looking for, but we didn't design the site for mobile because what it needs to do isn't really appropriate (or feasible) on mobile -- eg, the API console.
Well it is a news source, called hacker _news_. You telling me a developer doesn't read stuff on a cell is just complete BS. I never said i want a mobile site. Just a css that doesn't completely break on small resolutions. If you don't want to fix it fine. But don't give me such a BS answer. I acknowledge this might not be the answer you were looking for.
Earlier quoted context omitted.
Thanks! The stack which is required for the Streamified API is really quite large, too. Between node, mongo, elasticsearch, and a few other pieces of software... plus a few dozen node modules and even some custom linux configuration, it's really not feasible to expect devs to install it on their own machines ;)
Your welcome! I get that the service your providing is more than the sum of its code. Someone is doing the website, marketing, documentation, fixing bugs, keeping up with changes etc... not to mention paying the bills to reliably run the servers. If you want my opinion, I would recommend finding a small area of your tech stack that you wish was better and starting an opensource project to solve that specific problem.…