thebricklayr

Black holes don’t live forever. In principle, an external observer could watch you until the black hole evaporates. As mentioned above, if they never saw you fall in, then you never fell in. GR allows for disagreement on durations of events but not the events themselves.

For a region of space with time dilation approaching infinity, red shift to temperatures below even the microwave background would be nothing.

Agreed. Couldn’t black holes warp spacetime to the extent that there is no such place as “inside”? Time dilation is infinite at the event horizon, after all.

As you approach the event horizon, your frame of reference slows asymptotically to match that of the black hole while the universe around you fast-forwards toward heat death. I’d expect the hawking radiation to blue shift the closer you got until it was so bright as to be indistinguishable from a white hole. You’d never cross the event horizon; you’d be disintegrated and blasted outward into the distant future as part of that hawking radiation.

> I have a boatload of feature creep ideas for you to reject... Shall I post them here, or DM you?

Ha! Either, or feel free to email me at [email protected].

> Take a pic of a recipe, OCR if can

The app actually has an OCR recipe importer (tap "Add Recipe" > "Scan Recipe"). It uses Apple's native iOS OCR library, which inserts text directly from the camera.

It doesn't support importing from an existing photo yet though -- that's high up on my list to build (after Android).

> else host the pic?

You can upload photos for recipes!

> However, an interesting aspect of the "recipe" app logic is that it can apply to, say, mechanics

That's a really good point. I bet much of the underlying functionality could be re-used in a completely different app focused on something like mechanics. Another example I've thought about is a separate app specific to cocktail recipes, with features tailored around mixology and bar management.

Ironically, this is a great way to build actual products (if you’re open to letting them grow).

Three years ago I created a simple app for my family and friends to share recipes together. I kept adding features they requested, and after about two years, the app was apparently good enough that people started sharing it by word of mouth.

By October, the app had grown big enough that I had to start charging new users to cover server costs. I’m now contemplating a future where I work on it full-time.

I’m excited to start working on the Android version of Umami (https://umami.recipes). Like the iOS version, I’m building it 100% native, this time with Jetpack Compose.

I like to ask people _how_ non-deterministic laws of nature would give rise to free will, and listen as they stumble toward the realization that determinism is orthogonal to the subject.

Awesome work. Love your clean design and copy. Unwind has one of the best App Clip experiences I’ve seen. I’ve similarly built an app for my family to collaborate on recipes which I’ve since made public - https://umami.recipes

> does the server fetch the html itself?

Yep, the client just sends the recipe URL and then the server fetches the HTML. Agreed, it would be better to have the client send the HTML for paywalled sites, which is another reason I just want to do it all on the client.

> I spent quite some time on ingredient labelling (what’s a unit, quantity etc.)

I can relate to you there. It was a long process of trial and error for me to get right, and there are still plenty of edge cases left to handle. Long-term I think AI + NLP will make this kind of thing easier, but for me it wasn't fast, reliable, cheap, or portable enough to run in an iOS app in real time quite yet.

It's few enough users right now that I can cover the couple bucks per month in server costs. If more people start to use it, I'll make it paid (either upfront or subscription, not sure yet), but I'll grandfather all existing users as free.

Wow, this is awesome! Your layout, subtle dividers, and serifed font really come together perfectly.

At the moment, Umami's scraping is done server-side. I'd really like to speed it up, so I'm going to start working on a 100% client scraper soon (for the native apps & browser extensions; the web version will always have cross-domain browser restrictions though).

I just added multi-ingredient keyword search across all of your recipes to Umami (https://www.umami.recipes). If you’re on iOS, I’d recommend checking it out!

You may be right. My hope is the AVP is at least step toward something that could make potentially dangerous physical activities, like cooking, safer (e.g., by showing you the temperature of a surface before you touch it with your hands, as suggested elsewhere in this thread).

A temperature indicator is such a good idea. I’m going to add this to Umami.

Honestly, I am pretty excited to start building new AR-powered cooking experiences for Umami[1].

One thing I am worried about though: is the passthrough reliable enough for someone to use a sharp kitchen knife safely while wearing it?

[1] https://www.umami.recipes/

I'm open to it! Right now it runs on firebase and a unary gRPC service (nodejs). Probably firebase could be swapped out for supabase, and gRPC is easy enough to host.

Awesome, thanks for the feedback.

> 1. Import from other recipe apps.

Definitely agree. A couple days ago, someone asked for a Paprika recipe importer, which I've added here: https://www.umami.recipes/paprika-import I'll have to take a look at Pepperplate and NYT recipe box (though, you can already import any NYT recipe link!).

> Voice control

Love this idea.

> 3. Notes

There is indeed a notes section! Though I'm guessing you mean inline comments, like google docs style?

Thanks! Hopefully will have something in the next few months.

I tried that and it was super buggy... Thankfully I built the whole thing in SwiftUI so that I can port it to Mac fairly quickly. Moving as fast as I can!

Every iOS feature is available on web: https://www.umami.recipes/sign-in

But yes, you are right, as far as native apps go. FWIW, I just got an Android test phone so I can start on that version, should be ready in a few months.

Wow thank you! Fun fact: that orange color is actually part of the display-p3 color space: https://webkit.org/blog/10042/wide-gamut-color-in-css-with-d...

^ Colors in that space only just recently started getting supported by displays/browsers. And while p3 colors work in css on Safari, I had to use a single-pixel background png to make it work in Chrome.

Paprika is great, though Umami's importer is even better: https://www.umami.recipes

Umami has Chrome/Firefox extensions that you can use while on desktop, which will sync your recipes to the app. Disclaimer: I built it :)

Just last week, I added the ability to export Umami[1] recipes as Recipe JSON Schema[2]. Writing the code for it was quite pleasant thanks to schema-dts[3].

[1] https://www.umami.recipes [2] https://schema.org/Recipe [3] https://github.com/google/schema-dts