A Simple Django Site

I have created a small Django project on the Google Code Hosting platform under the name lrbserv to serve a client who has a concept for a "Resource Sharing Social Network for People with Disabilities".

http://code.google.com/p/lrbserv/

By plugging together Django apps and adding a few (very crude) templates it has already several useful features:

• User registration with email verification.
• Login/logout
• User profile
• User Groups
• Tagging support
• Image Avatars
• Django Admin

I'd like to use the project to serve several purposes simultaneously, to wit:

• For the client who desires the web site in itself.
• As a reference Django project for myself and anyone else who would use it.
• To explore advanced methods, e.g. "Lean", model- and behavior-driven, etc...
• A way to teach web application development to anyone who would like to learn.

Even as rough and minimal as it is at present it can still be a fairly compelling foundation for a number of different social networks or online communities.  It reminds me of how a single square of origami paper can become unlimited specific forms just by folding it different ways.

420 days, or 14 months, or about 115% of a year.

Who would have thought that script would come in handy again so soon?

Ah my life.

So it seems our solar system, in its orbit around the center of the galaxy, is entering a region of higher-intensity interstellar flux and we are already feeling the effects.  All the ancient calendars and systems come mysteriously to an end around the same time in December two years hence.

Because this will be a smooth transformation, an easy birth, there's not much to do.  We just have to clean everything up and be ready to go in 26 months.  Piece of cake.  All the cake, up to the wheat fields and streams.

Unrealistic? Realistic.

Looking back over the posts I made on this blog I am convinced that this is a fine use of my time. I want to teach people computing, purvey my concept of a super-cool user interface to benefit society, create a super-cool space-themed ongoing storyline game, build gigantic flying machines from Bucky's geometry and Magnus Effect aerodynes, consume the Great Pacific Garbage Patch, foster and spread the use of Permaculture, provide jobs, education, and food security to as many people as I can, and ensure that our civilization faces the future and survives in style.

And I want to do it all at the same time.

191 days, or 6 months, or about 52% of a year.

It's been a long time.

from datetime import date last_post = date(2008, 10, 24) today = date(2009, 5, 3) days = (today - last_post).days print '%i days, or %i months, or about %i%% of a year.' % ( days, days / 30, 100 * days / 365, )

That's all folks.

What's the Source of Value for Students' Gigs?

I was chatting with Spencer Padway yesterday and he asked me a very relevant question. He wanted to know how I thought the students of the "web design" school would be able to compete with the labor and talent pools overseas, the infamous "outsourcers".

In essence, he wanted to know what the business model was for my students, how would they take the information they learned from participating in the educational activities into the real world to earn a living.

This is a very important and often overlooked aspect of learning "web development", and it's one I want to address directly and prepare my students for. Ideally I'd like to place all students in jobs or with work enough to live well.

I want the business model of the school and the business models of the students to have a similar relationship to a garden and the plants growing in it. The garden produces what the plants produce and the plants too.

But who wants our crops? Especially when they're on sale so much cheaper just a hemisphere away?

What's in a Business Model?
In simple terms, a business model is an algorithm that specifies how one expects to satisfy some expenses consistently over time.

One super-simple model that I really love is Kiyosaki's: You have income and you have expenses. You own assets, which are anything that puts money in your pocket, and liabilities, defined as anything that takes money out of your pocket.

The name of game, the generalized algorithm, is straightforward: Reduce your expenses and increase your income until the latter exceeds the former, then invest the difference by purchasing more assets.

Given the above super-simple definition of "business model" and the model of viability and wealth generation outlined, there are three aspects I want to address, and in doing so I hope to elucidate both the interlocking projects discussed on this blog and the path to long-term viability I see for my students. To wit:

• Reducing expenses
• Increasing income to adequate levels and maintaining it
• Information Age Assets

Expenses
In programming we often take the tack of solving the general problem that some particular problem represents, and then apply the general solution to the particular problem and solve it. This works surprisingly often and is almost always easier and feels as magical as it sounds.

Broadly speaking, I advocate a Permaculture garden with energy efficient home and attached energy harvesting gear to supply its own power. For transportation I'm developing powered kites, no really.

"You can solve all your problems in a garden" -Geoff Lawton. It's true. There's a ton more to say, but for now on the subject of expense reduction I'm going to bunt and say "Permaculture" and continue.

Maintaining Adequate Levels of Income
How do you find reasons for people to give you money, and then do it again?

That's the name of the game in modern business. That's what it boils down to at the end of the day, and in the internet age the reasons can become very esoteric indeed.

