42 KiB

Raw Blame History

🔥 RSS Guard Documentation 🔥

Welcome to RSS Guard documentation. You can find everything about the application right here.
There is a Discord server for user communication.

What is RSS Guard?
Downloads
Supported Operating Systems
Major Features
Minor Features
For Contributors and Other Topics

What is RSS Guard?

RSS Guard is an open-source cross-platform multi-protocol desktop feed reader. It is able to fetch almost any of the known feed formats, including RSS/RDF/ATOM/JSON. RSS Guard is developed on top of the Qt library.

Downloads

Official place to download RSS Guard is at Github Releases. You can also download the development (beta) build, which is updated automatically every time the source code is updated.

Also, RSS Guard is available for many Linux distributions, and even via Flathub.

I highly recommend to download RSS Guard only from reputable sources.

Supported Operating Systems

RSS Guard is a cross-platform application, and at this point it is known to work on:

Windows 7+
GNU/Linux (including PinePhone and other Linux-based phone operating systems)
macOS 10.10+
OS/2 (ArcaOS, eComStation)

Major Features

Supported Feed Readers

RSS Guard is a multi-account application and supports many web-based feed readers via built-in plugins. One of the plugins, of course, provides the support for standard RSS/ATOM/JSON feeds with the set of features everyone would expect from classic feed reader, like OPML support, etc.

I organized the supported web-based feed readers into an elegant table:

Service	Two-way Synchronization	Intelligent Synchronization Algorithm (ISA) ¹	Synchronized Labels ²	OAuth
Feedly	✅	❌	✅	✅ (only for official binaries)
Gmail	✅	❌	❌	✅
Google Reader API ³	✅	✅	✅	✅ (only for Inoreader)
Nextcloud News	✅	❌	❌	❌
Tiny Tiny RSS	✅	❌	✅	❌

¹ Some plugins support next-gen intelligent synchronization algorithm (ISA) which has some benefits, as it usually offers superior synchronization speed, and transfers much less data over your network connection.

With ISA, RSS Guard only downloads articles which are new or were updated. While the old algorithm usually always fetch all available articles, even if they are not needed, which leads to unnecessary overload of your network connection and RSS Guard.

² Note that labels are supported for all plugins, but for some plugins they are local-only, and are not synchronized with the service. Usually because service itself does not support the feature.

³ Tested services are:

Bazqux
Reedah
Inoreader
TheOldReader
FreshRSS

Article Filtering

Sometimes you need to tweak incoming article - mark them starred, remove ads from their contents or simply ignore them. That's where filtering feature comes in.

Writing article filter

Article filters are fully scriptable and consist of arbitrary JavaScript code which must provide function with prototype:

function filterMessage() { }

The function should be fast enough, and must return values which belong to enumeration FilteringAction. You can either use direct numerical value of each enumerant, for example 2, or you can use self-descriptive name, for example MessageObject.Ignore. There are also names MSG_ACCEPT and MSG_IGNORE as aliases for MessageObject.Accept and MessageObject.Ignore.

Each message/article is accessible in your script via global variable named msg of type MessageObject, see this file for the declaration. Some properties are writeable, allowing you to change contents of the message before it is written to DB. You can mark message important, parse its description, perhaps change author name or even assign some label to it!!!

You can use special placeholders within article filter.

Also, there is a special variable named utils. This variable is of type FilterUtils and offers some useful utility functions for you to use in your filters.

RSS Guard also allows to use the list of labels assigned to each message. You can, therefore, execute actions in your filtering script, based on which labels are assigned to the message. The property is called assignedLabels and is array of Label objects. If you change assigned labels to the message, then the change will be eventually synchronized back to server if respective plugin supports it.

Passed message also offers special function:

Boolean MessageObject.isDuplicateWithAttribute(DuplicationAttributeCheck)

Which allows you to perform runtime check for existence of the message in RSS Guard's database. The parameter is integer value from enumeration DuplicationAttributeCheck and specifies how exactly you want to determine if given message is "duplicate". Again, you can use direct integer values or enumerant names.

For example, if you want to check if there is already another message with same author in database, you should call msg.isDuplicateWithAttribute(MessageObject.SameAuthor). Values of the enumeration can be combined via bitwise | operation in single call, for example like this: msg.isDuplicateWithAttribute(MessageObject.SameAuthor | MessageObject.SameUrl).

