permaculture

[negiliblek <negiliblek@yahoo.com>]

Rafter,
I've sent a jpg file to you (to your liberationecology email) that shows a 
plate with the original pod, the cleaned but untreated beans and the fully 
processed ready to eat beans (let me know if you didn't get it).

> do you eat the pulp that surrounds them as well? 

In the green stage (undeveloped/not mature), the entire pod can be eaten and 
it is mostly sugar as you've read.

>The pulp is supposed to be up to 30% sugar in some varieties!

In the mature brown stage, the pod skin is full of tannins. Inside of the 
brown pod, there is a green substance (looks like green sugar that got wet 
then dried) that is almost pure sugar (by taste) and is edible. The effort 
(using the pick each little bit out of the brown pod by finger nail method) 
to get this sugar out isn't worth the time (if someone has a suggestion of 
how to separate this sugar from the pod without getting the tannins too, feel 
free to share). The bean is 10 to 24 percent protien, but needs the tannins 
to be boiled out after removing from pod.

making the bean edible:
1-get them out of the pod and wash all the gunk of in a rinse of cold water.
2-put beans in a pan of cold water and boil for 30 min
3-pour off the hot brown water
4- put the beans in a pan of cold water and boil for another 30 min
5- pour off the hot brown water.

the beans are still hard as buttons at this time (but tannin free), I'd 
recommend freezing them at this stage cause if you don't, inspite of being 
boiled twice, little hard shelled beatles will emerge from the bean and leave 
you with a white powerdy dust + brown shell. That or roast them lightly like 
some do with corn to keep the weavils out.

6- when you're ready to eat the beans, boil for 1-2 hours like you would 
kidney beans or black beans.
7- the beans can then be added to meat for a chili like soup 
8- or the beans can be covered with honey and milk (tastes like a grain 
cereal)

(7 and 8 are true because the bean has a very mild meaty taste which could be 
swayed in either direction by what you add to it)

www.pfaf.org said it could be used as a coffee, so I tried the following:
1-get the beans out of the pod and wash in cold water a bit more than above.
2- roasted them until evenly browned 
(they'll burst a little but don't blacken them -I used a gas oven)
3- ground them into a fine powder in a hand grinder
4- poured boiling water through the ground powder

this resulted in a dark brown liquid which tasted like a gourmet coffee
I only drank six liquid ounces ...it was like drinking a triple expresso!!! 
DRINK THIS MIXTURE AT YOUR OWN RISK: if you get a heart attack or burst a 
blood vessel -tain't my fault you got a weak pressure system.

when the drink became cold, it tasted exactly like cold coffee with the same 
jolt I got when it was hot.

If anyone knows a better way to prepare honey locust beans, please let me 
know!



      
>From lflj@intrex.net  Wed Mar 18 01:27:30 2009
Return-Path: <lflj@intrex.net>
X-Original-To: permaculture@lists.ibiblio.org
Delivered-To: permaculture@lists.ibiblio.org
Received: by lists.ibiblio.org (Postfix, from userid 3002)
        id 9609D4C015; Wed, 18 Mar 2009 01:27:30 -0400 (EDT)
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on malecky
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled
        version=3.2.3
Received: from fmailhost01.isp.att.net (fmailhost01.isp.att.net
        [207.115.11.51])
        by lists.ibiblio.org (Postfix) with ESMTP id 8F5AB4C012
        for <permaculture@lists.ibiblio.org>;
        Wed, 18 Mar 2009 01:27:22 -0400 (EDT)
Received: from [192.168.2.102]
        (adsl-065-005-197-216.sip.rdu.bellsouth.net[65.5.197.216])
        by isp.att.net (frfwmhc01) with ESMTP
        id <20090318052721H0100kkuhve>; Wed, 18 Mar 2009 05:27:21 +0000
X-Originating-IP: [65.5.197.216]
Message-ID: <49C08636.8040203@intrex.net>
Date: Wed, 18 Mar 2009 01:27:18 -0400
From: "Lawrence F. London, Jr." <lflj@intrex.net>
Organization: Venaura Farm
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
        rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: permaculture <permaculture@lists.ibiblio.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [permaculture] Wolfram Alpha is Coming -- and It Could be as
 Important as Google - Also see: True Knowledge - technology
X-BeenThere: permaculture@lists.ibiblio.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: permaculture <permaculture@lists.ibiblio.org>
List-Id: permaculture <permaculture.lists.ibiblio.org>
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/permaculture>,
        <mailto:permaculture-request@lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/permaculture>
