Are you by any chance a manga fan? Does your favourite manga website not publish RSS feeds? Then you might be interested in this scraping example for mangas hosted at mangakatana.com.

This release brings small improvements to the trayicon plugin and content filtering using DOMPurify which should increase security against XSS attacks via feeds providing rich HTML content.

This release brings small fixes and a rework of the trayicon plugin.

This project went 20 this year. I do fondly remember having announced the most early releases on freshmeat.net which back then was the way to find out about good and active open source projects. Since those days many awesome contributors helped developing and maintaining Liferea to have the extensive feature set it has. For me the contributors suddenly appearing and without any conditions helping on the project is the most motivating and amazing thing about developing in open source.

This is a bugfix release for 1.15. Please upgrade!

Changes

This is a bugfix release. It provides an important stability fix regarding feed parsing. Kudos to Rich Coe for debugging and fixing the issue!

This is a new feature release. It introduces the long awaited switch to libsoup3 and libwebkit2gtk-4.1. Thanks to many testers helping testing the latest code from git some errors were ironed out already. Still there is an issue remaining where feed updates are getting stuck when updating while DNS resolution/Wifi/network… fails. Please comment if you also experience this issue!

If you are native German speaker and want to consume public TV station content using Liferea you can do so by following the RSS feeds provided by https://mediathekviewweb.de/.

This is a bugfix release for 1.14. Please upgrade!

This is the first release of the new unstable line 1.15. The current idea is to release a bit faster than every two years. So not so much features will be introduced before 1.16

This is another stabilizitation release for 1.14. I’m cautiously optimistic that we have solved most of the instabilities now :-)

1.14 is not as stable yet as intended and is suffering from startup race conditions. This bugfix release tries to further eliminate those issues.

This is another 1.14 bugfix release to address a crash affecting some users and a build issue when running tests.

This is a stability fix for 1.14.1. The fix of CVE-2023-1350 in 1.14.1 did contain a memory error that leads to crashes. Sorry about that. Please upgrade to avoid the problem!

This is an important security fix for 1.14. Please upgrade!

This is an important security fix for 1.12. Please upgrade!

Here comes the newest stable release line of Liferea 1.14!

This is a new release candidate for 1.14. It contains many bugfixes and translation updates. This will be the last release candidate. Next release will be 1.14.0.

This is the second release candidate for the next stable release line 1.14. There will be probably one more release candidates until 1.14.0.

This is the first release candidate for the next stable release line 1.14. There will be probably 2 more release candidates until 1.14.0.

When you upgrade to Mesa 22 and run on an Intel Iris graphic card you can run into a bug that suddenly no headline content is rendered anymore. This bug seems to be in WebkitGtk 4.0 up to 2.36: https://bugs.webkit.org/show_bug.cgi?id=238513 and probably will be solved in an upcoming WebkitGtk release.

Here comes a new development release in the 1.13 line.

Here comes a new development release in the 1.13 line.

This is a new development release mostly focusing on usability. Thanks for the many many contributions!

In recent weeks there are more issues with the WebKitGTK HTML renderer widget used by Liferea. Here is some insight on these problems and if you are impacted how to workaround…

This is a new development release mostly focusing on usability. Thanks for all the contributed bugfixes!

This is a new development release mostly focussing on usability. There is also a fix of a long-standing bug that search folder searches were not case-insensitive as documented.

It’s Christmas so let’s have a small present for everyone. Here is a new unstable release.

This is a followup to the post Better Favicons Part 1. While the change from April this year was about storing all favicons in a large resolution, to ensure there is no upscaling when presented in ‘Wide View’, this is about finding better quality favicons as used by iOS, Android and Microsoft Windows.

Status of the headerbar plugin

This is a new 1.13 development release with a lot of great improvements including zoom reset using Ctrl-0, enabling Webkit Intelligent Tracking Protection, CSS color updated on theme switch, progress bar support when loading web pages and many other improvements.