The TriGalactic game is a lot of things, and one of those is essentially a good reason for people to send in five bucks a month.

But why? And how do you find people to whom your answer to that question appeals?

Let's answer those questions in reverse order. I'm going to assume that TriGalactic has enough appeal, or that Student X has enough appeal, to attract customers, and address the question of how to find them.

Information Age Assets
There is an "asset" that's free, you don't have to pay for it, that requires little or no work (but can benefit from it), and that has the potential for open-ended returns, that is the returns are non-linear and can continue into the future, and it cannot lose money, i.e. it can never become a liability.

Furthermore, it is purely informational, so you can transfer it online and it has no direct environmental impact whatsoever.

As if this weren't enough, it has additional properties that answer the question above of how to find customers that want your particular value. It can connect you within a short time to a huge number of potential clients or customers thus providing the amount of work you need to meet your expenses.

I'm talking about the Dendrite Network, originally part of TriGalactic that I had planned to slowly "phase" into the real world. When I needed a social app to use as a teaching project for the school I figured it would be the perfect OpenSocial application.

The Dendrite Network, when used with a GameSeed that has a multi-tier affiliate program associated with it, becomes a sort of generic "amplifier" network both for the originator of the GameSeed and the transmitters who participate in the seed's propagation.

The Dendrite Network
In this day and age, I see a primary purpose of the Internet and computers in general as supplying you with whatever you require quickly and efficiently. Put another way, the web's job (one of them) is to connect you with the people who can supply your needs at a price you can afford.

This is the flip-side of the coin of finding enough customers.

The DN is designed to propagate "things", and multi-tier affiliate programs for those things give transmitters an additional motivation for participating in the propagation of quality "products". Any "product" attached to a multi-tier affiliate program that comes through the Dendrite Network becomes an asset with the properties described above.

To summarize, the Dendrite Network:

• Connects producers and customers of products.
• Allows rewarding of the intermediate transmitters. With properly designed affiliate programs these rewards can become significant. Participation in the network provides free quasi-passive "assets".
• Serves as a teaching project for our school.

Due to the generalized nature of the Dendrite Network it can handle both finding computer work for our students as well as finding healthy food (See "Promoting Permaculture Food Parks" in the previous blog post Everyone Eats, this ties back in to reducing expenses.)

Who wants our crops?
I am of the firmly held belief that viability in business is directly related to the value you provide your customers. If you're not providing a true value, then you won't last long in business, and conversely if you really are providing something of value then you'll seldom have a problem finding enough work.

The reason the DN can act as "mini-assets" is just that it provides the transmitters the opportunity to contribute something of value, namely their help "routing" the knowledge of the existance of something worthwhile to someone.

Really, if you can't provide something of more value than your brother programmers in the East then I'm certainly not willing to help you rip people off. There are a lot of ways to provide your customers value beyond simply writing code and html markup, and we'll explore those as we go, but I've already given you what I consider to be one of the most sure-fire: Aligning Levels, model on the blog, and directions for applying it on the FunkyGalaxy Mailing list.

If you are truly aligned on each of those levels then my experience indicates that you will never have to worry or struggle for clients or customers or what-have-you. If you're living your mission, you'll be taken care of in a way that seems magical. If you're not, then that's step one.

Introduction to Permaculture (excerpt)

A long quote from the pamphlet "Introduction to Permaculture" from Yankee Permaculture. I've clipped out what I think, in my warped biased mind, are some of the best bits. Mostly the parts where Mollison talks like Bucky really. This is agriculture the way Bucky's work was architecture, the synthesis of science and mystery. Enjoy:

We deal with the Earth, which has a fairly constant energy input from other parts of the universe. We are dealing with energy which has a renewable source, the sun. Between the source and the sink is where we intervene. The more useful storages to which we can direct energy between the source and the sink, the better we are as designers. So what we are up to is making an efficient set of storages that are useful to man. Some of these storages may be useful in the creation of other storages. The amount of complexity we can build into that flow, the amount that we can direct to useable storages in order to hold back energy until we start to use it, that's where the skill of the designer lies. Furthermore, a lot of energies unusable in a mechanical sense are usable in the biological sense. So we need biological as well as mechanical storages.

Energy can be transferred from one form to another, but it cannot disappear or be destroyed or created. So we have a choice in the type of flow that we allow through the system. We can determine whether it is stored or whether we let it leave.

That is the choice we have with water, with rainfall. We can store it or we can let it leave; and if we let it leave, it becomes unavailable to us.

