pea

Thanks for this. We'll hash something out in the next couple of days. If you want me to follow up, ping me at leo@kivo.com and I'll reach out to you with some more definite info.

Hi mate, sorry that was an error on my part. I've removed them and it should be good now. Cheers.

Hey guys, I'm one of the founders of TalkToUsers. If you've got any questions, just hit us up here or ping me at leo@kivo.com!

Woo! Thanks, I just pushed a fix which should sort that out. Thanks for your feedback. Failed web fonts begone :)

Yeah you're right for phrack. I never got why it was such a HUUUUGE issue for them. h0no was straight nihilist though.. http://shootingsawk.lescigales.org/h0no/h0no3.txt

Yeah it's a bit sensationalist: in the mid-2000s most hacker groups were just trollin' and pwning each other instead of trying to spread any political message. There was very little purpose in phrack.ru / h0no (apart from pwning whitehats and pissing people off. Their motto was literally rm -rf *)

This is great because a) I don't have to see youtube comments, b) it just keeps playing and seems to pick the ones I want to listen to, c) is simple

I've put them on Kivo, which might be easier to view and so people can annotate them.

https://kivo.com/p/h985rFcI

Hey guys, we're around to answer and questions about the product, so just ping us here or help@kivo.com. Cheers!

I agree with you in terms of abstraction; I do believe Scala adds a lot to practical programming as well. I feel the community is tainted by a bunch of type-nerds trying to compile their Haskell, and don't care about writing simple, maintainable code.

We use Scala because it is speedier to push features. I work much quicker in it, and we don't have to worry about a lot of the stuff we would in Java. That said, we don't use a bunch of the most complex features of the language (I am just talking simple pattern matching, map/flatmap/filter/unzip). So far, it's actually the most productive language we've used.

Our dig is the community and things peripheral from the core language: documentation is generally awful (Play, SBT). Dependencies management is awful (SBT doesn't work). Libraries are overly complex (Dispatch). And compile times suck.

Jesus, look at the difference between EPA and Palo Alto. I knew it was segregated, but amazing what one road can do..

http://imgur.com/JrLzd8X

The documentation also has an aura of "Isn't this all very clever?"

This attitude needs to die. Forever. Why the fuck should I need know about contravariance and parser combinators to write a basic web app? I hope this Scala forking will kill it in Typesafe. It has no place in actually building products.

I notice a lot of difference in quality between libraries released by enterprises and those by users. It's the difference between https://www.paypal-engineering.com/2014/02/13/hello-newman-a... and Dispatch. We need way more of the former.

Yeah I've wasted so much time dealing with code for the wrong version of Play. It's horrendously organised: case in point, the JSON parsing (WTF?)

Hey, we can build Onedrive integration. If you ping me on leo@kivo.com I'd be happy to discuss.

Hey, thanks for reaching out. It's something we are working on. Send me an email, I'd love to chat further: leo@kivo.com

Cheers!

Hey! Great questions: there is a definite need to collaborate online in some form. This 'collaboration' is currently emailing around the versions. We'd like to think if you can make a process that is just as easy as that, you're in the money for the majority of users. Plus, this is a really big pain in the arse for people, so they tend to look for solutions.

Re GDocs, Prezi, etc: we definitely could in the future, but PowerPoint is still the ubiquitous solution for making presentations for the large majority of people, so will keep us busy for a while. Plus, PowerPoint users are in much more dire straits as to existing solutions than GDocs ones are (we are fans of GDocs, but realise that most people cannot use it because they can't move away from MS Office).

Hey! Thanks for reaching out. We are a tool online which requires your documents to be in the cloud, but can slot into which cloud storage provider you are using (i.e. Dropbox, Box) easily. Ping me at leo@kivo.com and I'd be happy to walk you through it and get you guys set up.

Hey! So, we store the whole slide. In terms of deltas, we found the easiest way around it was a combination of tracking the slide through it's markup (OpenXML sucks, but you can extrapolate some UUIDs which help with tracking.) A lot of our analysis actually comes from the images themselves though, as they are an easier format (I.e. to help us see if the slide has changed.)

Hey guys, happy to answer any questions here or on email (leo@kivo.com). Enjoy!

Great job: making Git work outside it's familiar environment is a headache, but such an important problem to solve. It looks like they are some point on the way to doing it with Wordpress, so all the props to them. Keep on keeping on and don't let the naysayers get you down!

Kivo (YC S13) - London

We're building Github for documents and have started by creating the best way to store, share and get feedback on presentations. We're a team of three based in Soho, London. You'll be technical hire #2 and have a huge amount of responsibility and ownership of the product. We're looking for an excellent front-end developer. You love Javascript, but are comfortable picking up other languages, and obsess over building the best possible user experience. Customer feedback is our guiding light so working closely with users in shaping Kivo should excite you.

Our back end is Scala / Play and we're in the process of moving to Angular, so bonus points for experience with that.

Equity grants will be well above market for first hires and salary will be competitive. We want new partners, not just employees, so we are looking for people who are as driven to succeed as we are.

We're hiring for people who want to help lead the team as we continue to grow, so you should be excited to shape the development culture of a fast growing start-up.

We also know there's more to life than work. You get gym membership for gyms across London and an extremely sociable team to work with. We love poker, eating out, tennis, and nights at the pub.

If this sounds exciting, ping us (leo@kivo.com) and we'd love to buy you lunch and have a chat.

Hey Mike -- my bad, I just realised that the sign-up button on the blog actually takes you to kivo.com, instead of actually signing you up (and that you have to click sign-up there again). I'll get on fixing this ASAP. Thanks for your feedback!

Ah! Cheers!

Thanks for your reply! Sorry our homepage wasn't clear enough: Kivo is a way to annotate presentations and PDFs in the browser. If you want more info, check out the video on the homepage or try the example presentation below it.

Re the problem we are trying to solve: giving feedback on documents really sucks. Emailing around 'Slide 1: change x,y,z, Slide 2: change this' and other out-of-context comments is a massive pain-point for users, who want to be able to do it quickly, visually, and in their browser (instead of in an old piece of desktop software). Feel free to ping me on leo@kivo.com if you have any more questions.

Great! Chuck us on too if you'd like: www.kivo.com/jobs

Hey! Yeah, for now that would work. I can also add in editing if you think it would be useful? Shouldn't take long. If you have any more feedback or feature requests ping me on leo@kivo.com. Cheers!

Thanks a lot for the feedback!

1) Thanks, I will fix that; I agree it is not clear. We accept pptx, ppt, and pdf.

2) With early users, we found that content creation of Word documents can happen relatively easily outside of Word; this is not the case with PowerPoint. There are a couple of great online Word processors, and GDocs does a good job of annotating text. PowerPoint is different because it is still the ubiquitous way to make a presentation, a piece of software which has few alternatives, and currently no decent solution exists for this pain-point.

3.) That's a good idea. We did boxes first of all, because it's a one-size-fits-all approach and we wanted to keep it simple. We will be adding more specific annotations (text, shapes, graphs, etc.) in the future.

Thanks again for reaching out -- and feel free to email me (leo@kivo.com) if you have any more questions!

Hi guys -- yes, version-control is being added in in the next few weeks. Ping me on leo@kivo.com if you need any help, or have any ideas re what you guys would like it to look like.

Hey, pretty sure I did reply to your message, I just checked and the last email I got back from you was presumably sent in error, and we didn't see the preceding message. I'll follow up again now and happy to hear from any scala / js / otherwise-awesome devs in LDN (leo@kivo.com).. No pester at all :)