This is a new development release adding a new major feature “Reader mode”. “Reader mode” is always on filtering all feed content and HTML5 enriched content to remove ads, visual noise and any left-over website navigation elements that might end up in your feeds content.

This is a maintenance release fixing a translation bug and a Youtube video embedding issue.

This is a new unstable feature release for the 1.13 development series.

One known issue in Lifera v1.12 is the low resolution of favicons when using the 3-pane wide view mode. In this mode favicons are displayed larger to give a visual counter weight to the text excerpts shown below the headline.

New feature: HTML5-based website scraping fallback

This is the first release in the new unstable line. While this release does not have any large changes or new features there will be breaking changes soon :-)

When you are not satisfied with the menu key bindings defined by Liferea do not despair it is easy to change them!

This trick is valid for Liferea versions 1.12 to 1.15.

Edit Accels Plugin

There is a plugin by frequent Liferea contributor Mozbugbox allowing you to change keybindings. It is not installed per-default, so install it via Tools -> Plugin Installer. In the plugin preferences click Dump Accels to create a key binding file.

Open the keybinding file in ~/.local/share/liferea/plugins/accels/accels.txt in your favourite editor. This file will be now be read upon Liferea startup to set key bindings and contains lines like these:

[...]
# ["app.next-read-item", []]
["app.next-unread-item", ["<Primary>n"]]
# ["app.open-item-enclosure", []]
# ["app.open-link-in-browser", []]
[...]

Note how only app.next-unread-item has a defined key binding Ctrl-N and for example app.next-read-item has none.

To change a key binding:

• First remove any ‘#’ at the start of the line
• Then enter a valid key binding. Choose prefixes like <Primary> (for Ctrl), <Alt>, <Shift> as needed and append the key after it.
• Ensure the key binding you defined is not used elsewhere in the file

Recent Liferea Tricks

• #1: Middle Mouse Button
• #2: Drag and Drop URLs
• #3: Feed Auto Discovery
• #4: Full Screen
• #5: Privacy with SOCKS Proxy
• #6: Website Scraping
• #7: Force Read Full Posts
• #8: Change Menu Accelerators
• #9: Skimming Through the Headlines
• #10: Custom CSS for Article Rendering

This tutorial part is about how to localize core Python plugins so contributors can translate the user interface.

Here is another How-To on GTK/libpeas plugin development. This time it is on how to use the GTK Inspector to dive into application details.

Welcome to a new installment of the plugins tutorial! Todays issue will cover menu modifications. This allows you to add new menu options for features you introduce with your plugin.

Let’s continue the plugin tutorial! The last installement was on how plugins work and how to create the boilerplate for a new plugin. Now let’s look into how to access Liferea UI elements and how to modify them.

Some time ago a fellow Liferea user asked about documentation on writing Liferea plugins. I see the need and the benefit and want to start doing so with a series of blog posts that later can be compiled into a tutorial to be included on the website/sources.

Plugins with GObject Introspection

First it is important to know that Liferea 1.10+ uses GObject Introspection (GI) and libpeas to allow implementing plugins. This quote from the GNOME wiki explain how GI works:

GObject introspection is a middleware layer between C libraries (using GObject) and language bindings. The C library can be scanned at compile time and generate a metadata file, in addition to the actual native C library. Then at runtime, language bindings can read this metadata and automatically provide bindings to call into the C library.

The important point is: by Liferea using GI (as all GNOME applications and many other GTK applications do now) plugins can be written in practically any scripting language. Most users seem to favour Python and all current plugins included with the Liferea sources are in Python. Note that this tutorial will also focus on Python only.

How are plugins triggered from within Liferea?

Ok, I can write a script in Python! How will Liferea run it and when?

This is where libpeas comes in, which is a basic library to implement a plugin system. If you click the preferences dialog and switch to the “Plugins” button you see a dialog provided by the PeasGtkPluginsManager class of libpeas. Detection, activation and configuration of plugins is handled by libpeas.