If we would recover it, there is a lot of work to making it available again. Engineers go down to the valley, because everybody can see there is water down in the valley. So they put a block in the valley and the water backs up behind it and you have water, a big lake down in the valley where it is least useful. Where

it came from was up on the hills. Had the engineers stored the water where it came from, then they could have run it through all sorts of systems before they let it escape into the valley. The closer to the source that we can intervene, the greater use is the network that we can set up. So we edge up close to the source to start to intervene in the flow. It's not the amount of rainfall that counts, it is the number of duties we induce that water to perform that counts.

Resources are something you can feed into a system and increase its productivity, or its yield, or the number of useful storages. But if you continue beyond that point of productivity, then the system itself collapses. And that comes down to the statement that any integrated system can only accept that amount of energy that it can productively use. So you can over-manure anything, over-heat anything; you can over-plow anything. Whether we are talking about money or manure, you can put too much of it in. What then happens is first you start to get less and less increase in yield and then more and more increase in a lethal factor. You can't continue to pour in more of the same thing and get a continued increase in yield.

Then there are categories of resources that are of a totally different sort. There are resources which are unaffected by use. You can look at a beautiful view all day and it really doesn't affect the view. Information is such a resource. [But information is preserved by use. -DH]

There is another category of things that is interesting in that they increase if you use them. The more you use them, the more that they increase. Some forms of browse fall into that category. Some categories of animals and plants increase each other by interaction, and some other categories of resource also do that. And some resources, particularly quick turnover resources, simply decrease if you don't use them. Annual grass is a good example. If not used, the amount of annual grass in the system decreases. To some extent, so does firewood in a fire-prone situation. It accumulates as a fuel for wildfire when all of it is consumed at once.

But most resources lie in the category of resources that need to be managed to maintain them. They are those which decrease if used. We will call them finite resources.

There is still another category made up of resources that, if you use them, decrease everything else. We have a good example of that in uranium or plutonium. Plutonium in use tends to lay waste to other resources and some of those uses are horrific. Things like dioxins, if used as a resource, start to decrease the general resource.

So resources have a sort of hierarchy of management and a hierarchy of being beneficial or not beneficial. Most of the things that make us happy either are very manageable or there are plenty of them. There a few things which we think we need, but which make us miserable.

...it is not the number of elements in a system that is important, but the degree of functional organization of those elements - beneficial functions.

Yield is the sum of useful energy stores. It is the sum of energy conserved and generated in systems. It is never just product yield, not the number of pounds of tomatoes, or pounds of fish, or of acorns - which is the normal way people have of measuring yield - but it is the sum of the energy in useful storages. Yield is a function of design, and it is theoretically unlimited. That is, I haven't seen a system where we can't, by better design, increase the yield.

As the design itself is a function of our understanding of the system, so does the yield also depend upon the degree to which we understand things. It is the intellect that decides all these things, rather than any extrinsic factors. I am not quite sure what the intellect is. I have put it as our ability to understand, which may not be intellectual but empathetical.

Between the source and the sink, diversity increases: energy stores may increase and organizational complexity may increase. Our job is to convert those pauses in the flux of some of those categories into beneficial resources. It is the number of niches in a system that will allow a number of species and varieties to co-survive. It is the woodpecker's hole within the forest.

Now, again, the number of niches in a system depends on the design of the system. So now we have come to the active case. In situations which should be saturated with species, and with yield, we can make a vast difference by seeing where we can create more space, often by very small movements. [After first seeing where the unfilled niches, the empty spaces, exist, and filling them. Temperate ecosystems, in particular, often are incomplete.-DH] The numbers of pairs of pigeons breeding on a cliff depends on the number of ledges. It is easy to increase the ledges. Often, what is holding down a yield isn't the basic factor of food. In fact, food ceilings are very rare things to bump. It is some other factor totally unrelated to food. There are tons of food [acorns] around this environment [Wilton, New Hampshire], with nothing eating it.

What we must do is to see how things work, how different things work. Tribal lore prescribes that one should only carry out necessitous acts, that non-necessitous behavior tends to be very destructive. The rest follows. Therefore, one apologizes for whatever one has to do and does it. But you don't see people doing unnecessary acts.

Now there are different sorts of acts. There are necessitous acts and harmful acts. But there are also beneficial acts. And that gives us another hypothesis - that you probably will get more good back than you design. And this seems also to be true. What has probably been happening from the beginning of a consciously designed system is that when we put three elements in conjunction so that they are pretty harmonious, other beneficial results come out that we didn't design. Now that has happened almost without exception.

