That first idea has to do with how to integrate an answering machine like capability in an audio/video stream that adapts to bandwidth. It's not exactly new, yet I realized I had never wrote it down before.

The second idea has to do with the purpose of [Izumi|WhatIsIzumi] -- that is I'm an engineer so I tend to explain projects from a technical point of view of how they work, yet somehow I understand that it is sometimes more relevant to ignore all technical details and simply solve one problem. Even if a system is made generic to solve more than the one problem at hand, people may not understand what the generic system will solve. Instead it is easier to just tell them exactly what they can do with it. Then once they get used to it, they may start asking for more functionality and with some luck the system can be expanded to include that.
If I apply this view to [Izumi|WhatIsIzumi], instead of describing it as a content management system I could describe it has a place to keep links, photo albums and other kind of material centralized on a server, with automated mechanisms to publish it on the net (thus potentially indexable by search engines) and of course the ability to decide what is public or private.

In [Dev/IdeasForDev] you can read on version numbering and my point of view of Python

Finally I bought Design Patterns and started reading it. Very interesting stuff, especially since it may give me a good leverage. There's a number of patterns which I was already familiar with although I didn't quite knew their name (Singleton or Abstract Factories for example.) I realize also the part of [Xeres|Dev/Xeres] or [Dev/Nerdkill] where I focus more on the architecture rather than the end product can be though as developing my own patterns.