Wrapping worktrees + sessions into one place with some common actions actually seems pretty useful. Curious to try it out and see how it feels in practice.
19 karma · joined April 7, 2008
Wrapping worktrees + sessions into one place with some common actions actually seems pretty useful. Curious to try it out and see how it feels in practice.
"An angle grinder or drill bit will cut through the outer layer of a Proteus plate, but once it reaches the embedded ceramic spheres, the fun begins with vibrations that blunt the tool's sharp edges, and then fine particles of ceramic dust begin filling up gaps in the matrix-like structure of the metal."
message[pre_encryption]
with my unencrypted message in the POST data?
I suppose we could allow you to login to a more restricted account (no spamming since we do have email/sms out support) until you validate in some way.
The problem with a wiki, from my perspective, is the fact that it is unstructured. Some wiki's attempt to derive structure, or force users to use special syntax but that ends up being a little clunky. With structure comes some power. Tasks suddenly have meaning. A "Restaurant" data type can associate a map, or reviews. What we are trying to create is almost a personal content management system that helps users track all of that interesting structured data.
I am a fan of wiki's though. In fact I created
http://wikidpad.sourceforge.net/
Many moons ago.