YaCy '#[clientname]#': News Monitor

#(table)# :: #(/table)# #%env/templates/metas.template%#
#%env/templates/header.template%# #%env/templates/submenuComputation.template%# #(page)#

## Overview

::

## Incoming News

::

## Processed News

::

## Outgoing News

::

## Published News

#(/page)# #(table)#

This is the YaCyNews system (currently under testing).

The news service is controlled by several entry points:

- A crawl start with activated remote indexing will automatically create a news entry. Other peers may use this information to prevent double-crawls from the same start point. A table with recently started crawls is presented on the Index Create - page
- A change in the personal profile will create a news entry. You can see recently made changes of profile entries on the Network page, where that profile change is visualized with a '*' beside the 'P' (profile) - selector.
- Publishing of added or modified translation for the user interface. Other peers may include it in their local translation list. To publish a translation, use the integrated translation editor to add a translation and publish it afterwards.

More news services will follow.

Above you can see four menues:

- Incoming News (#[insize]#): latest news that arrived your peer. Only these news will be used to display specific news services as explained above. You can process these news with a button on the page to remove their appearance from the IndexCreate and Network page
- Processed News (#[prsize]#): this is simply an archive of incoming news that you removed by processing.
- Outgoing News (#[ousize]#): here your can see news entries that you have created. These news are currently broadcasted to other peers. you can stop the broadcast if you want.
- Published News (#[pusize]#): your news that have been broadcasted sufficiently or that you have removed from the broadcast list.

::

| Originator | Created | Category | Received | Distributed | Attributes
#{list}#
| #[ori]# | #[cre]# | #[cat]# | #[rec]# | #[dis]# | #[att]#
#{/list}#

#(/table)# #%env/templates/footer.template%#