Hacker News new | ask | show | jobs
by slavomirvojacek 1767 days ago
Hi all, since we've had a bit of traction today I thought I'd ask whether there are any additional features you'd like to see added?

For example, some sort of "self-serve" UI where you could get an API key which would allow users/teams have dedicated rate-limits and not use the default/public limits? Or a self-hosted option where the API could be deployed to the company's cloud of choice?

Or.. leave as is?

Please let us know! :)
2 comments
kodablah 1767 days ago
> Or a self-hosted option where the API could be deployed to the company's cloud of choice?

Can put it on Tor and give an ephemeral onion link (I wrote https://github.com/cretz/bine to help w/ just these use cases). So people could access via Tor browser or via the same CLI with a "client"/"get" command. Can even have the ephemeral server determine its been HTTP "GET"d and kill itself. Then you don't even need a public website.

link
bndw 1767 days ago
Is the server component running at api.ots.sniptt.com open source? I looked through the org's repositories and wasn't able to find it.
link
slavomirvojacek 1767 days ago
It is not at the moment but we are considering making the server + maybe infra repos public in the future, most likely when we've agreed on and implemented some sort of self-hosted option(s).

We will probably write a blog post or two about how we've designed the API + infra around it as there are some interesting topics to be covered.

One of the goals was to also have fun and experiment with a few approaches we've been wanting to use but could not on our daily jobs.

For reference, everything is on AWS and we are using AWS CDK (TypeScript), having moved away from serverless.com recently.

We are ONLY using managed services/resources which are "fully serverless" (API GW, WAF, Dynamo + Dynamo Streams, Lambda, EventBridge, ...) - to save cost, to minimise waste, to reduce ops, etc.

Hope this helps, happy to provide more details.

link