Here is the reference of methods and properties of some types available in your filtering scripts.

`MessageObject` class

Type	Name(Parameter)	Return value	Read-only	Description
Property	`assignedLabels`	`Array<Label>`	✅	List of labels assigned to the message/article.
Property	`availableLabels`	`Array<Label>`	✅	List of labels which are currently available and can be assigned to the message. Available in RSS Guard 3.8.1+.
Property	`feedCustomId`	`String`	✅	Service-specific ID of the feed which this message belongs to.
Property	`accountId`	`Number`	✅	RSS Guard's ID of the account activated in the program. This property is highly advanced and you probably do not need to use it at all.
Property	`id`	`Number`	✅	ID assigned to the message in RSS Guard local database.
Property	`customId`	`String`	✅	ID of the message as provided by the remote service.
Property	`title`	`String`		Title of the message.
Property	`url`	`String`		URL of the message.
Property	`author`	`String`		Author of the message.
Property	`contents`	`String`		Contents of the message.
Property	`rawContents`	`String`		This is RAW contents of the message as it was obtained from remote service/feed. You can expect raw `XML` or `JSON` element data here. Note that this attribute has some value only if `runningFilterWhenFetching` returns `true`. In other words, this attribute is not persistently stored inside RSS Guard's DB. Also, this attribute is artificially filled with ATOM-like data when testing the filter.
Property	`score`	`Number`		Arbitrary number in range <0.0, 100.0>. You can use this number to sort messages in a custom fashion as this attribute also has its own column in messages list.
Property	`created`	`Date`		Date/time of the message.
Property	`isRead`	`Boolean`		Is message read?
Property	`isImportant`	`Boolean`		Is message important?
Property	`isDeleted`	`Boolean`		Is message placed in recycle bin?
Method	`isDuplicate(DuplicationAttributeCheck)`	`Boolean`		Allows you to test if this particular message is already stored in RSS Guard's DB.
Method	`assignLabel(String)`	`Boolean`		Assigns label to this message. The passed `String` value is the `customId` property of `Label` type. See its API reference for relevant info.
Method	`deassignLabel(String)`	`Boolean`		Removes label from this message. The passed `String` value is the `customId` property of `Label` type. See its API reference for relevant info.
Property	`runningFilterWhenFetching`	`Boolean`	✅	Returns `true` if current run of the message filter is done when message is fetched. Returns `false` if message filter runs manually, for example from `Article filters` window.

`Label` class

Type	Name	Return value	Read-only	Description
Property	`title`	`String`	✅	Label title.
Property	`customId`	`String`	✅	Service-specific ID of this label. This ID is used as unique identifier for the label and is particularly useful if you want to assign/unassign the message label.
Property	`color`	`Color`	✅	Label color. Note that type `color` has its documentation here.

`FilteringAction` enum

Enumerant name	Integer value	Description
`Accept`	1	Message is accepted and will be added to DB or updated in DB.
`Ignore`	2	Message is ignored and will NOT be added or updated in DB, but will also not be purged if already exists.
`Purge`	4	Existing message is purged from the DB completely. Behavior is the same as `Ignore` when there is new incoming message.

Note that MessageObject attributes which can be synchronized with service are synchronized even if you return Purge or Ignore. In other words, even if your filter ignores the message, you can still tweak its properties which would be synchronized back to your server.

`DuplicationAttributeCheck` enum

Enumerant name	Integer value	Description
`SameTitle`	1	Check if message has same title as some another messages.
`SameUrl`	2	Check if message has same URL as some another messages.
`SameAuthor`	4	Check if message has same author as some another messages.
`SameDateCreated`	8	Check if message has same date of creation as some another messages.
`AllFeedsSameAccount`	16	Perform the check across all feeds from your account, not just "current" feed.
`SameCustomId`	32	Check if message with same custom ID exists in RSS Guard's DB.

`utils` object

Type	Name(Parameter)	Return value	How to call	Description
Method	`hostname()`	`String`	`utils.hostname()`	Returns name of your PC.
Method	`fromXmlToJson(String)`	`String`	`utils.fromXmlToJson('<h1>hello</h1>')`	Converts `XML` string into `JSON`.
Method	`parseDateTime(String)`	`Date`	`utils.parseDateTime('2020-02-24T08:00:00')`	Converts textual date/time representation into proper `Date` object.

