.
FRDCSA | internal codebases | ALL

ALL Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

First of all, there is an immense amount of knowledge that has been written. To expand our minds we ought to learn foreign languages. There are mystic languages (e.g. UniCode), which have enormous alphabets and have strange decipherment principles. We choose to learn various languages based on their strengths and weaknesses. Chinese will be useful for picform. Sanskrit is a formal language with a 5000 year history, some of which was oral. Gaelic was oral as well. Hebrew is useful for certain reasons, etc,etc,etc.

Capabilities

• Start trying out all software and declare flags for or against software.
• Make a phone list of all the contacts I have.
• note that I'm not sure all unilang.xml messages made it into the system.
• Should add to the camel case all known instances of our camelcase words, and use a best fit algorithm.
• all should do ontology extraction to build its phrase dictionary.
• Setup an ldap server and add all information to that.
• Get Everybody's email all into an address book on FRDCSA or something.
• Have a system to record all known instances of certain types of programs. In other words, have a tags system.
• architect should use game tree search and search out what should be developed based on all knowledge and estimation.
• Fix music to play many songs that we all like.
• Be sure to know how to operate all the different aspects of my systems.
• Suggest everyone start using movielens so that we get movies that we all want to see, on all of our wishlists.
• Remove all files called predator
• Write thank you letters to all authors of systems.
• They make it impossible to define truth here. That is how its all lies. You cannot define truth here.
• Pile up all my questions from this system and send them to maintainers.
• all: http://visl.sdu.dk/
• all: /var/lib/myfrdcsa/codebases/external/sims-20061126
• all should check into some of those databases for text.
• Leaving off - Need to complete the bridge between all::TTS::English and Festival as well as all::TTS::Irish.
• all does in fact contain spoken support and therefore that's where it belongs.
• Should extract all comment sentences out of scripts and add this to general knowledge prefixed by the context in which the script is written in.
• Write a central text processor that has links to all the cools systems and that can at a moments notice perform just about any analysis on a piece of text.
• Fix all the contact information in fweb and do a rebuild.
• Redo all passwords that use insecure passwords.
• Build representation for frdcas projects, create a bin dir and link all executables to it. Also track all project names for pid files, etc.
• need a program to list what all the other ones do
• Read all the sacred texts.
• all the different web pages open, terminals open, etc.
• Before going to bed, ensure that laptop is nearby with all the different items I need.
• Locate and remove all instances of passwords in scripts.
• Write a letter to the RT mailing list asking whether RT is usable to track very fine grained almost development work. Explain that I keep a database of all the various things I think of and whether or not RT would scale and be responsive to thousands upon thousands of open, nested tickets.
• For now, do maximal noun phrase extraction and summation over all tickets to try to identify projects. A rather good idea. Then project relation can be established through collocation.
• Use Proc::Daemon and Sys::Syslog or some other logging facility to create daemons out of unilang agents, allowing for proper starting and stopping of all daemons. Add the code into the unilang client software.
• Where is that system for recording all the perl modules we have installed.
• Figure out how to verify my packages and rebuild them all with verification.
• Locate all files linking into from bin releases and make them legit.
• o reasonbase should add links to all instances, for cross linking.
• An agent that does its own planning and reasoning. Right now all I do is write code.
• o Humor: Secure all animals in the barn!
• Let us scrub chess, maybe even gaelic history, let us scrub all forms of lust, let us pursue "looking toward the light".
• Is satisfaction the root of all evil?
• Let us find what all religions have in common and publish a document about the common values of all religions.
• setanta - Write a program and hook it to UPS smtp system to shutdown all non-critical services in the event of a power outage.
• all - there must be languages upon languages.
• all - Remember to start a new language, one with many rules, yet easily remembered. One with words for almost all useful concepts, a word that represents an action, reifies it, for instance a word to mean - I don't want to do that myself, but I don't mind if others do. The language must be generated from other rules, for instance, cannot just assign a word to this because there has to be contextual relevancy that is given away by the word itself. And also, most likely, words must satisfy more complex rules, especially of the cross-eyed language.
• He's probably offended that I'm pushing Gaelic music before listening to his all the way.
• Replace advertisements with Knovertizements. That is, instead of trying to sell products to people with salacious advertisements, we try to teach them things, with targetted knowledge. For instance, "Did you know that Ord is the proper class of all ordinals and is larger than any given set in axiomatic set theory. Click here to find out more!"
• all can have facilities for showing pronunciations of words we have yet to encounter.
• Develop document explaining the design of the FRDCSA for someone coming through it for the first time with all the different commonly used aspects and goals.
• Create a centralized link thing to all the Chicago hacklab related stuff (including key players, mailinglists, websites, groups, etc).
• Create a centralized link thing to all the hacklabs.
• For all, the system should scan the sentence first to see if there are any words where the user is unfamiliar with any of the senses. Only if a sense exists that the user is not necessarily familiar with should it be scanned. A model of which senses are common can be had by doing statistics over various books and discounting a certain number of the first words.
• Add food stores to all the places I normally stay at. MREs.
• Should be naturesque, and have poetry and singing recitals, along with a natural social arrangement with all the elements of culture.
• Throw a party and have all the elements as you can recognize should be there.
• So that it is all centralized and as simple as upgrading a package, and if changes are made on a remote server, edit them.
• Roll packages for all my work.
• all those that would work with me are dead and gone.
• Restart on all my projects!
• This is like my family coming to aid. "Well," said Donal, "if I was sitting right [65] close to a big fire, and you piled on it all the turf in a townland and all the wood in a barony, sooner than have to move I'd sit there till the boiling marrow would run out of my bones."
• Of all the good ideas.
• Make a movie of all these ideas.
• audience - Before responding to a message, consider that your understanding of the message or at least the intent of the writer may not have been correct in some or all ways, hence should not respond immediately.
• Write a system for helping the user readjust to a particular language. Show them all the features of the language.
• Refute this ridiculous argument that it is all a matter of personal responsibility.
• setanta should know the schedule of all actions, to know which services will slow as a result.
• setanta - all network changes should be announced to those affected several business days before the outages occur.
• study should use table of contents as the source for all extracted subject areas.
• Rule - always record all data during expensive time queries. That should be obvious, eh? Make a system that knows what data is worth storing.
• "What is happening in America is that television is transforming all serious public business into junk... Television disdains exposition, which is serious, sequential, rational, and complex. It offers instead a mode of discourse in which everything is accessible, simplistic, concrete, and above all, entertaining. As a result, America is the world\u2019s first culture in jeopardy of amusing itself to death."
• all - Note dictionary does not get cuckoos, should apply a stemmer in that case...
• Have all mail for setanta forwarded to the machine setanta is on?
• Log all my hours soon.
• By consolidating all information through setanta, we risk corrupting it if setanta has a problem. Ponder therefore how to prevent this.
• Have it generate long flags like ./unilang-command --upload-all-contents-of-wiki
• Write a program that goes through other program specifications and uses that the build an uber specification in order to run all things that are simple and don't depend on others.
• Possibly come up with object oriented library for processing all text. So you say $text->RecognizeEntities, etc.
• Hit great austerity in my van. Very simple vegetarian foods. That's all.
• Have a form that shows all the lately accomplished things.
• radar should log all queries.
• Use all to build a taxonomy from the text.
• Add a general program to do all tasks, so that if I am unsure how to do a task, I use that program, and it helps me to find the right functionality.
• Get all of this stuff working from the van.
• bard should do all the anagrams that make sense.
• Avoid postgres trap: in general, avoid all the traps... maintenance of the prototype code and support was taking up large amounts of time that should have been devoted to database research. In an effort to reduce this support burden, the project officially ended with Version 4.2.
• all the while being rooted in solid reality
• all my systems need to be redesigned to more intelligent.
• all should notice and report on things like "ac-knowledge" and "ac-quit", and report that knowledge as well. That way, it can successfully construct new words as needed.
• all programming interfaces should be formalized. There should be no room for interpretation. Should integrate with ITS.
• The infinite depths of haughtyness, cruelness and greediness of the world, as much as it sorrows you, rejoice in the knowledge that your true God, who defends each and every soul, is all the more so beautiful.
• For setanta, we need to sit down and identify all remote manipulation stuff
• SA can be used, with custom rulesets, to do our network severity testing, by adding rules that indicate greater importance based on certain tests. This can be used by our priority system. Therefore, a local version of SA should run to that effect, determining the importance of the various emails. It already integrates all the network tests, etc, that we need, and I can disconfigure any tests that are not necessary. This can give a preliminary report to the system as to why these mails are important, or indeed any mail. Knowing the importance can then assist us in other tasks, as we integrate more services. The flags can serve to guide the report system, which looks to isolate real problems and determine their response. This is what RT does presently.
• setanta should schedule network changes ahead of time, that way, before the actual change occurs, customers can be notified. Use GIPO to derive the planning domains. Set up proper time management to get all of this done.
• Rewrite perl programs, replacing all the facy perl stuff with the actual meaning behind the code...
• You really have to want it, above all other things, to treat everyone well.
• boss capabilities should utilize case if the word is a common word, such as all.
• all should use: Net::Dict
• It will record all work done on projects using ttyrec, bash history mechanism, etc.
• FRDCSA: It is our job to solve all the world's technical problems.
• Make packages for all of our useful systems.
• Setup a "fly.el" like mode for all that auto-highlights new words the user hasn't seen.
• The programming environment should have reinforcers to keep me working on good things. Such as photo's of all my friends looking on in expectation of good things.
• Replace boss::Config with AppConfig if appropriate. Generate refactorings for all projects. Upgrade them to the latest tech where possible!
• Adapt the all example to work with web page, where the definition is given on mouse over.
• Systematically study the properties of various systems, like logrotate -- all systems installed on this computer, and use them to maximimum advantage for these projects.
• Set up a central debian repository so that all anyone has to do is add that one sources.list entry
• Standardize all capitalization of terms across programs to avoid confusion.
• Create apartment finding software (helps do all the work)
• parse research papers to obtain all the different fields.
• Create a concept index for our website that contains links to all concepts, for instance Cyc, EBNF, etc.
• As part of code-monkey, write a script that lists all the significant functions in my systems and helps me to document them
• all should use Visual Interactive Syntax Learning
• A clever way to make my system smarter is by using manager::Dialog to record all decisions, per application, in a database.
• Process all cso items into long term searches.
• Find all linux people that you can that live near you. Do this by tracking all the users etc. This is not necessary, just find the next linux convention.
• Create a gnutella filter that gets rid of all that stupid sex stuff
• In building the classifier, we could replace the individual system names with thissystem, that way it wouldn't aid in selection at all
• How stupid is it that while I had all the students, I didn't bother to learn from them, only insult them.
• Implement search semantic dimension: i.e. searches a file for all related terms (for use in Emacs)
• Should update all my data sources.
• OpenCyc, (all-isa #$Poem-CW)
• OpenCyc, (all-isa $Poem-CW)
• OpenCyc, (all-term-assertions #$Poem-CW)
• OpenCyc, (all-term-assertions $Poem-CW)
• bard doesn't handle all morphology.
• My dream today. I dreamt that there were these guys and we all had motorcycles. There was a naval ship full of stolen people that turned up on US satellite imagery.
• packager ought to start recording to where it put things. Also, all of our systems should be obvious as to how to develop.
• Keep a spare all boxed up.,
• Gather together all rules about SVRE chair.
• I think probably best is just to get various technologies up and running, and integrated into our systems. That way, when we need the tech, we just look it up. Their capabilities should be searchable and possibly formalized. That way, all programming resorts to doing things with them.
• Derive all the correct legal principles for the operation of the commune. Do everything by the book and record this, in case of future legal attack against it.
• It would be great if someone could just pay me to hack on Open Source software all day.
• OpenCyc, (all-term-assertions #$InsultingSomeone)
• Find all the computer clubs, etc, in Naperville, a good place to start.
• Figure out some wa to use all the water in my jug.
• Make list of all things to do, etc.
• Don't just read the bible, read all the sacred texts.
• Make sure all of my tools are accessible and self documenting.
• Refactor all .emacs stuff.
• all code should reference appropriate documentation in digilib.
• Add a refactoring for converting all function arguments to hashes.
• Should create a dictionary object with common dictionary operations. In fact, in general, identify all things that would make objects and do so if this hasn't been done already.
• Develop technology trees, that represent not only all the relevant mathematical concepts in a given program, but also the significant implementational concepts.
• Hopefully all refactoring will be nearly automatic.
• Determine that all agents conform to certain specifications, and even develop new libraries to promote that stability.
• In the same way that we react to our environment, with all its information, we ought to also react to the information environment.
• Also look into refactoring all of the codebases.
• Could eventually do all speech through a speech recognition interface.
• Can feed learner::Method some SGML annotated text and expect it to learn the annotation scheme. It can do this by applying all the learners. It may wish to check with the author. That has to be determined before mission critical usage.
• Do entropic minimization of all the programs I have written to develop a shortcut language that implements them.
• I'm getting all the systems done but not necessarily as I would like.
• OpenCyc, (all-term-assertions #$Sound)
• Perhaps it should determine whether all packages have been uploaded. This seems more like predator. Since architect is more responsible for capabilities matching and so forth. Takes lists of capabilities and tries to match them.
• We are seeking for some kind of best fit from all possible subphrases to cycterms.
• OpenCyc, (all-term-assertions #$few)
• OpenCyc, (all-term-assertions #few)
• OpenCyc, (all-term-assertions #Collecting)
• Convert all of our systems.scripts into an object model?
• OpenCyc, (all-term-assertions #$Researcher)
• OpenCyc, (all-term-assertions #$Clover)
• OpenCyc, (all-term-assertions "Clover")
• If I have spent too much time on one project or task (as computed by some of the systems, initiate a change of task to prevent from wasting all day on a task)
• That way, you would never have to prepare your food, as it is all pre-prepared.
• It could all be built out of styrofoam.
• Before releasing akahige, get free exercise information for the personal stretch manager. all systems must be checked for information sources using license management system.
• Because when I program all day, I don't move around alot, my calorie intake should be lower. Need to know what it should be, and more over, for days where I am going to be moving around, need to increase my food intake maybe the day before.
• I kind of like all the emacs things, although, they are not as elegant as they could be. Their functions should form the basis for some future system.
• Delete all these silly things.
• I'm obviously not debugging perfectly. Nor typing perfectly for that matter. I'm generally not doing very well right now at all.
• Have a cross programming language method of date functions. In fact, to the maximum extent possible, all functions should be cross PL.
• I am not accurately recording all of my mistakes. When planning is further along, frequently schedule questions.
• Schedule all backups etc for when I am sleeping!
• Create an object oriented requirements system. For instance, we should be able to inspect all requirements that pertain to my chair, such as it having exercise equipment built in and be water/sweat repellant.
• One way to ensure accuracy of repotring ofor sinless is to have many minor sins, and to force the user to record all sins.
• all the initial bullshit for getting the stuff I needed has put me in contact with my family too much and broken the gem of isolation.
• OpenCyc, (all-term-assertions #$roommates)
• E.g. a system that does all of this already?
• Should breakdown all of our services into a selection process where you can select which features you want enabled.
• Think holistically of all data sources and how they affect security through the classification system.
• Here are some ideas. all we need now is a simplistic goal system, built from the ground up, _maybe_ with some basic common sense. On the other hand, then, we should get the event logging system working, and write helper functions, EventLog, etc, so that other systems can make use and analyze log data easier. We should generalize the functions found in sinless and manager that make use of the score event system, (moving that of course into the eventlog). problemspace should visualize the eventlog data, using nodebrain type filtering. That stuff has to work inferentially.
• Come up with important naming conventions and rename all functions to fit, have record of the transitions, so that people can view the code in old format versus new. You could edit in any function language you felt appropriate.
• Ensure that we look at all logs and files eventually. Model which files we have seen when! This ties in perfectly with this log system. That is what it is doing. So from that we may update timing information on all files. Maybe we do want to do an SQL db.
• all agents should use sinless!
• Need to consolitdate into a subsumption hieracrchy all the different search abilities. Actually, that would be a good way to utilize th algoriithms knowledge base.
• Obtain various types of prebuilt sentences classifiers and processors, and just see what all of them have to say and see if there isn't a way to learn. Could treat it as an information extraction problem.
• I've spent all my time today working on the time management system, when I could get it done instantly using something from the internet, but I need to finish the time management system before I regain internet access.
• Index frustrating searches. Store all previous searches in seeker.
• Telephone, if at all should be within hands reach. Everything should be.
• evangelist or hypermedia or whatever can control Emcas over UEA. Elements should be generalized into interfaces, to allow user input bcak from the different programs. Other programs can schedule elements. all interaction takes place as interactive movie. Can be used for collaborative/telepathic interface. Use unilang to distribute data over network. Add authentication to unilang over iSAKMP VPN.
• Come up with comparison matrices for all software.
• clear should compute an enormous meta-reading model consisting of all readable text on the drive.
• all should use malaga
• The planning system should actually send messages over unilang and all the programming be handled in Perl.
• sanctus should eliminate pornography, illegally obtained media, (should work with kbfs to tag all incoming data), etc.
• Is the final battle between good and evil where we simply all get along?
• In fact, all data must be cleared through the search system.
• all should have same functionality for human languages, to remember conventions.
• Maybe there is something at Fry's for my water. At any rate, we should make an all day event of going to Fry's soon.
• With a laptop, all public places become my home. Write the temporal planner, get the laptop, and you are good for development.
• I'd really like it if God had a backup of all the programs I've written for later use.
• For all programs, we can look at abstractions of their functionality, to compute a better way of writing the program in the first place. In other words, for every program P, there exists a system S which executes P in a more intelligent, versatile way. I know that isn't formal, but here is an example. The script that rates the apartments, well, hand writing that is silly because, what if you want to rate something else, you see. The notion of a system that helps you rate things is important. critic ideally subsumes that...
• Why do they get mad at us for being sexual when that's all the world shoves down our throats?
• Programming is kind of like cooking. all resources require that you really be interested in the thing.
• Create a clear.el function for reading all selected files in dired.
• Insert all sorts of hooks for manager/pse to know the current working context.
• Develop a methodology for teaching programmers about all these things. I guess that would come wrt their goals.
• I find that writing a first generation simplistic system gets the basic functionality in place without all the difficulties. It would then be fitting to do an entire rewrite. boss ought to keep track of that kind of information.
• Convert all programs over to proper, cross platform tempfile creation
• clear should consult all/Termios/picform/bard for understanding writings.
• Get a system together for storing addresses and stuff of all my friends.
• Pass arguments to all applications instructing them to announce their names when printing.
• Standardize save functions. In fact, standardize all functions. Use function names as well as string similarity over function definitions to get a ball park estimate of redundant functions.
• When one person sins we all sin.
• bard should be able to find all rhyme sets in some list of items, say internal codebases, or external codebases.
• Read more about how Emacs was developed and the theory. Read any and all theory CS books.
• You don't just know alot of math, you know all the math.
• Make it a top priority to get all of these items correctly classified!
• Delete all the incorrect classifications in the sql log when corpus classifier is working.
• Then we can have people see all the complex notes I take.
• I should read all the linux howtos now. Write something simple today, that makes sure clear is in basically constant utilization. This will of course include writing a compressor for voy files.
• Did we get anything working today at all? Not really!
• Integrate theorem proving with planner with knowledge base, all that's really needed. OpenCyc has to be involved, obviously. OpenCyc should handle terminology.
• Create a webpage about all my researcher friends.
• unilang agents should, defined through audience, have a nominal state that allows unilang while dynamically starting them upon messages received for them (so they don't all have to start at once), that indicates they are ready for processing.
• Now all we have to do is fix that data and worry about complexity/efficiency issues with corpus doing autoclassification. We also have to add more elegant classification than bayes, as well as talking amongst agents to support better categorization and command execution from our notes.
• We can have not only Bayesian classification for entries, but also apply all sorts of feature detectors, like (imperative statement), and subject matter, etc, to create a large list. Rule induction can then take place and the user edit the rules for still more control over the process.
• Not all agents should start at once, agents should only start when necessary or getting close to necessary.
• Maybe we can determine all instances of unilang debugging and not record those or something.
• Now all we have to do is have it give the results of the autoclassification after we enter it.
• What happens when unilang uses all the IDs.
• Some people might think it is excessive to record all the sins in detail, but it is of course necessary at this point to keep things on track.
• Roger, all clear, planetalk (for all).
• Pronunciation dictionaries for all foreign languagges.
• I just realized that all dictionaries express things in terms of others, but if you are lacking in even those you are in trouble. Most children have a basic vocabulary, which could be modelled and two products created - one a general dictionary at various age levels containing enough description to convey it to that age-level, and secondly a program which conveyed it to any.
• If necessary manually review all existing messages...
• For job-search calculate optimal reading/practice for all jobs together.
• all my other software is cool and all, but it is a lot of work.
• Generate critical path for next couple weeks, start planning out all things like that.
• Should probably make an effort to determine all files that are modified by us, and what they are and represent (i.e. kbfs)
• boss should keep track of all renamings of projects over time, so for instance, since today we merged Sorcerer into cso, should record that and add it to a log of operations on systems.
• (all other systems, like pse, then reference the SQL table via primary key)
• Find out how to have Docbook generate only 1 page instead of all those pages.
• List all items that people would pay money for that I can solve.
• Windows is the most widely used operating system and all throughout my work history I have used it.
• I am interested in learning more about all the latest trends with Windows development.
• Be sure to find all instances of pse.log
• all goals should require a parent.
• Using the log files which show all the items I've viewed using Sorcerer, we can easily feed this into the system that determines what I have already seen.
• My idea was this: for the movie, use all the different software like that movie data for infovis-nlp or whatever, from IMDB, to create a recommender system etc for movies for our perusal - then of course the movie systems are used for
• Should have a status viewer that displays progress for all our systems.
• The emacs logs I have are good because they actually show me building the packages. And all the actions, too bad the actual key sequences are not being recorded.
• I suppose for debugging purposes we should have full text indexes of all of our systems.
• Code monkey ought to have a corpus of examples for learning of error messages, etc, all marked by their full environmental context.
• I also dreamt about two warlords in Scotland. They were all decked out, but the one yelled to the other. Let's have piece. The other said I want to, but I know your human, and so I'm afraid, but that's also why I'll give it a shot.
• Use the ICalendar specification for all time tracking. http://www.faqs.org/rfcs/rfc2445.html
• I would like to replace all the bad notions from my systems. Like predator, should be called something better.
• Note, when I ate two things of Wendy's last night, and nothing for all morning, I have a painful stomach like when I went on trips.
• Should all web traffic flow through TOR
• Convert existing pgourmet application all into SQL backend.
• Need a comprehensive inventory of all good system capabilities.
• Need to set up regression tests for all systems.
• Write general purpose FRDCSA project scheduler, to schedule and coordinate the actions of all our various spiders.
• Eventually all these specific programs can be destroyed in favor of more general ones.
• Create software to index all pictures of people we know in Mach
• With all my systems, need to rewrite descriptions to be more "symbiotic"
• Tell the truth all the time.
• Attention all long-term thinkers, caring indviduals, etc...
• all I really need to do is stock up the truck and drive out west!
• Dad is here all the time.
• Make static compilations of all software as well as packages.
• WRT packaging software: "Users can't, and can't be expected to, sort this all out."
• OpenCyc, (all-term-assertions #$toThwartInEvent-SitType)
• OpenCyc, (all-instances #$NorthernIrishPerson)
• Of course, the key to getting all the women is to meet the aliens, charter a UFO, and abduct them.
• all you have to do is scrape out the members of certain interests or whatever, like "cslounge"
• This is a fucking joke. Live journal has all the social network information we need on the CMU students.
• all inventory should be stored in a normal form, a symmetric, balanced, designed form.
• Write a script to fetch images of people for us automatically, by spidering for their name on google and spidering a depth of one, say, and extracting all images.
• One thing we can do is have all posithons compete for some task. For instance, information extraction competition.
• Posithons should have a theme, for instance, "Document all code!"
• Write CMU and mention to them that I would like to keep the account for the full 6 months because I've been doing all correspondence for my job search with it, and I most likely will be working at CMU still.
• In all this time this morning I have succeeded in getting job-search to scrape some jobs and almost got it processing these, if we get the resume and cover letter generation functionality working today I would be happy.
• Once installed RSR, can prevent its removal by monitoring all commands.
• all movements must be done using "backroutes", these must be known beforehand.
• If you are going to nitpick at my code, I ask that you nitpick at all of it.
• LPG requires that you have object instances of all types I believe.
• Should put in some kind of type checker to ensure that things will work. Record all oddities about lpg.
• Object is to integrate all the various domains, using a context, and generate a plan. Simple.
• I know I'm the joke, but I swear, it's as if all of you people were a joke. Look at you!
• We can have agents print things like <audience: > using a library that we replace all print statements with, maybe even redefining print to make it easier.
• Interface this with the inventory management to find where all items are. Have it ensure all items are put back properly - lose points if someone else reports that you didn't - and when it's your turn - there's no escaping it.
• Lastly, you should have a basic model of how long you are good for at all times.
• Good practice is to eat all of the contents of your food tray - that way, you don't have to clean it out and you minimize shelter waste.
• I hope it doesn't route this message to him automaticlaly - part of the reason all messages should be apporved. In fact, this problem can be lessoned by attempted to determine whether the communications are problematic.
• Could build it in the basement, if all else fails.
• I cannot work with family because no matter what - despite all my good will - they are intent to see my work suffer.
• I am convinced now after all the progress I have made this month that I should definitely get in the shelter ASAP.
• (should be able to search systems by: all-open source-installed-packaged-available)
• And then instructs the robots (people), to load CDs into its tray, so that it can burn CDs to give to other people. We should have it detect their IM logs and deduce who their friends are, check this against a central database, and have them burn CDs and give it to all their friends who aren't using it.
• Can automatically compute code relevance by judging, using page rank algorithm, how much it is used, also using statistics on invocations. Therefore, need to have invocation statitics module written, that records in a log file all invocations of programs.
• I can replace all instances of Jason Sayne in my system with my name if need be.
• Would be nice when all this gets done right things. Getting towards that point, aren't we.
• Add copyright notices to all files
• Make this from the radar or predator script get dependencies run on all the boss codebases.
• One refactoring should be to replace all \((shift)+,\@_\) with \@_
• A funny joke would be to have microsoft's paper clip get all mangled.
• all this stuff is rather CPU intensive, but what the hey.
• Seems to me that it would not be that hard to adapt the class scheduling system to handle all events.
• I could live them all set, so that, in case of an emergency, no problem.
• Print out a giant diagram that illustrates all the relationships in the correct notations between all the systems.
• Replace all (shift,shift,...,shift) with @_;
• Here is all the code I've written in the past 6 months. It's a shame you can't understand a single line of it.
• When this is all done, I'd like to watch a replay.
• Tell him roughly what got done - that I stripped all timewasting programs and file dependency against them all, installed critical system.
• Of course, should have a backdoor to allow us to make it look like the computer is doing all the thinking. In otherwords, the connections between real and false/ computer and human IDs are just as ambiguous as in the rest of FAST.
• Write a little intro about all the features - we can have documentation that covers the code and keeps track of all aspects of the code, what it does and so forth - to make sure that all the code is accounted for in documentation, and even, based on usage trends, consider its importance.
• You can have a larger context as input to all learning files.
• You could use the CMU pronunciation dictionary to calculate all kinds of rhymes (stress, deibide, etc).
• all you can do is to attack me because you can't understand it! What a waste!
• new functionality s.t. all API are indexed, i.e. in architect
• Our basic model is that I control the development of the project, but that other people who have interest in doing things do various large tasks for the project, get all the credit, etc.
• Instead of typnign all the student reports up at once, do a couple at a time.
• Look at all my extra hard drives and try to remap them and copy things over so as to free up a few of them if possible. I don't think that anywhere is there any installations that are important, with the expection of maybe a mysql db.
• Have a word play system, one that knows all the rules for word play.
• Come up with lists of all the major problems to be solved for this POSITHON.
• Remove all porn files from computer.
• We also need a system that contacts all the programmers to obtain their votes.
• Some thoughts on how to run the shelter. Get a bicycle, several spare tires, to run groceries from time to time. Bury all money in rocks or the like, littered in special, out of the way locations. Keep a small system on me to maintain a plan when moving about. Have the bike hidden some distance from the shelter. Have the shelter near a trail for this reason.
• Write down existing conventions, so that people can be taught all of them.
• OpenCyc, (all-instances #$Predicate)
• Of course the property that all good lies are they are mathematically indistinguishable from the truth.
• In general I just realized that we can perlify all of our software, just like we did with ORA. We could do this for MinorThird, etc.
• Must make sure that I do not get lazy with reading. all skills - typing listening and reading should be enhanced.
• all my Perl code should be beautified before releasing.
• audience should simply summarize the incoming communications, for instance, 15 mail messages, 10 action items, 5 bugs reports, all resolved, etc.
• Ergonomics is knowledge intesive, for instance if we designed a helmet for me, taht incorporated hearing protection, well, the way the helmet lies against things, and what range of movement, and whetehr there are blood vessels, all factors in.
• Talked way too much to staff memebers. Need to be quiet, maybe create incident to be quiet, I don't know. Too tired to fucking type. Really strange, from the heart. Probably cause no food all day. Itchy all over the nexck. Must get selson blue.
• I suppose it will take time, yet see, how after all this time, things have only gotten worse.
• I should really finish that meal planner, of all things.
• all the discipline I create will be magnified 10000000 times by my software If I am to get a new job, RSR MUST be functioning.
• "As you grow older, Mom, I think of all the gifts you've given me. Like the
• all those techniques from the knuth should be used.
• Add are you awake feature to clear, every now and then it asks you, are you awake? You just have to hit enter or something. If it times out after asking a few times, it pauses until c is pressed after all, if a any key is hit it restarts the are you awake question, or Are you paying attention?
• Will be nice to have a system that does all of this data mining of event data.
• This water quality was really bad, we need to get a water filter or something. Also need to calculate the number of water filters I need to last a given time, etc. Figure out all basic needs and plan for 500 years or something.
• I shouldn't remove Mozilla or firefox, since I may need them, but I should be disciplined enough to use Emacs all the time.
• Hard to find connections, like the emacs 'pp pretty-printer should be all made explicit, in the cso
• Emacs ought to support code beautification/pretty-printing/reformatting for almost all languages.
• Found a bug with busroute, it is very slow when searching in the morning since it processing all departing routes after a given time
• We need a planning library - actions specifically with all the preconditions, etc.
• You don't have to worry about all the different reactions, abilities and understanding of everyone, so long as you ensure that they are all bigoted.
• all worship of movies such as the matrix must be abandoned - unless they are being talked about for valuable applications such as the 3d inventory browser.
• Here is the first useful observation. all these different areas are somewhat like locations. And there is a route, you have to have the resources to traverse it.
• I noticed that I can't get real work done inmy room because all I really need to do is sit down and flesh out these resumes and in so many days I was unable tol
• I want to make a giant list of all the actual committments for cooperation I've gotten.
• I did admit culpability, but instead of doing the same you guys just ganged up on me. Now, since I ran away, and since I have been gone so long, you can blame me all you want. Keep blaming me.
• OpenCyc, (all-genls #$Person)
• Broad list of contacts - don't keep in constant active communication with all of them you stay upsdated, what your doing what they're doing, sync iwith them, if any ututal projects. It's good to have this sort of contact.
• If I do get a nice paycheck from a grant, be sure to purchase necessities first, if at all. The money should be stored, as much as possible. College loans complicate this process.
• A great many ideas come to mind as I get back into, of all things, job-search.
• Rewrite fweb using proper URL objects, so that all the conversions becomes easier.
• If I got married, had a wife, and then had quintuplets, Dad would say that's impossible and kill them all.
• boss can use the perl source to determine whether all CLI options are covered in the manual.
• Before users use a system, they should probably read through the justifications of all things.
• kbfs should track what important project information is where. For instance, if we were to move all packages to the projectbox server, and delete them to free space, kbfs should know that
• It should be appropriate to compile a case of all the crimes I have inadvertantly committed - as well as those which were committed against me - and record this in a "legal-assistance" system. The system has two purpose - to evaluate actions with respect to legality, and to maintain records of illegal activities committed by or against us, both of these pursuant to ensure legitimate operation.
• clear needs to record all voys centrally and compressed
• Note that with the dependency information for educational materials all in order - we could begin classifying the knowledge axiomatically for two purposes - first, so that we can program systems that reference and make use of this information, and secondly, so that we can use this for clear. We can reference works by ISDN, etc, and use that among other things to begin indexing books. That way - we have an unambiguous identifier.
• Package clear by the end of the week - and get all of its dependencies in Pbuilder.
• I can do all the stuff for the gnu on their servers.
• Say things like not all the descriptions have been parsed (for ecodebases
• If I ever need to - here is a great survival plan. RSR, verber, audience, etc must be functioning. Bury all my important belongings except for necessities - as planned by verber. Then, having maybe one system hopefully a laptop, leave town with enough money and possibly a bike, and move to an area where there should be lots of low paying jobs (walmart, etc.)
• Should probably have all licenses manually verified - with information helpfully provided by radar/predator.
• With all the sleep I got just now and the nice cold room I had lots of dreams. One of which there was some kind of video game that I was playing but it was complex. When I really awoke, this got me thinking about ludology and game properties. As it was kind of a pursuit and evasion game, I thought about theoretical results and realized that that would be important information. Also we could teach about ludology in the Summer program.
• At all times the entire conformant plan should exist.
• Notice that we all suffer by bad persuasion tactics.
Why have this life when you can have a better one? Ancient scam, with no end of suckers.
• Areas for improvement with corpus. It's quite clear. The procedure I came up with isn't efficient but it is easily adaptable to an efficient procedure. Two things - don't do n^2, rather only look at reasonably related documents - this will cut down dramatically on run time. Second, make more efficient the sharedterm code, and lastly profile to see where spending all time.
• OpenCyc, (all-instances #$JewishPerson)
• One thing we could consider is simply to identify all the things we don't know how to do.
• What pisses me off is that here you have all the people playing games, and with just a little work the games would be actual reality, and they would be accomplishing good instead of wasting time.
• That's really what all these RDF tools do, etc.
• Need to create a backup pretty soon. Need to check out all of our current backups. Need to create secure system division. Have much work to do.
• Find all the open source groups you can and work with them - for instance openAI.
• Is sourceforge all we need? Or do we need more?
• Another idea is that verber::manager should take care to know all the different types of interfaces that the user may be interacting with it, and scale down to these. For instance, there is full computer, bidirection speech, TTS and keybrd entry, yes/no, all the way to none - just memory - etc,etc. verber should have special planning domains for which devices will be used at what times and how the plan data will be transferred.
• Another is more important - has to do with students and teaching - I could probably show them all of these systems. I think it was something about the kind of power they could get using this software.
• all the information in these projects is very valuable.
• Also get gourmet item scaled down and do resume. all this should be done first thing in the morning - it will be like a race.
• all I need is isolation to begin working in earnest.
• OpenCyc, (all-specs #$Event)
• I just realized that all of my work probably looks like cunning little treachery to my family.
• all in all pretty exciting stuff.
• OpenCyc, (all-specs #$Person)
• OpenCyc, (all-instances #$Person)
• Do not use hotmail or any other service that shows you pretty women on the side. all mail should be done with fetchmail and a text reader.
• I need to relax, that's all.
• I bet we could store all personal data on an encrypted loopback file system, which would be part of say, kbfs.
• RSR should determine the names of all people I talked to in a day, and have me record memcons.
• There is a chance that all the road navigation data comes from road segment image analysis
• I was living in my car, and I tried to get rid of it. I moved all my valyables into a large raft like bag, but somehow now the car, which was disabled, had moved close to the intersection and was interfering with traffic, so I went to move it and my bag was stolen.
• OpenCyc, (all-term-assertions #$CheeseFondue)
• OpenCyc, (all-term-asssertions #$CheeseFondue)
• OpenCyc, (all-specs #$Food #$UniversalVocabularyMt)
• OpenCyc, (all-specs #$Beef #$UniversalVocabularyMt)
• OpenCyc, (all-instances #$Beef #$UniversalVocabularyMt)
• OpenCyc, (all-term-assertions #$RoastBeef)
• OpenCyc, (all-genls #$RoastBeef)
• Should document all of my systems as soon as I can. For instance - acronym should be documented.
• It is notable that my knowledge seems to be weakening in the sense that I am forgetting a small layer on top of all of it which means that it doesn't fill its old shoes.
• Record all distractions.
• Need to refute all bullshit thrown at us, politcally.
• Don't talk to coworkers, at all, about anythuing of importance.
• I need to come up with descriptions, license information, and source locations for all my software.
• OpenCyc, (all-specs #$KosherFood)
• OpenCyc (all-specs #$KosherFood)
• OpenCyc, (all-genls #$Bean-Foodstuff)
• Remove all email from CMU account.
• OpenCyc, (all-term-assertions #$Food)
• OpenCyc, (all-instances #$Food)
• OpenCyc, (all-genls #$SpaghettiNoodle)
• For adopting new users to our system, we ought to first get them using RSR so that they develop good OPSEC, and then start involving them in more and more major planning steps, all the while verifying their reliability.
• Must collect all related terminology to people's notion of perfection and beauty and acquire it here.
• The beautify of our design, and the manner in which all processes of life are brought into harmony, should impress anyone.
• Trash, food prep, etc, should all be at hand.
• busroute's system should use the following algorithm - take a time window, and show all routes in that by starting at the beginning time, finding the next route, then setting the time to be 1 minute after that and repeating, until no solutions are found
• all work and no play makes Jack rich as fuck.
• Alter fortune to not read stupid quotes like "all work and no play make jack a dull boy"
• Write a system to categorize and index other people's actual code. Maybe there are other ways of determining preconditions - the way all this stuff will improve is if we have people mkaing packages and applying them.
• Had dream that I was walking with three Asian guys along to the river, and that they were asking how to get somewhere. I was aware that recently someone they knew had died. I pointed to them that the place was off in the distance, and they said, You don't get it we're not going there. Then they tackled me into the river and drowned me. Had I thought quicker, I would have maybe feigned convulsions, but saved energy to twist out once and for all, like that snake.
• OpenCyc, (all-instances #$Event)
• This tool will implement all of these facets of Requirements. Additionally, it will:
• I was thinking maybe mstevens would be interested in a deal where we all sit down, one day out of each week, and simply finish a system. For instance, we could sit down and finish shops.
• Business in order to make lots of money, there are two kinds of products, one r the other. One is that everyone will buy, no competition for all products. Second is you need veeryone needs, second veryfew people need, but those people can pay tons of money for it. Programmer productivity software, you could sell it for $2000, sell 100 licenses. That's set for life. If you can make something, you are set for life.
• Print up all direct route reports and keep them on my person.
• From the time I lay down with the keyboard until I fall asleep, all the logs I keep should be reread to me , or at least summarized, the next day.
• We should have it so we have to review and classify all thoughts at the end of the day.
• OpenCyc, (all-term-assertions #$CityOfChicagoIL)
• OpenCyc, (all-term-assertions #$UniversityOfChicago)
• I can have radar and predator record everytime they make a package so we can even calibrate on how all events affect one another.
• OpenCyc, (all-genls #$RichardNixon #$UniversalVocabularyMt)
• OpenCyc, (all-term-assertions #$RichardNixon)
• OpenCyc, (all-instances #$UnitedStatesPresident #$UniversalVocabularyMt)
• OpenCyc, (all-instances #$UnitedStatesPresident #$PeopleDataMt)
• OpenCyc, (all-instances #$UnitedStatesPresident #$PeopleDataMt>)
• OpenCyc, (all-instances #$UnitedStatesPresident #$UniversalVocabularyMt>)
• OpenCyc, (all-instances #$UnitedStatesPresident #$FamousHuman)
• OpenCyc, (all-instances #$UnitedStatesPresident #$BaseKB)
• OpenCyc, (all-term-assertions #$UnitedStatesPresident)
• OpenCyc, (all-instances #$UnitedStatesPresident)
• OpenCyc, (all-instances #$UnitedStatesPresident #$UnitedStatesSocialLifeMt)
• OpenCyc, (all-term-assertions #$GeorgeWBush)
• OpenCyc, (all-instances #$GeorgeWBush)
• OpenCyc, (all-instances #$USNationalSecurityAdvisor #$UnitedStatesSocialLifeMt)
• OpenCyc, (all-term-assertions #$USNationalSecurityAdvisor)
• OpenCyc, (all-instances #$USNationalSecurityAdvisor #$UniversalVocabularyMt)
• (all-instances #$USNationalSecurityAdvisor #$UniversalVocabularyMt>)
• OpenCyc, (all-instances #$USNationalSecurityAdvisor #$PeopleDataMt)
• OpenCyc, (all-term-assertions #$HenryKissinger)
• OpenCyc, (all-instances #$FamousHuman #$PeopleDataMt)
• opencyc, (all-instances #$FamousHuman #$PeopleDataMt)
• I can tie RSR in by running it at the end of a particular event. I.e. did you finish all your food? Well, why not, etc...
• Moreover you should be sure to finish all meals.
• Also, you should eat to have very little food remaining in your stock, meaning, that you should eat all of the cans, so entropy doesn't collect.
• They spend all their time coming up with these.
• The important thing is knowing the truth. Do not believe in all the constructs of the movies - power is beyond the jedi, etc, etc.
• I like the use of needs to drive the system development, as when I forced myself to generate a plan to eat before I ate. It was ironic and indicative that at that time I was too tired and thus didn't eat at all.
• We need to explicitly code the system that mstevens mentioned about involving people in only a small part of your operation. all of this stuff has to be done as programming operations.
• point out all the logical fallacies in the movie I just saw, if need be.
• perhaps I could write a system that analyzed my log files for instances of ideas that I'm not supposed to write about. This would be an effective way ! Yes! To curb this. all I need to is write it and add it to unilang.
• So that is all she wrote. At the end of the day I have to reassess the moment, and analyze this. I need to incorporate this into a system.
• The list of bad things is, in this order: socializing, watching movies, wacking off, being affected by advertisements from media webpages, sugar drink, working too much, not spending enough time per day working on my project, leaving my area, movements, purchasing items. Now all I need to do is find adequate punishments. This might be physical pain, such as leaving those nipple things on for a certain length of time. That should certainly qualify. Also, not using the computer for an hour, but this might be bad. They have to be followed. I can't think of any that are good enough right now, but they will come. Exercise would be a good one. 50 pushups, etc.
• Remember, that what I am doing is to get rid of all these problems, and it does work.
• The latest star wars movie hits pretty close to home. Many parallels with my life. It should of course be dismissed as meaningless propaganda, and furthermore, as not an example of sound reasoning but as an example of a story which has all the elements.
• That way, we can determine what people will want to do, and get that working. We need a basic system for ensuring this happens. Basically, our goaling system must be done first. Then, we need to ask other people. Then we need to identify mutual goals, and tasks that need doing. In other words, I should simply provide people with the information they need to do certain things. But if I don't provide it correctly, they may not wish to do it at all.
• Also, we need to separate the scope of the project. We need to keep accurate goal representations of people. This means, simply, listening to their goals and asserting them. It is not really all that complex!
• I think, minimally speaking, all movements must be planned, etc.
• Try to restrict (and enlarge) my scripts to all the functions that are found in CPAN files, and then, at that, only the good ones.
• Need to back my stuff up onto DVD. Nothing fancy, just clear out some of the directories. Build index of all DVDs.
• Forget it, maybe or not, all we need to do is write software, the rest will come.
• For every person or group we meet, we must do plan recognition. The problem is getting all this software together is tough. So maybe we should concentrate on finding a few high profile people.
• Need to convert all my documentation for perl modules to POD, and also, maybe make this conversion part of code-monkey
• Some thinking on verber, should have planning cycles, in which it plans out the acquisition of all necessary steps of life, and inducts so as to provide adequate time planning in the future. I.e., moves like an ant.
• Is there any better way to get nutrition information than to simply photograph all the food labels in stores?
• Organize a meeting for all people who feel like they are working very hard behind the scenes trying to support free software but that there software is either not being completed and hence not being used, or that for some reason or another they have not been able to get in contact with the community.
• Perhaps purchase an REM monitor device, and use it to wake me after a dream so I can record all my dreams.
• The basic goal of all of this is to get time. On the other hand, just easier would be to take a new job in a different city.
• I haven't felt very good all day. I need to get back to doing some programming. And developing that system that reminds me when to do things.
• Let's make a website, like "freeintelligence.org" or something, that get's very popular, and serves many CIA manuals and the like, all that we can collect, and in it, implore people to contact us to work with us...
• Note that simply checking all files to see which are contentually identical is patently wrong, as, for instance, the GPL will be the same in many extracted systems.
• We view solving problems as a battle, and we use all military concepts in support of solving problems. figured this out using fm 3-90
• In order to get clear working, I'm going to have to do certain things like ensure it has all of its run time dependencies and I'm not interested in that.
• One could take the idea of the Asperger to the extreme - that he knows all this stuff and no one will listen to him. That you could have a retarded person - who understand EVERYTHING.
• We can integrate learning into all the manager::Dialog components, by adding additional information to the arguments, and logging the results :)
• A system should be implemented to record all my voices.
• More and more I am realizing that all of these needs actually require a smaller, more limited set of tools. I.e., Java, haha.
• Add a step to Predator to have it load the debian control file for a system before asking "Have you made all your edits?: "
• Ask existing leaders of the free software movement the hard questions. What are we going to do about Palladium. What are we going to do, etc. about all these other things.
• WRite a system for posting all events that other people can get email reminders, and can email it events for other people's perusal.
• If all the seas were ink, if all the swamps were producing pens, if the whole expanse of the horizon were parchment, and all the men were scribes, the axioms of the FRDCSA could not be written in full.
• Right now document modelling is done very little at all. There is a lot of guess work about what your audience knows.
• I defined CKC stands for Common Knowledge Collaborators - these are people who reason that they must collaborate maximally in terms of collaboration, and in terms of finding all other collaborators.
• Note that Marwan said that when he graduates in 5 years we should start a start up and implement all the features here.
• They're all so smart that I mistakenly expected them to be more mature - yet I'm not a particularly mature person myself.
• technique for copying key - press key profile into left middle finger pad - careful to capture all features, and oriented so that you can later draw it with your right hand while looking at it.
• Dear all, the FRDCSA project is suffering from a general lack of interest. Therefore, I am interested in obtaining quotes from people about the project that I can use to illustrate to others what other people think about the project. I would like to use these quotes on all project public relations materials. If you want to be anonymous, just write so. Thanks!
• Set up a system to handle all the predictors we set up. A seer. What do you call that? Someone that can foresee events.
• The sparrow swooped up and the sparrow swooped down, the sparrow swooped left and he then flew all around, the sparrow swooped right through the air he sailed,
• The sparrow swooped up and the sparrow swooped down, the sparrow swooped left and he then flew all around, the sparrow swooped up through the air he sailed, all a big effort to cover his little tail.
• If my recommender system works as well on recipes as it does on pornography I think we're all in for a treat.
• Record the dream I had last night. There was a bunch of funny stuff. Ironically, as predicted, my dreams were complex. It was funny because the family was all gathered around in Mom and Dad's bedroom, and we were discussing things, when at long last after discussion I noticed a note which said that Dad had died.
• You know, I'd almost believe all this bullshit people were saying, just if there was a free meal planner and something equivalent to radar/predator
• For now, I should implement something that actually works so I can get in this habit. It will be necessary as this will prevent me from making certain mistakes. The probability of seeing a given person in a given location should eventually actually be calculated. all can take place through the speech interface.
• The neat thing, though, is that with these systems in place, it will be all the easier to interact and configure the real systems.
• In this way, way point routes can be had. I wish we had a waypoint DB of CMU's campus. I suppose that would not be too hard to generate. It would be nice to have connectivity information gleaned in this way. The most important point of all of this is prevent me from making the mistake of say going to the undergraduate lounge. Permission for any movement is to be had. Also, permission for any social interaction is to be had. Machiavelli, I suppose, must ultimately represent this list, not audience. Agentifying everything has the negative affect of forcing a certain design philosophy on all software, and a bad one at that since unilang is so primitive conceptually.
• Use Cyc, eventually logicmoo to model world state. Make sure that we have to ask manager "permission" to do everything, and also all requests. manager, I am hungry. This initiates manager to plan for the world state. This calls the Cyc agent for world state, which it sends to manager, who then sends the modified domain file to the verber agent, which then generates the plan, which is then returned to the manager agent.
• Since pse doesn't have goals added all that much, calling save after every goal is probably a good idea.
• For all agents. I.e., unilang::agent::agent should parse that automatically.
• OpenCyc, (all-term-assertions #$IrishEnglishMt)
• OpenCyc, (all-instances Microtheory)
• OpenCyc, (all-instance Microtheory)
• OpenCyc, (all-instances #$Mammal)
• OpenCyc, (all-instances #$Microtheory)
• Need to come up with a set of sentences which we might ask people to determine their interest level. This is a pretty useful idea actually, have audience administer adaptive quizzes to people since my conversations are not all that deep.
• Ensure that from now on, the sources of all images that we gather will be cited
• And I even have a backup of all vitals.
• Should configure this machine to have a webcam to detect motion at all times.
• Need to fix radar Perl method to make packages according to the correct name, and also to parse names correctly in all instances.
• (have NL question answering over all software features as well as for the inferencing KB)
• (I was just thinking about putting up a blog - but no one would have the time to read it or search through it. Then I realized, what is needed is a dialog interface that could discuss with the user to find out what would interest them. Then - the following idea is immediate: Users could have agents which automatically found out what the user finds interesting through dialogs, and these agents could thus interact with all other agents! So you would get instant relaying of what people found interesting/useful.)
• (I just wanted to apologize to everyone for all the inadvertant slights that I have given them over the years. As someone with Asperger's syndrome, being so much more awesomely intelligent than your peers is very difficult when you can't even tell what their feeble minds are thinking! I hope you did not take offense to any of my miscalculations as it is indeed very difficult to anticipate the whims of sheer irrationality! (In fact irrationality has cardinality Aleph_1, where as rationality only Aleph_0))
• (all of the sleep-learning stuff belongs with manager)
• Here are some of the things we need to do next: fix the way pse craps out all the time, get Clairvoyance working and with some basic document management systems, including for instance authorized reports to ensure back to me that various people are learning various things (based on testing), find some way to get those recipes normalized, get shops up and running and taking inventory of everything I have, add this information to verber, get MDR (minimum detection route) planning operational, get new tagsets for AWB/Predator working, fix problem with script determining perl dependencies, make packages of my systems and upload, fix mini-dinstall problem, write tutorial on agentification, agentify or otherwise get command line bugzilla working, fix up manager with sleep learning capabilities, create a sample course for clairvoyance, and run backup. You're such a lazy guy, you know that?