Be the first to post a text review of BlooGee. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Details on MCO Model

  More Details on the MicroContentObjectModel are now at http://code.google.com/p/mcom/

  posted by markusckoch 429 days ago

• New release coming soon - BlooGee 0.1 beta - Roadmap

  - Extended ReadMe for Version 0.1 beta [NOTE] A more comfortable presentation / version of this text ist to be found at http://docs.google.com/Present?revision=_latest&fs=true&docID=dhfz8pq8_29dq2skkgz Please righz-click and choose "open in new window!if the link doesn't work!! In short, the interface will be reduced to BG server communication, (the "VT-100" part) while the peer-to-peer server part will be made fully functional (hope so...), including RPC commuication, store and forward as well as data encryption. Still BG requires only PHP4/5 and a SQL DB so no additional services or root installion are required. Major Changes 0.00f -> 0.1 Verion 0.1 will contain major changes, a more compact code, better documentation. A much more practical approach which should be usable also for no-expert website owners. How to use - user's view BlooGee is an attempt to the next step in search technology. You login to a BG page with your script enabled web browser. BlooGee presents you with a simle command line interface (CLI) which is the shell (VT-100) of the adressed BG network. You now may search the local content as well as related content the BG knows about. If you have higher permissions or your BG has a high level of trust at other BGs, you may BG ask to deliver, store and foreward results as well as content from its own (or some other) BG network. BlooGee does not present a whole website (even if it fetches them for analysis) but assembles the related information elements. Some things to keep in mind BlooGee is a de-centralised search engine. The main idea behind this: if you search for cooking recipes it makes no sense searching car servicebooks. All you do is start with a BG enabled website, preferrably your own. Ask BlooGee, and it will learn about your preferations and where to ask for more. More, it will remember what it has been asked before and who seems to have relevance. BlooGee is no file sharing but information sharing system. The main communication and logic is between BlooGee protocol enabled CMSs. BG does not run and do a search for you. Instead, it runs and asks others if they know something about your key words. Additionally, it asks others to ask others (to a certain depth of course). The size of a BlooGee network is defined by the limits of local maintained serverlists and the limited resources of the webserver itself. If you are an anonymous user, then BG wll only be able to ask it's own servelist about this subject. If you are logged in, your BG will ask it's trusted peers to execute the search and ask their trusted peers, and to repeat this up to a certain per BG configurable depth. Website owners BlooGee requires PHP and its own DB tables. It is installed along with an existing CMS. By default, BlooGee does not alter original content or layout or permissions. If you have working Pings or an RPC on a blog, it is a good chance of making BG work. Too, you may use BlooGee to build dynamic websites on special subjects/keywords which feed from "auto-discovered" related content. Attention: configured unproperly BG may consume an unexpected amount of bandwidth! The installation package contains all dependencies, all you have to is ftp the package and edit the database adaptor/s. Edit permissions at own risk. There is no admin interface or backend. After initial configuration in a PHP file, all user or admin actions are performed at the comand line. In short - BG says:-) BloooGee says: "I know something about me, and maybe I know some others who were asked before about the same thing you're asking me now. I don't know the answer, but I will try to ask the others I know about your thing. If I trust you, I will ask others to ask your question all BGs they know. If anyone has the information, I will get it for you. And may be some related stuff, or at least information about where to ask again." Server List BlooGee does not require a central server. Instead, it searches for related content as wll as sites with BG protocol enabled. Server lists contain adresses and some key information about other BG enabled websites. Results may be ranked and sorted by local algorithms. BG protocol About a 99% of BG acivity is server2server communication on HTTP. The VT-100 part is provides combined search and command interface to BG server protcol based actions, as well as inline display relevant 3rd party content objects (MCO). BG protocol establishes several grades of trust which allow to perform several levels of RPC actions. By default, BG servers try to hand over user searches and exchange server lists. This is limited to a per-server configurable depth to prevent loops and exploding requests. BG protocol provides a unique hash for each message and its related actions. By default, only searches on the known peers are performed. "Databases" - "Adaptors" Every BG server has to reside on its own more or less unique content - which ist the "database". The "adaptor" connects BlooGee protocol to this database. Database adaptors even may connect to an API, a search engine or shopping system as well as existing websites, blogs, stores etc. Of courese, BG has to maintain its own database structure, based on public ADODB. "Text & Links Destiller" and the myth of "index of relative content density" Initially, this was a joke, just intended to separete content text, images, links from header , scripiting and layout. The numbers of elements are computed into an index number. In BlooGee by default this index is used to rank and sort the server lists/search results. Ranking algorhythms may be written and implemented as needed. Local parts / executables There is no *.exe or other binary at this time. I would apprecieate (i.e.) a browser plugin which enables and maintains a personal (local) BG which is not maintained in the public server lists but keeps full track on the networks of user requested information instead. MAJOR CHANGELIST TO V0.1 beta - The interface (which was quite pretty AJAX stuff two years ago) will be stripped down to the VT100 part. - The BG server protocol will be functional (well, in fact in the prvious version was more a scribble than a functional server protocol). - The MCOM model (which ist still the abstract part and father of the whole project) wll be extended (and given an own project page here at sourceforge.net). The MCO itself wil be nestable. - The DB abstraction layer and it's command language will becontinued (this not the heart, but makes life with BG a lot easyer). - The plugin interfaces will be documented and more stable so it is easyer to write own commands and DB adaptors, as needed. - Some of the AJAX librarys will be changed. The adaptor will be changed to Joomla, a sample adaptor for some major catalogue and search systems will be included soon. - inter-BG communication and data will be encrypted by default. Summary - BlooGee forces websites to establish de-centraliced peer2peer networks which are able to learn through searches. - BG is based on its own Micro Content Object Model MCOM. - BG networks are made of websites which maintain information about their related content as well as other known BG networks. - For delivery of information snippets, BG may store and forward messages between own peers and other BG networks as well. - It is no filesharing system, neither aimed to that. - BlooGee is hosted by an existing CMS. - BG may be used to edit and publish content from the owner's CMS in a comfortable way. - BlooGee is aimed to a maximum level of open architcture to enable 3rd party plugins, commands, rankings, interfaces, skins and adaptors. - BlooGee does not store personal user information, it stores information about other BlooGees instead. - Communcations are entirely on HTTP:80. License Still BG is GPL. Maybe some of the new parts will be published under CC-nc.

  posted by markusckoch 438 days ago