Examples

Accept only messages/articles from "Bob", while also mark them "important":

function filterMessage() {
  if (msg.author == "Bob") {
    msg.isImportant = true;
    return MessageObject.Accept;
  }
  else {
    return MessageObject.Ignore;
  }
}

Replace all "dogs" with "cats"!

function filterMessage() {
  msg.title = msg.title.replace("dogs", "cats");
  return MessageObject.Accept;
}

Use published element instead of updated element (for ATOM entries only):

function filterMessage() {
  // Read raw contents of message and
  // convert to JSON.
  json = utils.fromXmlToJson(msg.rawContents);
  jsonObj = JSON.parse(json)

  // Read published date and parse it.
  publishedDate = jsonObj.entry.published.__text;
  parsedDate = utils.parseDateTime(publishedDate);

  // Set new date/time for message and
  // proceed.
  msg.created = parsedDate;
  return MessageObject.Accept;
}

Dump RAW data of each message to RSS Guard's debug output:

function filterMessage() {
  console.log(msg.rawContents);
  return MessageObject.Accept;
}

When running the above script for Tiny Tiny RSS, it produces the following debug output:

...
time="    34.360" type="debug" -> feed-downloader: Hooking message took 4 microseconds.
time="    34.361" type="debug" -> {"always_display_attachments":false,"attachments":[],"author":"Aleš Kapica","comments_count":0,"comments_link":"","content":"<p>\nNaposledy jsem psal o čuňačení v MediaWiki asi před půl rokem, kdy jsem chtěl upozornit na to, že jsem přepracoval svoji původní šablonu Images tak, aby bylo možné používat výřezy z obrázků a stránek generovaných z DjVu a PDF dokumentů. Blogpost nebyl nijak extra hodnocen, takže mě vcelku nepřekvapuje, jak se do hlavní vývojové větve MediaWiki dostávají čím dál větší prasečiny.\n</p>","feed_id":"5903","feed_title":"abclinuxu - blogy","flavor_image":"","flavor_stream":"","guid":"{\"ver\":2,\"uid\":\"52\",\"hash\":\"SHA1:5b49e4d8f612984889ba25e7834e80604c795ff8\"}","id":6958843,"is_updated":false,"labels":[],"lang":"","link":"http://www.abclinuxu.cz/blog/kenyho_stesky/2021/1/cunacime-v-mediawiki-responzivni-obsah-ii","marked":false,"note":null,"published":false,"score":0,"tags":[""],"title":"Čuňačíme v MediaWiki - responzivní obsah II.","unread":true,"updated":1610044674}
time="    34.361" type="debug" -> feed-downloader: Running filter script, it took 348 microseconds.
time="    34.361" type="debug" -> feed-downloader: Hooking message took 4 microseconds.
time="    34.361" type="debug" -> {"always_display_attachments":false,"attachments":[],"author":"kol-ouch","comments_count":0,"comments_link":"","content":"Ahoj, 1. 6. se blíží, tak začínám řešit co s bambilionem fotek na google photos. \n<p class=\"separator\"></p>\nZa sebe můžu říct, že gp mi vyhovují - ne snad úplně tím, že jsou zadarmo, ale hlavně způsobem práce s fotkami, možnostmi vyhledávání v nich podle obsahu, vykopírování textu z nich, provázaností s mapami, recenzemi, možnostmi sdílení, automatickým seskupováním a podobně.","feed_id":"5903","feed_title":"abclinuxu - blogy","flavor_image":"","flavor_stream":"","guid":"{\"ver\":2,\"uid\":\"52\",\"hash\":\"SHA1:1277107408b159882b95ca7151a0ec0160a3971a\"}","id":6939327,"is_updated":false,"labels":[],"lang":"","link":"http://www.abclinuxu.cz/blog/Co_to_je/2021/1/kam-s-fotkama","marked":false,"note":null,"published":false,"score":0,"tags":[""],"title":"Kam s fotkama?","unread":true,"updated":1609750800}
...

For RSS 2.0 message, the result might look as follows:

