Log in

No account? Create an account
OK. I've just decided to take full responsibility for the download… - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

[Sep. 24th, 2001|12:11 pm]
LiveJournal Client Discussions
[music |Tortoise - Seneca]


I've just decided to take full responsibility for the download page.

If you want any information on the page changed, let me know.
(Also, let me know if any of the information is obsolete.)

The one difficult question is the order of listing the clients.
I think I'll sort by OS by popularity, and then by popularity within each OS, where "popularity" is found by looking at the stats page.

[User Picture]From: avva
2001-09-28 05:14 am (UTC)
Please take a look at the new sema's client (see the latest lj_clients entry).

This client grew from visions's official client, after I took its source and made a few unofficial betas back in May (added a checkfriends support, most importantly), sema took the code from me and has been improving it ever since.

I know that a completely new client is in works, but there's still no reason not to update the 'official' Windows client to this one. It has tons of new features, much better UI, is actively in development, etc. etc. And it's obvious that nothing's gonna happen to visions version of the client anymore; and he ignored my requests to publish the current beta code as 1.4.7. or release the current beta source.
(Reply) (Thread)
[User Picture]From: visions
2001-09-29 07:53 pm (UTC)
i disagree about the ui comment. "tons of new features" is a misnomer since it also removed old features.

as for your request for me to publish the 1.4.7-beta code, i responded. as for a push for the 1.4.7 beta to be an official build, i am not in charge of that.. so therefore can not do it.

i sent several emails to brad in the past about making a last release (making 1.4.7-beta into 1.4.7) and there was no resolution on the matter.

there are many reasons why it should not replace what is there, namely an untrusted source, violations of license, locality of development, and lack of packaging.
(Reply) (Parent) (Thread)