HNHacker News
TopNewBestAskShowJobs

neuroscr

26 karma · joined June 16, 2012

http://about.me/ryantharp

Also a 3rd party app.net developer active in the app.net community.

submissionscomments
neuroscr··on App.net Response to Brennan Novak, part II
Well, you don't get to use the handy apps with the cool UIs the 3rd party devs have made. But yea, I suppose you can consume it all on your own too.
neuroscr··on App.net Response to Brennan Novak, part II
So open-standards don't matter? While they haven't given their source for their backend, they've been pretty open about how it's built, plus they've open sourced several pieces of their platform (Omega, Pourover, Ohe).

App.net is for the general consumer that's not going to be able to run their own server stack. If you can run your own server stack, you can use all these open standards outlined in this blog posts to consume the data and do what you like.

There's even a http://dev-lite.jonathonduerig.com/ so you don't need to pay anything to tinker with their API.

neuroscr··on App.net Response to Brennan Novak, part II
I would say no. Free accounts are limited to following 40 accounts but are unlimited in followers. Which means publishers don't have to pay anything to have a large following. But a subscriber may have to pay if they wish to consume a lot of the content.
neuroscr··on App.net Response to Brennan Novak, part II
Well for new applications, at the start I can access a market of 100k (tokens) from Twitter or I can acccess a market of 140k+ and growing from App.net. I think a lot of developers/businesses will do the math.

One could also argue that less data means less noise and more signal. Also the data on app.net is more structured (see their annotation implementation).

neuroscr··on Darkjpeg - Steganography Redefined
Says my browser is out of date when it's not...
neuroscr··on Linus blasts again
These rants are what make him a good leader. He has a clear mission/focus of how he wants things to work, and clearly communicates when he feels things are broken.
neuroscr··on Linus blasts again
Props to the replies. His team there are responsible professionals. Any one could have stopped after the first took the blame but they all stepped up and this is how it's supposed to work. Hopefully Linus won't rip their heads off =]
neuroscr··on HTTP 2.0
Most of the complaints are around the ascii vs binary. Can we just make it accept both and move on?
neuroscr··on HTTP 2.0
Amen! Efficiency to who's standards or values? It's a financial issue for big Internet but what's the real values cost the rest of the Internet? It's obviously a minimal financial costs, as everyone I know that wants to publish can. Why sacrifice durability, readability, and the original core values of the Internet for saving "big dollars" from "big providers"?
neuroscr··on HTTP 2.0
So instead of doing things properly, we'll hack around it... Isn't that what we're all complaining about?

Let's do it right and then fix NAT

neuroscr··on HTTP 2.0
Real tools? I would argue that there are way more real tools for debugging ASCII-based protocols than there will ever be for binary-based one. ASCII-based protocol is highly compose-able by allows us to separate intent (contents of the message) from ever-evolving encodings (rebasing, encryption, compression, etc). In this world of fighting complexity, why are we not favoring the simple?
neuroscr··on Ask HN: How do you deal with Rabbit Hole Syndrome?
as an engineer you have to realized there's not a best solution overall but a best solution for this particular problem. Each solution has pros and cons.

I think you spend time weighing each design because you're unclear on your final vision of your product. You haven't definitely answered what your values and needs are that you're trying to solve.

This may be a hard question to answer. This is why MVP are neat, you can get a product out to consumers quickly and use their response to develop values and a overall direction.

I find you if you think too far ahead, you don't leave any room for random disruptive opportunities that can occur in each step.

So know where you're going. Figure out and focus on the next step that gets you close to that.

neuroscr··on Ask HN: I just inherited 700K+ lines of bad PHP. Advice?
You're not going to have serious progress for a year. The DB is borked, so you have no foundation at all.

Software Engineering is serious business, there's bugs, new features, maintenance, testing, etc. They failed to manage their code. You need to be realistic that with a team of 2-5 people it could take years to fix.

It might be best to put it out of its misery if they can't hold off their clients demands and buy you the time needed to rebuild it.

← PreviousPage 2 of 2