.
FRDCSA | internal codebases | ALL
Homepage

[Project image]
ALL

Architecture Diagram: GIF

Jump to: Project Description | Parent 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. 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.

In order to facilitate language learning we have several features. The first is our system models the various languages that we are to learn. It knows our vocabulary and is able to see patterns in the languages and teach us through analogical reasoning and custom Mnemonics. For each language a grammar is used, as well as for spoken languages a pronunciation system (TTS). The user is taught the basic 1400 or so words in each important language and continually refreshed upon them, and advanced vocabulary is developed wherever possible. They are incorporated in communication with the user to preserve use. Ancient and modern texts in the appropriate language are often read by clear to the user. Interesting artifacts in each language are documented and exposed (e.g. in Sanskrit there are poems that read forward as well as backwards, in Chinese there is a poem composed entirely of "Shi", etc.)

Spoken models are contrasted with the TTS and corrective feedback is given. By knowing what the user knows about the language, custom dictionary entries are generated based on the vocabulary the user already possesses. Furthermore, their language acquisition helps us to formalize the semantics of all the different languages. A model of common myths for each language is created to help expedite learning for large groups.

Incorporate Justin's writing on this topic when we have internet access. One subsystem of all is Termios which is the terminology management server. It is responsible for knowing all the word definitions. Naturally it makes use of many data sources: WordNet, OpenCyc, Sensus, EuroWordNet, OMCSNet, dictd, etc., as well as many programs: verber, Peterson's WSD, FLogic, Gate. The basic goal is to provide some level of meaning for as much terminology as possible, as well as construct thematic mappings.

