4 ms·

It's nice - maybe not yet final, but I like the idea and how it currently works! You could probably reuse the same engine to do the same with cocktails and may

It's nice - maybe not yet final, but I like the idea and how it currently works! You could probably reuse the same engine to do the same with cocktails and maybe other stuff.

jka 6y ago
Thank you. Sometimes it feels like development progress is slow and that the UI could do with a complete overhaul (the project does have some design volunteers offering time and improved designs which are being incorporated slowly - I'm the bottleneck!); but it's gradually improving and enjoyable to work on. All the components and dependencies are open source, so there's a social and learning element involved when integrating new features and finding bugs / improvements in other projects. Cocktails could certainly be another domain this could work for, and homebrewing is another that springs to mind. I'm not currently intentionally keeping the core services extensible to those, but forks and/or later generalization of the application are both possible.
- zepearl 6y ago
  Just some additional thoughts: 1) you might have to do in the future some deduplication of entries in your master index - e.g. by searching https://www.reciperadar.com/#search&action=search&include=bacon,pasta,onion,egg&sort=ingredients https://www.reciperadar.com/#search&action=search&include=ba... I see that the entries pointing to thepioneerwoman.com & tastykitchen.com for "Pasta Carbonara" are identical (the 2 sites might be mirrors of each other or one site might just have copied the contents of the other one) => depending on how much your index will grow you'll maybe want to show only 1 result pointing to 2 different URLs. 2) The scraping of contents of other websites coupled with displaying it directly on our own website might become problematic. Meaning that you would be an "ally" of the source websites if you would just show the results and the overview of the needed ingredients but then just point to the recipe hosted on the other website, but you would become an "enemy/opponent" if you would display the recipe directly on your site. Meaning that on one hand I would not be happy at all if somebody would steal my contents and stop users from getting to my website (I would therefore e.g. blacklist their bots and IPs from which they would try to scrape my site), but on the other hand for somebody that might increase traffic to my website I would potentially even provide a special API so that that bot could get better quality data (instead of scraping the html). Cheers & good luck :)

It's nice - maybe not yet final, but I like the idea and how it currently works! You could probably reuse the same engine to do the same with cocktails and maybe other stuff.

jka 6y ago

Thank you. Sometimes it feels like development progress is slow and that the UI could do with a complete overhaul (the project does have some design volunteers offering time and improved designs which are being incorporated slowly - I'm the bottleneck!); but it's gradually improving and enjoyable to work on. All the components and dependencies are open source, so there's a social and learning element involved when integrating new features and finding bugs / improvements in other projects. Cocktails could certainly be another domain this could work for, and homebrewing is another that springs to mind. I'm not currently intentionally keeping the core services extensible to those, but forks and/or later generalization of the application are both possible.

zepearl 6y ago
Just some additional thoughts: 1) you might have to do in the future some deduplication of entries in your master index - e.g. by searching https://www.reciperadar.com/#search&action=search&include=bacon,pasta,onion,egg&sort=ingredients https://www.reciperadar.com/#search&action=search&include=ba... I see that the entries pointing to thepioneerwoman.com & tastykitchen.com for "Pasta Carbonara" are identical (the 2 sites might be mirrors of each other or one site might just have copied the contents of the other one) => depending on how much your index will grow you'll maybe want to show only 1 result pointing to 2 different URLs. 2) The scraping of contents of other websites coupled with displaying it directly on our own website might become problematic. Meaning that you would be an "ally" of the source websites if you would just show the results and the overview of the needed ingredients but then just point to the recipe hosted on the other website, but you would become an "enemy/opponent" if you would display the recipe directly on your site. Meaning that on one hand I would not be happy at all if somebody would steal my contents and stop users from getting to my website (I would therefore e.g. blacklist their bots and IPs from which they would try to scrape my site), but on the other hand for somebody that might increase traffic to my website I would potentially even provide a special API so that that bot could get better quality data (instead of scraping the html). Cheers & good luck :)