Now for the “When?” question: To properly allow applications to hook plugins into different parts of the applications libpeas allow an application to define one or more so called “Activatable” interfaces.

For simplicity for Liferea I decided to only support a LifereaShellActivatable interface. This means all plugins are activated together with the LifereaShell instance (src/ui/liferea_shell.c). This class represents the main application window holding all widgets. So when your plugin gets activated all widgets exist and you can access everything like extending or modifying the GUI, changing settings, everything you can think of.

Note: in the code there are two more interfaces:

• LifereaAuthActivatable
• LifereaMediaPlayerActivatable

that are used to implement two important features (GNOME keyring support and a simple media player). Feel free to use those two, but be aware that they work differently and activate at other times and not just once as the LifereaShellActivatable.

Using LifereaShellActivatable

If you script in Python using LifereaShellActivatable means simply deriving a new class from it. For example:

from gi.repository import GObject, Peas, PeasGtk, Gtk, Liferea, Gdk

class ExamplePlugin (GObject.Object, Liferea.ShellActivatable):
    __gtype_name__ = 'ExamplePlugin'

    object = GObject.property (type=GObject.Object)
    shell = GObject.property (type=Liferea.Shell)

    def do_activate (self):
        # Do something here...

    def do_deactivate (self):
        # Maybe do somethin here too...

The activate() and deactivate() methods are required by libpeas and provide you with the starting points to do stuff. By fetching the Liferea.Shell instance you gain access to the main window. Using this you can both lookup widgets or other Liferea classes like the Liferea.FeedList to perform actions against business objects of Liferea.

Providing a plugin configuration

Along with the actual plugin code libpeas requires a plugin configuration file defining the language the plugin is implemented with and metadata (name, description, website…) for this plugin. Such a file looks like this:

[Plugin]
Module=example
Loader=python3
IAge=2
Name=Example Plugin
Description=Illustrates how to implement plugins in Liferea
Authors=Lars Windolf <[email protected]>
Copyright=Copyright © 2014 Lars Windolf
Website=https://lzone.de/liferea/
Help=https://lzone.de/liferea/

Most important is the Loader setting indicating the correct scripting language and the Module setting which together with the Loader setting as python3 indicates that our plugin script is to be named “example.py”. Both the “example.py” plugin script and its example.plugin config file needs to be put into the Liferea plugins directory…

Where to put my plugin script?

There are two possible locations for the plugin script (and it’s configuration file):

• For user provided plugins: usually ~/.local/share/liferea/plugins
• For distro package provided plugins: usually /usr/lib/liferea/plugins

Note that paths can be different with different XDG settings.

When writing and testing don’t bother installing the plugin in the package directories. Just put it in ~/.config/liferea/plugins and fire up Liferea.

More about how to check for activation, debug problems and handling enabling/disabling in the next installment of this tutorial!

Related

Also check out the other plugin tutorial posts

• Plugin Tutorial Part 1 (Plugin Boiler Plate)
• Plugin Tutorial Part 2 (Acessing and modify UI elements)
• Plugin Tutorial Part 3 (Adding menu elements)
• Plugin Tutorial Part 4 (Using GTK inspector)
• Plugin Tutorial Part 5 (Enabling translations for plugins)

I’m not sure about how many users are aware of the feature, but I’m certain it is worth to know about as it saves a lot of clicking and pointing with the mouse. If you are a keyboard user it’s worth knowing about the hotkey to skim through headlines.

The Problem

Not every interesting website provides a feed. Some feeds are broken. And some websites do provide summaries only or no content at all. Besides asking the owner of the website to add a feed or provide more details the only choice left might be to “scrape” the website content.

Starting with Liferea 1.10 you can use a SOCKS proxy. This is possible because Liferea uses the libproxy support provided by the libsoup networking library since 1.10.

What is a SOCKS Proxy?

SOCKS stands for “socket secure” it simply means to use an encrypted connection for whatever you do. Configuring a SOCKS proxy in your desktop environment means that you want all applications to do internet access via an encrypted connection to a safe server you have access to.