...
time="     3.568" type="debug" -> feed-downloader: Hooking message took 6 microseconds.
time="     3.568" type="debug" -> <item>
<title><![CDATA[Man Utd's Cavani 'not comfortable' in England, says father]]></title>
<description><![CDATA[Manchester United striker Edinson Cavani "does not feel comfortable" and could move back to his native South America, his father said.]]></description>
<link>https://www.bbc.co.uk/sport/football/56341983</link>
<guid isPermaLink="true">https://www.bbc.co.uk/sport/football/56341983</guid>
<pubDate>Tue, 09 Mar 2021 23:46:03 GMT</pubDate>
</item>

time="     3.568" type="debug" -> feed-downloader: Running filter script, it took 416 microseconds.
...

Write details of available labels and assign the first label to the message:

function filterMessage() {
  console.log('Number of assigned labels: ' + msg.assignedLabels.length);
  console.log('Number of available labels: ' + msg.availableLabels.length);

  var i;
  for (i = 0; i < msg.availableLabels.length; i++) {
    var lbl = msg.availableLabels[i];

    console.log('Available label:');
    console.log('  Title: \'' + lbl.title + '\' ID: \'' + lbl.customId + '\'');
  }

  if (msg.availableLabels.length > 0) {
    console.log('Assigning first label to message...');
    msg.assignLabel(msg.availableLabels[0].customId);

    console.log('Number of assigned labels ' + msg.assignedLabels.length);
  }

  console.log();
  return MessageObject.Accept;
}

Make sure that your receive only one message/article with particular URL across all your feeds (from same plugin) and all other messages with same URL are subsequently ignored:

function filterMessage() {
  if (msg.isDuplicateWithAttribute(MessageObject.SameUrl | MessageObject.AllFeedsSameAccount)) {
    return MessageObject.Ignore;
  }
  else {
    return MessageObject.Accept;
  }
}

Remove "ads" from messages received from Inoreader. Method simply removes div which contains the advertisement:

function filterMessage() {
  msg.contents = msg.contents.replace(/<div>\s*Ads[\S\s]+Remove<\/a>[\S\s]+adv\/www\/delivery[\S\s]+?<\/div>/im, '');

  return MessageObject.Accept;
}

Websites Scraping

[CAUTION!] Only proceed if you consider yourself a power user and you know what you are doing!

RSS Guard offers additional advanced features inspired by Liferea.

You can select source type of each feed. If you select URL, then RSS Guard simply downloads feed file from given location and behaves like everyone would expect.

However, if you choose Script option, then you cannot provide URL of your feed and you rely on custom script to generate feed file and provide its contents to standard output. Resulting data written to standard output should be valid feed file, for example RSS or ATOM XML file.

Fetch it now button also works with Script option. Therefore, if your source script and (optional) post-process script in cooperation deliver a valid feed file to the output, then all important metadata, like title or icon of the feed, can be discovered ✨ automagically ✨.

Any errors in your script must be written to error output.

Note that you must provide full execution line to your custom script, including interpreter binary path and name and all that must be written in special format <interpreter>#<argument1>#<argument2>#..... The # character is there to separate interpreter and individual arguments. I had to select some character as separator because simply using space is not that easy as it might sound, as sometimes space could be a part of an argument itself.

If everything went well, script must return 0 as the process exit code, or a non-zero exit code if some error happened.

Binary name (interpreter) must be always be specified, while arguments not. Be very careful when quoting arguments. Some examples of valid and tested execution lines are:

Command	Explanation
`bash#-c#curl https://github.com/martinrotter.atom`	Download ATOM feed file using Bash and Curl.
`Powershell#Invoke-WebRequest 'https://github.com/martinrotter.atom' \| Select-Object -ExpandProperty Content`	Download ATOM feed file with Powershell.
`php#tweeper.php#-v#0#https://twitter.com/NSACareers`	Scrape Twitter RSS feed file with Tweeper. Tweeper is the utility which is able to produce RSS feed from Twitter and other similar social platforms.

Note that the above examples are cross-platform and you can use the exact same command on Windows, Linux or macOS, if your operating system is properly configured.

RSS Guard offers placeholder %data% which is automatically replaced with full path to RSS Guard's user data folder, allowing you to make your configuration fully portable. You can, therefore, use something like this as source script line: bash#%data%/scripts/download-feed.sh.

Also, working directory of process executing the script is set to point to RSS Guard's user data folder.

There are some examples of website scrapers here, most of them are written in Python 3, thus their execution line is similar to python#script.py. Make sure to examine each script for more information on how to use it.

After your source feed data are downloaded either via URL or custom script, you can optionally post-process the data with one more custom script, which will take raw source data as input and must produce processed valid feed data to standard output while printing all error messages to error output.

Format of post-process script execution line is the same as above.

Typical post-processing filter might do things like advanced CSS formatting, localization of content to another language, downloading of full articles, some kind of filtering or removing ads.

It's completely up to you if you decide to only use script as Source of the script or separate your custom functionality between Source script and Post-process script. Sometimes you might need different Source scripts for different online sources and the same Post-process script and vice versa.

Notifications

RSS Guard allows you to configure behavior of desktop notifications. There is a number of events which can be configured:

New (unread) articles fetched
Fetching of articles is started
Login OAuth tokens are refreshed
New RSS Guard version is available
etc.

Your notification can also play .wav sounds which you can place under your user data folder and use them via special placeholder. Other audio formats are not supported.

Database Backends

RSS Guard offers switchable database backends which hold your data. At this point, two backends are available:

MariaDB
SQLite (default)

SQLite backend is very simple to use, no further configuration is needed and all your data is stored in single file

<user-data-root-folder>\database\local\database.db

Check About RSS Guard -> Resources dialog to find more info on significant paths used. This backend offers "in-memory" database option, which automatically copies all your data into RAM when application launches, and then works solely with that RAM data, which makes RSS Guard incredibly fast. Data is also written back to database file when application exits. Note that this option should be used very rarely because RSS Guard should be fast enough with classic SQLite persistent DB files. Only use this with a huge amount of article data, and when you know what you are doing.

MariaDB (MySQL) backend is there for users, who want to store their data in a centralized way. You can have single server in your network and use multiple RSS Guard instances to access the data.

For database-related configuration see Settings -> Data storage dialog.

User Data Portability

One of the main goals of RSS Guard is to have local application data portable (relocatable) so that they can be use across all supported operating systems.

RSS Guard is able to run in two modes:

Default mode is "non-portable" mode, where user data folder is placed in user-wide "config directory" (this is C:\Users\<user>\AppData\Local on Windows). If subfolder with file

RSS Guard 4\data\config\config.ini

exists, then this user folder is used.

The other mode is that user data folder is placed in subfolder data4 in the same directory as RSS Guard binary (rssguard.exe on Windows). This "portable" mode is automatically enabled if "non-portable" mode detection fails.

User data folder can host your custom icon themes in icons subfolder and custom skins in skins subfolder.

`%data%` placeholder

RSS Guard stores its data and settings in single folder. What exact folder it is is described here. RSS Guard allows you to use the folder programmatically in some special contexts via %data% placeholder. You can use this placeholder in these RSS Guard contexts:

Contents of your article filters - you can, therefore, place some scripts under your user data folder and include them via JavaScript into your article filter.
Contents of each file included in your custom skins. Note that in this case, the semantics of %data% are little changed and %data% points directly to base folder of your skin.
source and post-process script attributes of for scraping feed - you can use the placeholder to load scripts to generate/process feed from user data folder.
Notifications also support the placeholder in path to audio files which are to be played when some event happens. For example you could place audio files in your data folder and then use them in notification with %data%\audio\new-messages.wav. See more about notifications here.

Built-in Web Browser with AdBlock

RSS Guard is distributed in two variants:

Standard package with WebEngine-based bundled article viewer: This variant displays messages/articles with their full formatting and layout in embedded Chromium-based web viewer. This variant of RSS Guard should be nice for everyone. Also, installation packages are relatively big.

Lite package with simple text-based article viewer: This variant displays message/article in much simpler and more lightweight text-based component. All packages of this variant have nowebengine keyword in their names. Layout and formatting of displayed message is simplified, no big external web viewers are used, which results in much smaller installation packages, much smaller memory footprint and increased privacy of the user, because many web resources are not downloaded by default like pictures, JavaScript and so on. This variant of RSS Guard is meant for advanced users.

If you're not sure which version to use, use the WebEngine-based RSS Guard.

AdBlock

Web-based variant of RSS Guard offers ad-blocking functionality via Adblocker. Adblocker offers similar performance to uBlock Origin.

You need to have have Node.js with NPM (which is usually included in Node.js installer) installed to have ad-blocking in RSS Guard working. Also, the implementation requires additional npm modules to be installed. You see the list of needed modules near the top of this file.

I understand that the above installation of needed dependencies is not trivial, but it is necessary evil to have up-to-date and modern implementation of AdBlock in RSS Guard. Previous, "C++"-based, implementation was buggy, quite slow, and hard to maintain.

You can find elaborate lists of AdBlock rules here. You can just copy direct hyperlinks to those lists and paste them into the "Filter lists" text-box as shown below. Remember to always separate individual links with newlines. Same applies to "Custom filters", where you can insert individual filters, for example filter "idnes" to block all URLs with "idnes" in them.

The way ad-blocking internally works is that RSS Guard starts local HTTP browser which provides ad-blocking API, which is subsequently called by RSS Guard. There is some caching done in between, which speeds up some ad-blocking decisions.

Minor Features

Files Downloader

RSS Guard offers simple embedded file downloader.

You can right click on any item in embedded web browser and hit Save as button. RSS Guard will then automatically display the downloader, and will download your file. This feature works in both RSS Guard variants.

You can download up to 6 files simultaneously.

Labels

RSS Guard supports labels (tags). Any number of tags can be assigned to any article.

Note that tags in some plugins are synchronizable. While labels are synchronized with these services, sometimes they cannot be directly created via RSS Guard. In this case, you have to create them via web interface of the respective service, and only after that perform Synchronize folders & other items, which will fetch newly created labels too.

Labels can be easily added via Labels root item.

New label's title and color can also be chosen.

Unassigning a message label might easily be done through the message viewer.

Note that unassigning a message labels is also synchronized at regular intervals (with services that support label synch).

Also, message filters can assign or remove labels to/from messages.

Skins

RSS Guard is a skin-able application. Its GUI can be almost completely styled with stylesheets.

You can select style and skin in settings category User interface.

RSS Guard encapsulates styling capabilities via skins feature. Each skin is placed in its own folder and must contain several files. There are some built-in skins, but you can place your custom skins in your user data folder. You can find exact path to your user data folder in About dialog. Note that there must be subfolder skins. Create it if it does not exist and place your custom skins inside.

The base for your custom skin may serve an empty "plain" skin. Look the README file there, for some commentaries to it.

So for example if your new skin is called greenland, you must place it in folder

<user-data-path>\skins\greenland

As stated above, there are several files in each skin:

metadata.xml - XML file with some basic information about the skin's name, author etc. Also,
theme.css - Qt stylesheet file.
html_*.html - These are (partial) HTML files which are used by RSS Guard in various situations like displaying article or error page.

GUI Tweaking

RSS Guard's main window appearance can be tweaked in many ways. You can hide menu, toolbars, status bar, you can also change orientation of article viewer to suit widescreen devices.

Command Line Interface

RSS Guard offers CLI (command line interface). For overview of its features, run rssguard --help in your terminal. You will see the overview of the interface.

rssguard [options] [url-1 ... url-n]

Options:
  -l, --log <log-file>           Write application debug log to file. Note that
                                 logging to file may slow application down.
  -d, --data <user-data-folder>  Use custom folder for user data and disable
                                 single instance application mode.
  -s, --no-single-instance       Allow running of multiple application
                                 instances.
  -n, --no-debug-output          Completely disable stdout/stderr outputs.
  -?, -h, --help                 Displays help on commandline options.
  --help-all                     Displays help including Qt specific options.
  -v, --version                  Displays version information.

Arguments:
  urls                           List of URL addresses pointing to individual
                                 online feeds which should be added.

RSS Guard can add feeds passed as URLs via command line arguments. Feed URI scheme is supported, so that you can call RSS Guard like this:

rssguard.exe "feed://archlinux.org/feeds/news"
rssguard.exe "feed:https//archlinux.org/feeds/news"
rssguard.exe "https://archlinux.org/feeds/news"

So in order to comfortably add feed directly to RSS Guard from you browser without copying its URL manually, you have to "open" RSS Guard "with" feed URL passed as parameter. There are extensions which can do it.

For Contributors

Donations

You can support author of RSS Guard via donations.

Compiling RSS Guard

RSS Guard is C++ application and all common build instructions can be found in top of project file.

Plugin API

RSS Guard offers simple C++ API for creating new service plugins. All base API classes are in folder abstract. User must subclass and implement all interface classes:

Class	Purpose
`ServiceEntryPoint`	Very base class which provides basic information about the plugin name, author, etc. It also provides methods which are called when new account should be created and when existing accounts should be loaded from database.
`ServiceRoot`	This is the core "account" class which represents an account node in feed's list, and offers interface for all critical functionality of a plugin, including handlers which are being called with a plugin's start/stop, marking messages as read/unread/starred/deleted, unassigning labels, etc.

API is reasonably simple to understand but relatively large. Sane default behavior is employed where it makes sense.

Perhaps the best approach to use when writing new plugin is to copy existing one and start from there.

Note that RSS Guard can support loading of plugins from external libraries (.dll, .so, etc.) but the functionality must be polished because so far all plugins are directly bundled into the application as no one really requested run-time loading of plugins so far.

Reporting Bugs or Feature Requests

Please report all issues/bugs/ideas to Issues section. Describe your problem as precisely as possible, along with steps taken leading up to the issue occurring.

If you report any bug, you must provide application debug log. So make sure to start RSS Guard from command line (cmd.exe on Windows) with --log switch and path where you want to store log file, for example rssguard.exe --log '.\rssguard.log' which will save log file into your RSS Guard folder. After you've started RSS Guard this way, then reproduce your problem and upload log file to the ticket.

Also, for some broader questions or general ideas, use discussions rather than issues.

Localization

RSS Guard currently includes many localizations.

If you are interested in creating translations for RSS Guard, then do this:

Go here and check status of currently supported localizations.
Login (you can use social networks to login) and work on existing translations. If no translation team for your country/language exists, then ask for creating of localization team via the website.

All translators commit themselves to keep their translations up-to-date. If some translations are not updated by their authors regularly, and only a small number of strings is translated then those translations along with their teams will eventually be REMOVED from the project!!! At least 50% of strings must be translated for translation to be added to project.

Migrating data

RSS Guard automatically migrates all your user data if you install newer minor version, for example if you update from 3.7.5 to 3.9.1.

If you decide to upgrade to new major version, for example from 3.x.x to 4.x.x, then you cannot use your existing user data as major versions are declared as backwards incompatible, so such data transition are not supported.

Migrating user data from `3.9.2` to `4.x.x`

Only proceed if you consider yourself to be a SQL power user and you know what you are doing!

Also, make sure that last RSS Guard from 3.x.x line you used with your data was the most up-to-date 3.9.2 version.

Here is short DIY manual on how to manually update your database.db file to 4.x.x format. Similar approach can be taken if you use MariaDB database backend.

Here are SQLs for old schema and new schema.

Converting `*Accounts` tables

In 3.x.x each plugin/account type had its own table where it kept your login usernames, service URLs etc. In 4.x.x all plugins share one table Accounts and place account-specific data into custom_data column. You simply can take all rows from any *Accounts table (for example TtRssAccounts) and insert them into Accounts, keeping all columns their default values, except of type, which must have one of these values:

std-rss - for standard RSS/ATOM feeds.
tt-rss - for Tiny Tiny RSS.
owncloud - for Nextcloud News.
greader - For all Google Reader API services, including Inoreader.
feedly - for Feedly.
gmail - for Gmail.

Then you need to go to Edit dialog of your account in RSS Guard (once you complete this migration guide) and check for all missing login information etc.

Also, once you add any rows the Accounts table, your row will be assigned unique id value which is integer and is used as foreign key in other DB tables, via column account_id.

Converting `Feeds` table

There are some changes in Feeds table:

url column is now named source,
source_type, post_process, encoding, type, protected, username, password columns are removed and their data are now stored in JSON-serialized form in new column custom_data. Here is sample value of custom_data:

{
  "encoding": "UTF-8",
  "password": "AwUujeO2efOgYpX3g1/zoOTp9JULcLTZzwfY",
  "post_process": "",
  "protected": false,
  "source_type": 0,
  "type": 3,
  "username": ""
}

Pay attention to account_id column as this column is the ID of your account as stated in the above section.

Converting `Messages` table

Columns were reordered and other than that new column score with sane default value was added. Therefore you can simply copy your data in a column-to-column mode.