• Overview

  What is BlooGee? Initially, Bloo Gee was developed as a proof-of-concept work for a simple object model concerning microcontent. Main target is to provide an instrument to establish semantic networks, based on communications between webservers. BlooGee is (for now) a kind of add-on for weblogs an content management systems; it works on any structured content which can be described by a simple model: identifyer, short description (or headline) and extended description (the main content). In this sense, almost any table with text data may be used by BlooGee. It is not intended as a replacement for existing systems, but as add-on for common blog systems to establish communcation based on semantics between different weblogs. How does BlooGee work? In this first version, BlooGee simply provides a kind of desktop interface to exsiting blog content as well as a command shell to access (not only) server functionality. There are some nice features like in-place editing, a lot of AJAX-stuff and some basic tools to test and establish communications between different BlooGees. It basically supports a "site to site" protocol, based on simple HTTP requests. Concerning the content, BlooGee adds a special property to single items: relations between micro content objects. In this sense, BlooGee provides search capabilities which are no longer based on keywords, but on semantics. If a search is done, it still starts with a keyword (and only one single keyword), but then focusses on (user provided) relations between items - on different sites. BlooGee core functions Basically BlooGee adds an abstraction layer for existing content. This layer is strictly embedded into a security layer which controls access to its core command set. BlooGee supports unlimited users, user rights and command rights are expressed as simple numbers:if the command "level" is less or eqaul than the user "level", the command is executed. In this sense, the BlooGee security model may easily be extended or used for own development. And - of course - own commands may be implemented. Communication between BlooGee servers The BlooGee protocoll is inspired by existing peer-to-peer networks. Each time a request is made, lists of known other servers are exchanged between servers. And - of course - search requests are exchanged too. If a site is unreachable (but still up), a semantic network of BlooGees may fetch the content. What is BlooGee made of? BlooGee consists of a set of PHP pages, a system database and a (individual configurable) main content database. Since BlooGee integrates ADODB, it is quite flexible regarding its environment. The surface is based on Scriptaculous and Prototype libraries. For coming versions, PEAR classes will be integrated for generating HTML pages. Extensibility BlooGee provides some simple APIs so it may be easily extended to own needs. Basically it needs an appropiate adaptor for its main content database. Since it is written strictly in the MVC model, BlooGee may easyly be extended with own controllers to set up special functions. Command shell - VT-100 ;-) Originally written as a debugger, the command shell provides terminal like access to BlooGee. It is like "telneting weblogs" and has some interesting features for accessing content and BlooGees system database as well. Using the command shell, a simple webserver may be used like a "HTTP machine" to construct headers, monitor BlooGee activities, fetch and inspect remote sites, filter links from remote sites... How to use BlooGee BlooGee may live in any subdir on the webserver. If configured properly, it provides a nice "blog desktop" with drag 'n drop capabilities, in place editing, user login and a page menu. If the command shell is opened, it provides access to server functions as described. To take full advantage of BlooGee, a change in the model of the content is required: single items have to be "tagged" with keywords and/or the URLs (permalinks) of related items. The more relatives, the more effective the semantic network. And the less the need of "keyword matches" for successful searches...

  posted by markusckoch 441 days ago

