Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

realartists.com

Post reply on HN
Print view View original

31–40 of 106 posts

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#31

Post by rsanheim »

This is a impressive amount of work to keep things fast and to avoid hammering GitHub with redundant requests, which can get you rate limited[1] pretty quickly.

Couple questions:

* I'm assuming you are using the actual end user's token for auth, so at least you have the 5000 requests per user per hour?

* It sounds like the Ship server has a lot of (potentially private) user data sitting around to keep things fast. What sort of security do you have in place to prevent data leaks or malicious access?

[1] - https://developer.github.com/v3/#rate-limiting

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#32

Post by wlesieutre »

csomar wrote: post #19
fpotter wrote: post #15

Earlier quoted context omitted.

Yep - it's a 30 day free trial. After that it's $9/month. Like GitHub, we're also offering a plan for organizations that want to provide Ship to their whole team. Our pricing page goes into more detail -- https://www.realartists.com/pricing.html You're right, though - we should mention the free trial part on the front page. Thanks for the feedback and for trying it out!

How do you charge a subscription for a downloadable, native app? Does the app stop working if I stop payments?

Just ask Autodesk and Adobe, it's all they do anymore

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#33

Post by weaksauce »

rsanheim wrote: post #31

This is a impressive amount of work to keep things fast and to avoid hammering GitHub with redundant requests, which can get you rate limited[1] pretty quickly. Couple questions: * I'm assuming you are using the actual end user's token for auth, so at least you have the 5000 requests per user per hour? * It sounds like the Ship server has a lot of (potentially private) user data sitting around to keep things fast. Wh…

> Ship isn't just another GitHub API client app. Ship's custom server code listens and watches for changes from GitHub, and pushes efficient delta updates to clients.

Looks like you connect to their servers for updates.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#36

Post by kogir »

rsanheim wrote: post #31

This is a impressive amount of work to keep things fast and to avoid hammering GitHub with redundant requests, which can get you rate limited[1] pretty quickly. Couple questions: * I'm assuming you are using the actual end user's token for auth, so at least you have the 5000 requests per user per hour? * It sounds like the Ship server has a lot of (potentially private) user data sitting around to keep things fast. Wh…

> I'm assuming you are using the actual end user's token for auth

Yes. 5000 requests seems like a lot, though the GitHub API requires us to be pretty chatty. To show reactions we have to request them for every issue and comment individually, for example. Even doing it on demand (which we do) still requires a lot of requests.

> What sort of security do you have in place to prevent data leaks or malicious access?

We take this really seriously, but it's hard to answer comprehensively in a comment. Short story: Principle of least privilege, encryption where appropriate, strong passwords and 2FA for everything, write-only logging, super strict firewall rules, and parameterized queries.

I've been interested in security for quite a while and even briefly did security consulting, so to the extent I'm able, I've been doing everything as "correctly" as I know how from the beginning.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#37

Post by fpotter »

curun1r wrote: post #23
kogir wrote: post #2

Fred, James and I are in the thread and happy to answer any questions about the product and how we built it. There's definitely more detail than made sense to include in the blog post.

This looks cool, but superficially very similar to GitScout. Can you talk about what differentiates your product from that one? I'm not trying to be negative, but as a user of that program, I just want to know a bit more about the differences I can expect before I invest the time to trial your product.

Sure. The unique thing about Ship is that it is backed by a continuously synchronized local database of your issues, across all of your repos. This lets Ship run incredibly quickly. Because all of your data is already on hand and up to date, you never wait on the network.

Re: Show HN: Ship 2.0 – A macOS Native Interface to GitHub Issues

#38

Post by koolba »

> Ship 2.0 is two parts, a hybrid Cocoa/ObjC/CoreData/JavaScript/React application that runs on your Mac, and a C#/MSSQL/Orleans server that runs in Azure. Oh, and a little bit of glue written in Python running on AWS lambda. Yes, it's truly an unholy alliance.

What compels someone to write a net new application (from scratch with no legacy DB) that uses MSSQL?

In my book it's in front of only DB2 and Oracle on the "Will not use unless you're already using it, migration is impossible, and you're going to have to seriously pay me to deal with this" list.

Post reply on HN