61–70 of 83 posts
Earlier quoted context omitted.
Pretty sure this is meant for prototyping and maybe demoing in controlled environments. As soon as you involve auth, things get boring and annoying.
> As soon as you involve auth, things get boring and annoying. No, JWT is easy enough to implement.
FYI, there is a name clash with Caffeine, a Mac OS menu bar app that keeps the screen awake: https://intelliscapesolutions.com/apps/caffeine . But I guess this is expected with a name like this, and the scopes of the projects are clearly different, so this should be relatively harmless.
A very basic REST service for JSON data - enough for prototyping and MVPs! Features: no need to set up a database, all data is managed automagically* REST paradigm CRUD for multiple entities/namespaces schema validation search using jq like syntax CORS enabled easy to deploy as container
Just a heads-up, you might want to take down the example website. Now that it's been posted to HN you might see malicious actors. I also think it's prone to SQL injection at the moment? At least, it's raising a syntax error when inputting an apostrophe.
This needs to be an HN fN Masterclass by @Dang....
We should have regular visibility into /how/ HN is used by malicious actors.... HN has enough pedigree to get some insight from some of the top security folks... and it would be REALLY good to know how HN is being harvested in this space.
Earlier quoted context omitted.
> As soon as you involve auth, things get boring and annoying. No, JWT is easy enough to implement.
JWT is crazy annoying compared to "pass an API key" in the header.
Bare minimum JWT implementation is easy.
It never actually stores data on the server (it echos it into a cookie instead), so the dataset is only ever visible to you, no auth or service keys required.
Am I the only person who rolls their eyes when I see another Caffeine / Coffee named project?
Sorry if this is a little off topic, but what is it with devs and naming projects Caffeine? Am I the only person who rolls their eyes when I see another Caffeine / Coffee named project?
Of course Indonesian islands were the other possibility...
Similar project -> https://sheet2api.com/
I don't think this has a good price-performance ratio - all other solutions I know are cheaper...
Earlier quoted context omitted.
Are you saying that %v should be avoided in general, or just in the context of queries? (Go noob who doesn't understand %v)
First, don't build strings like this for sql. But for other strings built with sprintf, yes I am saying don't use %v unless for debugging, it's just one more avenue where you might be surprised by input, even if you're not building strings for sql. For example, someone might do this with user supplied data: myoutput := fmt.Sprintf("user:%v",userID) and if userID is a string like "foo" it'll end up in their string and…
Sorry if this is a little off topic, but what is it with devs and naming projects Caffeine? Am I the only person who rolls their eyes when I see another Caffeine / Coffee named project?