I spent this weekend on adding search to feedraider. Things progressed with such pace after a saturday lull (great weather -- not enough of that in Finland!), that I've managed to play with a working setup on my home box for most of Sunday. The result? I'm impressed how much ooomph a simple search box can bring to a site and I've only scratched the surface. Good start for sprint #2!
Search should be up and live on feedraider monday evening.
Monday: Search up and running!
Search should be up and live on feedraider monday evening.
Monday: Search up and running!
Labels: search
I want a big search box placed onto the mainpage.
That itch will be scratched as the second sprint gets underway with an ETA of July 31st.
Also time will go into addressing the following: spammers singing up to promote NSFW/shady content, feed rotation, metrics, "related articles", ...
That itch will be scratched as the second sprint gets underway with an ETA of July 31st.
Also time will go into addressing the following: spammers singing up to promote NSFW/shady content, feed rotation, metrics, "related articles", ...
Labels: 2.02
Two and a half weeks after launch and a 100 fixes later there's still no proper release notes for 2.0! I'll aim to blog about the functionality more now in future posts. No good developing in the dark.
Visible fixes/upgrades in 2.01:
- Pages are even more lighter and thus faster due adding minifying to javascripts
- Emails had a small glitch at launch time with those mails never reaching their destinations. Manual intervention got those mails to their destinations. Still, some never made it as feedback from a registrant close to 2.0 launch made clear.
- Small changes to what makes it onto the mainpage. The mainpage will be a focus in the coming month with a grand overhaul on the way. Currently there's very little interesting going on, it can get filled up with NSFW content, multiple languages are mixed together... a mess!
- Some pages gave a 404 error
This is a big project and with the recent release I'm more "in control" of what I have created. As there's less oil leaks and smoke coming out of the engine behind the service I have more focus on new functionality and features. More on this in an upcoming post.
Enjoy!
Visible fixes/upgrades in 2.01:
- Pages are even more lighter and thus faster due adding minifying to javascripts
- Emails had a small glitch at launch time with those mails never reaching their destinations. Manual intervention got those mails to their destinations. Still, some never made it as feedback from a registrant close to 2.0 launch made clear.
- Small changes to what makes it onto the mainpage. The mainpage will be a focus in the coming month with a grand overhaul on the way. Currently there's very little interesting going on, it can get filled up with NSFW content, multiple languages are mixed together... a mess!
- Some pages gave a 404 error
This is a big project and with the recent release I'm more "in control" of what I have created. As there's less oil leaks and smoke coming out of the engine behind the service I have more focus on new functionality and features. More on this in an upcoming post.
Enjoy!
Labels: 2.01
There are some duplicate articles visible that will be fixed in a few hours time as the database is swept through a filter.
The cause? A script I'm testing ran amok. No harm done, just temporary chaos.
The cause? A script I'm testing ran amok. No harm done, just temporary chaos.
I'm planning two sprints this month with releases on the 17th and 31st. Contents of the sprints will be announced on blog posts during those days. July will skew towards many backend changes, fending of spammers, fixes for known bugs and giving me a better idea on how fast I can move to improving the service from a user perspective.
At launch time feed handling was a bit iffy. It all worked, but there were problematic edge cases that required manual intervention. The launch helped me figure most/all out and come up with a continuation plan that took most of the week to carry out. I looked into the "Circuit Breaker" pattern and implemented it with added feedraider specific requirements. The end result -- solid performance and less worries for me!
Favicons are offline (=default icon for all) until an upcoming fix.
Feed freshness is also being continually looked into. I noticed there are several splog submissions per day. I wonder if a certain SEO e-book is to blame. I won't pay for it to find out. These splogs will likely have some magic applied to them in near future with a disappearance spell.
Favicons are offline (=default icon for all) until an upcoming fix.
Feed freshness is also being continually looked into. I noticed there are several splog submissions per day. I wonder if a certain SEO e-book is to blame. I won't pay for it to find out. These splogs will likely have some magic applied to them in near future with a disappearance spell.
As I noted to Andre earlier the 2.0 rollout came with a slight snag, that is, a lag on feed updates for a few days until things are back to normal. This time schedule calculation seems to be holding and at this pace feeds are fresh tomorrow afternoon onwards.