List-Post: <mailto:permaculture@lists.ibiblio.org>
List-Help: <mailto:sympa@lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/permaculture>,
        <mailto:permaculture-request@lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2009 05:27:30 -0000


Again, For the Permaculture Knowledgebase/Database/Guild 
Database/Plant/Animal Relationships Database enthusiasts
from previous projects that arose from this list:
========================================

True Knowledge - technology
http://www.trueknowledge.com/technology/
"       
+TECHNOLOGY

Summary

Architecture

Demo Video
                
Our Technology

Very basically we have created a technology which can represent the world's 
knowledge in a form that is clear and 
accessible to humans, as well as being comprehensible to computers. This is 
different from the knowledge stored in 
websites and books, which is written in natural language that is good for 
humans, but incomprehensible to computers.
Because it is so different it is hard to describe the technology by direct 
comparison with anything else: instead there 
are several completely valid ways of looking at it. These include:
A Question-Answering Site
One way of thinking about our technology is that it is a website where you 
can ask questions about any subject and get a 
direct response. Unlike human-powered Q&A sites, you don't need to wait for 
someone to respond. The computer answers 
your question using knowledge stored in a form it can comprehend, and isn't 
just regurgitating text that it doesn't 
understand. For this reason it can answer questions it hasn't seen before and 
can combine knowledge through a process of 
inference and cross-referencing stored information to produce a reasoned 
answer.
The Answer Engine - The Perfect Complement to Search
Another way of thinking about our technology is as the perfect complement to 
search. A user can treat our site just as 
you did your previous search engine, but in addition to receiving a list of 
documents, your query will also be passed 
through our technology - if we can help more directly we will. Your query may 
be a standard question; even if it isn't, 
we may be able to work out what you are looking for and give you the answer 
directly, at the top of your screen. Because 
of the way facts are assessed you can enjoy a high degree of confidence that 
any information we retrieve will be 
accurate (unlike information on any single web page).

Using our question-answering technology we can also interpret the typical two 
and three word "keywordese" queries that 
people have learned to type into search engines as questions and can produce 
an inline response. Where what is typed is 
just the name of an entity, our technology can produce a small information 
screen giving core information about the 
entity (as well as search engine results). This information screen is 
populated from our knowledge base and determined 
by the type of thing that has been entered by the user. For example, a 
business screen can contain contact details and 
their official website.

Platform partners can similarly use our API to integrate our question 
answering with their search results.
A "Wikipedia for Facts"
The knowledge in our system comes from two main sources: information we have 
imported ourselves and facts added by users 
like you. A big part of our technology is enabling users to add knowledge 
without having to have any technical 
understanding of the underlying computer processes.

The crucial difference between our technology and sites like Wikipedia is 
that, whereas their users create and edit 
documents in natural language, here the information is in the form of 
discrete facts. Unlike natural language, these 
facts are in a form that computers can understand and process.

One advantage of having the computer understand the knowledge it holds is 
that the quality of the knowledge can be 
maintained. With our system once a fact has been established with enough 
evidence it can't be easily changed. 
Furthermore, facts that contradict this knowledge are also automatically 
prevented. Within Wikipedia when someone 
maliciously or erroneously edits a page, the only solution is for someone 
else to change it back. Any page being looked 
at is the opinion of the last person to edit the page.
A Universal Database
With a typical database-driven application the developers sit down and create 
a schema - a number of related database 
tables and fields which store the data required. They then write code which 
manipulates and processes the data in that 
schema and when the application is finished this code is run by users. The 
knowledge that such a system can process is 
extremely narrow and remains so because nothing that happens after launch 
expands the scope of the application. Users 
may add data to the tables but the schema remains fixed.

Our technology is like a database application except that everything in it is 
amenable to expansion by users. The scope 
of the knowledge that it can store expands every time a user adds a new 
class, relation or attribute; and knowledge 
about every conceivable entity can be put into our system and used to answer 
questions.
A Platform for Building Knowledge Services
Every database driven application that has ever been written starts by 
knowing nothing.

Building a knowledge service thus involves many thousands of hours of hard 
work creating and populating database tables, 
and writing software to manipulate and present those tables. Such systems 
needs to be taught everything from scratch, 
and at the end they know very little: only the narrow knowledge put in by the 
developers.

Building a knowledge service on top of our technology is different. The 
system already knows a great deal; new services 
can be built on this and existing knowledge can often be leveraged - 
massively reducing implementation time and 
ultimately increasing the quality of the delivered service.

We experience this every day as we add knowledge services to our system."