My personal solution is so much more simple than this shitbowl solution and is trivial to implement. I have been using it for years and can personally vouch for it's effectiveness and scalability. Skip the bowl entirely. When you finish with something just set it down. It really DOES NOT MATTER WHERE! Honestly. Set it on a flat surface, under a chair or a pillow, in a depression in your yard. Set it on your neighbor'…
Shitbowl: The algorithmically powered in-home physical caching platform
161–170 of 247 posts
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#162Doesn't support Node or JSON. This is stupid.
By profiling an individual using their online behaviour, and using only a small cluster, we could produce a prediction of what objects should be sorted to the top of the bowl. Simple IOT connectivity could then tell if the right objects are near the top and send push notifications to your phone. These would warn you that what you thought you wanted next was not what your social network would have wanted.
Altogether a much simpler solution
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#163Why is this a product? I could implement this myself in a weekend with a few open source libraries.
Am I a millionaire yet?
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#164Re: Shitbowl: The algorithmically powered in-home physical caching platform
#165My personal solution is so much more simple than this shitbowl solution and is trivial to implement. I have been using it for years and can personally vouch for it's effectiveness and scalability. Skip the bowl entirely. When you finish with something just set it down. It really DOES NOT MATTER WHERE! Honestly. Set it on a flat surface, under a chair or a pillow, in a depression in your yard. Set it on your neighbor'…
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#166Earlier quoted context omitted.
I don't care about that as long as it efficiently handles the worst-case of the sock tuple matching problem.
I just implemented a proper cache for unmatched socks this morning! I just got a dresser and dedicated one drawer to socks embedded in a plastic hexagon matrix, with an area on one side for unmatched socks awaiting the re-appearance of their mate on some future laundry day. It is a slow process but it is very low energy.
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#167Why is this a product? I could implement this myself in a weekend with a few open source libraries.
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#168Shitbowl v3.0: Adds a multi-tiered dumbwaiter, that makes retrieval and storage to center of the earth a snap;
Shitbowl v4.0: Adds a reciprocal well that extends to the antipode of the earth, and allows users, so-situated, to borrow from their counterpart, least-used items of the counterpart, Uber-style.
Shitbowl v5.0: Implements a heat-hardened round-house router to universally exchange least-used items, near the earth's core
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#169My personal solution is so much more simple than this shitbowl solution and is trivial to implement. I have been using it for years and can personally vouch for it's effectiveness and scalability. Skip the bowl entirely. When you finish with something just set it down. It really DOES NOT MATTER WHERE! Honestly. Set it on a flat surface, under a chair or a pillow, in a depression in your yard. Set it on your neighbor'…
Put things back in the first place you looked, or the first place you would look for it.
Re: Shitbowl: The algorithmically powered in-home physical caching platform
#170Why is this a product? I could implement this myself in a weekend with a few open source libraries.
Little known fact, the PDP11 had a machine instruction that implemented shitbowls in the cpu. It’s interesting that these days you need ruby, a vm, two layers of package managers and oauth just for a shotbowl. Also, someone should rewrite this in rust.