keithasaurus

12 ms·

91.
by keithasaurus 9y ago
That's the idea. Still needs some work :)
92.
by keithasaurus 9y ago
It's undocumented, but feel free to check out the calls in your browser's debugger. There's no guarantee of API stability or token permanence at this point. So integrations are not advised yet.
93.
by keithasaurus 9y ago
AWS/nginx on a fairly minimal instance. speed probably comes from: - it's an SPA, so it's mostly just doing API calls. - the database is designed to be fast at a few orders of magnitude of size beyond its current state - ever
94.
by keithasaurus 9y ago
lol
95.
by keithasaurus 9y ago
Nope. It's a pretty simple relation to express without external libraries, so I figured I'd keep the granular control and just do foreign keys. Easier to refactor schema or migrate data that way.
96.
by keithasaurus 9y ago
Thanks! All useful thoughts.
97.
by keithasaurus 9y ago
Thanks for the great feedback. Yeah, the version history, etc will have a UI at some point. You're also right that needs to be some sort of indication for the diff between forks. We'll get there. People haven't been going cra
98.
by keithasaurus 9y ago
It's meant to be a pun for "kitchen sink," and also to work with the notion of "sync"-ing. It's pronounced like "sink." Cinc is the number 5 in Catalan and refers to the amount of senses we use when c
99.
by keithasaurus 9y ago
I built it primarily for myself. It's able to run on cheap hardware and is very lightweight, so I plan to keep it up indefinitely at minimal cost. I haven't begun looking into funding/monetization, but that may happen soon. A
100.
by keithasaurus 9y ago
Cool. Hadn't seen this before. Is it your site?
101.
by keithasaurus 9y ago
Looks like a 502 error on the site. Is it still up? I'd be interested to see your approach if possible.
102.
by keithasaurus 9y ago
Yeah, I have this problem with Mac's keychain on Safari as well. I haven't had the time to fix yet, but it's helpful to hear the same from someone else. Thanks.
103.
by keithasaurus 9y ago
Yeah, there's a whole concept of how it may work for collaboration that has yet to be implemented. Thanks for the feedback.
104.
by keithasaurus 9y ago
Always happy to have feedback! The initial version will be rolled out in the coming weeks. Since it's a major product addition, there'll be some sort of announcement. So either sign up and you'll get a wonderful mass email no
105.
by keithasaurus 9y ago
This cracks me up. At the same time, it sounds like it's something that should be taken seriously. Thanks for the feedback.
106.
by keithasaurus 9y ago
already in the works :)
107.
by keithasaurus 9y ago
Yeah, densities and fuzzy matching. It'll get more intelligent eventually, but does a pretty good job on common ingredients at the moment.
108.
by keithasaurus 9y ago
Yeah, it's on the list of things to do. Once there are enough recipes/users it will also be useful to see the history/ancestry of recipe. There are already a few that are forks of forks. All the recipe data is immutable and v
109.
by keithasaurus 9y ago
If anyone wants to know the stack it's Django/Postgres on the backend, and an Elm SPA frontend. All data goes through an undocumented REST API.
110.
Show HN: Cinc – GitHub for recipes(cinc.kitchen)
363 points by keithasaurus 9y ago|152 comments
111.
by keithasaurus 9y ago
I can't access the linked page, but I run https://www.cinc.kitchen . It tries to be the GitHub for recipes, but also has some of the most advanced scaling and parsing available. So a lot of thought has gone into how data is