• Tracker artifact added

  markusckoch created the MySQL specific code in security.php.inc artifact

  posted by markusckoch 1059 days ago

• Installation

  If you decide to use this version: - Copy all files and directories to your webserver. - Edit the configuration values for your MySQL database (in this version, you will have to edit the fieldnames in the SQL statements by hand) which will work with nearly any basic CMS table with id, title, text structure. - Many systems use a field like "pinged_urls" for remote blog messages - this is fine to be used as "relatives". - Edit the stylesheets as you need and like. - CAUTION: if you are running MovableType, check what you are doing if you execute the SQL.txt on your db server. If not: - edit SQL.txt to your needs and execute on your db server. // This is only an alpha version, use at own full risk. // // You preferably may use this version to edit local content or use read only datasources.// Notice: values for db (dbhost, dbuser...) have to be edited in mydb.config.php. All other config values are found in BGCONFIG.php!!! To configure the dbadaptor with your blog: read http://sourceforge.net/docman/display_doc.php?docid=38528&group_id=168630 To integrate server communications into your own code please see https://sourceforge.net/docman/display_doc.php?docid=38532&group_id=168630 .

  posted by markusckoch 1059 days ago

• Readme First - Alpha-Release

  This is the first Version of BlooGee - still below 0.1 ;-) - which has the following capabilities: - a full security layer, supporting an - abstract layer of basic datbase commands. - a full featured command shell to access the - basic set of server-to-server protocoll functions; and - an AJAX based desktop for blog-style display. - Integration of ADODB. - A widely open architecture for extensions and third party plugins. Some brief basics are to be found at http://sourceforge.net/docman/index.php?group_id=168630 . An additional PDF for PHP developers, generated from sorce code, is available at http://bloogee.sourceforge.net/documentation.pdf . However, please see https://sourceforge.net/docman/display_doc.php?docid=38524&group_id=168630 . About BlooGee BlooGee is (for now) a kind of add-on for weblogs an content management systems; it works on any structured content which can be described by a simple model: identifyer, short description (or headline) and extended description (the main content). In this sense, almost any table with text data may be used by BlooGee. It is not intended as a replacement for existing systems, but as add-on for common blog systems to establish communcation based on semantics between different weblogs. How does BlooGee work? In this first version, BlooGee simply provides a kind of desktop interface to exsiting blog content as well as a command shell to access (not only) server functionality. There are some nice features like in-place editing, a lot of AJAX-stuff and some basic tools to test and establish communications between different BlooGees. It basically supports a "site to site" protocol, based on simple HTTP requests. Concerning the content, BlooGee adds a special property to single items: relations between micro content objects. In this sense, BlooGee provides search capabilities which are no longer based on keywords, but on semantics. If a search is done, it still starts with a keyword (and only one single keyword), but then focusses on (user provided) relations between items - on different sites. BlooGee core functions Basically BlooGee adds an abstraction layer for existing content. This layer is strictly embedded into a security layer which controls access to its core command set. BlooGee supports unlimited users, user rights and command rights are expressed as simple numbers:if the command "level" is less or eqaul than the user "level", the command is executed. In this sense, the BlooGee security model may easily be extended or used for own development. And - of course - own commands may be implemented. Communication between BlooGee servers The BlooGee protocoll is inspired by existing peer-to-peer networks. Each time a request is made, lists of known other servers are exchanged between servers. And - of course - search requests are exchanged too. If a site is unreachable (but still up), a semantic network of BlooGees may fetch the content. This is the first developer release of BlooGee which should work with most CMS(after some little configuration/modification). Please see release notes and additional documentation before installing.

  posted by markusckoch 1059 days ago

• BlooGeeV0.00fpublc.rar BlooGeeV0.00fpublc.rar file released: BlooGeeV0.00fpublc.rar

  posted 1059 days ago

• File released: /BlooGeeV0.00fpublc/BlooGeeV0.00fpublc.rar/BlooGeeV0.00fpublc.rar

  posted 1060 days ago

• Code committed

  markusckoch committed patchset 1 of module BlooGee to the BlooGee CVS repository, changing 46 files

  posted by markusckoch 1060 days ago

• Code committed

  Anonymous committed patchset 1 of module CVSROOT to the BlooGee CVS repository, changing 11 files

  posted by nobody 1263 days ago