I’ve created a page on the codex with information about privacy and how Lilina uses your data. This includes what Lilina sends to other sites, along with what this website collects about you.
To summarize: Lilina sends the installation URL in user agent with every feed request, also sends your PHP version and localization when checking for updates.
Also included on the page are ways to change this if you wish.
Posted in General
Tagged codex, privacy
I’m proud to announce the first beta of Lilina 1.0 is now available for your testing pleasure!
The release of this beta brings with it a feature freeze. Any new features will be scheduled for 1.1 and will not make it into 1.0. The majority of development from now until release of 1.0 will focus on bug fixing and stabilising the code.
I know I haven’t been keeping this blog up to date, but that’s because I’ve been too busy working on Lilina (and other things).
So, what’s been happening recently in the world of Lilina? I’ve been working on getting Lilina closer to a release, and I think I’m almost ready for a beta of 1.0. Expect that coming in the next week or so, as soon as I fix up some bugs.
Since the last blog post, Lilina has been changed to now keep your items forever in a persistent database. I’m not sure yet whether to add the ability to automatically remove older items, as I’m not sure how much it is actually needed. (This was added a while ago, but I haven’t posted on here in a while either. )
Lilina now also has the ability to update items via a cron job, and also via Ajax. The only template that currently can be updated via Ajax is the Razor template (not included with Lilina at the moment), though I hope to update a few more to be able to work with it too.
So, that’s what has been happening, now on to what’s currently happening. I’m working on stabilising Lilina, which means rigorously testing features, and importing from almost every feed reader known to man. If anyone has any issues at all with importing, please let me know via the forums, as I can’t test every feed.
As you may have noticed, two of Lilina’s major dependencies, SimplePie and HTML Purifier are becoming PHP5 only, with HTML Purifier’s latest releases being available for PHP4 only. I’ve posted previously on SimplePie’s availability for PHP5 only and how we could not switch to it. I later went back and completely backtracked, adding SimplePie to Lilina. It has now been used in Lilina for quite a while, mostly for the better. An old branch of HTML Purifier, 2.*, is used in Lilina and its new 3.* branch has a wealth of new features. Lilina is unable to utilise these at the moment for PHP4 compatibility. This disadvantages our PHP5 users, who could be getting faster and better parsing from HTML Purifier.
PHP5 has been around for more than 3 years and it is time to move on and embrace new developments and standards. PHP4 support and critical security updates have been dropped completely, as of 08/08/08 and all hosts are encouraged to upgrade to PHP5.
As of today, PHP4 compatibility is being dropped from Lilina. We join a whole group of projects who have dropped support for PHP4.
What does this mean for me?
If your host is currently running PHP 5.2, nothing changes for you. If your host is currently running PHP4, 5.0.* or 5.1.*, convince your host to upgrade to PHP 5.2 or change hosts. Lilina will not be supporting PHP4 for future releases. For more information, check out this FAQ, published by GoPHP5.
What does this mean for Lilina?
This decision will enable faster development of Lilina, with many features being easier to achieve and faster. It also enables cleaner code, which can reduce the size of the codebase substantially.
This announcement will have benefits for everyone and I hope that it will have no ill effects on any users.
We’ve changed our logo a few times now but we’ve finally settled on the current one. I’d like to take a brief moment to explain the reasoning behind it.
One of our main logos that we used was a logo designed by NeoRame. This was a great logo and we thank him for his efforts. However, we decided that the logo was too complicated, as we were trying to show simplicity.
I headed back to the drawing board and went through quite a few different revisions of the logo. I finally settled on the current version of the logo.
But, what exactly is the logo? The blue “wave” at the top of the logo is meant to integrate aspects of the feed icon used in Internet Explorer and Firefox. It also takes place of the tittles (dots on the ‘i’s). Further, the ‘ili’ represents a group of servers, with the middle one pushing out content to the other two via the wave.
If you would like to use the Lilina logo in a publication, you can grab the original or one with a brown background (#4D4D4D to be specific).
Posted in General
As you may know if you’re following the development on Subversion, we’re experimenting with a few different templates.
For the future development of these, we’d like to hear from you: what are you looking for in your reader and how do you read your feeds?
(Further posts will be coming soon, I’ve been extremely busy in my “Real Life”™, however development is still continuing on Subversion)
The code in Subversion is now stable, however currently the source list is not being generated. We are aware of this and are working on it.