Live data from Hacker News

Show HN: Paid, an API for invoicing

paidapi.com

31–37 of 37 posts

Re: Show HN: Paid, an API for invoicing

#31
post #8

Earlier quoted context omitted.

Why should that be noted?

There's no About page or any context to the team and qualifications for running a high-responsibility service, so this is the only information available about the quality of the platform.

Before reading that comment, it should be noted that minimaxir has been rejected from Stanford.

Re: Show HN: Paid, an API for invoicing

#32
post #8

Earlier quoted context omitted.

Why should that be noted?

A vendor's history and potential obligations are important.

What decision would this information inform?

"Well, that sounds like an awesome service, I just wish that Paul Graham had OKd it, then we would be in the clear"?

Re: Show HN: Paid, an API for invoicing

#33
I'm curious, on the technical side, what stack/technologies have you used? Also, did you scaffold the typical crud endpoints or manually wrote them, for each resource?

I'm trying to gain experience in building APIs and yours seems like a good model for doing so :)

Re: Show HN: Paid, an API for invoicing

#34

Does the laptop in the splash photo bother anyone else? It looks like they photoshopped the keyboard to be much shorter. Look how tall the screen is, then imagine you folded that down to meet the keyboard. That's no laptop I've ever seen!

The whole image is being stretched vertically in CSS ("background-size: 104% 160%;"). You can see the same distortion on the man's arm, the phone, and the pencil holder.

Definitely a "once seen, can't unsee" type of thing but I'll admit I didn't notice it initially. :)

Re: Show HN: Paid, an API for invoicing

#35
post #21

Earlier quoted context omitted.

The docs are an awesome repo by TripIt ( https://github.com/tripit/slate ). They aren't perfect, but they get you pretty far pretty quickly. Not sure what you mean by "links between your resources." Have an example? May be there (or we can build it if not). Correct on Unix time. Just being extra redundant.

Roy says[1] that to be truly RESTful, your resources (documents) need to be linked between each other, just like HTML pages. There are no definite standards yet (that I'm aware of), but JSON HAL[1] seems to be on the IETF standards track to be the one solution we settle on (just like we "settled on" in HTML). See also [3] for a broader overview on links in JSON and [4] for more information on resource linking and stu…

What about JSON-LD and linked data platform. At least JSON-LD comes from the W3C Web payement workgroup

Re: Show HN: Paid, an API for invoicing

#36
post #35
post #21

Earlier quoted context omitted.

Roy says[1] that to be truly RESTful, your resources (documents) need to be linked between each other, just like HTML pages. There are no definite standards yet (that I'm aware of), but JSON HAL[1] seems to be on the IETF standards track to be the one solution we settle on (just like we "settled on" in HTML). See also [3] for a broader overview on links in JSON and [4] for more information on resource linking and stu…

What about JSON-LD and linked data platform. At least JSON-LD comes from the W3C Web payement workgroup

I haven't looked into the available techniques for a few months. JSON HAL works fine for me for now. ;)

Re: Show HN: Paid, an API for invoicing

#37
post #32

Earlier quoted context omitted.

A vendor's history and potential obligations are important.

What decision would this information inform? "Well, that sounds like an awesome service, I just wish that Paul Graham had OKd it, then we would be in the clear"?

You should think about possible answers to the questions you ask before you ask them. And then, when you do ask them, do it in a better way.
Post reply on HN