Why Use a SOCKS Proxy for Feed Reading?

Well, this of course is useful if you are in an environment were you do not want others to see what you are reading. Be it political blogs or private but unencrypted feeds. Also you simply might not want for your employer to know what servers you are polling news feeds from anyway. There are many good and bad reasons.

How To Use SOCKS Proxy with Liferea and GNOME?

First please note that Liferea supports using a SOCKS proxy only via the GNOME network preferences. Actually it relies on libsoup using the SOCKS settings from there.

Requirements

1. Liferea 1.10+ with GNOME desktop
2. You have a private server to use as a proxy
3. You can connect via SSH to this server

Step 1: Connecting the SOCKS Proxy

There are many ways to do this and many online tutorials. The easiest way is to use SSH like this

ssh -D 8080 <user>@<private server>

Step 2: Client Proxy Configuration

So the first thing to do is to configure Liferea to use the GNOME network settings:

Ensure to set the preferences to proxy auto-detect as shown in the screenshot above. Next go to the GNOME preferences and configure a SOCKS proxy on “localhost” and port “8080” or whatever port you used when you ran the SSH command.

That’s it! Try to update feeds in Liferea and watch out for errors in the status line.

What About Older Liferea Versions?

If you are running an older version of Liferea have a look at this post about a SOCKS proxy workaround using the tool redsocks.

Recent Liferea Tricks

• #1: Middle Mouse Button
• #2: Drag and Drop URLs
• #3: Feed Auto Discovery
• #4: Full Screen
• #5: Privacy with SOCKS Proxy
• #6: Website Scraping
• #7: Force Read Full Posts
• #8: Change Menu Accelerators
• #9: Skimming Through the Headlines
• #10: Custom CSS for Article Rendering

Are you using a smaller laptop and have not much screen real estate? Then wether it is a mail client or web browser or news aggregator using it in full screen mode gets you more content visible. Less space is wasted for menu elements and window decoration.

This is an easy one: Don’t bother entering the exact feed URL when subscribing!

Maybe it is obvious, but you can of course use drag&drop to add feed subscriptions to Liferea.

For all the readers of this development blog I want to share same hidden usability things in Liferea. Today I want to start with using the 3rd mouse button.

Liferea renders articles as HTML content using Webkit (the Safari rendering engine) with colors adapted to the active GTK theme in a somewhat neutral and mail like style. If you dislike it you might want to change aspects of the CSS used to render the articles.

ChangeLog

    * Fixes #287: media:content support broken
      (patch by Leiaz)
    * Fixes #279: Rules not visible in searchdialog
      (patch by Leiaz)
    * Fixes #83: Segfault when sorting feeds in folder
      (patch by Leiaz)
    * Fixes #302: Broken compilation with --disable-notify
      (reported by vostorga)

ChangeLog

    * Fixes Github #194: Add source dialog visually broken
      (reported by k0377)
    * Fixes Github #195: Out-dated documentation on enclosure download
      (reported by brian-in-crawford)
    * Fixes Github #223: Search folder dialog don't show rules
      (reported by Guido Masella)
    * Fixes Github #227: Preference dialog fails to load with latest
      GtkBuilder (patch by Yanko Kaneti)
    * Fixes Github #234: Segmentation fault upon attempting to add an OPML
      (reported by GreenLunar)
    * Fixes compilation error when there is no libnotify
    * Added debugging for #258: Dialog loading issues
      (patch by glitsj16)

ChangeLog

    * Fixes Github #180: Removing item from (v)folder marks all read
      (reported by GreenLunar)
    * Fixes Github #140, #158: Vertical pane placement is forgotten.
      (patch by foresto)
    * Fixes Github #182: Missing config.h include in date.c
      (reported by Paul Gevers)

Download

ChangeLog

ChangeLog