This is something that isn't being taught: that once we have done one thing correctly it goes on and it proceeds to do a lot of other things by itself. This seems to be happening. So it looks like there is something going on there, and it is very hard to analyze. Sometimes you make a single move, simple and right, which you intend to be beneficial, and you discover, if you stand back and observe it and leave it alone, that it goes on and gives you maybe another 10 benefits which you didn't count on. Then, if you look into it closely, although you put it together for a single reason - you had reasoned it out - you see that once you did that, there were 12 or 15 other reasons why you should have done it. I think we all know examples of this.

When somebody clamped the greenhouse onto the front of the house instead of standing it out there in the sun, he may have done it for a single reason, to heat the house, perhaps, or simply to make it easier to tend it. But then lots of other good things came out of that.

We are not quite sure what they are doing, but the aboriginal groups go around polishing up their country with little ceremonies. They are fairly secretive about what they do, but certainly they are doing a little countryside adjustment. They have to do a little ceremony to keep the springs flowing along certain a mountainside. We laugh at them. We know those springs will flow whether they have a ceremony there or not. But if we take their religions away, the springs will stop flowing. You don't talk to idiots about advanced concepts. Anyway, they won't tell us much about what they know. I suppose they would worry about what we would do with the information.

There is something we ought to be sitting on the floor and talking about a lot. There is this harmonic that, if we could get hold of it, would give us a lot of understanding, a lot of control over events. Our job is to put things in the right place and then let them rip. But to get one in the right place, we have to have a lot of information about it. Anything we are trying to place, whether it is a building or a tree or an animal or a road or a structure or a person, we have to know these things about it. We have to know its intrinsic functions, what is natural for it to do,the things it can't help doing by virtue of just being itself, being alive. Some animals and plants must spawn and they do that in different ways. Then there are things that we can categorize as yield, which we might be interested in. These may be of two or three levels or natures. There are what we might call direct yields. Chickens lay eggs. Then perhaps there are yields which are derived, secondary, or processed yields. Chicken manure will yield methane. And we have to know what the different yields are.

It also pays to know how elements function. They have behaviors, things that they do. They walk around or they sway about. They have properties. They will or will not reflect light. They have properties by reason of what they are. They have a color. They behave. They have a whole set of interactions and stimulus-response behaviors. Behaviors are short -term and long-term, too. Too often we comment on the short-term behavior of things, which isn't how they behave in the long term. Our science, and particularly psychology, suffers a great deal by not looking at the long-term behavior.

Now if we knew enough, if we had enough information, then a lot of these things could be listed for each element in the system, each entity. And then we could make a tremendous amount of design use of it. But they are not the things that are being listed as knowledge about the entities. You can obtain knowledge of almost anything about a tree except these things. Bad luck! Very little is known about the properties of a tree. As to the yield, it may be almost unknowable. I once tried to find out how people have used walnut trees. I found out that there is a people who base their whole culture on the walnut; other people may base their culture on bamboo. Or you can just take the walnuts by themselves. It is up to you.

If you have a fair idea of what is known about something, then you are able to place it so that it can function, so that its intrinsic function is possible to it. Then it will give its yields and its secondary yields can be taken advantage of, and it will behave in a friendly way because we put it near to things that are beneficial to it.

There is an enormous difference between the way we make a design in permaculture and the way an agriculturist would make it. Really, what we are up to is trying to let things function in a natural way.

Pretty breathtaking, hey?

Permaculture is why I look at the Great Garbage Patch as free candy.

First draft Tensegrity Kite Cell

First draft Tensegrity Kite Cell
Originally uploaded by trigalactic

This is a different design to Alexander G. Bell's. I wanted to make a true Tensegrity design to take advantage of the structural efficiencies.

The hallmark of a Tensegrity design is that none of the compression members (the coffee stirrers in this kite model) touch each other. They never experience anything but a direct inline compression.

This cell is easy to build. You take three struts and put them in a jig that holds them in the proper geometric relationship. You clip on two sails, one to the top and one to the bottom, then clip on the three tension cables. Release your new cell from the jig and repeat as desired.

I want to add sensors, wireless mesh comms, micro-aero-turbines for power generation, and small microprocessors to make each cell a sort of flocking robot. The corners of each strut-and-sail triangle can clip onto the edges of other cells to create a variety of tessellations in a plane. I'm still thinking about ways to stack planes to make volume-filling kites. That's one of the reasons I made this model, to have something concrete to handle and help figure that out.