Could we get the full updates page back?

[maro]

There used to be a full updates page in addition to the "Recently Updated Extensions" page. The latter only shows a fairly short list (e.g. today and yesterday) and I believe it would be helpful to gain an overview of the updates covering a longer timeframe.

If the size of that longer list is seen as an issue I would suggest to use monthly lists (e.g. "updates_2011-02.html").

[tinypoodle]

There used to be a full updates page in addition to the "Recently Updated Extensions" page. The latter only shows a fairly short list (e.g. today and yesterday) and I believe it would be helpful to gain an overview of the updates covering a longer timeframe.

If the size of that longer list is seen as an issue I would suggest to use monthly lists (e.g. "updates_2011-02.html").

http://forum.tinycorelinux.net/index.php?topic=6640.msg46475#msg46475

[tinypoodle]

Hmmm...
I should have checked first...
There is another abridged update history here:
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/updates/updates.html

But in between, it looks like there is about one month missing  

[Jason W]

I agree that a full update history can be useful info, and we are pondering on how to go about offering it without the need for a download of 650+kb and growing each time someone views the page.

[tinypoodle]

Perhaps using gzip compression?

[Jason W]

Yeah, offering a zipped archive file would be much easier than trying to break it up and archive it each month and then offer links to each month's archive.  

Actually it is 835kb at this moment, and bzip2 shrinks it to 44kb.  I will see what we think.   

[tinypoodle]

Suggestion to extend the consideration of compression to the main extensions page

[maro]

Yeah downloading a whole 850+ kBytes file was not what I had in mind. Whilst using compression would bring down the amount of bytes to be transferred it would OTOH make it impossible to directly use a browser for viewing the information (hence the idea of a monthly breakdown with 'previous' and 'next' links).

I'm happy to take a stab at the scripting side of this but can't make any promise of delivery for this week.

[tinypoodle]

Whilst using compression would bring down the amount of bytes to be transferred it would OTOH make it impossible to directly use a browser for viewing the information

That's not what I had in mind, but compressed in order to be viewed in browsers which support it.

Edit: perhaps I should have said transparent compression.

[tinypoodle]

http://redmine.lighttpd.net/wiki/1/Docs:ModCompress

[roberts]

Yeah downloading a whole 850+ kBytes file was not what I had in mind. Whilst using compression would bring down the amount of bytes to be transferred it would OTOH make it impossible to directly use a browser for viewing the information (hence the idea of a monthly breakdown with 'previous' and 'next' links).

I'm happy to take a stab at the scripting side of this but can't make any promise of delivery for this week.

It is not a matter of scripting but instead still related to ibiblio's migration.
I have just been notified of a second phase is scheduled to begin March 8.
It is best that we lay low until things at ibiblio settle down. As much scripting was necessary just to be able to post a release and extensions.

[^thehatsrule^]

and I don't think we would have the permissions to change lighttpd's config

[tinypoodle]

That would be a showstopper then, I guess