The FeedLounge team is looking for some browser developers to help with testing. This is to help distinguish better between bugs that may be in the FeedLounge application or in the browser itself. By getting some browser programmers on-board, they may be able to get problems fixed at both ends.
We feel that this will be a mutually beneficial arrangement:
- We push the limits of the browser and potentially find bugs that don’t normally get surfaced, report them to you (the browser developer) and provide test and use cases.
- Bugs that affect FeedLounge get fixed (or we get work-arounds for them) which is a great thing for our users.
Alpha testing is going pretty good so far. They recently moved things onto a beefier server, and the system response times are nice and snappy now. There are still a few little quirks to be worked out, but it’s really shaping up to be an awesome service.
Related posts:
- FeedLounge 1.0a2
" The FeedLounge team updated the server with some new code today. They’ve fixed several bugs, and added some new features. I found some bugs..." - The State of FeedLounge
" Alex has posted a moderately detailed article explaining The State of FeedLounge. For any newcomers who don’t know what FeedLounge is, it’s a web..." - Feedlounge is live
" This is old news now, but what the heck — I haven’t posted in a while, and this will be quick. In case you..." - Feedlounge web-based aggregator
" Alex King and Scott Sanders have announced FeedLounge, a “state of the art web-based feed reader.” Alex invited me to be an alpha tester,..." - Old wine in a new bottle
" The topic of Ajax is pretty hot right now. And some people are getting a little hot over the naming. As I pointed out..."
One Comment
The current server is actually almost identical to the previous server in terms of hardware, it just doesn’t have all the load (e-mail, web sites, forums, blogs, etc.) that the other server did.