1. This feature will be included starting with release 1.8.15 and 1.10-RC4. Don't worry you can migrate all data even after Google Reader shuts down as all data is kept locally in the Liferea sqlite database. Just do not delete the Google Reader subscription in the meantime.
2. While the conversion is quite simple it is not perfect. There will be item duplication afterwards as the item id matching is not consistent. Google Reader item ids do not match the original item ids so Liferea will produce some duplicates right after converting. But only for those items overlapping at this moment. Please just mark them as read!

I'm using version 1.8.10 on Kubuntu and the "Integrate with the 
messaging menu" doesn't cause the program to appear in the KDE 
system tray. When I click to close the application, I can see that it 
is still running in the background, and when I try to re-open it, it 
immediately pops up the window. I would assume that it is trying to 
integrate itself into a non-existent Gnome system tray instead of 
playing nice with KDE. I feel having this is essential to KDE users.

• inoreader.com
• reedah.com

State of Feedly

State of Digg

State of AOL Reader

Just some information for people wanting to use Liferea with SOCKS.

I'd strongly recommend that you install the package redsocks.  
I've found that this works perfectly, not only for liferea, but for 
*ALL* other applications whether they support SOCKS or not, 
to tunnel all their traffic through a SOCKS (or SSH Tunnel) server.

It is no longer necessary, today, to build SOCKS support into 
every network application, even if you *MUST* use SOCKS.   
For this reason, it's unlikely liferea will ever get SOCKS support. 
There's just no reason for it.

I've just completed testing of liferea + redsocks through a SOCK5 
connection created inside an SSH tunnel and it works just fine.  
I used the guide available here: http://dtbaker.com.au/random-bits/redirect-all-traffic-through-transparent-socks5-proxy-in-linux.html

Thanks for your time.

git clone ssh://[email protected]/p/liferea/code liferea-code

Nothing Gets Lost!

The Future

* Fixes #1056, #1089, #1098: Honor preferences when opening links
  (patch by Daniel Seither)
* Fixes SF #1096: missing installation of liferea.convert file
  (reported by stqn) 
* Fixes Redhat #947358: popup notification only for new items
  (patch by Fabrice Bellet)

Changes in Release Notifications

• the development blog http://lzone.de/liferea
• Freecode Feed http://freecode.com/projects/liferea/releases.atom
• GitHub Feed https://github.com/lwindolf/liferea/releases
• or the mailing list [email protected]

Download Releases

• https://github.com/lwindolf/liferea/releases/download/v1.8.16/liferea-1.8.16.tar.bz2
• https://github.com/lwindolf/liferea/releases/download/v1.10.5/liferea-1.10.5.tar.bz2

* Added an option to convert Google Reader subscriptions
  to local feeds (Lars Windolf)
* Fixes SF #1080: segfault opening attachment due to incorrect g_free()
  (reported by Adam Nielsen)
* Fixes SF #1075: GLib warnings of "string != NULL" assertion failure
  (reported by Simon Kågedal Reimer)
* Fixes search folders including comment items
  (reported by David Willmore)

* Fixes SF #1041: Some GPLv2 license headers were outdated
  (reported by Emmanuel Seyman)
* Fixes SF #1044: tt-rss API changed (we now support only 1.6 API)
  (patch by Sebastian Noel)
* Fixes XHTML errors caused by extra tags from tt-rss
* Update of German translation

        Version 1.8.11

        Please note that due to the SourceForge upgrade bug ticket numbering
        did change. This might be confusing... Old numbers are 7 figures, 
        newer ones only 4!

        * Added Google Plus to social bookmarking options.
        * Fix for Debian #668197: x-www-browser preference not working
          (David Smith)
        * Updated Hebrew translation (Genghis Khan, Yaron Sheffer)
        * Fixes SF #1037: Incorrect notifications for Google Reader 
          (patch by David Smith)
        * Fixes SF #1048: Removed all feedvalidator.org references from FAQ 
          and XSLT as it was reported to host malware.
          (reported by bkat)

