text
stringlengths
9
408
[2191.86 --> 2194.22] an old JB project isn't it
[2194.22 --> 2196.26] yeah that's true that is true
[2196.26 --> 2198.56] there is the the open your
[2198.56 --> 2200.30] mouth recipes which we
[2200.30 --> 2201.56] actually used GitHub and
[2201.56 --> 2203.30] Markdown for those I was
[2203.30 --> 2204.18] thinking you know Scott could
[2204.18 --> 2206.54] get started with even out any
[2206.54 --> 2207.96] without any software selected
[2207.96 --> 2209.36] yet by just getting good
[2209.36 --> 2212.26] quality captures of those cards
[2212.26 --> 2213.84] and he's gonna want probably
[2213.84 --> 2214.98] something he can take over to
[2214.98 --> 2216.90] grandma's house or mom's house
[2216.90 --> 2219.98] or whoever whoever the the
[2219.98 --> 2220.70] family members you want to
[2220.70 --> 2221.60] capture these from because why
[2221.60 --> 2223.14] not get them all right you
[2223.14 --> 2224.50] could probably get away with
[2224.50 --> 2226.56] something like scan bot or the
[2226.56 --> 2229.16] other available scanning apps on
[2229.16 --> 2230.02] your phone but you might look
[2230.02 --> 2231.10] into scanner options too and
[2231.10 --> 2232.80] just start there start getting the
[2232.80 --> 2234.86] high quality images from there and
[2234.86 --> 2237.06] then the software will come I
[2237.06 --> 2238.60] found it okay it's called
[2238.60 --> 2243.70] vapeen 1111 slash recipes what a
[2243.70 --> 2245.68] catchy name huh it's a Django
[2245.68 --> 2247.26] application designed for managing
[2247.26 --> 2249.96] recipes and it's a web app so I
[2249.96 --> 2251.56] would imagine it runs out of a
[2251.56 --> 2253.52] container but it's got a search
[2253.52 --> 2256.26] built on top of Django's trigram
[2256.26 --> 2259.24] similarity search engine and it
[2259.24 --> 2260.72] allows you to create and search for
[2260.72 --> 2263.28] tags and assign them in batches to
[2263.28 --> 2264.64] certain files matching certain
[2264.64 --> 2266.90] criteria it will sync with both
[2266.90 --> 2269.80] dropbox and next cloud with more
[2269.80 --> 2271.62] support being added every every
[2271.62 --> 2273.96] week and you can import lots of
[2273.96 --> 2275.72] recipes from different websites
[2275.72 --> 2278.14] with JSON objects and stuff like
[2278.14 --> 2279.94] that and there are also apps for
[2279.94 --> 2281.52] mobile devices like phones and
[2281.52 --> 2283.96] tablets so yeah lots and lots of
[2283.96 --> 2285.80] stuff in there runs in a docker
[2285.80 --> 2289.38] this is what the reddit collective
[2289.38 --> 2292.98] thought recommends at the moment so I
[2292.98 --> 2294.56] haven't tried this one I just
[2294.56 --> 2295.72] haven't got to it but it's on my
[2295.72 --> 2297.00] short list so go and take a look at
[2297.00 --> 2299.10] that link in the show notes I also
[2299.10 --> 2302.16] recall that groceries had a bit of a
[2302.16 --> 2304.12] recipe manager I don't recall how
[2304.12 --> 2306.76] extensive it was but that's a past
[2306.76 --> 2308.92] pick too so we'll put links to all of
[2308.92 --> 2310.06] these the one that Alex just talked
[2310.06 --> 2312.02] about you could see the example of
[2312.02 --> 2313.34] how we used open your mouth on
[2313.34 --> 2315.08] github and just made it a community
[2315.08 --> 2316.30] project so you could have multiple
[2316.30 --> 2317.78] family members that contribute that
[2317.78 --> 2320.02] way or perhaps somebody out there will
[2320.02 --> 2322.34] know a great software project that we
[2322.34 --> 2323.86] haven't mentioned and inform us all
[2323.86 --> 2325.40] itself posted that show slash contact
[2325.40 --> 2327.58] the last one in our holiday
[2327.58 --> 2329.82] extravaganza mailbag here is a jasua
[2329.82 --> 2332.90] writes in regarding thoughts that were
[2332.90 --> 2334.84] inspired by self hosted episode 33
[2334.84 --> 2337.58] triggered by the helio 64 discussion he
[2337.58 --> 2338.92] says hey guys I was listening to your
[2338.92 --> 2340.82] review of the helio 64 with some
[2340.82 --> 2342.38] interest since I am the owner of their
[2342.38 --> 2344.86] previous product the helios for I
[2345.56 --> 2346.92] believe the points you make about
[2346.92 --> 2348.84] software are quite valid yet I'd like to
[2348.84 --> 2350.46] point out that there's a really hard
[2350.46 --> 2353.02] problem to solve I work personally with
[2353.02 --> 2355.40] a company in Israel that makes SBCs and
[2355.40 --> 2358.62] SOMs mostly with ARM based system on
[2358.62 --> 2361.06] chips it's my job to make Debian
[2361.06 --> 2362.76] available for each product to their
[2362.76 --> 2365.62] customers long ago when I started I
[2365.62 --> 2367.12] really wanted to do this the right way
[2367.12 --> 2369.14] I submitted bug reports and patches to
[2369.14 --> 2370.50] the Debian project for enabling all
[2370.50 --> 2373.04] kinds of small things a kernel.config for
[2373.04 --> 2374.68] a driver here a customized boot script
[2374.68 --> 2377.12] there enabling open GL ES backends and
[2377.12 --> 2379.88] shared libraries and continuously watching
[2379.88 --> 2382.42] and testing the distributions for things
[2382.42 --> 2385.04] that break turns out I never got to the
[2385.04 --> 2386.78] point where I could give customers a
[2386.78 --> 2388.64] pure Debian system there's always
[2388.64 --> 2390.54] another tweak that I had to carry out
[2390.54 --> 2392.78] of tree so to this day I'm creating
[2392.78 --> 2394.54] block device images with custom kernel