Capabilities

  • our system should pass all downloaded and visited webpages, probably using a squid proxy, through an analysis system. It can check for things like repo links, formalize the text knowledge using workhorse, etc. etc.
  • Make kmax-search-buffers not return all buffers in event of no matches.
  • Figure out all the pdfs that belong to a given project, and make a list.
  • Gather all pddl, ppddl, rddl, etc files into an archive, and use that to extract formalizations we can use in our systems
  • all packages should have tests that can run after installation, in a standard location, to ensure that the system is working.
  • Create a function for text search of all of our pdf documents and such.
  • Fix where if you say to "Have you made all your edits?: n" it does: "lintian -vi /var/lib/myfrdcsa/sandbox/alpprolog-20160401/alpprolog_20160401-1_amd64.changes: C-c C-c"
  • Come up with a function that tells us all bills that are coming due, and plans to send them well in advance, knows the latest date it can send them (for instance through the mail or electronically), knows the earliest, etc, has useful knowledge regarding all aspects. Create inventory management of our goods, look into the KnowRob system for examples.
  • Ensure that assertions are properly displayed and pretty printed when exporting from cmh-act-on-referent-and-push-onto-ring using all-term-assertions as the function.
  • Have a function for grepping through all of freekbs2.
  • Fix FCMS so it doesn't register a boatload of new agents all the time.
  • Write a unified API for tasks that spans all the different methods of representing them.
  • Add localization to the free-life-planner system. it's more than just translations for all the names, as there will be cultural differences.
  • Create a keybinding for audience that jumps to a paper, which is globally bound so we can start cycling through. Or maybe make it load a list of all papers.
  • See about writing a prolog module that can just consult files like this. Instead of wasting all this time reloading into KBS2
  • Just thought of a system. Knowing all the different things that we use, we can surjectively search the cso for everything that has to do with important topics. For instance, we could search elpa and melpa for Prolog, etc. And make a ranking over all packages.
  • Find out how to get all answers back from Emacs.
  • Write a function to search all to.do files.
  • Index all software in our archive for all terminology and links that may lead to related systems.
  • Index opensim4opencog for all terminology that may lead to related systems.
  • Having all these first-order formula for FLUX means ILP could be very handy here for learning preconditions, domain constraints, etc. Such as Aleph which Doug has integrated.
  • move that function that lists all the spse2 domains out so that we can use it with spse2 -l
  • Come up with contingency plans for a certain number of things being misplaced at all times.
  • Write a function which lists all buffers that have audio turned on in erc.
  • Get IAEC VM set up, control IAEC from within Emacs, have it have the ability to open files of interest and annotate them. Kind of like do::ListProcessor4, only all from within Emacs. Allow the user to control it as well. Monitor the state of Emacs, as input to the planning process.
  • The planning system might be able to plan the movement of an item, when we find it in a different place, so that all preconditions and effects are observed. It should for sure plan any movement we make.
  • Fix this question mark based error: request: (cyclify "\'The recent vulnerabilities "StageFright" and "One Class to Rule them all" affect hundreds of millions of Android systems, and are just the latest entries in a long series of incidents that show the magnitude of the problem.\'")'
  • Implement something to automatically generate backups and diffs of all of our repositories for kbfs.
  • Go through all of our do-todo mode entries and automatically recognize questions.
  • Fix System::KNext to auto compress all it's output files.
  • do a study of all the files which are not showing up in 'boss updatedb', i.e. things like frdcsa/emacs/ and maybe things like cyc-mode/hybrid/..
  • Update freekbs2 to have a partial or total order over all the assertions, for use with Prolog and Cyc and other order based logical languages.
  • Write tool to review all domains to see if they are indeed SPSE2 domains or not, and if they are, add a tag that SPSE2 will assert into all new domains that they are indeed and SPSE2 domain.
  • Make IAEC fluent with all data representations.
  • Google images doesn't balance the different meanings of terms out very well. For instance, I searched for RPG for "Role-Playing Game" and all I got was a bunch of rocket propelled grenade pictures.
  • Model all the typical arguments about voting, and determine the political game, if any, and advice given to promote different agendas.
  • Maybe use stet with all the formalforum/reasonbase/Eolas stuff.
  • Get proper error handling with System::KNext, also get it to handle all those errors CLISP was spitting out.
  • Enter all of Michael Iltis' documents and software into the kbfs system, and begin annotating it using NLU and such, in order to derive our representation and also to have the information required. Write a document mentioning all the different layers. Fix the NLU code to work with kbfs. etc.
  • Have clear store all instances of documents that it cannot parse for analysis.
  • clear should use kbfs to represent the state of a file, so that we can read a file and then read all changes between versions, etc.
  • Create a mode system using headset by using double press of middle button as escape or something for clear. Have the ability to change up the reading list, and all kinds of other tasks using the headset's 3 buttons, with double clicks for each of them or something.
  • Take all the assumptions of computer science, for instance, the Church Turing thesis, and see if we can break these. Try to exploit them.
  • Set up a system with kbfs using Prolog which understands whether a directory has been updated or not. And reminds us, when doing the kmax-update-frdcsa-repositories to do all the different ones that need updating.
  • Have a function for finding all symlinks that point to a given location.
  • For kbfs have Perl load the kbfs ids of all the source files it is loading. Somehow get this from the Perl interpreter.
  • Make a knowledge base which stores the names of all the systems which Cyc uses to convert text to knowledge.
  • Get in touch with the authors of all the systems we are using, and use them as the primary contact points for people to work with on AI.
  • Develop a system for looking at all the possible rules we have, and determining, based on text to logic conversion and also textual entailment recognition, when the rules are satisfied and what the consequences of this are.
  • Locate all the voy.gz files, and convert them to use page turn markers, and then add to the KB which pages have been read. Maybe before doing this, figure out how to represent page ranges and use where applicable.
  • Just as in how I would define things that I hadn't seen very often by remembering all the bindings or examples of their use, NLU/IAEC/Sayer2 should remember all invocations of text / data in context. So for instance, if it saw a particular word, it would track all usages of the word, and all data sources like WordNet mentioning it, and cross reference them.
  • Develop something to download all the pages we have in our history, and then make them searchable.
  • For reference-systems, have an index of all the packages on the different systems and their executables, etc, so that we can tell which system can run a command we need.
  • Play Inform7 games to get a better idea of how it all works.
  • Develop a context mechanism for assessing meaning, add to NLU. For instance, the expression "Chris might know someone" had a lot of context, that we were looking at the time for someone to do tech support, things like that. all these assertions could be made in a KB and used as contextual knowledge for the statement. Build this manually at first, followed by automatically.
  • NLU should use an algorithm which takes all the objects in Sayer that are plain text instances and matches them in strings. For instance if the following were sayer data points: 'the' and 'there', and the text read "there's a lot of stuff", it would assert the matches for 'the' and 'there'. Obviously this needs to be constrained somehow, as there would often be individual words, so there might be an interestingness or relevance constraint - or maybe some kind of procedural semantics.
  • Use kbfs, have it learn when to automatically attribute facts to files based on certain correlations. Also use Sayer and Sayer-learner, and Thinker to learn when these facts apply to the files. Then, for instance, do automatic classification of text files into subject headings. Ultimately organize all of the research papers and documents I have into a coherent, cohesive whole.
  • Add the ability to filter items on the stack, such as removing all entries that match a given regular expression, etc.
  • Work with MDR to make lists of all the tabled information.
  • Develop an agent to comb through all of the files on my system and categorize them and place them in an order.
  • I was thinking, am I the only one who likes to shore up truths by making them necessary truths, and then I started wondering, maybe necessity is the key to things like truth maintainence and assert unassert and all that kind of temporal consistency stuff.
  • Is there a function for searching all the comment strings in Cyc?
  • Fix FRDCSA Cyc access to not reconnect all the time, to do proper error handling, and to , hrm forget
  • For our system which is related to AM eurisko cyc bps, listen to the song a whole new world, and extract all the nouns and adjectives which relate to interestingness, such as "a wonder", "sights" or "fantastic". Have the AI apply such descriptions if it merits it.
  • If you cannot implement a algorithm that checks the correctness of proofs for all true theorems, can you implement one that is in some sense defeasibly correct?
  • all of sayer should be searchable with an index.
  • Work out all our supplies one day - to make sure we have enough.
  • Process all the writings about Eurisko, and analyze them in order to develop evidence that the program was constructed in a particular way.
  • Go through and index all the resources we have for AI and use them to develop the normal form etc systems.
  • Somehow deal with the fact that our external codebases can sometimes have multiple archive files in them, but our sandboxes can only have one directory for all of them.
  • Develop a search interface for finding software that explodes all the clue we have about it, and uses google to search.
  • There is a notion of what are all the commands I can run at point, so for instance if certain commands would fail at point, then they would not count. This concept is part of the kmax-object-manipulation-system.
  • Get a text to speech engine that speak Latin so we know what it sounds like. Actually, may have already done that with all. Try setting all up again.
  • Possibly have FRDCSA index all .do and .notes files and index the answers to all (solution (X) (Y)) statements, and make that searchable.
  • Add an option to clean packager build environment. i.e. get rid of all the files that aren't .orig.xz or the dir, and some in dir/debian
  • Above all, make all of this fun.
  • Use kbfs to tag which files are known to be software archives, versus which are known to be data sets, versus which are not known to be either, versus which we know nothing about at all. This database could be bootstrapped by iterating over /var/lib/myfrdcsa/codebases/external versus /var/lib/myfrdcsa/codebases/datasets, and then tagging several of neither kind. Then extract features of those data points, using Sayer, etc, to do machine learning to automatically classify items as being software collections or not.
  • Extract all links from the CSX data.
  • Create different levels of desiring to read something. Desire to read all of it at some future time. Desire to read part of it at some future time. Desire to read it while Phi is unknown. Etc.
  • Make a service inventory, for all the different things that are offered by different servers. I think I started on this somewhere. Should be in myconfig-private.
  • find-or-create a library that is capable of iterating over common numbered pages and grabbing all entries.
  • Create a freekbs2 command like all term assertions to get all assertions in one or more contexts involving the item.
  • update search-old to search all of our available systems.
  • Have functions for telling Academcian that all pages are not read, have a fluent for length of document, have it infer defeasibly that document is completely read.
  • Make it easy to analyze where data gets written by Sayer etc all, and to remove it, say for instance some private information is processed by it.
  • Build the Sayer/NLU/kbfs system that asserts information about files and explores all the possible things to assert about them.
  • Make a toggle mode for KBS2-KE mode where you can fully insert all text
  • Have the ability for NLU to reason with multiple possible meanings simultaneously. For instance, suppose there was a word on one page ending with a -, and then a different word on the next page, but it was unclear whether these were one conjoined word or simply two words separated by a dash. NLU should be able to answer questions and such regarding all or some meanings of these.
  • make xsb, flora2 and liblanguage-xsb-perl all depend on the proper packages.
  • Want to provide some kind of regression testing to make sure that our libraries cover all required areas and don't have gaps and inconsistencies.
  • Start recording all the issues with freekbs2 in order to rewrite freekbs3 to be better.
  • Install all the KBP stuff as packages.
  • Work out the issues with fitting all the data and backing it up on ai.frdcsa.org
  • One day, take the time to go through all the old stuff in the project, things like a bookmark folder full of tabs that have been copied there, and get all the nitty gritty useful info for the project.
  • Reload the packages from here: /media/andrewdo/backup/backup/aloysius.frdcsa.org/myfrdcsa/packages/debian/unstable into the unstable package repository. Get all the packages back into version control.
  • Apply KNext and in general Capability::TextAnalyzer (fully loaded) to all the items in my browsing history.
  • Record all bad keys, like 'C-c C-k u p' killing unilang instead of starting update-frdcsa-git.
  • Eventually install all cron files in /frdcsa/cron*, but for now just manually add them. Add that to the installer. Add a hook whenever something is installed to test for that.
  • New years resolutions. Aggregate all resources of the FRDCSA. to.do, .notes, daily todos, unilang logs, etc, into a unified information access system across the FRDCSA, add search abilities
  • Find all items on our ai.frdcsa.org that symlink to /media/andrewdo/backup and move them to s3
  • The system should work with all the knowledge it has about the contents.
  • Add something to update-frdcsa-git so that it will track the current statuses of all of it
  • Using recovery-frdcsa, make a list of all files that have not changed presumably based on file dates if possible, or at least sizes.
  • Write an extension for system-recommender which looks at all the project specific files as purposes and prints out recommended links for each project.
  • Make a place, probably in 'mush', to collect all the tutorials that we've used, and logs of IRC chats for things like fixing the RAID array on the xen server
  • Get rid of all non applicative declarations in project .el files that are not config files.
  • Use the bookshelf of paperless office to represent the readinglist of clear. Tie that all in somehow. Make different repositories.
  • Rewrite install-script-dependencies to keep a log of all the modules it installs.
  • Convert audience ball-in-court to a gui program that allows us to mark threads as read. And this way, stay on top of all of my important messages across all accounts.
  • Compile a central registry of all of our git repos.
  • Find all the most interesting projects on code.google.com and related sites and speak with their authors about collaborating.
  • Start mapping out all conferences of interest and their proceedings that we can get a hold of, for instance AAMAS
  • We can do all of this and more with this new system.
  • Have kmax-search extend to searching all emacs stuff in memory, such as documentation etc
  • Have a way to search all of the KBS2 items, not just in a particular context. But tell which context.
  • Develop a list of all the virtual machines we want.
  • Keep a database of all of my hardware and manuals.
  • Add a function to academician to show all the assertions that are related to the current buffer.
  • Implement info to piece together all that is known about a current buffer from academician.
  • Fix ghosting to strip all the whitespace from a page before md5summing, so that it tends to preserve across formatting differences.
  • Have a way of asking for an explanation of a particular piece of text, for instance: "In actuality, all of a class's metaclasses must be compatible, not just the class metaclass."
  • Add to my schedule to practice emacs keys learning them all
  • js-rapid-response: Implement a system for cleaning up the database, removing all entries that were not viewed, etc.
  • Start filling out all petitions that we should.
  • Develop a core operating system that gets all the essential stuff up and running.
  • Make an index of all skills required for daily life.
  • Develop a backup plan for all of my computers.
  • Develop an index of all the news we read, using the GNUS 'setting marks' capabilities, and build a database of that news and analyze the sentiment of various named entities in the news, and various notes about those entities. formalize the news contents.
  • Fix the ability of the all-translate-text item to work with foreign language character sets. oops.
  • Set up software tests for all systems.
  • Develop a list of all free entertainment and entertainment software
  • Start keeping a record of all items I read in a repository, use a SOCKS proxy or something to keep track of all that is downloaded, and use other hooks to keep track of what we actually read.
  • install and use all the NLP components from: http://cl.naist.jp/~eric-n/ubuntu-nlp/
  • Send Chris a zip file of all my papers.
  • Definitely get PSE2 working and have all of the functions in there upgraded.
  • Fix the problem whereby unasserting (desires andrewdo) will unassert all the items like (desires andrewdo X)
  • Remove the possibility of error messages getting intertwined with messages from Perl to Emacs by switching to all unilang.
  • Reset all of the sayer data on NLU because it's all messed up, figure out where it's going wrong and right the wrong.
  • Cyc, (all-term-assertions #$testCollectionProjectResponsible)
  • Make a list of all possible references and sort them in order of professionality.
  • Agenda: all new Liferea entries> Fri Sep 24 10:00:01 CDT 2010
    ("due-date-for-entry" "150333" "3 hours")
  • Agenda: all systems> Fri Sep 24 10:00:00 CDT 2010
    ("due-date-for-entry" "150332" "3 hours")
  • Agenda: all new Liferea entries> Thu Sep 23 10:00:00 CDT 2010
    ("due-date-for-entry" "150286" "3 hours")
  • Agenda: all new Liferea entries> Wed Sep 22 10:00:00 CDT 2010
    ("due-date-for-entry" "150210" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 22 06:00:00 CDT 2010
    ("due-date-for-entry" "150200" "3 hours")
  • Agenda: all new Liferea entries> Tue Sep 21 10:00:00 CDT 2010
    ("due-date-for-entry" "150165" "3 hours")
  • Agenda: all new Liferea entries> Mon Sep 20 10:00:00 CDT 2010
  • Agenda: all new Liferea entries> Sun Sep 19 10:00:00 CDT 2010
    ("due-date-for-entry" "150012" "3 hours")
  • Agenda: all new Liferea entries> Sat Sep 18 10:00:00 CDT 2010
    ("due-date-for-entry" "149981" "3 hours")
  • Agenda: all new Liferea entries> Fri Sep 17 10:00:00 CDT 2010
    ("due-date-for-entry" "149923" "3 hours")
  • Agenda: all systems> Fri Sep 17 10:00:00 CDT 2010
    ("due-date-for-entry" "149922" "3 hours")
  • Agenda: all new Liferea entries> Thu Sep 16 10:00:00 CDT 2010
    ("due-date-for-entry" "149863" "3 hours")
  • Agenda: all new Liferea entries> Wed Sep 15 10:00:00 CDT 2010
    ("due-date-for-entry" "149584" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 15 06:00:00 CDT 2010
    ("due-date-for-entry" "149574" "3 hours")
  • Agenda: all new Liferea entries> Tue Sep 14 10:00:00 CDT 2010
    ("due-date-for-entry" "149537" "3 hours")
  • Agenda: all new Liferea entries> Mon Sep 13 10:00:00 CDT 2010
    ("due-date-for-entry" "149471" "3 hours")
  • Agenda: all new Liferea entries> Sun Sep 12 10:00:00 CDT 2010
    ("due-date-for-entry" "149382" "3 hours")
  • Agenda: all new Liferea entries> Fri Sep 10 10:00:02 CDT 2010
    ("due-date-for-entry" "149280" "3 hours")
  • Agenda: all systems> Fri Sep 10 10:00:00 CDT 2010
    ("due-date-for-entry" "149279" "3 hours")
  • Agenda: all new Liferea entries> Thu Sep 9 10:00:00 CDT 2010
    ("due-date-for-entry" "149111" "3 hours")
  • Agenda: all new Liferea entries> Mon Sep 6 10:00:00 CDT 2010
    ("due-date-for-entry" "149000" "3 hours")
  • Agenda: all new Liferea entries> Sun Sep 5 10:00:00 CDT 2010
    ("due-date-for-entry" "148953" "3 hours")
  • Agenda: all new Liferea entries> Thu Sep 2 10:00:00 CDT 2010
    ("due-date-for-entry" "148788" "3 hours")
  • Agenda: all new Liferea entries> Wed Sep 1 10:00:00 CDT 2010
    ("due-date-for-entry" "148705" "3 hours")
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 1 06:00:00 CDT 2010%' 148685" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 1 06:00:00 CDT 2010
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: all new Liferea entries> Tue Aug 31 10:00:00 CDT 2010%'" "3 hours")
  • Agenda: all new Liferea entries> Tue Aug 31 10:00:00 CDT 2010
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: all new Liferea entries> Mon Aug 30 10:00:00 CDT 2010%' 148565" "3 hours")
  • Agenda: all new Liferea entries> Mon Aug 30 10:00:00 CDT 2010
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: all new Liferea entries> Sun Aug 29 10:00:00 CDT 2010%' 148519" "3 hours")
  • Agenda: all new Liferea entries> Sun Aug 29 10:00:00 CDT 2010
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: all new Liferea entries> Sat Aug 28 10:00:00 CDT 2010%' 148461" "3 hours")
  • Agenda: all new Liferea entries> Sat Aug 28 10:00:00 CDT 2010
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: all new Liferea entries> Fri Aug 27 10:00:00 CDT 2010%' 148414" "3 hours")
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: all systems> Fri Aug 27 10:00:00 CDT 2010%' 148413" "3 hours")
  • Agenda: all systems> Fri Aug 27 10:00:00 CDT 2010
  • Agenda: all new Liferea entries> Fri Aug 27 10:00:00 CDT 2010
  • KBS, MySQL:freekbs:default assert ("due-date-for-entry" "select * from messages where Contents like '%Agenda: all new Liferea entries> Thu Aug 26 10:00:00 CDT 2010%' 148350" "3 hours")
  • Agenda: all new Liferea entries> Thu Aug 26 10:00:00 CDT 2010
  • Agenda: all new Liferea entries> Wed Aug 25 10:00:00 CDT 2010
    ("due-date-for-entry" "148276" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 25 06:00:00 CDT 2010
    ("due-date-for-entry" "148241" "3 hours")
  • Agenda: all new Liferea entries> Tue Aug 24 10:00:00 CDT 2010
    ("due-date-for-entry" "148203" "3 hours")
  • Agenda: all new Liferea entries> Mon Aug 23 10:00:00 CDT 2010
    ("due-date-for-entry" "148144" "3 hours")
  • Agenda: all new Liferea entries> Sun Aug 22 10:00:00 CDT 2010
    ("due-date-for-entry" "148064" "3 hours")
  • Agenda: all new Liferea entries> Thu Aug 19 10:00:00 CDT 2010
    ("due-date-for-entry" "148006" "3 hours")
  • Agenda: all new Liferea entries> Wed Aug 18 10:00:00 CDT 2010
    ("due-date-for-entry" "147956" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 18 06:00:00 CDT 2010
    ("due-date-for-entry" "147935" "3 hours")
  • Agenda: all new Liferea entries> Tue Aug 17 10:00:00 CDT 2010
    ("due-date-for-entry" "147888" "3 hours")
  • Agenda: all new Liferea entries> Mon Aug 16 10:00:00 CDT 2010
    ("due-date-for-entry" "147791" "3 hours")
  • Agenda: all new Liferea entries> Sun Aug 15 10:00:00 CDT 2010
    ("due-date-for-entry" "147744" "3 hours")
  • Agenda: all new Liferea entries> Sat Aug 14 10:00:01 CDT 2010
    ("due-date-for-entry" "147674" "3 hours")
  • Agenda: all new Liferea entries> Fri Aug 13 10:00:01 CDT 2010
    ("due-date-for-entry" "147523" "3 hours")
  • Agenda: all systems> Fri Aug 13 10:00:00 CDT 2010
    ("due-date-for-entry" "147522" "3 hours")
  • Agenda: all new Liferea entries> Thu Aug 12 10:00:00 CDT 2010
    ("due-date-for-entry" "147478" "3 hours")
  • Agenda: all new Liferea entries> Wed Aug 11 10:00:01 CDT 2010
    ("due-date-for-entry" "147383" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 11 06:00:00 CDT 2010
    ("due-date-for-entry" "147372" "3 hours")
  • Agenda: all new Liferea entries> Tue Aug 10 10:00:00 CDT 2010
    ("due-date-for-entry" "147183" "3 hours")
  • Agenda: all new Liferea entries> Mon Aug 9 10:00:00 CDT 2010
    ("due-date-for-entry" "146902" "3 hours")
  • Agenda: all new Liferea entries> Sat Aug 7 10:00:00 CDT 2010
    ("due-date-for-entry" "146585" "3 hours")
  • Agenda: all new Liferea entries> Fri Aug 6 10:00:00 CDT 2010
    ("due-date-for-entry" "146513" "3 hours")
  • Agenda: all systems> Fri Aug 6 10:00:00 CDT 2010
    ("due-date-for-entry" "146511" "3 hours")
  • Agenda: all new Liferea entries> Thu Aug 5 10:00:00 CDT 2010
    ("due-date-for-entry" "146336" "3 hours")
  • Agenda: all new Liferea entries> Wed Aug 4 10:00:00 CDT 2010
    ("due-date-for-entry" "146103" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 4 06:00:00 CDT 2010
    ("due-date-for-entry" "146073" "3 hours")
  • Agenda: all new Liferea entries> Sun Aug 1 10:00:00 CDT 2010
  • Agenda: all new Liferea entries> Sat Jul 31 10:00:00 CDT 2010
    ("due-date-for-entry" "145753" "3 hours")
  • Agenda: all systems> Fri Jul 30 19:22:28 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Fri Jul 30 19:22:21 CDT 2010
  • Agenda: all new Liferea entries> Fri Jul 30 19:22:01 CDT 2010
  • Agenda: all new Liferea entries> Mon Jul 26 10:00:00 CDT 2010
    ("due-date-for-entry" "145633" "3 hours")
  • Agenda: all new Liferea entries> Sun Jul 25 10:00:00 CDT 2010
    ("due-date-for-entry" "145585" "3 hours")
  • Agenda: all new Liferea entries> Sat Jul 24 10:00:00 CDT 2010
    ("due-date-for-entry" "145544" "3 hours")
  • Agenda: all new Liferea entries> Fri Jul 23 10:00:00 CDT 2010
    ("due-date-for-entry" "145497" "3 hours")
  • Agenda: all systems> Fri Jul 23 10:00:00 CDT 2010
    ("due-date-for-entry" "145498" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 21 06:00:00 CDT 2010
  • Agenda: all new Liferea entries> Sun Jul 18 10:00:01 CDT 2010
    ("due-date-for-entry" "145116" "3 hours")
  • Agenda: all new Liferea entries> Sat Jul 17 10:00:00 CDT 2010
    ("due-date-for-entry" "145033" "3 hours")
  • Agenda: all new Liferea entries> Fri Jul 16 10:00:00 CDT 2010
    ("due-date-for-entry" "144869" "3 hours")
  • Agenda: all systems> Fri Jul 16 10:00:00 CDT 2010
    ("due-date-for-entry" "144868" "3 hours")
  • Agenda: all new Liferea entries> Wed Jul 14 10:00:00 CDT 2010
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 14 06:00:00 CDT 2010
  • Agenda: all new Liferea entries> Mon Jul 12 10:00:00 CDT 2010
    ("due-date-for-entry" "144406" "3 hours")
  • Agenda: all new Liferea entries> Sun Jul 11 10:00:00 CDT 2010
    ("due-date-for-entry" "144341" "3 hours")
  • Agenda: all new Liferea entries> Sat Jul 10 10:00:00 CDT 2010
  • Agenda: all systems> Fri Jul 9 10:00:00 CDT 2010
    ("due-date-for-entry" "143867" "3 hours")
  • Agenda: all new Liferea entries> Fri Jul 9 10:00:00 CDT 2010
    ("due-date-for-entry" "143868" "3 hours")
  • Agenda: all new Liferea entries> Thu Jul 8 10:00:00 CDT 2010
    ("due-date-for-entry" "143815" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 7 06:00:00 CDT 2010
  • Agenda: all new Liferea entries> Mon Jul 5 10:00:00 CDT 2010
  • Agenda: all new Liferea entries> Sun Jul 4 10:00:00 CDT 2010
    ("due-date-for-entry" "143423" "3 hours")
  • Agenda: all new Liferea entries> Sat Jul 3 10:00:00 CDT 2010
    ("due-date-for-entry" "143378" "3 hours")
  • Agenda: all new Liferea entries> Fri Jul 2 10:00:01 CDT 2010
    ("due-date-for-entry" "143330" "3 hours")
  • Agenda: all systems> Fri Jul 2 10:00:00 CDT 2010
    ("due-date-for-entry" "143329" "3 hours")
  • Agenda: all new Liferea entries> Wed Jun 30 10:00:00 CDT 2010
    ("due-date-for-entry" "142927" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 30 06:00:00 CDT 2010
    ("due-date-for-entry" "142916" "3 hours")
  • Agenda: all new Liferea entries> Tue Jun 29 10:00:00 CDT 2010
    ("due-date-for-entry" "142653" "3 hours")
  • Agenda: all new Liferea entries> Mon Jun 28 10:00:00 CDT 2010
    ("due-date-for-entry" "142534" "3 hours")
  • Agenda: all new Liferea entries> Sun Jun 27 10:00:00 CDT 2010
    ("due-date-for-entry" "142260" "3 hours")
  • Agenda: all new Liferea entries> Sat Jun 26 10:00:00 CDT 2010
    ("due-date-for-entry" "141991" "3 hours")
  • Agenda: all systems> Fri Jun 25 10:00:00 CDT 2010
    ("due-date-for-entry" "141622" "3 hours")
  • Agenda: all new Liferea entries> Fri Jun 25 10:00:00 CDT 2010
    ("due-date-for-entry" "141624" "3 hours")
  • Agenda: all new Liferea entries> Thu Jun 24 10:00:00 CDT 2010
    ("due-date-for-entry" "141314" "3 hours")
  • Agenda: all new Liferea entries> Wed Jun 23 10:00:00 CDT 2010
    ("due-date-for-entry" "141265" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 23 06:00:00 CDT 2010
    ("due-date-for-entry" "141254" "3 hours")
  • Agenda: all new Liferea entries> Mon Jun 21 10:00:00 CDT 2010
    ("due-date-for-entry" "141125" "3 hours")
  • Agenda: all new Liferea entries> Sun Jun 20 10:00:00 CDT 2010
    ("due-date-for-entry" "141073" "3 hours")
  • Agenda: all new Liferea entries> Sat Jun 19 10:00:00 CDT 2010
    ("due-date-for-entry" "141030" "3 hours")
  • Agenda: all new Liferea entries> Wed Jun 16 10:00:00 CDT 2010
    ("due-date-for-entry" "140661" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 16 06:00:02 CDT 2010
    ("due-date-for-entry" "140651" "3 hours")
  • Agenda: all new Liferea entries> Tue Jun 15 10:00:00 CDT 2010
    ("due-date-for-entry" "140567" "3 hours")
  • Agenda: all new Liferea entries> Wed Jun 9 10:00:00 CDT 2010
    ("due-date-for-entry" "140115" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 9 06:00:00 CDT 2010
    ("due-date-for-entry" "140105" "3 hours")
  • Agenda: all new Liferea entries> Tue Jun 8 10:00:00 CDT 2010
    ("due-date-for-entry" "140019" "3 hours")
  • Agenda: all new Liferea entries> Mon Jun 7 10:00:00 CDT 2010
    ("due-date-for-entry" "139966" "3 hours")
  • Agenda: all new Liferea entries> Sun Jun 6 10:00:00 CDT 2010
    ("due-date-for-entry" "139915" "3 hours")
  • Agenda: all new Liferea entries> Sat Jun 5 10:00:00 CDT 2010
    ("due-date-for-entry" "139698" "3 hours")
  • Agenda: all systems> Fri Jun 4 10:00:00 CDT 2010
    ("due-date-for-entry" "139273" "3 hours")
  • Agenda: all new Liferea entries> Fri Jun 4 10:00:00 CDT 2010
    ("due-date-for-entry" "139272" "3 hours")
  • Agenda: all new Liferea entries> Thu Jun 3 10:00:00 CDT 2010
    ("due-date-for-entry" "138749" "3 hours")
  • Agenda: all new Liferea entries> Wed Jun 2 10:00:00 CDT 2010
    ("due-date-for-entry" "138476" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jun 2 06:00:00 CDT 2010
    ("due-date-for-entry" "138465" "3 hours")
  • Agenda: all new Liferea entries> Tue Jun 1 10:00:01 CDT 2010
    ("due-date-for-entry" "138405" "3 hours")
  • Agenda: all systems> Fri May 28 10:00:00 CDT 2010
    ("due-date-for-entry" "138181" "3 hours")
  • Agenda: all new Liferea entries> Fri May 28 10:00:00 CDT 2010
    ("due-date-for-entry" "138183" "3 hours")
  • Agenda: all new Liferea entries> Thu May 27 10:00:00 CDT 2010
    ("due-date-for-entry" "138035" "3 hours")
  • Agenda: all new Liferea entries> Wed May 26 10:00:00 CDT 2010
    ("due-date-for-entry" "137985" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed May 26 06:00:00 CDT 2010
    ("due-date-for-entry" "137975" "3 hours")
  • Agenda: all new Liferea entries> Tue May 25 10:00:00 CDT 2010
    ("due-date-for-entry" "137938" "3 hours")
  • Agenda: all new Liferea entries> Mon May 24 10:00:00 CDT 2010
    ("due-date-for-entry" "137890" "3 hours")
  • Agenda: all new Liferea entries> Sun May 23 10:00:00 CDT 2010
    ("due-date-for-entry" "137721" "3 hours")
  • Agenda: all new Liferea entries> Fri May 21 10:00:01 CDT 2010
    ("due-date-for-entry" "137391" "3 hours")
  • Agenda: all systems> Fri May 21 10:00:00 CDT 2010
    ("due-date-for-entry" "137390" "3 hours")
  • Agenda: all new Liferea entries> Thu May 20 10:00:00 CDT 2010
    ("due-date-for-entry" "137072" "3 hours")
  • Agenda: all new Liferea entries> Mon May 17 10:00:00 CDT 2010
    ("due-date-for-entry" "137016" "3 hours")
  • Agenda: all new Liferea entries> Sun May 16 10:00:00 CDT 2010
    ("due-date-for-entry" "136971" "3 hours")
  • Agenda: all new Liferea entries> Sat May 15 10:00:00 CDT 2010
    ("due-date-for-entry" "136928" "3 hours")
  • Agenda: all new Liferea entries> Fri May 14 10:00:00 CDT 2010
    ("due-date-for-entry" "136794" "3 hours")
  • Agenda: all systems> Fri May 14 10:00:00 CDT 2010
    ("due-date-for-entry" "136793" "3 hours")
  • Agenda: all new Liferea entries> Wed May 12 10:00:00 CDT 2010
    ("due-date-for-entry" "136474" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed May 12 06:00:00 CDT 2010
    ("due-date-for-entry" "136464" "3 hours")
  • Agenda: all new Liferea entries> Sun May 9 10:00:00 CDT 2010
  • Agenda: all systems> Fri May 7 10:00:00 CDT 2010
    ("due-date-for-entry" "135685" "3 hours")
  • Agenda: all new Liferea entries> Fri May 7 10:00:00 CDT 2010
    ("due-date-for-entry" "135687" "3 hours")
  • Agenda: all new Liferea entries> Thu May 6 10:00:00 CDT 2010
    ("due-date-for-entry" "135454" "3 hours")
  • Agenda: all new Liferea entries> Wed May 5 10:00:00 CDT 2010
    ("due-date-for-entry" "135387" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed May 5 06:00:00 CDT 2010
    ("due-date-for-entry" "135377" "3 hours")
  • Agenda: all new Liferea entries> Tue May 4 10:00:00 CDT 2010
    ("due-date-for-entry" "134736" "3 hours")
  • Agenda: all new Liferea entries> Mon May 3 10:00:00 CDT 2010
    ("due-date-for-entry" "134376" "3 hours")
  • Agenda: all new Liferea entries> Sun May 2 10:00:00 CDT 2010
    ("due-date-for-entry" "134328" "3 hours")
  • Agenda: all new Liferea entries> Sat May 1 10:00:00 CDT 2010
    ("due-date-for-entry" "134284" "3 hours")
  • Agenda: all new Liferea entries> Wed Apr 28 10:00:00 CDT 2010
    ("due-date-for-entry" "133935" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 28 06:00:00 CDT 2010
    ("due-date-for-entry" "133925" "3 hours")
  • Agenda: all new Liferea entries> Tue Apr 27 10:00:00 CDT 2010
    ("due-date-for-entry" "133827" "3 hours")
  • Agenda: all new Liferea entries> Thu Apr 22 10:00:00 CDT 2010
    ("due-date-for-entry" "132961" "3 hours")
  • Agenda: all new Liferea entries> Wed Apr 21 10:00:00 CDT 2010
    ("due-date-for-entry" "132408" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 21 06:00:00 CDT 2010
    ("due-date-for-entry" "132391" "3 hours")
  • Agenda: all new Liferea entries> Tue Apr 20 10:00:00 CDT 2010
    ("due-date-for-entry" "132304" "3 hours")
  • Agenda: all new Liferea entries> Sun Apr 18 10:00:00 CDT 2010
    ("due-date-for-entry" "132111" "3 hours")
  • Agenda: all new Liferea entries> Sat Apr 17 10:00:00 CDT 2010
    ("due-date-for-entry" "132069" "3 hours")
  • Agenda: all systems> Fri Apr 16 10:00:00 CDT 2010
    ("due-date-for-entry" "131915" "3 hours")
  • Agenda: all new Liferea entries> Fri Apr 16 10:00:00 CDT 2010
    ("due-date-for-entry" "131916" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 14 06:00:00 CDT 2010
    ("due-date-for-entry" "131135" "3 hours")
  • Agenda: all new Liferea entries> Sun Apr 11 10:00:00 CDT 2010
    ("due-date-for-entry" "131073" "3 hours")
  • Agenda: all new Liferea entries> Sat Apr 10 10:00:00 CDT 2010
    ("due-date-for-entry" "131032" "3 hours")
  • Agenda: all systems> Fri Apr 9 10:00:00 CDT 2010
    ("due-date-for-entry" "129946" "3 hours")
  • Agenda: all new Liferea entries> Fri Apr 9 10:00:00 CDT 2010
    ("due-date-for-entry" "129948" "3 hours")
  • Cyc, (all-term-assertions #$CatholicPerson)
  • Cyc, (all-instances #$Person)
  • Cyc, (all-instances "Person")
  • Cyc, (all-isa "Person" #$BaseKB)
  • Cyc, (all-isa "")
  • Agenda: all new Liferea entries> Thu Apr 8 10:00:00 CDT 2010
    ("due-date-for-entry" "129652" "3 hours")
  • Agenda: all new Liferea entries> Wed Apr 7 10:00:00 CDT 2010
    ("due-date-for-entry" "129538" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Apr 7 06:00:00 CDT 2010
    ("due-date-for-entry" "129524" "3 hours")
  • Agenda: all new Liferea entries> Sat Apr 3 10:00:00 CDT 2010
    ("due-date-for-entry" "129442" "3 hours")
  • Agenda: all new Liferea entries> Tue Mar 30 10:00:00 CDT 2010
    ("due-date-for-entry" "129384" "3 hours")
  • Agenda: all new Liferea entries> Mon Mar 29 10:00:00 CDT 2010
    ("due-date-for-entry" "129276" "3 hours")
  • Agenda: all new Liferea entries> Sun Mar 28 10:00:00 CDT 2010
    ("due-date-for-entry" "128904" "3 hours")
  • Agenda: all new Liferea entries> Sat Mar 27 10:00:00 CDT 2010
    ("due-date-for-entry" "127592" "3 hours")
  • Agenda: all systems> Fri Mar 26 10:00:01 CDT 2010
    ("due-date-for-entry" "127545" "3 hours")
  • Agenda: all new Liferea entries> Fri Mar 26 10:00:01 CDT 2010
    ("due-date-for-entry" "127547" "3 hours")
  • Agenda: all new Liferea entries> Thu Mar 25 10:00:00 CDT 2010
    ("due-date-for-entry" "127498" "3 hours")
  • Agenda: all new Liferea entries> Sat Mar 13 10:00:00 CST 2010
    ("due-date-for-entry" "127450" "3 hours")
  • Agenda: all new Liferea entries> Fri Mar 12 10:00:00 CST 2010
    ("due-date-for-entry" "127404" "3 hours")
  • Agenda: all systems> Fri Mar 12 10:00:00 CST 2010
    ("due-date-for-entry" "127403" "3 hours")
  • Agenda: all new Liferea entries> Thu Mar 11 10:00:00 CST 2010
    ("due-date-for-entry" "127360" "3 hours")
  • Agenda: all new Liferea entries> Wed Mar 10 10:00:00 CST 2010
    ("due-date-for-entry" "127311" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Mar 10 06:00:00 CST 2010
    ("due-date-for-entry" "127301" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Mar 3 06:00:00 CST 2010
    ("due-date-for-entry" "127264" "3 hours")
  • Agenda: all new Liferea entries> Tue Mar 2 10:00:01 CST 2010
    ("due-date-for-entry" "127227" "3 hours")
  • Agenda: all new Liferea entries> Mon Mar 1 10:00:00 CST 2010
    ("due-date-for-entry" "127176" "3 hours")
  • Agenda: all new Liferea entries> Sun Feb 28 10:00:01 CST 2010
    ("due-date-for-entry" "127118" "3 hours")
  • Agenda: all new Liferea entries> Sat Feb 27 10:00:00 CST 2010
    ("due-date-for-entry" "127076" "3 hours")
  • Agenda: all new Liferea entries> Fri Feb 26 10:00:00 CST 2010
    ("due-date-for-entry" "126892" "3 hours")
  • Agenda: all systems> Fri Feb 26 10:00:00 CST 2010
    ("due-date-for-entry" "126891" "3 hours")
  • Agenda: all new Liferea entries> Thu Feb 25 10:00:00 CST 2010
    ("due-date-for-entry" "126633" "3 hours")
  • Agenda: all new Liferea entries> Tue Feb 23 10:00:00 CST 2010
    ("due-date-for-entry" "126531" "3 hours")
  • Agenda: all new Liferea entries> Thu Feb 18 10:00:00 CST 2010
    ("due-date-for-entry" "125957" "3 hours")
  • Agenda: all new Liferea entries> Sun Feb 14 10:00:00 CST 2010
    ("due-date-for-entry" "125905" "3 hours")
  • Agenda: all new Liferea entries> Sat Feb 13 10:00:00 CST 2010
    ("due-date-for-entry" "125851" "3 hours")
  • Agenda: all new Liferea entries> Mon Jan 25 10:00:00 CST 2010
    ("due-date-for-entry" "125749" "3 hours")
  • Agenda: all new Liferea entries> Sun Jan 24 10:00:00 CST 2010
    ("due-date-for-entry" "125704" "3 hours")
  • Agenda: all new Liferea entries> Sat Jan 23 10:00:00 CST 2010
    ("due-date-for-entry" "125662" "3 hours")
  • Agenda: all new Liferea entries> Wed Jan 13 10:00:00 CST 2010
    ("due-date-for-entry" "125611" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 13 06:00:00 CST 2010
    ("due-date-for-entry" "125600" "3 hours")
  • Agenda: all systems> Fri Jan 1 10:00:00 CST 2010
    ("due-date-for-entry" "125536" "3 hours")
  • Agenda: all new Liferea entries> Fri Jan 1 10:00:00 CST 2010
    ("due-date-for-entry" "125534" "3 hours")
  • Agenda: all new Liferea entries> Thu Dec 31 10:00:00 CST 2009
    ("due-date-for-entry" "125479" "3 hours")
  • Agenda: all new Liferea entries> Thu Dec 24 10:00:00 CST 2009
    ("due-date-for-entry" "125365" "3 hours")
  • Agenda: all new Liferea entries> Wed Dec 23 10:00:00 CST 2009
    ("due-date-for-entry" "125183" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 23 06:00:00 CST 2009
    ("due-date-for-entry" "125173" "3 hours")
  • Cyc, (all-instances #$Person #$BaseKB)
  • Agenda: all new Liferea entries> Sun Dec 13 10:00:00 CST 2009
    ("due-date-for-entry" "124772" "3 hours")
  • Agenda: all new Liferea entries> Sat Dec 12 10:00:00 CST 2009
    ("due-date-for-entry" "124730" "3 hours")
  • Agenda: all systems> Fri Dec 11 10:00:00 CST 2009
    ("due-date-for-entry" "124684" "3 hours")
  • Agenda: all new Liferea entries> Fri Dec 11 10:00:00 CST 2009
    ("due-date-for-entry" "124685" "3 hours")
  • Agenda: all new Liferea entries> Thu Dec 10 10:00:00 CST 2009
    ("due-date-for-entry" "124640" "3 hours")
  • Agenda: all new Liferea entries> Mon Dec 7 10:00:00 CST 2009
    ("due-date-for-entry" "124602" "3 hours")
  • Agenda: all new Liferea entries> Sun Dec 6 10:00:00 CST 2009
    ("due-date-for-entry" "124552" "3 hours")
  • Agenda: all new Liferea entries> Sat Dec 5 10:00:00 CST 2009
    ("due-date-for-entry" "124510" "3 hours")
  • Agenda: all systems> Fri Dec 4 10:00:00 CST 2009
    ("due-date-for-entry" "124464" "3 hours")
  • Agenda: all new Liferea entries> Fri Dec 4 10:00:00 CST 2009
    ("due-date-for-entry" "124466" "3 hours")
  • Agenda: all new Liferea entries> Tue Dec 1 10:00:00 CST 2009
    ("due-date-for-entry" "124418" "3 hours")
  • Agenda: all new Liferea entries> Mon Nov 30 10:00:00 CST 2009
    ("due-date-for-entry" "124176" "3 hours")
  • Agenda: all new Liferea entries> Sun Nov 29 10:00:00 CST 2009
    ("due-date-for-entry" "123268" "3 hours")
  • Agenda: all new Liferea entries> Sat Nov 28 10:00:00 CST 2009
    ("due-date-for-entry" "123226" "3 hours")
  • Agenda: all systems> Fri Nov 27 10:00:01 CST 2009
  • Agenda: all new Liferea entries> Fri Nov 27 10:00:01 CST 2009
  • Agenda: all new Liferea entries> Thu Nov 26 10:00:00 CST 2009
    ("due-date-for-entry" "123137" "3 hours")
  • Agenda: all new Liferea entries> Wed Nov 25 10:00:00 CST 2009
    ("due-date-for-entry" "122171" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Nov 25 06:00:00 CST 2009
    ("due-date-for-entry" "122100" "3 hours")
  • Cyc, (cyclify "My System by Aron Nimzowitsch, first published in 1925, has its place among the two or three all-time most instructive books in the literature of chess.")
  • Agenda: all new Liferea entries> Mon Nov 23 10:00:00 CST 2009
    ("due-date-for-entry" "122012" "3 hours")
  • Agenda: all new Liferea entries> Sun Nov 22 10:00:00 CST 2009
    ("due-date-for-entry" "121966" "3 hours")
  • Agenda: all new Liferea entries> Sat Nov 21 10:00:00 CST 2009
    ("due-date-for-entry" "121924" "3 hours")
  • Agenda: all systems> Fri Nov 20 10:00:01 CST 2009
  • Agenda: all new Liferea entries> Fri Nov 20 10:00:01 CST 2009
  • Agenda: all new Liferea entries> Thu Nov 19 10:00:00 CST 2009
  • Cyc, (all-term-assertions #$Licorice)
  • Cyc, (all-instances "Basic")
  • Agenda: all new Liferea entries> Tue Nov 17 10:00:00 CST 2009
    ("due-date-for-entry" "121135" "3 hours")
  • Agenda: all new Liferea entries> Thu Nov 12 10:00:00 CST 2009
    ("due-date-for-entry" "120842" "3 hours")
  • Agenda: all new Liferea entries> Tue Nov 10 10:00:00 CST 2009
    ("due-date-for-entry" "119958" "3 hours")
  • Agenda: all new Liferea entries> Mon Nov 9 10:00:00 CST 2009
    ("due-date-for-entry" "119910" "3 hours")
  • Agenda: all new Liferea entries> Sun Nov 8 14:59:31 CST 2009
    ("due-date-for-entry" "119861" "3 hours")
  • Agenda: all new Liferea entries> Sat Nov 7 10:00:00 CST 2009
  • Agenda: all new Liferea entries> Fri Nov 6 10:00:00 CST 2009
    ("due-date-for-entry" "119423" "3 hours")
  • Agenda: all systems> Fri Nov 6 10:00:00 CST 2009
    ("due-date-for-entry" "119422" "3 hours")
  • KBS, MySQL2:freekbs2:formalize all-asserted-knowledge
  • KBS, MySQL2:freekbs2:formalize all-assertions
  • Agenda: all systems> Fri Oct 30 10:00:00 CDT 2009
    ("due-date-for-entry" "118644" "3 hours")
  • Agenda: all new Liferea entries> Fri Oct 30 10:00:00 CDT 2009
    ("due-date-for-entry" "118645" "3 hours")
  • Agenda: all new Liferea entries> Thu Oct 29 10:00:00 CDT 2009
    ("due-date-for-entry" "117375" "3 hours")
  • KBS, MySQL2:freekbs2:test all-asserted-knowledge
  • Agenda: all new Liferea entries> Wed Oct 28 10:00:00 CDT 2009
    ("due-date-for-entry" "116857" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Oct 28 06:00:01 CDT 2009
  • Agenda: all new Liferea entries> Tue Oct 27 10:00:00 CDT 2009
    ("due-date-for-entry" "116103" "3 hours")
  • Agenda: all new Liferea entries> Fri Oct 23 10:00:00 CDT 2009
    ("due-date-for-entry" "115576" "3 hours")
  • Agenda: all systems> Fri Oct 23 10:00:00 CDT 2009
    ("due-date-for-entry" "115575" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Oct 21 06:00:00 CDT 2009
    ("due-date-for-entry" "115401" "3 hours")
  • Agenda: all new Liferea entries> Mon Oct 5 10:00:00 CDT 2009
    ("due-date-for-entry" "115346" "3 hours")
  • Agenda: all new Liferea entries> Thu Oct 1 10:00:01 CDT 2009
    ("due-date-for-entry" "114563" "3 hours")
  • Agenda: all new Liferea entries> Wed Sep 30 10:00:00 CDT 2009
    ("due-date-for-entry" "114465" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Sep 30 06:00:00 CDT 2009
    ("due-date-for-entry" "114455" "3 hours")
  • Agenda: all new Liferea entries> Tue Sep 29 10:00:01 CDT 2009
    ("due-date-for-entry" "114420" "3 hours")
  • Agenda: all new Liferea entries> Mon Sep 28 10:00:00 CDT 2009
    ("due-date-for-entry" "113891" "3 hours")
  • Agenda: all new Liferea entries> Sun Aug 23 10:00:00 CDT 2009
    ("due-date-for-entry" "113746" "3 hours")
  • Agenda: all new Liferea entries> Sat Aug 22 10:00:00 CDT 2009
    ("due-date-for-entry" "113703" "3 hours")
  • Agenda: all systems> Fri Aug 21 10:00:00 CDT 2009
    ("due-date-for-entry" "113658" "3 hours")
  • Agenda: all new Liferea entries> Fri Aug 21 10:00:00 CDT 2009
    ("due-date-for-entry" "113659" "3 hours")
  • Agenda: all new Liferea entries> Thu Aug 20 10:00:00 CDT 2009
    ("due-date-for-entry" "113597" "3 hours")
  • Agenda: all new Liferea entries> Wed Aug 19 10:00:00 CDT 2009
    ("due-date-for-entry" "113546" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Aug 19 06:00:00 CDT 2009
    ("due-date-for-entry" "113535" "3 hours")
  • Agenda: all new Liferea entries> Sun Aug 9 10:00:00 CDT 2009
    ("due-date-for-entry" "113462" "3 hours")
  • Agenda: all new Liferea entries> Sat Aug 8 10:00:00 CDT 2009
    ("due-date-for-entry" "113383" "3 hours")
  • Agenda: all systems> Fri Aug 7 10:00:00 CDT 2009
    ("due-date-for-entry" "113334" "3 hours")
  • Agenda: all new Liferea entries> Fri Aug 7 10:00:00 CDT 2009
    ("due-date-for-entry" "113335" "3 hours")
  • Agenda: all new Liferea entries> Thu Jul 9 10:00:00 CDT 2009
    ("due-date-for-entry" "113273" "3 hours")
  • Agenda: all new Liferea entries> Wed Jul 8 10:00:00 CDT 2009
    ("due-date-for-entry" "113224" "3 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jul 8 06:00:00 CDT 2009
    ("due-date-for-entry" "113214" "3 hours")
  • Agenda: all new Liferea entries> Tue Jul 7 10:00:00 CDT 2009
    ("due-date-for-entry" "113178" "3 hours")
  • Agenda: all new Liferea entries> Tue Jun 16 10:00:00 CDT 2009
    ("due-date-for-entry" "113125" "3 hours")
  • Agenda: all new Liferea entries> Wed Jun 10 10:00:00 CDT 2009
    ("due-date-for-entry" "113079" "3 hours")
  • Agenda: all new Liferea entries> Mon Jun 1 10:00:00 CDT 2009
    ("due-date-for-entry" "112987" "3 hours")
  • Agenda: all systems> Fri May 29 10:00:00 CDT 2009
    ("due-date-for-entry" "112909" "3 hours")
  • Agenda: all new Liferea entries> Fri May 29 10:00:00 CDT 2009
    ("due-date-for-entry" "112910" "3 hours")
  • Agenda: all new Liferea entries> Sat May 23 10:00:00 CDT 2009
    ("due-date-for-entry" "112816" "3 hours")
  • Agenda: all new Liferea entries> Thu May 14 10:00:00 CDT 2009
    ("due-date-for-entry" "112721" "3 hours")
  • Keep tabs on all modes of use.
  • Agenda: all new Liferea entries> Sun May 10 10:00:09 CDT 2009
    ("due-date-for-entry" "112637" "3 hours")
  • KBS, all-asserted-knowledge default
  • KBS, all-term-assertions
  • Agenda: all new Liferea entries> Tue Apr 21 10:00:00 CDT 2009
    ("due-date-for-entry" "112003" "3 hours")
  • Agenda: all new Liferea entries> Sun Apr 12 10:00:00 CDT 2009
    ("due-date-for-entry" "111822" "3 hours")
  • Agenda: all new Liferea entries> Thu Apr 9 10:00:00 CDT 2009
    ("due-date-for-entry" "111717" "3 hours")
  • Agenda: all new Liferea entries> Fri Mar 27 10:00:00 CDT 2009
    ("due-date-for-entry" "111454" "3 hours")
  • Agenda: all systems> Fri Mar 27 10:00:00 CDT 2009
    ("due-date-for-entry" "111453" "3 hours")
  • Agenda: all new Liferea entries> Thu Mar 26 10:00:01 CDT 2009
    ("due-date-for-entry" "111197" "3 hours")
    ("skipped" "111197")
  • Agenda: all new Liferea entries> Tue Mar 24 10:00:00 CDT 2009
    ("due-date-for-entry" "111130" "3 hours")
    ("skipped" "111130")
  • Agenda: all new Liferea entries> Sun Mar 22 10:00:00 CDT 2009
    ("due-date-for-entry" "111037" "3 hours")
    ("skipped" "111037")
  • Agenda: all new Liferea entries> Sat Mar 21 10:00:00 CDT 2009
    ("due-date-for-entry" "110977" "3 hours")
    ("skipped" "110977")
  • Agenda: all new Liferea entries> Wed Mar 18 10:00:00 CDT 2009
    ("due-date-for-entry" "110765" "3 hours")
  • KBS, work all-asserted-knowledge >=
  • KBS, work all-asserted-knowledge >= "2009-03-18"
  • KBS, work all-asserted-knowledge > "2009-03-18"
  • Agenda: all new Liferea entries> Tue Mar 17 10:00:01 CDT 2009
    ("due-date-for-entry" "110596" "3 hours")
    ("skipped" "110596")
  • KBS, work all-asserted-knowledge
  • As part of the FRDCSA, use systemx to ensure that people are familiar with all aspects of the FRDCSA project.
  • Agenda: all new Liferea entries> Mon Mar 16 10:00:00 CDT 2009
    ("due-date-for-entry" "110324" "3 hours")
    ("skipped" "110324")
  • Transfer over all the stuff from work context to default
  • Agenda: all new Liferea entries> Fri Mar 13 10:00:00 CDT 2009
    ("due-date-for-entry" "109998" "3 hours")
    ("skipped" "109998")
  • Agenda: all systems> Fri Mar 13 10:00:00 CDT 2009
    ("due-date-for-entry" "109999" "3 hours")
  • Agenda: all new Liferea entries> Wed Mar 11 10:00:00 CDT 2009
    ("due-date-for-entry" "109800" "3 hours")
    ("skipped" "109800")
  • Develop a system for pausing/silencing all TTS agents and music when an incoming phone call arrives.
  • Agenda: all new Liferea entries> Tue Mar 10 10:00:00 CDT 2009
    ("due-date-for-entry" "109383" "3 hours")
    ("skipped" "109383")
  • Have the assignment email system email me a copy of all the assignments
  • Ball in court should show all emails since the other party has contacted
  • Create all documentation.
    ("depends" "108888" "108883")
  • Agenda: all new Liferea entries> Sat Mar 7 10:00:00 CST 2009
    ("due-date-for-entry" "108790" "3 hours")
    ("skipped" "108790")
  • Agenda: all new Liferea entries> Fri Mar 6 10:00:00 CST 2009
    ("due-date-for-entry" "108684" "3 hours")
    ("skipped" "108684")
  • Agenda: all systems> Fri Mar 6 10:00:00 CST 2009
    ("due-date-for-entry" "108683" "3 hours")
    ("skipped" "108683")
  • Agenda: all new Liferea entries> Thu Mar 5 10:00:00 CST 2009
    ("due-date-for-entry" "108061" "3 hours")
    ("skipped" "108061")
  • KBS, pse-x all-assertions
  • Agenda: all systems> Wed Mar 4 10:00:00 CST 2009
    ("due-date-for-entry" "107884" "3 hours")
    ("skipped" "107884")
  • Agenda: all new Liferea entries> Wed Mar 4 10:00:00 CST 2009
    ("due-date-for-entry" "107885" "3 hours")
    ("skipped" "107885")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Mar 4 06:00:00 CST 2009
    ("due-date-for-entry" "107857" "3 hours")
    ("skipped" "107857")
  • Locate and identify all the writings on the FRDCSA.
    ("due-date-for-entry" "107688" "7 days")
  • Agenda: all systems> Mon Mar 2 10:00:00 CST 2009
    ("due-date-for-entry" "107638" "3 hours")
    ("skipped" "107638")
  • Agenda: all new Liferea entries> Mon Mar 2 10:00:00 CST 2009
    ("due-date-for-entry" "107637" "3 hours")
    ("skipped" "107637")
  • Start tracking all online orders...
  • KBS, pse-x all-asserted-knowledge
  • Agenda: all new Liferea entries> Sun Mar 1 10:00:01 CST 2009
    ("due-date-for-entry" "107394" "3 hours")
    ("skipped" "107394")
  • Agenda: all systems> Sun Mar 1 10:00:01 CST 2009
    ("due-date-for-entry" "107392" "3 hours")
    ("skipped" "107392")
  • Make a list of all the services we are subscribed to.
  • Agenda: all systems> Sat Feb 28 10:00:00 CST 2009
    ("due-date-for-entry" "107305" "3 hours")
    ("skipped" "107305")
  • Agenda: all new Liferea entries> Sat Feb 28 10:00:00 CST 2009
    ("due-date-for-entry" "107306" "3 hours")
    ("skipped" "107306")
  • Add dependency information for all tasks in agenda queue.
    ("due-date-for-entry" "107291" "3 days")
    ("pse-has-property" "107291" "very important")
  • Start documenting all processes.
  • Make sure that the business we do business with all have good models, like perhaps diamondcard.us, etc.
  • Agenda: all new Liferea entries> Thu Feb 26 10:00:00 CST 2009
    ("due-date-for-entry" "107060" "3 hours")
    ("skipped" "107060")
  • Agenda: all systems> Thu Feb 26 10:00:00 CST 2009
    ("due-date-for-entry" "107062" "3 hours")
    ("skipped" "107062")
  • Agenda: all new Liferea entries> Wed Feb 25 10:00:00 CST 2009
    ("due-date-for-entry" "106977" "3 hours")
    ("skipped" "106977")
  • Agenda: all systems> Wed Feb 25 10:00:00 CST 2009
    ("due-date-for-entry" "106978" "3 hours")
    ("skipped" "106978")
  • Agenda: all systems> Tue Feb 24 10:00:00 CST 2009
    ("due-date-for-entry" "106921" "3 hours")
    ("skipped" "106921")
  • Agenda: all new Liferea entries> Tue Feb 24 10:00:00 CST 2009
    ("due-date-for-entry" "106922" "3 hours")
    ("skipped" "106922")
  • Review all jobs on Craigslist for suitability and start contacting people.
  • Agenda: all systems> Mon Feb 23 10:00:00 CST 2009
    ("due-date-for-entry" "106697" "3 hours")
    ("skipped" "106697")
  • Agenda: all new Liferea entries> Mon Feb 23 10:00:00 CST 2009
    ("due-date-for-entry" "106698" "3 hours")
    ("skipped" "106698")
  • Get my encryption keys all in a row.
  • do something about all the files in my home dir.
  • Agenda: all new Liferea entries> Sun Feb 22 10:00:00 CST 2009
    ("due-date-for-entry" "106590" "3 hours")
    ("skipped" "106590")
  • Agenda: all systems> Sun Feb 22 10:00:00 CST 2009
    ("due-date-for-entry" "106589" "3 hours")
    ("skipped" "106589")
  • Agenda: all systems> Sat Feb 21 10:00:00 CST 2009
    ("due-date-for-entry" "106510" "3 hours")
    ("skipped" "106510")
  • Agenda: all new Liferea entries> Sat Feb 21 10:00:00 CST 2009
    ("due-date-for-entry" "106509" "3 hours")
    ("skipped" "106509")
  • Respond to all the people from this week's trip.
    ("due-date-for-entry" "106488" "1 days")
    ("pse-has-property" "106488" "important")
  • Exhaustively determine the meaning of all manually added unilang entries.
  • Start recording IRC logs of all channels I am on.
    ("pse-has-property" "106364" "important")
  • Agenda: all systems> Wed Feb 18 10:00:00 CST 2009
    ("due-date-for-entry" "106328" "3 hours")
    ("skipped" "106328")
  • Agenda: all new Liferea entries> Wed Feb 18 10:00:00 CST 2009
    ("due-date-for-entry" "106327" "3 hours")
    ("skipped" "106327")
  • Mail Justin all his stuff.
    ("due-date-for-entry" "106262" "1 days")
    ("pse-has-property" "106262" "hard deadline")
  • Have the ability for the computer to retrieve missed phone calls from the phone, so that if I don't look at my phone all day, I don't not return calls like what just happened.
  • Write the abair.ie and grammadoir bot as part of all...
  • Fix all the strange data that's just sitting there in /s1/temp/frdcsa.org and getting all confused on other systems. do more data handling.
  • Write something that classifies unilang entries by taking all the addressed messages, stripping them of their addressed names, and then running a feature learner over the text.
  • Agenda: all systems> Sun Feb 15 10:00:00 CST 2009
    ("due-date-for-entry" "106053" "3 hours")
    ("skipped" "106053")
  • Agenda: all new Liferea entries> Sun Feb 15 10:00:00 CST 2009
    ("due-date-for-entry" "106055" "3 hours")
    ("skipped" "106055")
  • Agenda: all new Liferea entries> Sat Feb 14 10:00:00 CST 2009
    ("due-date-for-entry" "106013" "3 hours")
    ("skipped" "106013")
  • Agenda: all systems> Sat Feb 14 10:00:00 CST 2009
    ("due-date-for-entry" "106012" "3 hours")
    ("skipped" "106012")
  • Find that page of useful papers, and process them all for links, and run links through radar to find software
  • Generate an enormous resume based on all my AI tools - set a day aside to do this.
  • Make a list of all FRDCSA files we want to analyze and then run Eolas on them.
    ("due-date-for-entry" "105847" "3 days")
    ("pse-has-property" "105847" "important")
  • Agenda: all systems> Wed Feb 11 10:00:00 CST 2009
    ("due-date-for-entry" "105786" "3 hours")
    ("skipped" "105786")
  • Agenda: all new Liferea entries> Wed Feb 11 10:00:00 CST 2009
    ("due-date-for-entry" "105787" "3 hours")
    ("skipped" "105787")
  • Help Justin find a command to convert all his jpgs into a pdf.
    ("due-date-for-entry" "105778" "10 hours")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Feb 11 06:00:00 CST 2009
    ("due-date-for-entry" "105776" "3 hours")
    ("skipped" "105776")
  • To edit the book into all capitalized letters. The book is available on archive.org.
    ("due-date-for-entry" "105747" "1 days")
  • Agenda: all new Liferea entries> Mon Feb 9 10:00:00 CST 2009
    ("due-date-for-entry" "105700" "3 hours")
    ("skipped" "105700")
  • Agenda: all systems> Mon Feb 9 10:00:00 CST 2009
    ("due-date-for-entry" "105699" "3 hours")
    ("completed" "105699")
  • Need to make a glossary of all my demos and tests (demonstrations), so that I can quickly find how to do certain things.
  • Agenda: all new Liferea entries> Fri Feb 6 10:00:00 CST 2009
    ("due-date-for-entry" "105618" "3 hours")
    ("skipped" "105618")
  • Agenda: all systems> Fri Feb 6 10:00:00 CST 2009
    ("due-date-for-entry" "105616" "3 hours")
    ("skipped" "105616")
  • Agenda: all new Liferea entries> Thu Feb 5 10:00:00 CST 2009
    ("due-date-for-entry" "105568" "3 hours")
    ("skipped" "105568")
  • Agenda: all systems> Thu Feb 5 10:00:00 CST 2009
    ("due-date-for-entry" "105569" "3 hours")
    ("skipped" "105569")
  • Get the openmind-commonsense database dump, and extract all of the english sentences from it, one per line
    ("due-date-for-entry" "105504" "1 days")
    ("assigned-by" "105504" "Linas Vepstas")
  • Agenda: all new Liferea entries> Wed Feb 4 10:00:00 CST 2009
    ("due-date-for-entry" "105401" "3 hours")
    ("skipped" "105401")
  • Agenda: all systems> Wed Feb 4 10:00:00 CST 2009
    ("due-date-for-entry" "105400" "3 hours")
    ("skipped" "105400")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Feb 4 06:00:00 CST 2009
    ("due-date-for-entry" "105394" "3 hours")
    ("skipped" "105394")
  • Agenda: all new Liferea entries> Tue Feb 3 10:00:00 CST 2009
    ("due-date-for-entry" "105330" "3 hours")
    ("skipped" "105330")
  • Agenda: all systems> Tue Feb 3 10:00:00 CST 2009
    ("due-date-for-entry" "105331" "3 hours")
    ("skipped" "105331")
  • Agenda: all systems> Mon Feb 2 10:00:00 CST 2009
    ("due-date-for-entry" "105284" "3 hours")
    ("skipped" "105284")
  • Agenda: all new Liferea entries> Mon Feb 2 10:00:00 CST 2009
    ("due-date-for-entry" "105285" "3 hours")
    ("skipped" "105285")
  • Start working on getting all people signed up for the collective who are interested.
    ("due-date-for-entry" "105215" "3 days")
    ("comment" "105215" "talk to pumpingstationone people, get included in their wiork")
    ("pse-has-property" "105215" "habitual")
    ("comment" "105215" "pumping station one seems to be a good thing in this regard")
  • Agenda: all new Liferea entries> Sun Feb 1 10:00:00 CST 2009
    ("due-date-for-entry" "105185" "3 hours")
    ("skipped" "105185")
  • Agenda: all systems> Sun Feb 1 10:00:00 CST 2009
    ("due-date-for-entry" "105183" "3 hours")
    ("skipped" "105183")
  • Backup all data remotely
  • Process all emails from Peig Reid for possible records, not just the ones that we have up until this date.
  • Write software to analyze these hidden requirements that are all the time not being added to the agenda but should be.
    ("due-date-for-entry" "105055" "3 days")
  • Make a website containing all the tools for learning Irish, email the mailinglist
    ("comment" "105046" "gaelix.(net?)")
  • Setup LifeHelper or whatever, the service that takes peoples issues and resolves them. Track all kinds of issues, such as online irc channel stuff, etc.
  • Talk to peann on bearla about his verb learning program, and goibhniu about all, etc.
  • Agenda: all systems> Sun Jan 25 10:00:00 CST 2009
    ("due-date-for-entry" "104833" "3 hours")
    ("skipped" "104833")
  • Agenda: all new Liferea entries> Sun Jan 25 10:00:00 CST 2009
    ("due-date-for-entry" "104834" "3 hours")
    ("skipped" "104834")
  • Agenda: all systems> Sat Jan 24 10:00:01 CST 2009
    ("due-date-for-entry" "104807" "3 hours")
    ("skipped" "104807")
  • Agenda: all new Liferea entries> Sat Jan 24 10:00:01 CST 2009
    ("due-date-for-entry" "104806" "3 hours")
    ("skipped" "104806")
  • Agenda: all new Liferea entries> Fri Jan 23 10:00:00 CST 2009
    ("due-date-for-entry" "104779" "3 hours")
    ("skipped" "104779")
  • Agenda: all systems> Fri Jan 23 10:00:00 CST 2009
    ("due-date-for-entry" "104777" "3 hours")
    ("skipped" "104777")
  • Agenda: all systems> Thu Jan 22 10:00:00 CST 2009
    ("due-date-for-entry" "104746" "3 hours")
    ("skipped" "104746")
  • Agenda: all new Liferea entries> Thu Jan 22 10:00:00 CST 2009
    ("due-date-for-entry" "104745" "3 hours")
    ("skipped" "104745")
  • Agenda: all new Liferea entries> Wed Jan 21 10:00:00 CST 2009
    ("due-date-for-entry" "104709" "3 hours")
    ("skipped" "104709")
  • Agenda: all systems> Wed Jan 21 10:00:00 CST 2009
    ("due-date-for-entry" "104707" "3 hours")
    ("skipped" "104707")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 21 06:00:00 CST 2009
    ("due-date-for-entry" "104701" "3 hours")
    ("skipped" "104701")
  • Agenda: all systems> Tue Jan 20 10:00:00 CST 2009
    ("due-date-for-entry" "104681" "3 hours")
    ("skipped" "104681")
  • Agenda: all new Liferea entries> Tue Jan 20 10:00:00 CST 2009
    ("due-date-for-entry" "104680" "3 hours")
    ("skipped" "104680")
  • Agenda: all systems> Mon Jan 19 10:00:00 CST 2009
    ("due-date-for-entry" "104647" "3 hours")
    ("skipped" "104647")
  • Agenda: all new Liferea entries> Mon Jan 19 10:00:00 CST 2009
    ("due-date-for-entry" "104648" "3 hours")
    ("skipped" "104648")
  • Agenda: all systems> Sun Jan 18 10:00:00 CST 2009
    ("due-date-for-entry" "104616" "3 hours")
    ("skipped" "104616")
  • Agenda: all new Liferea entries> Sun Jan 18 10:00:00 CST 2009
    ("due-date-for-entry" "104615" "3 hours")
    ("skipped" "104615")
  • Agenda: all systems> Sat Jan 17 10:00:01 CST 2009
    ("due-date-for-entry" "104587" "3 hours")
    ("skipped" "104587")
  • Agenda: all new Liferea entries> Sat Jan 17 10:00:00 CST 2009
    ("due-date-for-entry" "104585" "3 hours")
    ("skipped" "104585")
  • Agenda: all systems> Fri Jan 16 10:00:00 CST 2009
    ("due-date-for-entry" "104555" "3 hours")
    ("skipped" "104555")
  • Agenda: all new Liferea entries> Fri Jan 16 10:00:00 CST 2009
    ("due-date-for-entry" "104556" "3 hours")
    ("skipped" "104556")
  • Agenda: all new Liferea entries> Thu Jan 15 10:00:00 CST 2009
    ("due-date-for-entry" "104526" "3 hours")
    ("skipped" "104526")
  • Agenda: all systems> Thu Jan 15 10:00:00 CST 2009
    ("due-date-for-entry" "104524" "3 hours")
    ("skipped" "104524")
  • Agenda: all systems> Wed Jan 14 10:00:00 CST 2009
    ("due-date-for-entry" "104486" "3 hours")
    ("skipped" "104486")
  • Agenda: all new Liferea entries> Wed Jan 14 10:00:00 CST 2009
    ("due-date-for-entry" "104487" "3 hours")
    ("skipped" "104487")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 14 06:00:00 CST 2009
    ("due-date-for-entry" "104473" "3 hours")
    ("skipped" "104473")
  • Agenda: all systems> Tue Jan 13 10:00:00 CST 2009
    ("due-date-for-entry" "104450" "3 hours")
    ("skipped" "104450")
  • Agenda: all new Liferea entries> Tue Jan 13 10:00:00 CST 2009
    ("due-date-for-entry" "104451" "3 hours")
    ("skipped" "104451")
  • Agenda: all systems> Mon Jan 12 10:00:00 CST 2009
    ("due-date-for-entry" "104422" "3 hours")
    ("skipped" "104422")
  • Agenda: all new Liferea entries> Mon Jan 12 10:00:00 CST 2009
    ("due-date-for-entry" "104424" "3 hours")
    ("skipped" "104424")
  • Agenda: all systems> Sun Jan 11 10:00:00 CST 2009
    ("due-date-for-entry" "104393" "3 hours")
    ("skipped" "104393")
  • Agenda: all new Liferea entries> Sun Jan 11 10:00:00 CST 2009
    ("due-date-for-entry" "104391" "3 hours")
    ("skipped" "104391")
  • Agenda: all new Liferea entries> Sat Jan 10 10:00:00 CST 2009
    ("due-date-for-entry" "104363" "3 hours")
    ("skipped" "104363")
  • Agenda: all systems> Sat Jan 10 10:00:00 CST 2009
    ("due-date-for-entry" "104364" "3 hours")
    ("skipped" "104364")
  • Agenda: all systems> Fri Jan 9 10:00:00 CST 2009
    ("due-date-for-entry" "104333" "3 hours")
    ("skipped" "104333")
  • Agenda: all new Liferea entries> Fri Jan 9 10:00:00 CST 2009
    ("due-date-for-entry" "104334" "3 hours")
    ("skipped" "104334")
  • Develop a library of all the e-books that we can find the text searchable and knowledge searchable.
  • Figure out a way to have the speech recognition bind to a particular window so that it can continue to do all the work in that window will open elsewhere.
  • Agenda: all new Liferea entries> Thu Jan 8 10:00:02 CST 2009
    ("due-date-for-entry" "104275" "3 hours")
    ("skipped" "104275")
  • Agenda: all systems> Thu Jan 8 10:00:01 CST 2009
    ("due-date-for-entry" "104274" "3 hours")
    ("skipped" "104274")
  • Agenda: all new Liferea entries> Wed Jan 7 10:00:01 CST 2009
    ("due-date-for-entry" "104240" "3 hours")
    ("skipped" "104240")
  • Agenda: all systems> Wed Jan 7 10:00:00 CST 2009
    ("due-date-for-entry" "104239" "3 hours")
    ("skipped" "104239")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Jan 7 06:00:00 CST 2009
  • Agenda: all systems> Tue Jan 6 10:00:00 CST 2009
    ("due-date-for-entry" "104190" "3 hours")
    ("skipped" "104190")
  • Agenda: all new Liferea entries> Tue Jan 6 10:00:02 CST 2009
    ("due-date-for-entry" "104191" "3 hours")
    ("skipped" "104191")
  • Agenda: all new Liferea entries> Mon Jan 5 10:00:00 CST 2009
    ("due-date-for-entry" "104159" "3 hours")
    ("skipped" "104159")
  • Agenda: all systems> Mon Jan 5 10:00:00 CST 2009
    ("due-date-for-entry" "104160" "3 hours")
    ("skipped" "104160")
  • Agenda: all new Liferea entries> Sun Jan 4 10:00:00 CST 2009
    ("due-date-for-entry" "104133" "3 hours")
    ("skipped" "104133")
  • Agenda: all systems> Sun Jan 4 10:00:00 CST 2009
    ("due-date-for-entry" "104131" "3 hours")
    ("skipped" "104131")
  • Agenda: all systems> Sat Jan 3 10:00:00 CST 2009
    ("due-date-for-entry" "104107" "3 hours")
    ("skipped" "104107")
  • Agenda: all new Liferea entries> Sat Jan 3 10:00:00 CST 2009
    ("due-date-for-entry" "104108" "3 hours")
    ("skipped" "104108")
  • Agenda: all new Liferea entries> Thu Jan 1 10:00:00 CST 2009
    ("due-date-for-entry" "104073" "3 hours")
    ("skipped" "104073")
  • Agenda: all systems> Thu Jan 1 10:00:00 CST 2009
    ("due-date-for-entry" "104071" "3 hours")
    ("skipped" "104071")
  • Agenda: all new Liferea entries> Wed Dec 31 10:00:00 CST 2008
    ("due-date-for-entry" "104034" "3 hours")
    ("skipped" "104034")
  • Agenda: all systems> Wed Dec 31 10:00:00 CST 2008
    ("due-date-for-entry" "104035" "3 hours")
    ("skipped" "104035")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 31 06:00:00 CST 2008
  • Agenda: all new Liferea entries> Tue Dec 30 10:00:00 CST 2008
    ("due-date-for-entry" "104006" "3 hours")
    ("skipped" "104006")
  • Agenda: all systems> Tue Dec 30 10:00:00 CST 2008
    ("due-date-for-entry" "104005" "3 hours")
    ("skipped" "104005")
  • Agenda: all systems> Mon Dec 29 10:00:01 CST 2008
    ("due-date-for-entry" "103979" "3 hours")
    ("skipped" "103979")
  • Agenda: all new Liferea entries> Mon Dec 29 10:00:01 CST 2008
    ("due-date-for-entry" "103977" "3 hours")
    ("skipped" "103977")
  • Agenda: all systems> Sun Dec 28 10:00:00 CST 2008
    ("due-date-for-entry" "103950" "3 hours")
    ("skipped" "103950")
  • Agenda: all new Liferea entries> Sun Dec 28 10:00:00 CST 2008
    ("due-date-for-entry" "103951" "3 hours")
    ("skipped" "103951")
  • Agenda: all new Liferea entries> Fri Dec 26 10:00:04 CST 2008
    ("due-date-for-entry" "103886" "3 hours")
    ("skipped" "103886")
  • Agenda: all systems> Fri Dec 26 10:00:02 CST 2008
    ("due-date-for-entry" "103885" "3 hours")
    ("skipped" "103885")
  • Agenda: all systems> Thu Dec 25 10:00:00 CST 2008
    ("due-date-for-entry" "103855" "3 hours")
    ("skipped" "103855")
  • Agenda: all new Liferea entries> Thu Dec 25 10:00:00 CST 2008
    ("due-date-for-entry" "103853" "3 hours")
    ("skipped" "103853")
  • Agenda: all new Liferea entries> Wed Dec 24 10:00:00 CST 2008
    ("due-date-for-entry" "103818" "3 hours")
    ("skipped" "103818")
  • Agenda: all systems> Wed Dec 24 10:00:00 CST 2008
    ("due-date-for-entry" "103817" "3 hours")
    ("skipped" "103817")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 24 06:00:00 CST 2008
    ("due-date-for-entry" "103811" "3 hours")
    ("skipped" "103811")
  • Agenda: all systems> Tue Dec 23 10:00:01 CST 2008
    ("due-date-for-entry" "103787" "3 hours")
    ("skipped" "103787")
  • Agenda: all new Liferea entries> Tue Dec 23 10:00:01 CST 2008
    ("due-date-for-entry" "103786" "3 hours")
    ("skipped" "103786")
  • Agenda: all new Liferea entries> Mon Dec 22 10:00:02 CST 2008
    ("due-date-for-entry" "103753" "3 hours")
    ("skipped" "103753")
  • Agenda: all systems> Mon Dec 22 10:00:00 CST 2008
    ("due-date-for-entry" "103751" "3 hours")
    ("skipped" "103751")
  • Agenda: all new Liferea entries> Sun Dec 21 10:00:01 CST 2008
    ("due-date-for-entry" "103719" "3 hours")
    ("skipped" "103719")
  • Agenda: all systems> Sun Dec 21 10:00:00 CST 2008
    ("due-date-for-entry" "103718" "3 hours")
    ("skipped" "103718")
  • Agenda: all systems> Sat Dec 20 10:00:00 CST 2008
    ("due-date-for-entry" "103693" "3 hours")
    ("skipped" "103693")
  • Agenda: all new Liferea entries> Sat Dec 20 10:00:00 CST 2008
    ("due-date-for-entry" "103694" "3 hours")
    ("skipped" "103694")
  • Agenda: all new Liferea entries> Fri Dec 19 10:00:01 CST 2008
    ("due-date-for-entry" "103652" "3 hours")
    ("skipped" "103652")
  • Agenda: all systems> Fri Dec 19 10:00:00 CST 2008
    ("due-date-for-entry" "103653" "3 hours")
    ("skipped" "103653")
  • Agenda: all systems> Thu Dec 18 10:00:02 CST 2008
    ("due-date-for-entry" "103609" "3 hours")
    ("skipped" "103609")
  • Agenda: all new Liferea entries> Thu Dec 18 10:00:00 CST 2008
    ("due-date-for-entry" "103608" "3 hours")
    ("skipped" "103608")
  • Agenda: all systems> Wed Dec 17 10:00:00 CST 2008
    ("due-date-for-entry" "103568" "3 hours")
    ("skipped" "103568")
  • Agenda: all new Liferea entries> Wed Dec 17 10:00:00 CST 2008
    ("due-date-for-entry" "103566" "3 hours")
    ("skipped" "103566")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 17 06:00:00 CST 2008
  • Agenda: all new Liferea entries> Tue Dec 16 10:00:02 CST 2008
    ("due-date-for-entry" "103524" "3 hours")
    ("skipped" "103524")
  • Agenda: all systems> Tue Dec 16 10:00:01 CST 2008
    ("due-date-for-entry" "103523" "3 hours")
    ("skipped" "103523")
  • Agenda: all systems> Mon Dec 15 10:00:00 CST 2008
    ("due-date-for-entry" "103452" "3 hours")
    ("skipped" "103452")
  • Agenda: all new Liferea entries> Mon Dec 15 10:00:00 CST 2008
    ("due-date-for-entry" "103454" "3 hours")
    ("skipped" "103454")
  • Agenda: all systems> Sun Dec 14 10:00:01 CST 2008
    ("due-date-for-entry" "103417" "3 hours")
    ("skipped" "103417")
  • Agenda: all new Liferea entries> Sun Dec 14 10:00:01 CST 2008
    ("due-date-for-entry" "103416" "3 hours")
    ("skipped" "103416")
  • Agenda: all new Liferea entries> Sat Dec 13 10:00:02 CST 2008
    ("due-date-for-entry" "103102" "3 hours")
    ("completed" "103102")
  • Agenda: all systems> Sat Dec 13 10:00:00 CST 2008
    ("due-date-for-entry" "103101" "3 hours")
    ("completed" "103101")
  • INPUT all LIBRARY RECORDS TOMORROW
    ("due-date-for-entry" "103050" "3 days")
    ("pse-has-property" "103050" "very important")
    ("hard-deadline" "103050")
    ("completed" "103050")
  • Replace all instances of if ($x) with if (defined $x) where desired to avoid the case of 0 making it false
  • Agenda: all new Liferea entries> Fri Dec 12 10:00:01 CST 2008
    ("due-date-for-entry" "103033" "3 hours")
    ("completed" "103033")
  • Agenda: all systems> Fri Dec 12 10:00:00 CST 2008
    ("due-date-for-entry" "103032" "3 hours")
    ("completed" "103032")
  • Setup wake on lan (WOL) for all our systems.
  • Enhance posi-unilang-bot, adding all the features we envision
    ("due-date-for-entry" "102954" "12 hours")
    ("pse-has-property" "102954" "very important")
  • One strategy for the movie clip program is to download all the scripts and only save the ones that actually line up
  • Agenda: all new Liferea entries> Thu Dec 11 10:00:00 CST 2008
    ("due-date-for-entry" "102686" "3 hours")
    ("completed" "102686")
  • Agenda: all systems> Thu Dec 11 10:00:00 CST 2008
    ("due-date-for-entry" "102687" "3 hours")
    ("skipped" "102687")
  • Your donation supports the MECCS/EI Project which publishes the websites The Electronic Intifada, Electronic Iraq and Electronic Lebanon. Our work is demanding all year round, so the most effective way to support EI's educational mission is with a monthly recurring donation. That way we can spend less time worrying about paying bills, and more time reporting the truth about Palestine, Iraq and the Middle East. Thank you!
  • Agenda: all systems> Wed Dec 10 10:00:02 CST 2008
    ("due-date-for-entry" "102105" "3 hours")
    ("completed" "102105")
  • Agenda: all new Liferea entries> Wed Dec 10 10:00:01 CST 2008
    ("due-date-for-entry" "102104" "3 hours")
    ("completed" "102104")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 10 06:00:00 CST 2008
    ("due-date-for-entry" "102069" "3 hours")
    ("skipped" "102069")
  • Agenda: all new Liferea entries> Tue Dec 9 10:00:01 CST 2008
    ("due-date-for-entry" "101658" "3 hours")
    ("completed" "101658")
  • Agenda: all systems> Tue Dec 9 10:00:01 CST 2008
    ("due-date-for-entry" "101657" "3 hours")
    ("completed" "101657")
  • Agenda: all systems> Mon Dec 8 10:00:00 CST 2008
    ("due-date-for-entry" "100817" "3 hours")
    ("skipped" "100817")
  • Agenda: all systems> Sun Dec 7 10:00:00 CST 2008
    ("due-date-for-entry" "100677" "3 hours")
    ("skipped" "100677")
  • Agenda: all systems> Sat Dec 6 10:00:00 CST 2008
    ("due-date-for-entry" "100667" "3 hours")
    ("skipped" "100667")
  • Agenda: all systems> Fri Dec 5 10:00:00 CST 2008
  • Agenda: all systems> Thu Dec 4 10:00:00 CST 2008
    ("due-date-for-entry" "100569" "3 hours")
    ("completed" "100569")
  • Make a list of all my blogs, with guidelines to choosing how to post. Perhaps even have a program that determines where to put it.
  • Agenda: all systems> Wed Dec 3 10:00:00 CST 2008
    ("due-date-for-entry" "100053" "3 hours")
    ("skipped" "100053")
  • Agenda: <do all-day-task> <do an all day programming task (list is in manager Todo doc)> Wed Dec 3 06:00:00 CST 2008
    ("due-date-for-entry" "99534" "3 hours")
    ("skipped" "99534")
  • KBS, default all-asserted-knowledge
  • KBS, all-asserted-knowledge
  • 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 the incorrect classifications in the sql log when corpus classifier is working.
  • 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.
  • Before releasing akahige, get free exercise information for the personal stretch manager. all systems must be checked for information sources using license management system.
  • bard should be able to find all rhyme sets in some list of items, say internal codebases, or external codebases.
  • Develop a methodology for teaching programmers about all these things. I guess that would come wrt their goals.
  • 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.
  • Programming is kind of like cooking. all resources require that you really be interested in the thing.
  • 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.
  • Read more about how Emacs was developed and the theory. Read any and all theory CS books.
  • 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.
  • 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.
  • 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.
  • 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.
  • Integrate theorem proving with planner with knowledge base, all that's really needed. OpenCyc has to be involved, obviously. OpenCyc should handle terminology.
  • I'm obviously not debugging perfectly. Nor typing perfectly for that matter. I'm generally not doing very well right now at all.
  • all my other software is cool and all, but it is a lot of work.
  • 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.
  • all should use malaga
  • 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...
  • 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.
  • What happens when unilang uses all the IDs.
  • With a laptop, all public places become my home. Write the temporal planner, get the laptop, and you are good for development.
  • clear should consult all/Termios/picform/bard for understanding writings.
  • Realized how to go about building the scheduling system. Use it to develop itself. In fact, this is generally the way we can solve all problems that are (circular references) eigenvectors. We know that by solving themselves using themselves, we will develop themselves. So for instance, to solve the scheduling problem, we start scheduling the building of the scheduling system.
  • I am not accurately recording all of my mistakes. When planning is further along, frequently schedule questions.
  • Should probably make an effort to determine all files that are modified by us, and what they are and represent (i.e. kbfs)
  • 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.
  • 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.
  • sanctus should eliminate pornography, illegally obtained media, (should work with kbfs to tag all incoming data), etc.
  • Develop terminology management system that creates giant definition of all terms we are using (Justin's thesauri). I do not need to wait for him to work on that.
  • 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.
  • 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 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.
  • Have a cross programming language method of date functions. In fact, to the maximum extent possible, all functions should be cross PL.
  • Here's my new years resolutions - no masturbation, work all the time on my software!, return to original understanding of AI augmented with what I know now and live that way however possible
  • Telephone, if at all should be within hands reach. Everything should be.
  • Insert all sorts of hooks for manager/pse to know the current working context.
  • 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.
  • 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.
  • Write the autistic survival guide by throwing together all available information resources, as pruned by my programs.
  • Be sure to read all of Justin's writings sooner or later. Once we have a good clear KB, that knows what we are reading.
  • all should have same functionality for human languages, to remember conventions.
  • Roger, all clear, planetalk (for all).
  • Did we get anything working today at all? Not really!
  • The planning system should actually send messages over unilang and all the programming be handled in Perl.
  • Index frustrating searches. Store all previous searches in seeker.
  • 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 agents should use sinless!
  • clear should compute an enormous meta-reading model consisting of all readable text on the drive.
  • 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).
  • Replace all (shift,shift,...,shift) with @_;
  • 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.
  • 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.
  • I could live them all set, so that, in case of an emergency, no problem.
  • Seems to me that it would not be that hard to adapt the class scheduling system to handle all events.
  • Print out a giant diagram that illustrates all the relationships in the correct notations between all the systems.
  • 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.
  • Make this from the radar or predator script get dependencies run on all the boss codebases.
  • 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)
  • I can replace all instances of Jason Sayne in my system with my name if need be.
  • Add copyright notices to all files
  • 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.
  • Could build it in the basement, if all else fails.
  • Lastly, you should have a basic model of how long you are good for at all times.
  • 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.
  • 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.
  • 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.
  • Posithons should have a theme, for instance, "Document all code!"
  • Once installed RSR, can prevent its removal by monitoring all commands.
  • 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.
  • all you have to do is scrape out the members of certain interests or whatever, like "cslounge"
  • Of course, the key to getting all the women is to meet the aliens, charter a UFO, and abduct them.
  • 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.
  • all inventory should be stored in a normal form, a symmetric, balanced, designed form.
  • OpenCyc, (all-term-assertions #$toThwartInEvent-SitType)
  • WRT packaging software: "Users can't, and can't be expected to, sort this all out."
  • OpenCyc, (all-instances #$NorthernIrishPerson)
  • Dad is here all the time.
  • Make static compilations of all software as well as packages.
  • all I really need to do is stock up the truck and drive out west!
  • Attention all long-term thinkers, caring indviduals, etc...
  • With all my systems, need to rewrite descriptions to be more "symbiotic"
  • 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
  • Tell the truth all the time.
  • Need a comprehensive inventory of all good system capabilities.
  • Convert existing pgourmet application all into SQL backend.
  • Write general purpose FRDCSA project scheduler, to schedule and coordinate the actions of all our various spiders.
  • Need to set up regression tests for all systems.
  • Should all web traffic flow through TOR
  • 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.
  • 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.
  • Should have a status viewer that displays progress for all our systems.
  • all goals should require a parent.
  • 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
  • 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.
  • I am interested in learning more about all the latest trends with Windows development.
  • 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.
  • Be sure to find all instances of pse.log
  • (all other systems, like pse, then reference the SQL table via primary key)
  • 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.
  • Find out how to have Docbook generate only 1 page instead of all those pages.
  • 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.
  • 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.
  • Pronunciation dictionaries for all foreign languagges.
  • Roger, all clear, planetalk (for all).
  • Maybe we can determine all instances of unilang debugging and not record those or something.
  • What happens when unilang uses all the IDs.
  • Now all we have to do is have it give the results of the autoclassification after we enter it.
  • Not all agents should start at once, agents should only start when necessary or getting close to necessary.
  • 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.
  • Create a webpage about all my researcher friends.
  • Then we can have people see all the complex notes I take.
  • 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.
  • bard should be able to find all rhyme sets in some list of items, say internal codebases, or external codebases.
  • You don't just know alot of math, you know all the math.
  • clear should consult all/Termios/picform/bard for understanding writings.
  • Pass arguments to all applications instructing them to announce their names when printing.
  • When one person sins we all sin.
  • Get a system together for storing addresses and stuff of all my friends.
  • I'd really like it if God had a backup of all the programs I've written for later use.
  • Why do they get mad at us for being sexual when that's all the world shoves down our throats?
  • 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.
  • Convert all programs over to proper, cross platform tempfile creation
  • 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.
  • The planning system should actually send messages over unilang and all the programming be handled in Perl.
  • clear should compute an enormous meta-reading model consisting of all readable text on the drive.
  • Come up with comparison matrices for all software.
  • all should use malaga
  • Think holistically of all data sources and how they affect security through the classification system.
  • 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.
  • Should breakdown all of our services into a selection process where you can select which features you want enabled.
  • all agents should use sinless!
  • One way to ensure accuracy of repotring ofor sinless is to have many minor sins, and to force the user to record all sins.
  • OpenCyc, (all-term-assertions #$roommates)
  • E.g. a system that does all of this already?
  • Schedule all backups etc for when I am sleeping!
  • That way, you would never have to prepare your food, as it is all pre-prepared.
  • 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)
  • Delete all these silly things.
  • It could all be built out of styrofoam.
  • OpenCyc, (all-term-assertions "Clover")
  • Convert all of our systems.scripts into an object model?
  • OpenCyc, (all-term-assertions #Collecting)
  • OpenCyc, (all-term-assertions #$Researcher)
  • OpenCyc, (all-term-assertions #$Clover)
  • OpenCyc, (all-term-assertions #$few)
  • OpenCyc, (all-term-assertions #few)
  • We are seeking for some kind of best fit from all possible subphrases to cycterms.
  • do entropic minimization of all the programs I have written to develop a shortcut language that implements them.
  • Also look into refactoring all of the codebases.
  • I'm getting all the systems done but not necessarily as I would like.
  • Could eventually do all speech through a speech recognition interface.
  • In the same way that we react to our environment, with all its information, we ought to also react to the information environment.
  • 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.
  • Add a refactoring for converting all function arguments to hashes.
  • all code should reference appropriate documentation in digilib.
  • Make sure all of my tools are accessible and self documenting.
  • Figure out some wa to use all the water in my jug.
  • Don't just read the bible, read all the sacred texts.
  • Make list of all things to do, etc.
  • Refactor all .emacs stuff.
  • OpenCyc, (all-term-assertions #$InsultingSomeone)
  • Find all the computer clubs, etc, in Naperville, a good place to start.
  • Keep a spare all boxed up.,
  • It would be great if someone could just pay me to hack on Open Source software all day.
  • Gather together all rules about svre chair.
  • OpenCyc, (all-term-assertions #$Poem-CW)
  • OpenCyc, (all-isa #$Poem-CW)
  • OpenCyc, (all-term-assertions $Poem-CW)
  • bard doesn't handle all morphology.
  • OpenCyc, (all-isa $Poem-CW)
  • How stupid is it that while I had all the students, I didn't bother to learn from them, only insult them.
  • In building the classifier, we could replace the individual system names with thissystem, that way it wouldn't aid in selection at all
  • Should update all my data sources.
  • Create a gnutella filter that gets rid of all that stupid sex stuff
  • Implement search semantic dimension: i.e. searches a file for all related terms (for use in Emacs)
  • 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.
  • Create a concept index for our website that contains links to all concepts, for instance Cyc, EBNF, etc.
  • Process all cso items into long term searches.
  • As part of code-monkey, write a script that lists all the significant functions in my systems and helps me to document them
  • Systematically study the properties of various systems, like logrotate -- all systems installed on this computer, and use them to maximimum advantage for these projects.
  • Create apartment finding software (helps do all the work)
  • 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.
  • parse research papers to obtain all the different fields.
  • 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.
  • Adapt the all example to work with web page, where the definition is given on mouse over.
  • FRDCSA: It is our job to solve all the world's technical problems.
  • all should use: Net::Dict
  • Rewrite perl programs, replacing all the facy perl stuff with the actual meaning behind the code...
  • It will record all work done on projects using ttyrec, bash history mechanism, etc.
  • 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 the while being rooted in solid reality
  • bard should do all the anagrams that make sense.
  • For setanta, we need to sit down and identify all remote manipulation stuff
  • all my systems need to be redesigned to more intelligent.
  • 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.
  • Have a form that shows all the lately accomplished things.
  • radar should log all queries.
  • Get all of this stuff working from the van.
  • 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.
  • Use all to build a taxonomy from the text.
  • Log all my hours soon.
  • study should use table of contents as the source for all extracted subject areas.
  • Have all mail for setanta forwarded to the machine setanta is on?
  • 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.
  • all - Note dictionary does not get cuckoos, should apply a stemmer in that case...
  • setanta - all network changes should be announced to those affected several business days before the outages occur.
  • 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.
  • 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.
  • all those that would work with me are dead and gone.
  • Of all the good ideas.
  • Restart on all my projects!
  • Make a movie of all these ideas.
  • Roll packages for all my work.
  • So that it is all centralized and as simple as upgrading a package, and if changes are made on a remote server, edit them.
  • 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.
  • Should be naturesque, and have poetry and singing recitals, along with a natural social arrangement with all the elements of culture.
  • 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.
  • Throw a party and have all the elements as you can recognize should be there.
  • setanta - Write a program and hook it to UPS smtp system to shutdown all non-critical services in the event of a power outage.
  • Let us find what all religions have in common and publish a document about the common values of all religions.
  • all can have facilities for showing pronunciations of words we have yet to encounter.
  • all - there must be languages upon languages.
  • He's probably offended that I'm pushing Gaelic music before listening to his all the way.
  • o Humor: Secure all animals in the barn!
  • Is satisfaction the root of all evil?
  • o reasonbase should add links to all instances, for cross linking.
  • Let us scrub chess, maybe even gaelic history, let us scrub all forms of lust, let us pursue "looking toward the light".
  • Locate all files linking into from bin releases and make them legit.
  • Locate and remove all instances of passwords in scripts.
  • 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.
  • Before going to bed, ensure that laptop is nearby with all the different items I need.
  • 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.
  • need a program to list what all the other ones do
  • Read all the sacred texts.
  • Redo all passwords that use insecure passwords.
  • Fix all the contact information in fweb and do a rebuild.
  • all the different web pages open, terminals open, etc.
  • all should check into some of those databases for text.
  • all does in fact contain spoken support and therefore that's where it belongs.
  • Leaving off - Need to complete the bridge between all::TTS::English and Festival as well as all::TTS::Irish.
  • 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.
  • all: /var/lib/myfrdcsa/codebases/external/sims-20061126
  • all: http://visl.sdu.dk/
  • Write thank you letters to all authors of systems.
  • Pile up all my questions from this system and send them to maintainers.
  • Remove all files called predator
  • Suggest everyone start using movielens so that we get movies that we all want to see, on all of our wishlists.
  • Be sure to know how to operate all the different aspects of my systems.
  • 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.
  • Get Everybody's email all into an address book on FRDCSA or something.
  • Setup an ldap server and add all information to that.
  • 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.
  • Make a phone list of all the contacts I have.
  • Start trying out all software and declare flags for or against software.
  • note that I'm not sure all unilang.xml messages made it into the system.
  • Agenda: all systems> Mon Dec 1 10:00:00 CST 2008
    ("due-date-for-entry" "89137" "3 hours")
    ("completed" "89137")
  • For an "agenda -u", only set it to print the output if anything has changed. not all completions, etc, affect the schedule.
  • I bet unilang isn't dropping all it's connections. Need to have it send out "ping" messages every now and then.
  • do an inner-annotator agreement test on the FRDCSA Cleanse project, make sure all interested parties are signed up to the FRDCSA mailinglist, and email them with a request to join the release party. Put the date on a calendar, maybe the posi calendar.
    ("pse-has-property" "83499" "very important")
  • When I have some free time, write a system that spiders Match.com or EHarmony. or whatever, and scrapes the profiles of all the women, then processes them for mistakes and writing level, values, etc, and finally outputs the top listings.
  • Figure out why "./QADepParsing -train -n my-data/qa_pairs.trec8_9.txt -v my-data/relation_vocabulary_file -t my-data/relation_sim_table" yields "unknown function link-file\ndb all.hdr\nSegmentation fault"
  • Interesting: I just have proven that you can listen to stuff while sleeping. I set up my computer to read several texts to me, incidentally, all the contents of http://www.sacred-texts.com/neu/celt/lfic/index.htm. It starts off secular, and I think I fell asleep. Well, the dreams that I remember were very religious, with my sisters being suddenly very devout Christians. I remember in the dream being in lecture halls as they read us various texts. In looking at the title now, I remember them reading the text "The baptism of Angus" while I was sleeping, and soon after, me telling the lecturer that I had already heard this story. That's my "proof", more anecdotal but still enough to convince me that you can listen to stuff in your sleep.
  • Interesting, I just have proven that you can listen to stuff while sleeping. I set up my computer to read several texts to me, incidentally, all the contents of http://www.sacred-texts.com/neu/celt/lfic/index.htm. It starts off secular, and I think I fell asleep. Well, the dreams that I remember were very religious, with my sisters being suddenly very devout Christians. I remember in the dream being in lecture halls as they read us various texts. In looking at the title now, I remember them reading the text "The baptism of Angus" while I was sleeping, and soon after, me telling the lecturer that I had already heard this story. That's my "proof", more anecdotal but still enough to convince me that you can listen to stuff in your sleep.
  • Add stuff to log-analysis that makes it subsetselect all different log sequences to choose from
  • At all times keep well fed - so that you can work...
  • Fix problem that prevents playing all clear queued links
    ("completed" "77973")
  • OpenCyc, (all-isa #$Researcher)
  • find out from nixternal all about semantic desktop
  • Write a system for updating all the FRDCSA git repos on several machines... using Expect and a terminal or something.
  • Fix problems with posi-log-bot, which seems to have lost all our messages for over 2 months.
    ("completed" "74534")
  • Fix the problems with clear-queue-all-links
  • Archive all early FRDCSA pages with dates and times in case of a new for prior art.
  • Fix all improper uses of temp files, like /tmp/totext.txt, which just caused some problems with the enormous wiki job.
  • create a hermetic seal over what can be added to the frdcsa, and have all files that are added have proven license information associated with them
  • Update all repos
  • all http://www.ilc.cnr.it/ne-repository/index.php?option=com_frontpage&Itemid=1
  • Create a search engine for all academic ftp sites, so that we can easily locate files, etc.
  • Fix problem with all passwords being removed from web browser
  • clean up my home directories on all servers
  • clean up home directories on all servers
  • Make a list of all mailinglists I am subscribed to.
  • Put together all the links about O'Doherty and send to "O'Brien, Debbie"
    ("completed" "69839")
  • when all of them are done, you can go back into the stack before that
  • Make sure that after a certain date, all user entered comments are classified
  • Finish the due-date calculator and have it do reminders and all kinds of neat things.
  • My systems are useful after all.
  • Create a central directory for all feedback received. Note, some of it may be private.
    ("comment" "68024" "regarding POSI")
  • Write up a document that details all the questions I am having about pse, freekbs, etc
    ("completed" "67915")
  • Note my frdcsa packages are all for i386, need to setup for amd65
  • Make sure to analyze all feedback on posi.
    ("same-as" "68367" "67085")
  • Put all Perl modules in version control.
    ("completed" "66839")
  • Create a new agent that listens to all of our goals, etc.?
  • Add all sorts of cool things like named-entity-at-point to freekbs
  • We need to implement a better system, obviously we instructed something that wiped out all the data we had.
  • Write a unilang command to deregister all temp-agents
  • Setup tests to make sure freekbs can handle all sorts of characters.
  • Interrelate all the major goals from the system.
    ("pse-has-property" "62059" "habitual")
  • KBS, all-asserted-knowledge depends
  • KBS, all-asserted-knowledge 59191
  • do a thorough review of all the people at Barcamp Chicago and see who wants to collaborate.
  • Reorganize all my writings.
  • Create a log of all asserted knowledge (and unasserted knowledge) for analysis.
  • Write my all language learner script, for espanol.
  • One of my projects is to make OGG files of all the free Irish midis out there and put them in an archive. I can use ampache for that.
    ("completed" "58814")
  • Extend my Irish "board game" with all the laws from the legal tracts.
    ("comment" "57628" "I wrote the author, Fergus Kelly")
  • System for making sure we've gotten responses should also check whether we've responded to others. Part of audience after all.
  • Sayer: the problem is similar to the unilang classification problem. of course I knew this. however, for instance, like the problem of multiple dispatch, could be solved by training a learner. like the problem of longest token for the perl 6 parser. all related. The problem of figuring out what function to call based on the type of inputs.
  • Maybe I should set quac up to record all answers it makes. Use learner?
  • Replace all bogus file temp efforts with File::Temp, which works pretty well.
  • Make sure we get all the right people involved in our projects.
  • Create a system for extracting all references to something out of the unilang logs, etc. For instance in 53757 CW means Computing Workshop.
  • In addition to writing thank you letters to all authors, send them money based on our calculated utility of their software and perhaps an adjustment for need.
  • find-or-create tool to show all of the file conflicts that would happen if you force installed a particular set of debian packages.
    ("comment" "52501" "the --no-act doesn't tell you enough")
  • Create a central perl module for all sorts of util like Save, etc. Maybe perllib::Util?
  • After all this time I still do not have a good web page caching agent.
    ("completed" "51167")
    ("comment" "51167" "Actually there is HTTP::Cache::Transparent")
  • I'd like to see all calls of ProcessFormalism.
  • Need to refresh on all my commands every now and then.
  • Note how all the time I am popping off to subtasks. Maybe should keep a deliberate stack of problems, so that when I accomplish one, I can easily revert to the thing that it depended on. Should have a system for find-or-creating tasks.
  • Develop a list of all major projects that people can work on, such as license detection, etc.
  • Write a program that looks at all my writings and determines what I am interested in, and then searches all the sites like yahoo groups, dmoz, irc channels, etc. for places and resources of interest.
    ("due-date-for-entry" "41572" "Important")
  • Write software to locate all my todo lists and process them into one base.
    ("comment" "41150" "There is something similar to this in PSE, a collection of several todo lists, but it is old.")
  • Respond to all those emails.
  • OpenCyc, (all-term-assertions #$Sound)
  • Make a list of all the free software we wish to have.
  • When I get into Chicago, hang out with all the linux people.
  • Need to write software that given a particular purpose, downloads all systems for comparison.
  • Develop file classifier, that is a system that looks at all the files and determines where new ones belong.
  • Write software to find all references to Tara in the Irish Annals.
  • Rename all frdcsa perl modules from X -> FRDCSA::X, make modules and upload to CPAN
  • Start making source packages for all icodebases.
  • Once you have all the items in your inventory properly, then you can lookup their manuals in an integrated fashion.
  • Make an index of all known packaging tools/ formats.
  • I once recorded an entry about how all should see how certain syntactic/phonetic features of words relate to their meaning. Well that's a field called: Phonosemantics
  • Write a program which searches all the sources in turn.
  • Centralize all the papers I've written about stuff like unilang, etc.
  • Determine the proper licenses for all packaged software and remove those systems from the archive which are not properly licensed.
  • Backup all databases, as well as home directory.
  • Keep a log of all forums I am party to.
  • Make an index of all my postings so I can easily navigate back to them to check on responses.
  • Generate software bundles, that is, things like packages, but that are all in one, so that they can run with no additional software installed.
  • Now get the learn system working to record all this information.
  • Write all those people who I responded positively, see if they are still interested.
  • Make a list of all the online people we have contacted, like linas, etc.
    ("comment" "20426" "need to update this")
  • Make a password manager that assists with changing all passwords, remembers when to do it, and assists with executijng it.
  • Write a proxy which strips all the facist links out and replaces them with better ones.
  • Get back to all who emailed me. Find some system of marking email for later reference.
  • gourmet: it would be better if all packaging had an IPv6 number and you could just send an XML query to it asking what it contains :)
  • This is a bit unrelated to what you guys are talking about, but I've been thinking about something for deb files. LLVM allows you to compile code to an intermediate, platform neutral format. So it would be very cool if debs could use those. Such debs would work for all platforms; the moment the deb is installed, it would invoke LLVM to compile the platform neutral object files to machine code
  • Fix update links to detect all perl modules installed, using the code from task1
  • Dump a list of all installed packages as part of my configurator... where does configurator belong.
  • Sit down and write out a detailed manual for all systems.
  • Start getting integrated with all the different communities.
  • Write various groups seeking money to index all existing research software.
  • Send out messages to the maintainers of packages saying that I will package their software for a fixed sum for all different major distributions.
  • Correct all instances of = $VAR1
  • Go through all systems and clean them out.
  • Create an execution wrapper that you call like this: wrapper systemname command and it prints out in front of all stdout from that command the following: "systemname: blahblahblah"
  • Update all cso data and add new sources from FLOSSMOLE
  • Update all the FRDCSA emacs to use requires instead of actually loading stuff.
  • Make the unilang code autovivify all messages by creating a function and replacing the corresponding parts with a function call, every time any message is sent, not just through "," syntax
  • Increase my dictionary to include all the terms I regularly use.
  • Note that not all stuff is in capability-map.pl that's on the website. Great disaster really.
  • Use espeak for all
  • 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.
    ("completed" "9355")
  • all et al should use Alvis::TermTagger and NLPPlatform.
  • Show Mom all word based games.
  • Here are a couple of ideas regarding using freekbs as a backend for lots of other systems. Annotations should be stored in the DB regarding all aspects of entries, even as they are created. There should be predicates such as (completeable-p ?ENTRY) and rules like
  • freekbs needs a log of all assertions and times, etc.
  • Record all schemas. do a regular backup to DVD on systems.
  • Periodically unilang should see if all sockets are still open and if not, close them and remove the agent from the DB
  • Periodically, unilang should see if all sockets are still open and if not, close them and remove the agent from the DB
  • 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.
  • Want to inform Al about all of this so that he can help guide us
  • Have a word play system, one that knows all the rules for word play.
  • At some point we're going to have to go and make profiles for all the people in machiavelli. Note that it is possible to search for all instances of these names, and common nicknames/misspellings, for a collocation.
  • 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.
  • Could have Bill's TV showing problemspace.el, with a feed of all problems being solved.
  • 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.
  • "To all the seven kingdoms thou didst go
  • 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.
  • Maybe I should buy Jim's van after all?
  • 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.
  • You cannot use me as a scapegoat for all the flaws characteristic of the Dougherty's. I'm not going to let you get away with it.
  • Mary said that I should compare myself to Mike, which I don't think is fair at all.
  • 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.
  • 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
  • Your comments on EGO made me consider this and my research appears to have found a scientific relation between my work on AI and the human EGO. EGO stands for the conscious self. My goal with AI is to improve the conditions of our lives, and possibly all human life, by solving problems that affect us. By using computer intelligence to augment our own, we have a way to solve problems that can be copied instantly ad infinitum. In mathematics, we have formalized two important predicates - the truth predicate (Tarski) and the proof predicate (Goedel) in this century. These accomplishments in mathematical logic have thus reduced the conditions of knowledge to satisfy the holy grail condition of scientific scrutiny - an operationalist scientific basis. This basis implicitly assumes a consciousness as an agent in the event. That consciousness is the EGO.
  • 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.
    ("depends" "3689" "45777")
    ("comment" "3689" "Use fossology for this.")
  • At all times the entire conformant plan should exist.
  • Notice that we all suffer by bad persuasion tactics.
  • Of all the stupid prey animals in the world - from the mouse or frog that is gobbled up by the snake, to the deer or wilderbeast that is eaten by the alligator or lion, there is no create more stupid than the christian - who has been made on the basis of complete logical nonsense delivered with perfect technique - has been scammed into the "really really good" sounding "eternal life". Why have this life when you can have a better one? Ancient scam, with no end of suckers.
  • (Gawking at Jana in my dreams of all things)
    ("critic-unilang-classification" "3558" "personal")
  • 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?
  • Compile a list of all the dirt Justin has on me and prepare responses.
  • Tell Mike that I want to make lunches for all of the days in advance so I don't have to pay lots of money to eat.
  • 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)
  • Should remove all political content from our website so that we don't ruin our chances by being politically committed.
  • We could send out emails to all the people on the Cyc discussion list who look to be somewhat Amatuer or not. Perhaps we could get them officially to be CycL groups. This would be useful in terms of getting their attention - appeal to authority. We could ask them to send back either their address or a rated list of major cities they would be willing to drive to in order to meet - and we will use this information to automatically construct a list of meeting spots that requires the least driving for everyone. We would then meet at a free venue in that city for a period of one or two days.
  • 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.
  • Dad's statement at the end about how we were going to get rolling on this is perfectly indicative of his plan - all along. He wants to make me feel as though I've made a commitment. In other words I opened a new front. I do best when I reduce complexity so this was an error - now I have anxiety about it. And that is all fine and well. That may be enough to do me in. Mike is right I have to write that software and yet I am pressured by all these factors. The truth is isolation but even that is complex. I should none-the-less ask Mary to pick up the drums and perhaps drive them to Justin's. But not after we pick up a dolly.
  • 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.
  • Dreamt that Al was in town at a store of his. And there were two ladies singing in the store at closing time. We briefly discussed a few things. Al really showed his intelligence in this dream executing all of his tasks perfectly. I told him over IM in the store that I had ported shops. His brother could use it. I said it didn't have a gui.
  • Lately I'm feeling a little fatigued with all this. And its not because things are going right, but because they are going wrong. all the bullshit is affecting me. Especially Jana's work style. So I very much don't want to work for CASOS anymore.
  • 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.
  • Just had a cool idea - come up with a system that you say - I need to go to the paycheck office, and spend from 5-10 minutes, then go to the bank, where I'll probably spend 20, then come home, and it computes all the busroutes for all time possibilities - along with certain safety checks, like even if I'm an hour, I can still come home.
  • 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.
  • should be able to simply tell manager what time you need to be at work, and using verber, etc, manager schedules the bus, and the wake up time, then wakes you up, does all morning activities, informs you of time critical events (busride, etc), and drives you into work. This is one of the best examples of weak AI growing I've done yet. That's non-trivial, but major issues remain.
  • 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
  • I can do an all night study/sleep thing, actually. Best to go home.
  • all work and no play makes Jack rich as fuck.
  • RSR today too many things to mention - slept until 3:00 pm, went of and got food, slow to achieve all tasks, way too much recreation. However, good things are that made some progress after in depth discussion with Mike. Goal is to make Jeff not realize I knew so much about C++, time is dwindling. Very hot in here, no comfortable clothes, etc.
  • Here is my dream. I was in the steam tunnels or something, and John Sleezer or someone was telling me bad things about IMSA, like how their chess club got demoted. And, its pretty stupid but, some guy was showing me a game called L2, it had two rowes and maybe 18 columns, and you would put two sets of coins (I guess cause we didn't have the right pieces), along, and I still wasn't sure about the rules. I must have fallen asleep though, because everyone left. I suppose to ambush me. Then a bunch of people came to beat me up, and I had my left leg turned all the way to the right (must have been sleeping funny). I think he had a knife. That was the dream.
  • 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.
  • jik -` iNTERESTING IDEAS ON gO. WAS DREAMING OF PLAYING gO. tHERE WERE MANY FREE TEXST ON GO WHICH WE WERE TO USE. tHAT'S all i REALLY REMEMBER.
  • 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)
  • First of all, here are some ways a fly doesn't invent AI. Buzzing around larger beings annoyingly.
  • 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.
  • Maybe all I need is a system for purifying rainwater, a camp axe, rope, and I can build the rest. I will probably want a gun to kill wildlife that threatens me. Again, all of these would be good, lightweight items. Go with solar power too, and all I need is a battery, and to be honest, I could even use a system to pump water up to a higher elevation and use that to run a generator. Ram pumps. I could use the water as a transport, by having a canoe. Or I could build a secret underwater system for river transport. That would be better. It could be motorized as well, using an electric battery bank for near silent operation. I could don a wet suit. So really, I need to work on the temperature controlled bodysuit.
  • 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.
  • More on lessons learned here, we finally went but the lady in front of us was really slow so we were late getting to the movie. However we did see it. Seeing the movie was painful for me. It is interesting to learn how the group interacts, Peter did it for the sake of the group, we all kind of did it. This forced me to go see it. I didn't want to, and although entertaining, it was just more mind control.
  • 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.
  • A tactic that will be useful when meeting other people is to not tell them about our project at all. Or to have a pitchman for our project, and watch on the sidelines. Have the mark, and the helper, whatever he is called. This has to work. This will be a way to get commitments out of people.
  • 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.
  • And we need to drop the association with AI, since this by expectation makes us fail. We should remove all mention and create a dual set of books, on in which we just use notions from free and open source software.
  • 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.
  • Note that this notion of not talking at all within earshot applies to any activity measurable by Justin.
  • 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.
  • Note that go is very useful indeed, since, in some sense, ideas are a territory and they need to be connected in order to make inferences, so the attacking of certain ideas breaks inferences. Therefore, all you have to do is put a white piece on a square in order to break the connection.
  • 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.
  • Also, here is some speculation on questions. I observe that Justin takes up a lot of my time. A lot. So we want to give him more autonomy. My thinking processes are slowly becoming shot. The weight of the world. So I need to come up with a schedule. Also a nagging system. But I don't want to get stuck at Justin's with nothing to do or to watch a movie. I think that I should get in contact with Stallman, and get things lined up that way. Then I should accept a move home as a pretense for leaving. I move home, but I have another job lined up. After I move home, I job search some. Then, when gets ineffective, I move to the new job, with parental approval. Of course, all along, I've had a third job waiting for me to arrive.
  • 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.
  • Design tests for people - we need real time simulator for group involvement, and record of who passed which tests. Mainly however, we need people to work on software. We have to avoid laywers as well. It must all be conducted rather clandestinely. One thing we can do that will aid the cause is the training of people. We have to keep Justin out of the loop and functioning well. He is mentally ill and will misperceive many things and ultimately hurt us. His ethics are right on the money of course, and we shall not deviate from those. We must be against the killing of beings of any kind.
  • 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.
  • Develop a planning domain for manager to be able to do certain things, like, obviously, for instance, when I go to sleep, start all computation intensive processes on my personal machine.
  • 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.
  • record all speech - write a module for this. Thomas has said that one can store, for a fixed price all the speech for the rest of their life.
  • 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.
  • We need to add to our daily routine the following: when we go to retrieve all of the supplies needed for during the day.
  • In my hour of need I received no sympathy from any of you towards my AI. Rather than the accomplishment it is, you chose to view it as a failure on my part to act sociably. You fucking bastards care so much about saving face that all over the world people get wiped out. FOAD.
  • 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.
    ("unilang-message-classify" "784" "poem")
  • Interesting observation - just now I accidentally engaged in bad behaviour - I chatted for far too long. I really need to do a variety of things, esp, laundry, get food, and so on. The stupid thing is it is always just before the deadline that I come up with the plan. So for instance, it's too late to take the bus now to do laundry. I'll have to wait till morning. So all of this is known in advance. How do I win. Note that Jana didn't seem happy to see me walk into the information retrieval course. Anyways, we have to log who we ran into.
  • If my recommender system works as well on recipes as it does on pornography I think we're all in for a treat.
  • 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)
  • "With DotGNU and Mono, you will be able to use C# if you wish, without surrendering your freedom to study, share, change and generally control all the software that you use," Free Software Foundation President Richard Stallman said in a statement Monday.
  • 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.)
  • (all of the sleep-learning stuff belongs with manager)
  • (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))
  • Note that all this capability will be destroyed in a little time when school resumes. To counter this, we must have everything planned out for this. We must create a new project, if we haven't already, that manages communication with my boss and also finish the event-system with course auditing information for John Parker, Peter Walker, and so on. Not to mention, that we should really get OpenCyc operational so we can start logging things semantically, like who works on what. New project Paper Authoring System.
    ("critic-unilang-classification" "10" "personal")
  • 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?
  • System to automatically manage all options for all of FRDCSA to standardize them.
  • Need to keep track of all the keybindings we are setting.
  • I should study the mono framework, and study all these other application topics. Add topical support to clairvoyance, so that it know what topics I am studying.
  • Clairvoyance should automatically compute prerequisite material, by finding sources with definitions of all terms used and creating dependency lists. Also, automated classification based on the users ratings should apply.
  • This way we could read all these sites simultaneously, and get breaking news in this fashion as well. Speaking of Jaime Carbonell's text zooming, etc.
  • Crack a joke to mstevens - I trust you've finished all your readings about my project?
  • Need to send letter to Al with testimony that all I did for two years was clean out that basement according to plans to run a business out of it.
  • So today was pretty rough, having worked all night. I found some good references on nutrition from the nuclear survival manual, which should be integrated into that. Perhaps Justin wants to take up that part of the project. What Justin? Ok, obviously I am way tired here. Let's see if I can't finally get any real work done.
  • Have CASOS stuff done - should take no time at all.
  • I think I can ask Mike Stevens about high quality microphones. In addition to an OCR server, we ought to have a multispeaker speech recognition system that we can use to recongitize contents/speakers of all conversations. As a CMU student, I should have access to this. And it occurred to me that mstevens has access to my system, so naturally, he would attempt to gather as much interesting stuff about it as possible. Therefore, I ought to leave it unplugged by default. I also don't have a way to see if it is transfering any files, and he could have transfered some.
  • In thinking it over, it is a big leap to have been able to see past the seed AI - to see that one needs all this software. Really, it is just part of an inference. I am certainly getting really dumb these days. I need to design the svre. Perhaps the lounge donation was a mistake. Anyhow, it was a leap, and why? Because of Vivian, and because of how motivated I was/am to solve these problems.
  • Perfect example of K-max: (all-instances #$MajorMode)
  • classified has to have a certain feature: (version control), but yes, here it is, we want to be able to manage all locations of certain bits of information, with infinity/unknown being the unbounded thing. For instance, consider a bank account, you want to be able to know where all copies of your bank account information are, right? And then, if this system gets compromised, it should not however reveal this to anyone, therefore the system ought to be classified personal secret or something.
  • For each open source or otherwise system out there, we must make a specific effort to compare its functionality with our systems having simliar functionality, and determine which is better over all, and which features each is lacking compared to the other, etc.
  • Another notable thing was that Jana got all offended (I'm too stupid to understand this) - when I explained about the isomorphism of proofs and that if not, then not.
  • Trying to recruit Jana to work with me was a notable failure. She said "how old are you" - so as to put thing into context. "Human's are irrational". I can't stand all this BS, actually, that is a mostly statement - but she was using it to say that the human process is irrational. I say, what does that have to do with whether or not computers can solve subproblems. This whole notion about computers not being able to solve problems is the height of irony. Now, to get on with it, I need to hide from this kind of stuff. However, they make it hard for chickens to hide in the food pen of earth. Well one thing that I hope is not too late is to get castrated. Another thing, I talked with William Cohen, that seemed to go well.
  • Debrief on all significant social interaction during the day to build a model.
  • Should find some method of testing all Emacs customizations - finding compatability.
  • The division of capitalism actually does us well as there are not going to be such all-encompassing efforts as mine, are there?
  • Secondly, we want to have all the materials planned out for the meeting coming up soon.
  • We'll also want to document all of our perl modules.
  • My main priority should be to get a system together for logging how much time I am spending on all of this stuff put together. Especially work. I think I should write my buffer management system. (It won't be out there, so I should get it done ASAP. If only the camera worked.
  • Thinking back about Octavio's joke about just using word and excel, it is evident that he knows something, so he should be regarded with all due respect.
  • Thinking about kbfs pack, it makes at least some sense that, with the project still being unclassified, that we implement a compressed, cryptographic filesystem on top of a tiny live linux disk as the basis of the backup. An interesting idea is then that any machine that has two dvd drives could serve to access all the data since we can then have an arbitrary number of additional data fses.
  • Had an interesting idea. Was thinking about the definition of intelligence, and how its a bad word. Not really though, as I am only falling because of stupidty, yet I will mention this stupid idea. The thing is that why is it that the vision field is so all important in terms of our experience. The answer is of course it is not. It is experienced as it is, but thought and reason form a much larger part of our experience than we are likely to be aware of.
  • Interesting idea, I never saw anything of my fathers that would lead me to believe that he was not in the furniture industry. So, supposing he was involved in secret work, wouldn't the ideal way to do this be to code information in all those furniture design books?
  • use semi-supervised TDT to seperate all those commands
  • The single greatest intelligence failure I have ever seen is the public's lack of familiarity with the concept of a "transitive closure violation". This single concept explains more "paradoxes" than all others put together, and it also accounts for almost all cases of stupidity. Look it up on google.
  • What do you have to use. Given the extent of your present need, I refuse to believe that you would pass on free assistance all because of some minor ambiguity!
  • What do you have to use. Given the extent of your need, I refuse to believe that you would risk not receiving aid all because of minor ambiguities.
  • Conduct a breadth first search of all the open source websites we know about to find important web sources of information - automate recommendation of these...
  • Note that those current methods for extracting control fields don't work at all
  • a major problem I am having is keeping track of all the different functionality, and providing a uniform interface to it.
  • all of this needs to be planned.
  • all my life I've been put down by others, why have I not forgotten this fundamental fact. It's not like other people suddenly changed.
  • Clairvoyance should listen to the foxtrot project: Foxtrot is an evolution of a previous project Quickstep. Web browsing is unobtrusively monitored using a Squid web proxy and all browsed research papers shared between users within a central paper database. Foxtrot uses pearson-r correlation to recommend and boosted kNN classification to profile user interests. An ontological approach is taken to represent user profiles which allows inference of interests, bootstrapping from an external ontology and profile visualization.
  • Many of these systems, if not all, follow the strategy of planned obscelescence, so that we know, when we write them, that they will fail on many accounts by the time we are done, but still they will perform the desired task.
  • integrate all the p2p networks
  • What am I thinking? The myfrdcsa system is best done as an ontology! all this time, I have struggled to make Cyc work for this, when really, I just needed Protege, or Kaon. Se la vie!
  • excellent, amazingly enough, but for all the frustration it wasn't
  • it cost $80 for all the items we needed, although some of them are
  • Need a system for declassifying documents (files, etc). all documents should be assumed classified until they are proven otherwise. When a document changes, the portions which remain the same are either ignored or mentioned, but the user probably does not have to re-review them, unless of course certain things apply.
  • humor: why do all top CS departments refer to everyone by only their first name? Because everyone's last name is Cohen.
  • The authorities rely on human intelligence far more than any other type of intelligence. It all starts with a lead or a tip.
  • For want of a nail, the shoe was lost. For want of the shoe the horse was lost. For want of the horse the rider was lost. For want of the rider the battle was lost. For want of the battle the Kingdom was lost. And all for the want of a nail.
  • Often times software will be hiding in silly places, and so we need to for instance, extract all ftp site/location references we can.
  • Providing justification and reasoning about all its deciisons.
  • Alot of what predator is doing is really just makefile stuff (by no means all, of course)
  • Life was so boring for me until I discovered all of this.
  • Build reference lists to words, so for instance, find all instances in documents of the word ModSAF, and then, disambiguated to the proper sense.
  • Ask sameer the following question: I know my general project is too inspecific and "grandiose" for you, or any other practically minded computer scientist, to really take note of, however, I have been putting an effort into studying software engineering, and have attempted to divide, as do the engineers, the problem (i.e. real world) domain from the solution (i.e. program) domain, and I call the problem domain projects, and the solution domain systems, and I was wondering whether you would be interested working on some of the systems, since we have put an effort to make them conform to standard software engineering considerations, and so therefore some of them are very practical. Perhaps, you will find the purpose of all of them to be boring, in which case, would you consider starting some projects?
  • Be able to track all instances of a function in use in order to illustrate use cases, find related functions;
  • Watch all pages I go to and index them as part of the system, require online classification, say for instance, when I arrive at the page, launch a popup, which asks me to classify it, or perhaps, when I hit a globally bound key.
  • The first step of all of this is the creation of the tools for representing the software resources, without downloading them.
  • What we really need is a comprehensive system to model all people, all projects, all universities as one giant database. No doubt, I would imagine, and hope, that they have acheived this, and that those beaurocratic funding decisions are not made ad hoc as has been suggested.
  • i.e. that /chinese name/ or perhaps \{Chinese Name} matches all chinese names, from say a database...
  • How to find all the ftp servers in a domain
  • Consider all share networks, not just gnutella.
  • Analyze de jur and de facto legality of all public actions
  • Use audience and radar to, instead of sending many emails to one person, find all the projects they are PI on and contact them about the release status.
  • Add some nice algorithms for not downloading all systems right away, but for using inference to decide when to begin to archive and perhaps package a certain program.
  • I have an idea now for a useful system. The system monitors social networks, and tries to find ways to persuade large networks of people of some points. For instance, if we want to overtly convert people to become FRDCSA members, it does extensive social network analysis and learning/simulation in order to send messages/etc that obtain the given objective. Or it can try its hand at recruiting covert resources. (Modelling of weaknesses/etc will be an important goal. Notice that the detection of helplessless is important.) Obviously - this is a HARD problem in many senses, but what we will do is gather a system together that does situational awareness - a kind of social intelligence flight simulator, and then begin improving its learning and interaction capabilities - all to the point where a precise, data-driven model of other people can be obtained.
  • Need to consolidate software that recognizes file types, perhaps using MIME, and even learns like my software for files, apply this to both files and URL prediction - i.e. learn all information from the name and context possible - that's a big thing, the context. In fact this is even a bigger problem, but can be factored, that deciding how data is to be organized. We have to look into the primary classification rules, for instance, that one can classify with a formula, by file type, etc, and come up with a scheme for classifying this data. Ultimately this is indeed the kbfs, and so should this predictive capability lie within its domain? Or shouldn't it? These questions are interesting, yet my previous background indicates to me they are trivial, just not from our vantage.
  • Get answers to common questions from people like Stallman, like: if it were possible to simultaneously release all of our packages for both free and non free OSes, would this in your mind be a good or bad thing.
  • For radar note that not all project pages include links to software, some include commands to use CVS.
  • Document all programs soon, since I am already forgetting what they do.
  • Replace all the uses of use Package qw ( F1 F2 ... ) and simply export these functions instead.
  • Put all images together, have a pictures file.
  • Looking at what was actually programmed with manager, I became sort of distraught. It seemed as though nothing existed, and yet I recall doing all sorts of thought about it. What I suppose I didn't realize immediately is that there is still a huge specification embedded within my system. My exposure to outside forces has delayed my understanding of the system a little. And thus, t seemed to me to not be very imporatnt. It couldn't be further rom the truth.
  • Ask Cameron all about how to change your identity.
  • For instance if you scan an item, it should tell you all the pending actions against that item: for instance, if you scan a dirty water cooler, it will tell you that it should be cleaned, since someagent had requested this at somepoint.
  • That's her way of insulting the project, as though she doesn't care at all about it.
  • It will be a glorious day that all my actions are just exactly what I had planned a long time ago, when I finish one thing, the computer notes what now is possible, etc, what should be done next, and tells me - glorious!
  • Kevin, would you really rather work when you could have everything provided for you where all you can do is research?
  • I had some more dreams. They involved me exploring a university looking for AI, but I couldn't really find anything of interest or relevance. I could see it though as one sees in normal waking life. I also was reading with some permanence to the words. I wonder why it is that I can remember so well and yet not spell at all. I suppose I don't train myself or set up reward mechanisms for spelling.
  • Life is OK. Although, the AI researchers are probably almost all humanitarians, the chieftains may have other purposes for them. Chieftains don't just get each other's goats to get each other's goats.
  • I have all this time simply been negotiating with you so that you expected me to come home and thus did not as actively design schemes that would interfere with my ability to become truly alone.
  • Perhaps we can have Al explain these things to Kevin. Kevin doesn't understand the transitive closure violation that is implicit in a program's ability to write a better program, although he understands what happens when the program is able to mine the resources of the net. do we need to teach him? I think so so that he is informed in his approach. Moreover, there is also his argumentative opposition to human beings being selfish, which although I would agree tends to be the case it is not true that all human beings are selfish since some of them are sincere in their desires, and his 2nd-law of thermodynamics argument fails.
  • At once they set about destroying all stores; three guns, a quantity of carriages, and a large accumulation of powder and ball were thrown into the river. A number of barrels of flour were also thrown in the same place and spoilt.
  • The nature of the country lent itself to the mode of fighting of the insurgents. But their own genius also counted for much. They used every kind of cover, seldom exposed themselves, and at all times took care not to let bravery degenerate into rashness.
  • MARRIAGES ARE all HAPPY . IT\x{2019}S HAVING BREAKFAST TOGETHER THAT CAUSES all THE TROUBLE
  • To conceal the truth of history is the blackest of all infamies.
  • Some of the things we would like: reading research papers on special topics like Soar will give an understanding of what needs to be done. Another thing that would be of use would be to use a KBS or something and go through all of the instances of types of learning, etc, in the literature and where they are referenced. I just don't see this process being very unified. Such knowledge could feed algorithms for dynamic selection of these.
  • Some of the things we ought to do: for our FRDCSA release on the web, we should make sure to spider to download a lot of software and populate the archive this way. We can take software from our different sources. The first version should simply have the tools of the FRDCSA and not mention packaging all of this software. Then when we have more money, and we are further along, we can release all of the packages and sell it again, perhaps giving a discount to those who purchased the first disk.
  • Should look into all existing systems and their expertise level to determine some things.
  • Oh, so people with Asperger's don't vary at all.
  • You call it academic? do you really understand the value of academia? Who do you think wrote the program that performed the difficult task of planning and scheduling all the attacks in Iraq? Most of the military is using the so-called academic systems to protect you?
  • I really don't have the time to refute all possible logical fallacies.
  • We needn't take the time to refute all possible fallacious arguments yet.
  • all proceeds go to the development of opensource software.
  • You could say, do you acknowledge that I am the stronger chess player? do you acknowledge that I have studied mathematical logic in greater depth? Ok, I know you are phenomenonally intelligent, but to be honest I don't think that you have been able to understand some of the finer points of mathematical logic. I regret that I seem to have contacted you too late. I was hoping that you would have survived West High without developing the mentality of a leader of a small pack. And most of all, I regret that you do not care about the plight of other peoples and therefore I cannot care about you. But if you want to tinker with some of the projects be our guest but as far as making a serious contribution I don't think you have the ability.
  • I don't think you understand. I want to see you all. That is my greatest wish. In fact, I want everybody to be with their families. And I think I have a way to make this happen. Everyone expects some gigantic thing, like an end to military invasions. They don't realize that that is achieved by guaranteeing individual safety and by mediation by AIs.
  • Dear Kristine Lerman. I found some of your insights in paperparenting book fascinating. SpecificallAlthough the notion that baby talk develops their pronunciation. And I got to thiking about another thing. What possible reason could there be for monsters at night, or for making sure your feet are all tucked in. Another thing, I noticed today is the 4th birthday of the electronic elves. As someone who is intersted in AI, I was wondering whether there was a way to aquire this software. Thanks, Andy
  • It's time for an experiment, a concerted effort not to see anyone, and a secret letter to Al about this bullshit. I appreciate what she does but she is living the lie that somehow she is not bad for me. Its becoming evident to me she is, so we have to negotiate secretly here. First of all, she cannot know about Al visiting.
  • Next thing is what I was saying about intelligence. I was thinking about how the AI is to operate. I ws thinking that an overt attmempt is rather easy to annihilate. Simply annihilate Andre J Dougherty. Then I thought, well, what about a covert attempt. And I said that is all fine and well, but once agai there is a size limit to an effective program. This of course implies taht there are only certain ammounts of intel we can distribute. This has the effect of creating some inequlities of size that limit the moves that we are able to make.
  • I liken it to the following situation. Imagine you have a chess master, who is sitting at the board, pondering which move to play. In looking at all possibilities, not directly but through the theorems about chess he has deduced, he realizes that none of the moves are worth making. He stops playing and starts thinking about what the correct move is, what the correct actions to take are. After a very long time thinking, he shouts "Eureka!" He has just solved an important question of mathematical logic and must now begin work implementing the solution. A general procedure for deduction. Naively telling other people, they get trapped in various lines of reasoning which will not result in the system. Amazingly, he must go it alone, but due to the correctness, he must. He found it, no one showed it to him, he figured it out, and it implies certain actions, which he takes, independent of peer pressure.
  • when writing a paper, we can use our systems to ensure that all the necessary concepts are defined to a certain level of detail.
  • Should train the user to survive on and using all the algorithms we know. Also print things up for reference.
  • Pretty soon gramps will be reunited will all those dogs he shot.
  • He hopes to have a fun "Dougherty" style get together where we all torture and decapitate small defenseless animals.
  • I'm fighting a tremendous technical battle that you say you don't have the first idea aobut how to understand and yet you are full of all this advice? Since when has a battle been irrespective of the details, the tactics the strategy and the reality?
  • Another thing Kevin and I need to do is to, having set this up, find an autistic child to be the "one", and to have all of our resources.
  • Should, obviously, index all documentation using question answering software.
  • Should formulate predicate for the fact that say Project Halo entry 3 uses Prolog, some how. We can ask, what are all systems that are using the Prolog language.
  • sort out all that stuff.
  • Sit down sometime and formalize all concepts for the system. Refer to work on formalizing enterprise concepts by Austin Tate.
  • You asked whether AI was dedicated to Ann. What do you think AI is all about?
  • F-16 pilot: Finds snake, drops two CBU-87 cluster bombs, and misses snake target, but gets direct hit on Embassy 100 KM East of snake due to weather (Too Hot also Too Cold, Was clear but too overcast, Too dry with Rain, Unlimited ceiling with low cloud cover etc.) Claims that purchasing multi-million dollar, high-tech snake-killing device will enable it in the future to kill all snakes and achieve a revolution in military affairs.
  • be sure to put all important dates on the calendar, so we can see what is coming, for instance, any Debian conventions, any CMU lectures, etc. Also, at certain times one can expect new information to be posted, so we should retrieve that as well.
  • Thoughts on studying. Open systems theory. How does it know what I am looking at? I suppose it could make note of all programs I use, etc. But in general, here we run into what I am guessing is an open system problem. We don't want to disturb the user but we want to know what he is working on.
  • here is something interesting. the website, or whatever ought learn about the user and determine whether they know such things as: it is useful to read research papers from related projects and use those ideas. Also, all information we present must be consistent with some plan of action along the lines of what we want the user to do.
  • Here is how things ought to work. Suppose we implement a stable perl module for reading configuration files. Suppose further that there is some indication that we ought to standardize all of our systems to use this to read their conf files. Then the user authorizes an order to do so. The time required is estimated and the programmers involved are contacted and the process begins, almost like a scroll bar in progress, by the simple observation of programmers working.
  • I'm not shooting anybody down, I'm proposing solutions. Now you can nitpick all you like, find this or that. It is extraordinarily easy to fail. Its much tougher to succeed. But the problem is nobody's done that yet.
  • Write Kevin with a nice letter wondering whether he knew about CMU, whether he wanted to have all his needs provided for, and whether he wanted to audit classes from 8:00 am until 6:30 for two semesters, gathering diverse knowledge from the top university all the while building an AI.
  • Although in some sense we are simply by-passing that issue all together with AI.
  • look at gnutrition mailing lists and get all the people who emailed it together and organized to work on stuff.
  • I think that with unilang we simply have to ensure that all watchers have a timeout.
  • all there was at CMU today was a bunch of women - where is all of the mathematics and logic? I even doubt somewhat the words of Manuel Blum, and the director of the neuroscience program watches entertainment. We are seriously in need of some strengthening of our values, and getting our goals accomplished. Let us therefore ensure that we get our goals accomplished. Reliable verification that a goal is being accomplished.
  • Write a letter asking whether releasing all those packages would be good for national security or not.
  • Why is it that all the great people get shot.
  • Important things were the picture of Coabs using prodigy, etc. all the pages AI read. The comments on the proof of AI sstmes being related to Godel's theorem.
  • I read all the directions, but like you say, I pretty much did the write
  • evil aliens leave you alone, attacking him all the time
  • all the travel aliments are learned by yourself.
  • I exited to one side, and now all I see is wounded 2d.
  • Justin, you have all the makings of a math god, just think, you have all this time to study, and you all the privacy in the world. This is quite good and I am sure that in your present situation you could become quite excelled at mathematics. You certainly have the brains. all you require is to take some input.
  • actually, look at all of CMU's CS/AI/etc classes and make sure you have proficiency in subject matter.
  • add the ability for opencyc-common to, when translating scripts, find all occurances (or likely mispellings of an item and baed on the constraints on the arguments that it has, clarify its isa, etc, with the user)
  • the same system that applies to going home and fixing all their problems also applies to developers of open source software. we can systematically index project groups like our own and begin servicing them with help, basically solving all of their outstanding software problems.
  • should make sure to clean out unnecessary files from all locations, for instance nut extracted in source-archives.
  • "Given the existence...of a personal God...outside time...who...loves us dearly...and suffers...with those who...are plunged in torment...it is established...beyond all doubt...that man..."
  • Traditionally, planning systems are all about finding ways to solve the combinatoric problem of satisfying a few goals. Why these goals are selected is not usually of any consequence. What we really need is a system that understands what happens if, for instance, you do not pay your rent. Another thing, is that it make sure that the daily average of some required thing exceeds what it needs to be, hence ensuring that you don't fall behind. So, our system is for instance able to reason as to what consequences will happen if certain actions are taken or forsaken, and on the basis of this, determine what it thinks are important goals.
  • My work with the critic system has made me extremely bitter. I keep trying to fix nonsense bugs, but the system is too unwieldy. I'll think its something and modulate this back and forth, trying all possibilities, until it becomes obvious that the problem is somewhere else. This is a lesson, mainly, that we will have to break tasks down into more manageable chucks and verify them. Divide and conquer. The ideal way to do this therefore involves listing tasks, decomposing them, and verifying the completion of each subtask manually. Inductively, so that when the system is run, we methodically check all possibilities until we have eliminated them. I.e. we must be able to prove correctness of plans, etc. But in order to even implement this ability, we will have to apply these rules manually until we have some systems to do this. This means interactively building up a system from small, but verified components.
  • should get a minimal shops system written and deployed very soon. it just logs sales, with a nice GUI, and prints receipts, etc. Should only do basic things, be very forgiving, and then we should scan in their entire inventory. get this all planned out. deploy it on a given day.
  • perhaps move related systems into boss or into normal area, with simple declarations in FRDCSA.xml that these are related systems. That way, all code in a given directory is ours, and this encourages things to be more modular.
  • need to release packages of all my software, and have a set of testing systems.
  • should make a unilang system service, and package it so that it operates, all testing can operate on another test network with a different code
  • send email to all metasites that we make packages for telling them about our system, and encouraging them to add links. as well, we could ask them politely to try to encourage people having non-free software to release it free.
  • delete all fucking games already]
  • think about a strengthening of free software: hyperfree software. make our website have all the keywords and give away our technology freely, but make sure to get the message out and develop individuals capable of using it.
  • We can also trade with Al if he needs a van. And gas won't be all that more expensive.
  • scan all their inventory with prices, etc. use various online suppliers to do the reordering.
  • There was some funny stuff in my dreams. I was lost and locked out somewhere late at night, and I managed to get into to flight visions. Inside tehere was some chess playing going on, with Mike Liu an dRicky Moreno. Who both had thick stuble. They kind of ignored me at first. Later I was driving somewhere with them, and I kind of sat there waiting in the car. Really though, I was pplaying a wierd game of chess, with some knight defenses etc. Then I was lying there when Haydee, calling herself Jaime knocked on the door,a sking if I wanted to go rolerblading. I was paralyzed, but I wanted her to come over and sit down (on me.) So I was whispering, Yeah, Yeah, I'm purulized, com ofer, com ofer. And she came over, but didn't quite understand what I was doing. Then finally I was able to move my arm, and of course she wasn't really there after all.
  • GAME OVER! That's all we have to do. Approve it with Al, figure out a place to put everyone, get it all set up. And there you have it.
  • find these "professional programmers and figure out a place for all of them to live."
  • well, lets give a go ahead for the system and just have it sort all of these anyway, and then see what we can do with them.
  • for instance, that mpeg, mpg, wmv, avi etc all get classified under movie, etc.
  • perhaps ironically, I set here debating whether to write a perl regex for detecting nested parenthesis, and all I can think of is Reingold and his pumping lemma, IT'S IMPOSSIBLE!!!
  • Top ten reasons you are autistic? 10. Every girl thinks you're stalking her because you know all her information: home, cell and work phone numbers, social security number, credit card number, all her passwords, and everything else she's every typed into a computer.
  • recently I have become noticably bogged down. I did a lot of work on the webpage, but this was not fun at all. I just wanted that material up there. now I am not so sure that was the best choice. I am still being affected by all the schemes against AI. For certain. Now, both from individuals and coordinated group action. too bad my famil is unwilling to understand this.
  • The real trick to all of this is simply to have an intelligent machine. What are now projects could simply be emphasises with such a machine.
  • We have to thoroughly explore the issue of how to maintain facts. For instance, suppose we decide to change the project name. This should effect all sorts of hooks, includings one which state opposing reasons, such as the project name is already clearly established, etc. Then the system should be able to reason out the issue and then come up with a solution.
  • I was thinking that boss could handle FRDCSA.xml files and specifically would be able to, interfacing with unilang, add feature requests, dependencies, etc, all project related information to the file with tagging of which messages justify the inclusion.
  • I just manually redid all of these FRDCSA.xml entries, which is total stupidity, since it would not have been very hard to write a program to do it. Sheer stupidity. I am thinking like someone else. The thing is now we have wasted all that time and we don't even have a program that could be used with auto-package for automatically generating these!!!! duh!!!
  • I left to break that vicous cycle, to short circuit it and free myself from its effects, so that I can go on to break the cycle with AI. But at presents it seems that all we have done is to lengthen its period.
  • all that stupid movement has rendered my typig pretty bad, and especially my right arm is dead.
  • I really need to get cracking. My goal should be to have all messages on pse by tomorrow, also with pse having some features.
  • so from now on all games should be uninstalled, not that that really helps, but it just a sane policy. There would never e a legitmate purpose for a game, and furtheremore, games are blacklisted in our software search, no games allowed.
  • Having each other is necessary, but not sufficient. If it were sufficient, we could all quit our jobs. Same with material objects, they are necessary, but not sufficient.
  • have links in the frdcsa-website come with all sorts of options, and have a very diverse and correlated automatically generated front page. look like the yellow pages.
  • we should write a research grant proposal that explains about the current disorganized state of software location tools, and the FRDCSA model, covering the process of locating software with radar, packaging it with predator, and how this all ideally fits in with the Debian system.
  • we could have a list of "criteria for coming home", which lists all of the do's and don'ts, what constitutes material breach of this list, etc.
  • consider all the topics deemed difficult and tough. Now most of these are probably jokes, but one could infer what professors find difficult as being a little more difficult. It follows that discussing with professors is a good method.
  • at some point we'll need to keep a database of all things the user has ever typed into unilang. And then, those which are deemed to be a certain type etc, can register themselves with other agents. We should also have all agents support recall of a message, i.e. some support for negating the contents of a message. How does this affect things? We can keep a database of which agents implement which core functions.
  • here are some good ideas. The first is probable actions under consideration should be run through a simulator to see how it benefits or harms various interests and what their reaction to the actions would be. all of this ought to be empirically corroborated.
  • perhaps one could make a knowledge based programming language had all sorts of knowledge of running times, etc of data structures and used this to calculate and compile it better, as well as interact with the user to achieve their design goals.
  • in all instances of any sort of assumption, such as the assumption of a file name, etc, eventually, there ought to either exist the original external justification/specification in the system, or a well-defined meaning of our own given to it, but no decision ought to be left unjustified.
  • be sure to enter all useful information from our remaining data totes, and also ask Al what he wants done with them.
  • You probably think I have had no success with AI, where is it, you probably say. First of all, you cannot understand it, you cannot see it, so you cannot reach a conclusion. But do you like to jump to conclusions? I have had much success, great success, but this has no doubt been mitigated by the fierce enemy tone and complete lack of any assistance.
  • I said right now I am filling up the ocean with a teaspoon. I also said that it is easy to fill up the ocean, all you have to do is let the rivers open. The rivers are damned however! There are lakes of software, just waiting to be released!
  • I should have it record a log of all commands issued when making a particular package, and then do logfile analysis and have commentary from the person trying to group these into abstract tasks that can be computed in someway from the package contents.
  • What about all the reading and attending lectures, and classes. Did this count for nothing?
  • contact scott gar or whatever from advogator and tell him that we intend to create an organization whose sole purpose is to recruit programmers to dish top notch code to support the open source effort. This will be entirely funded by another business which exists solely to do so. Our advantage will be in the quality of our software engineering processes, our extensive software libraries, and so forth. We are extremely interested in this but agree that we cannot find people who are qualified and take the threats seriously enough, since, after all, they don't really care about intellectual freedoms, since if they did, they would get a helluva lot more organized.
  • ironically, all that time I spent wandering around rooms and so forth has come in handy. It is thus possible that I could disappear probably anywhere. Simply determine where to go, dress up in a suit, and then you will be fine. Move a microwave in, etc. Use the bathroom at the right time, or find a secret one, etc.
  • the organization of everything should be handle by a system, and it is but a simple manner to generate all or parts of the site dynamically from the current organization.
  • we should probably formalize this all in a KB sometime, if we ever get a KB!
  • run substitute "radar install perl" on that list to obtain all objects installed on our system
  • need to look into all libraries of functionality
  • consider downloading all attack warning systems
  • interesting, I had pop in the fridge all this time
  • all games should be purged from frdcsa distribution releases
  • as part of PR, remove all abstract terms like AI that can be overloaded.
  • I don't like this false cnfidence. It makes you thikn you are safem eb. I retract all of tgus,
  • as part of the exploration versus exploitation, we wonder whether to revert to existing functionality rather than use our own, supposing we have already written our own. The question reduces to how used is the existing method, does it fit in nicely with others, and could we disemminate our method. all of this should be calculated in detail.
  • tell Al, that one method of doing things is that I write scripts to do what I need. when the scripts perform what they are supposed to do, I have the resources to go ahead and refactor the functionality of the scripts into the project which coordinates a set of related capabilities, and write them with lasting structure, making a library. Then all applications can use these features. As far as automatically building libraries from not just my own code, but other people's code, that, too, is a capability we are investigating.
  • They have all the money.
  • They have all the software.
  • I've been TRECing through all this MUC, and isn't that what its all about, competition?
  • work on the unilang system has been temporarily abandoned. all concentration going to simply designing algorithms for pse.
  • Should collect all of my arguments together, in case it becomes necessary to prove I have Asperger's syndrome. For instance, as proof of Asperger's syndrome, simply describe in detail how I perseverated at flight visions, made mistakes, and obsessively wrote software of no use, how I perseverated in class and studied 90 hours on my own, attended all lectures at the expense of school, etc..
  • assemble a list of all the programs I have written, in the last year, evidence of my laziness, send it home.
  • An essential strategy for achieving projects is to reduce the complexity of the task. For instance, rather than require that we first collect all existing log/todo/thoughts files for analysis, we can simply run it on our existing files. Or for instance, rather than copy all of the old frdcsa files to the new machine, we introduces a whole slew of new problems, we can simply resort to a simplified unilang system that doesn't depend on OAA, get the todo set up, and then begin calculating what order will accomplish things most effectively.
  • need to integrate all my stuffs
  • After all, tried to disappear. But that might be it, search for Asperger's on missing persons list. Should also check with IMSA people, who might be interested after all, especially if some of our tech can be demonstrated to them. Maybe we could make a recruitment DVD distribution.
  • improve the cohesive properties of unilang data, for instance, make sure it is all saved under ~/.unilang
  • Should try to implement a basic system that is capable of downloading all programs in a given search, and put these in FRDCSA, correctly recognized.
    ("completed" "96455")
  • First of all, the field of AI is alive and well. Whereas people who don't understand how AI works, and what it does, were most probably let down by the 1980's AI depression, the fact remains that people who were successful with AI have been extremely successful with it. And moreover, many people object to my AI, saying I don't know what I am doing, and I think this has more to do with their ignorance and my difficulty with communication than with my actual methods and sources.
  • So, we have been running around doing all sorts of things. Right now I have the following items on my todo:
  • Most of the time life sucks and then you have sex and then its ook for a second, but all you do is create more life. AI is like permanent sex because it is so effective tha.
  • With AI, you can have all types of people. The number of people who want to kill is probablt equal to the number who want to be killed. In the end, we can simply go on understnading more truth, however this is not what most people want.
  • It is all about inelligence on what people need. So in the end, there is a nice fit to intelligence about what people need, owever, there is a monetary expectancy, and this breaks down when there is no profit motive.
  • : vrf3cFor all your talk about what a great country this is, you don't seem to realize what makes it so great. You tought capialism, but you don't seem to understand it. The point of capilasim, and the point whole idea of this country, is to take a risk. Only if you take a risk, can you mak eprogress. Now whether you understand it or not, AI is not a pipe dream. It's too bad that you think you're smart. If you understood why I was doing this, you would see that there are some good reasons for it. You would see that there is enough truth in it to bet your life on. I would rather die than stop work on AI, because it is that important. Now isn't that what his whole country is about?
  • There are several imporatntc considerations in seeting up shops to run your store. The first is to Teh first consideration is installation of the computer system runing SHPS . If your To do this, you need to insert the CD into a system. WARNING: YOU WILL LOSE all DATA ON THE SYSTEM. shops REFORMATS YOUR SSTEM. Only use a PC thatyou don't need any more data an.
  • That is true. My parents don't know what they are talking about sometimes. Even though I had to move all those things, I still could have achieved better results, with a little help. So, I think i made things a little better, I also made them worse.
  • Complete understanding and knowledge of all existing terms would be a good start.
  • Tomorrow, go through these recent notes and create and print your usual plan covering all the major topics.
  • Dad has done less than to help again. EVidence of this is that I said accidentally that "when I die", indiciated regression to earlier patterns of thought. Now, some things are possible now that weren't before, perhaps as a result of this design of mine, but I don't think it has gone as well. Although, the money from parents is useful in getting what I need. But this illusrtates a flaw in my thinking. I should have asked Al for some money to get all set up. But I think I am pretty much in the clear. I should also call and get my paycheck. I'll ask Al whether this may be used to finance my outstanding needs.
  • It may be worthwhile to work on developing a language which represents linguistic referals, and to make sure that all possible linguistic forms are corresponding to the proper language construct. For instance, the linguistic form "for instance" should indicate a specific relationship between two sentences. In other words, a semantic understanding of linguistic forms rooted in a KQML language for expressing them as plan objects.
  • I must say, that I wrote a letter today about becoming an interrogator, all of this when I could have been programming this pse system. This is obviously a problem and again, we must patiently, correctively bear through such mistakes. In general, writing should be avoided, programming should be encouraged. This ought to go in manager.
  • Take photos of the freezer full of frozen food, (make it so you can see a row of it going all the way down.)
  • Even if he didn't think it was that way, what kind of proof would that be. And why isn't theree any reason to think that they wouldn't go all the way.
  • Dad thinks he is wise but I think he is a erk, a dull stupid fatuotous person. He iis foolish and create problems not even a wise person could solve. He Nothing is more emblematic of his mokery defeatist attidtude than his inane rejection of my cooking program. If he cannot even be persueaded of the usefulness of a dieting program, then what would he think of some advanced AI capabilities. Perhaps it is better to let things take their course, and then maybe mom woudl come and help me. This resistence I find hard to believe. It is not wise at all, it is the greatest stupidity.
  • I simply cannot believe the way you joke about this seriuos topic of AI. You seem to want me to bear all the proof that I am right. What you fail to see is that you must also bear such a burden. I can only say what I see and there is no doubt in my mind that I can make ...
  • I think maybe we ought to have a planner that looks at all possible actions.
  • Now it is important to mention all the thoughts I had last night.


This page is part of the FWeb package.
Last updated Sat Oct 26 16:50:06 EDT 2019 .