ChangeLog

    * Fixes Github #134: Broken default news feed.
      (reported by pvdl)
    * Fixes Github #133: Subscribe into TheOldReader categories
    * Fixes Github #122: Crashes at launch, "segmentation fault"
      (reported by geoffm)
    * Fixes some memory leaks
      (patch by Rich Coe)
    * Fixes Github #145: Incorrect method triggered for 'Launch External'
      (patch by mozbugbox)
    * Fixes Github #48: Window stays hidden on next start after Ctrl+W
      (reported by Jeff Fortin)
    * Expose LifereaHtmlView to GObject Introspection
      (patch by mozbugbox)
    * Improves Google Reader API error handling
    * Now using HTTPS only when accessing TheOldReader
    * Added LifereaNodeSourceActivatable interface to allow plugins
      implementing new node source types.
    * Downgrade enclosure drop warning from Glib warning to debug trace.

Download

    * Fixes Github #81: Inability to add subscriptions
      (reported by GreenLunar)
    * Fixes Javascript links not opening in new browser tabs

    * Updated Hebrew translation (Genghis Khan)
    * Fixes Github #88: Minor DE translation mistake (moraxy)

Download

Change Details

    * Added experimental InoReader support
    * Added experimental Reedah support

    * Fixes SF #1123: Mistakenly claims "TinyTinyRSS source is not self-updating"
      (reported by Dominik Grafenhoher)
    * Fixes SF #1119: Crash on font resize at startup.
      (reported by David Smith)
    * Fixes #1056, #1089, #1098: Honor preferences when opening links
      (patch by Daniel Seither)
    * Fixes #1117: Selecting last unread item in reduced feed list jumps to next feed
      (reported by Bruce Guenter)
    * Fixes missing "Via" metadata type
      (patch by Rich Coe)
    * Fixes incorrect new count reset handling in item_state.c and 
      some of the node source implementations.
    * Fixes SF #1096: missing installation of liferea.convert file
      (reported by stqn) 
    * Fixes SF #1135: liferea-add-feed doesn't process feed:https//
      (patch by Kevin Walke)
    * Fixes SF #1137, #1142: startup race with LifereaHtmlView
      (reported by Yanko Kaneti)
    * Fixes Github #13: Parsing errors not visible with dark themes
      (reported by Steve Kelly)
    * Fixes Github #29: Do not use bold text for feeds/folders with unread items
      in the leftmost treeview (repored by Jeff Fortin)
    * Fixes SF #1141: Liferea does not update feeds with TinyTinyRSS
      (reported by Dominik Grafenhofer, denk_mal, Fabian Henze)
    * Fixes SF #1150: subscription prop/source: not all fields and
      buttons visible (reported by David Smith)
    * Fixes Github #26: RTL comments appear incorrectly
      (reported by yaconf)
    * Fixes Github #27: Images do not autosize to fit the available space
      (reported by Jeff Fortin)
    * Fixes Github #34: Add TinyTinyRSS Enclosure Support
      (reported by Adrixan)
    * Fixes Github #43: "Any of the following" search condition doesn't work
      (reported by Jeff Fortin)
    * Fixes Github #49: Some dialogs scrolling areas do not request enough height
      (reported by Jeff Fortin)
    * Fixes Github #53: Doesn't automatically update feed name and favicon
      for new feed (reported by asl97)
    * Patch SF #224: Update to new libxml2 buffer API
      (Simon Kagedal Reimer)
    * Patch SF #209: Avoid copying list in itemset_merge_items
      (kaloyan)
    * Make Liferea use ETags and send If-None-Match
      (patch by Chris Siebenmann)
    * Support NOCONFIGURE for RPM builds
      (Charles A Edwards)

    * Rename README to README.md
    * Removing libindicate support (to be added as plugin maybe)
    * Removing libnotify support (to be added as plugin maybe)
    * Removing build in tray icon support
    * Added tray icon plugin
    * Added category/folder support for TheOldReader
    * Added folder auto-removal for TinyTinyRSS & TheOldReader

    * Updated README on plugin contribution
    * Updated Arabic translation (Khaled Hosny)

