HN is not Reddit. Plenty of people make humorous or entertaining comments, but distracting joke threads full of obvious one-liners and no real content aren't generally welcome.
There's actually a really interesting discussion on Quora, I think, about why they had something along the lines of a no-humor policy.
The problem isn't that people are humorless– it's that when you reward people for humor (often resulting in puns and pithy one liners), after a while, people start competing to be as funny as possible– and that's all that ever rises to the top. It crowds out more deliberate, thoughtful discussion.
I love humor and comedy myself, but it makes sense to me why a discussion forum might deliberately choose to discourage it.
And you know, it's interesting to think about why that is, and how that helps anybody.
Have you ever gone onto a blogpost about procrastination and found the "I'll read this later" comment, and the "I'm here reading this instead of working" comment? Are those comments ever valuable?
It makes sense to downvote them to the bottom, so that people who go looking for them can find them, but the discussion is kept as fresh and relevant as possible.
we are getting meta but I think these type of comments are of a different breed. These do not provide any meaningful (or value) to the conversation nor are related to the subject, on the other hand the "tl;dr" was totally related to the context of the article, and a nice pun intended for the sense of humor.
Also it was how this whole conversation started, although really tangential to the OP; which encouraged a conversation.
Definitely could see this coming. While it's a shame that linkedin is closing down their API even more, they are just shooting themselves in the head which is great news :)
Anyway, the future of professional social networks is destined to be rich ones for each profession/vertical, not the "crappy/high noise for everyone" linkedin model.
I know I'm focusing more on crunchbase[0] and angellist[1] APIs for my startup.
Yup, we saw this coming years ago, and have taken a number of steps to move away from them and leverage other networks more (Github, Twitter, Crunchbase, AngelList, etc.). If you're interested in chatting about this, shoot me a note.
Hey vivek, same thing I said to srjk goes for you as well. I write for Gigaom and I'm hoping to talk to some developers about the news. If you're up for it, would like to hear about why you started migrating awhile ago. I'm at carmel.deamicis@gigaom.com
Hey srjk, I write for Gigaom and I'm hoping to talk to some developers about the news. Up for chatting about why you saw this coming awhile ago? if so, drop me a line at carmel.deamicis@gigaom.com
They have been moving into "sales intelligence". Their data/professional graph is a pretty big (maybe only) competitive advantage for the next year or two in that area. So, it follows that they would block off access for possible competitors and/or cordon off more data. This move became inevitable when they partitioned their API by "partner access" a while back.
However, this is great news :) It will just make linkedin irrelevant quicker. They are moving away from being a social network for professionals to being a source of sales intelligence. Most users wont be too happy with that. And, unlike facebook, linkedin is much easier to migrate off of. Really, linkedin was the first big professional network, not the last one.
IMHO angellist is more in line with what the future of professional networks is.
Ringio(http://ringio.com) provides internet phone service to small businesses to improve the quality of their phone interactions. We have some great ideas for owning this domain and are looking for a few great software engineers to help take our product to the next level. If you're interested (or know someone who is), read more and email srijak AT ringio.com[1]. If you are interested in Go or node.js you should definitely get in touch.
Major areas of development focus:
- Scaling: We are growing at a rate where our current stack and architecture need
to be rethought. So, there is a lot of interesting work to be done.
- Modern HTML Applications: We’re very excited about JavaScript frameworks that
have grown in popularity (like Angular.js, D3). We’re interested in
using web technologies for our mobile and desktop applications, so if
you’re experienced with (or just interested in) JavaScript,
CoffeeScript, SCSS, WebSockets, or BOSH, there’s a lot of research
and development to be done.
- Voice Technology: All calls using Ringio run through our voice systems to enable
things like on-hold music, call screening, and transfers.
We have a lot of new voice functionality that we’d like to build,
as well as technology we’d like to integrate. This is fairly unique to
our industry and involves some interesting timing, reliability,
concurrency, and state management problems.
- API Development: Integration with CRM systems and reselling partners requires APIs
for large pieces of our platform. We need help expanding our APIs,
making sure they’re usable and secure, and testing that they’re working
correctly.
We’re Looking For People Who Are:
- Smart software developers
- Familiar with object oriented programming. We use Grails and Java for our major
systems but are moving towards Go, Node.js for our service layer. We don't require
you know any of these languages, but expertise in *a* language is desired.
If you are interested in Go or node.js you should definitely get in touch.
- Familiar with Unix/Linux command-line systems. Logging into a Linux server to count
the number of ERROR lines in a log file grouped by hour wouldn’t be difficult
for you.
- Excited about joining a startup and wearing many hats.
- Authorized to work in the US
- Able to work from our Courthouse Metro office (flexibility to work from home
sometimes, but most time will be at the office)
If you're interested, email srijak AT ringio.com[1].
[1] Email should have your resume attached, have the string "from hackernews" somewhere in the subject line, and tell us why you think Ringio should hire you :)
Maybe just zk clients that listen to updates (watchers) on specific znodes? Business/validation logic can be on clients that can either be embedded in the app or write out to a config file consumed by another process.
Links are awesome in a small dataset, but on a larger cluster, the probability that each link walk means both an extra seek and a network roundtrip makes them less attractive.
Local graph databases avoid the extra seeks by keeping extra copies of the destination vertex immediately next to the source vertex on disk, but I don't think Riak is doing this, or that it is actually practical in an eventually consistent system.
Robert Morris, around 2004. I had an assignment that asked me to write about the Morris worm. So, I decided to shoot him an email with a few questions.
Needless to say, it made my semester (and not only because I got 20% extra credit on an assignment where that wasn't an option).
This scared me. I just installed a wallpaper app yesterday and while doing so thought "that's weird, why does it my personal information, phone calls etcs". But I still got the app. I guess my excuse is being used to my iphone, I didn't think about exactly how much access I was granting to this random app.
Anyway, I just checked, and the wallpaper app I had wasn't from jackeey. It's a top free app on the marketplace named Backgrounds by Stylem Media. And, it requires access to network communication, personal information, storage, phone calls, and system tools.
I have no idea how the warnings are generated.
Maybe devs are just including random libraries in their app (copy paste?) which are setting off these warnings? If not, why does this wallpaper app need my personal info?
Anyway, good wake up call, I will definitely be more careful wrt what I install on my phone.
EDIT: App request: something that logs/polices information going out from my phone. Firewall? we'll be needing a anti-virus next :(