Download

    * Fixes Github #19: non void function should return value
      (reported by kwm81)
    * Fixes SF #1141: Liferea does not update feeds with TinyTinyRSS
      (reported by Dominik Grafenhofer, denk_mal, Fabian Henze)
    * Fixes SF #1150: subscription prop/source: not all fields and
      buttons visible (reported by David Smith)

Download Liferea 1.10.9

* Fixes Github #13: Parsing errors not visible with dark themes
  (reported by Steve Kelly)
* Fixes SF #1137, #1142: startup race with LifereaHtmlView
  (reported by Yanko Kaneti)

Download Liferea 1.10.8

 * Make Liferea use ETags and send If-None-Match
   (patch by Chris Siebenmann)

Download Liferea 1.10.7

* Fixes SF #1135: liferea-add-feed doesn't process feed:https//
  (patch by Kevin Walke)
* Fixes SF #1137: crash on startup in enclosure_list_view_load
  (reported in Redhat #1048499, Fedora #214888)

Download Liferea 1.10.6

* Fixes SF #1123: Mistakenly claims "TinyTinyRSS source is not self-updating"
  (reported by Dominik Grafenhoher)
* Fixes SF #1119: Crash on font resize at startup.
  (reported by David Smith)
* Fixes #1117: Selecting last unread item in reduced feed list jumps to next feed
  (reported by Bruce Guenter)

* Updated Arabic translation (Khaled Hosny)

* Asking for credentials again if TinyTinyRSS login fails
* Asking for TinyTinyRSS credentials only 3 times
* Checking wether TinyTinyRSS base URL is lost
* Added warning on TinyTinyRSS login when source is not self-updating
* "--debug-net --debug-verbose" now traces POST data
* Patch #230 Add GNOME AppData XML (Mikel Olasagasti)

* Updated Italian translation (Gianvito Cavasoli)
* Updated Italian localized feed list (Gianvito Cavasoli)

* Patch SF #222: Make media player seekable
  (Simon Kågedal Reimer)
* Fixes SF #1102: Spelling error in man page
  (David Smith)
* Fixes SF #1104: liferea.desktop missing keywords
  (David Smith)
* Fixes SF #1105: Start Minimized to Tray Does Not Work
  (reported by bitlord)
* Fixes SF #1114: Crashes opening browser on item without link via popup
  (reported by Rich Coe, David Smith)
* Improved handling of broken Atom author information.
  (Lars Windolf)
* Removed dead Google Reader code to avoid doing requests to Google.
  Replaced with dummy source that even allows normal feed updates.
  (Lars Windolf)
* Added hint to FAQ on how to workaround broken Flash support
  (Lars Windolf)
* Dumping feedlist.opml with indentation for readability.
  (suggested by Christoph Temmel and Simon Kågedal Reimer)

ChangeLog

    * Fixes Github #134: Broken default news feed.
      (reported by pvdl)
    * Fixes Github #133: Subscribe into TheOldReader categories
    * Fixes Github #122: Crashes at launch, "segmentation fault"
      (reported by geoffm)
    * Fixes some memory leaks
      (patch by Rich Coe)
    * Fixes Github #145: Incorrect method triggered for 'Launch External'
      (patch by mozbugbox)
    * Fixes Github #48: Window stays hidden on next start after Ctrl+W
      (reported by Jeff Fortin)
    * Expose LifereaHtmlView to GObject Introspection
      (patch by mozbugbox)
    * Improves Google Reader API error handling
    * Now using HTTPS only when accessing TheOldReader
    * Added LifereaNodeSourceActivatable interface to allow plugins
      implementing new node source types.
    * Downgrade enclosure drop warning from Glib warning to debug trace.

Download

	* Fixes Github #86: Support HTTP content negotiation
	  (suggested by DanMan)
	* Fixes Github #98:  Stop calling Atom person constructs w/ URI invalid
	  (patch by Aristotle Pagaltzis)
	* Fixes Github #100: Problems with dark Adwaita theme in GTK 3.14
	  (reported by majutsushi)

Download

    * Fixes Github #53: Doesn't automatically update feed name and favicon
      for new feed (reported by asl97)
    * Fixes Github #67: Missing dist files for documentation
      (patch by Mikel Olasagasti)
    * Fixes Javascript links not opening in new browser tabs

    * Updated French translation (Guillaume Bernard)
    * Updated Hebrew translation (Genghis Khan)

Download

* Added an option to convert Google Reader subscriptions
  to local feeds (Lars Windolf)
* Fixes SF #1080: segfault opening attachment due to incorrect g_free()
  (reported by Adam Nielsen)
* Fixes SF #1075: GLib warnings of "string != NULL" assertion failure
  (reported by Simon Kågedal Reimer)
* Fixes missing shading in 2-pane mode rendering
  (reported by Zoho Vignochi)
* Fixes search folders including comment items
  (reported by David Willmore)

(liferea:3798): GLib-GIO-ERROR **: Settings schema 'net.sf.liferea' does not contain a key named 'last-node-selected'
Trace/breakpoint trap

/usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas

Workarounds

1. Either simply choose "GNOME Default Browser".
2. Or choose "Manual" and set command to

   firefox %s

(liferea:3798): GLib-GIO-ERROR **: Settings schema 'net.sf.liferea' 
does not contain a key named 'last-node-selected'

/usr/bin/glib-compile-schemas /usr/share/glib-2.0/schemas

seahorse

Before

After

    * Patch SF #3407290: Migrate to GSettings
      (by Mikel Olasagasti)
    * Patch SF #3579177: Change .desktop category to News;Feed;
      (by Stanislav Brabec)
    * Fix for Debian #668197: x-www-browser preference not working
      (David Smith)
    * Added slider and time display to media player plugin.
    * Added Google Plus to social bookmarking options.
    * Removing deprecated g_thread_init() call
    * Auto-enable plugins on migration
    * Added missing -a option to manpage
    * Updated manpage to reflect XDG path migration
    * Changing GSettings path from /apps/liferea to /org/gnome/liferea
    * Changes default download thread concurrency from 2 to 3
    * Fixes regression about using the GNOME default font
    * Improves all item/link launching menus to consistently provide
      three options: Tab, Browser and External Browser
    * Fixes SF #1037: Incorrect notifications for Google Reader
      (patch by David Smith)
    * Fixes SF #1048: Removed all feedvalidator.org references from FAQ
      and XSLT as it was reported to host malware.
      (reported by bkat)
    * Fixes SF #1041: Some GPLv2 license headers were outdated
      (reported by Emmanuel Seyman)
    * Fixes SF #1044: tt-rss API changed (we now support only 1.6 API)
      (patch by Sebastian Noel)
    * Fixes assertion when creating new tt-rss subscriptions
    * Fixes XHTML errors caused by extra tags returned by tt-rss
    * Fixes missing item list update when browsing item URLs in Liferea 

Morpheus suggested in a comment to check recent Mozilla sqlite changes for their places database. They basically switched to the new WAL journaling that is supported since sqlite 3.7. Therefore I performed some measurements on the update behaviour in WAL mode with different sqlite page sizes and “PRAGMA synchronous” settings.

Just a short note on what we are doing for 1.8. Right now we try to reduce startup time by killing costly cleanup stuff done on startup by cleaning up the DB schema and we are also thinking about a good way to periodically vacuum the database on startup. The problem there is to find a good interval and to avoid doing it too often as it costs time even if the DB is in a 100% clean state.

During the various performance discussions during the last time here and there people suggested to run “VACUUM” on the Liferea database once it gets slow. This is in line with the sqlite documentation which says:

As explained in the last post I see no way to automatically run the “VACUUM” command of sqlite which more or less defragments the DB structure. Nonetheless for everyone who wants to run it manually here is how to do it: