(Untitled)

[quirrc]

Poll
(the aim is to allow people to work with other sites from the same client, not to work with LJ using another protocol because all other protocols besides LJ-specific one lack features)
Next release of the client will support Atom.

Comments

[decadence1]

I'm glad you asked this; I voted for Atom. I think that's definitely the one to support, for several reasons. While the Atom API had problems in past years with the working group reaching a consensus on various things, real progress has been made.
For those less familiar with all this, just like Semagic is a LiveJournal client, there are clients for other journal/blog sites too. Talking about APIs (Application Programming Interface) is about discussing tools and protocols that allow people to use an editor without having to use a textbox on a webpage (just like Semagic allows). LiveJournal has its own API called XML-RPC. Theirs is special [:-)] because it has things like Friends groups support, moods, music & the like (specific to LiveJournal based sites). That's all cool - they had to write their own so that programs (like the great Semagic) could connect and post to use these LJ features. Plus, at the time, there was pretty much no Atom (formerly Echo), no MetaWeblog yet either I believe

[quirrc]

The problem here is not some general extensibility etc. but if it is needed by anyone. There were requests for support of MT, in particular for at least basic functionality for crossposing to LJ and MT which is rather easy to make (just post/edit/delete/list categories), but many sites support Atom while LJ does not support MetaWeblog API (so I could not test with LJ) so it may be better to add support of Atom. Another problem is authentication and in Atom it is more secure without requirement of SSL.

[decadence1]

1) The Nokia Lifeblog (PC-mobile phone software combo) recently chose Atom over MetaWeblog. link

2) Sun Microsystems bloggers state they're very much in favour of Atom. One discussed waiting to: "dump this API to finally use Atom". Continuing: "It seems like it will be a "real" specification, and its design last time I looked was pretty clean. The problem with the Meta Weblog API is that the specification is open to interpretation and very often clients and servers implement it either incorrectly or using different interpretations, resulting half working solutions and strange error messages. Atom should be more strict, so more straightforward to validate, yielding better interoperability." link3. a) MetaWeblog is VERY tied to RSS 2.0 (syndication format). That (some might say is) NOT good. The effect is explained by a key Atom community figure: "RSS has long been controlled by a single vendor or entity," said Mark Pilgrim, an early contributor to Atom. "Atom's an open standard, so people can point at the spec and say they're

[decadence1]

More: 4) Atom means one API for both posting & serving/producing a journal feed. Google said "If there are a lot of these feeds out there, we think it will be easier to develop toward it, and the extensibility of ATOM will take out a lot of support and potential confusion for our users." link | link.

5) MetaWeblog has a poor concept of security, sending passwords as plain text on the wire as part of the XML msg. Atom authentication is more practical.

6) Everywhere supporting MetaWeblog supports other APIs anyway. Quote: The MetaWeblog API only allows someone to post and edit blog entries, fetch information about a specific user or change the website template.

7) Wholehearted MovableType crew support. 6A - Jan 27 '04

8) Brad Fitzpatrick also pledged support for the Atom API. LJ already offers all feeds in Atom: "I looked into supporting MetaWeblog, but it doesn't look worth it, considering it's basically identical to Blogger with some random stuff added and removed." [link]

[pantless_cat]

Is there a way to delete old usernames in the log on screen? I looked around, but I couldn't find an entry already asking about this. Thanks.

[quirrc]

See "Hide this username" in options

Would it make sense to support multiple alternative APIs

[josephrjustice]

I'm not a LJ-client or 'blog-client in general coder, but I wonder if it would be possible, feasible, desirable to support multiple APIs. If the idea is to allow this client to as fully support as possible other types of weblogs and the like, as opposed to just providing the maximum possible support specifically for LJ-class blogs. Since some blogs might be best / most maximally supported using one API, while still others might be best supported by another API.

Presumably if you did this, you'd want to specify what API to use for each defined blog instance, on a per-blog basis.

Anyway. One being's musings. Hope this is of some use, interest. Thanks for your time. Be well.

-- Joseph

Re: Would it make sense to support multiple alternative APIs

[quirrc]

Currently it fully supports LJ API and with small changes (most of which I already made since this poll) it will support most of other blog sites.

[vanushah]

Excuse me for offtopic.

Readme file says: "Ctrl+D - Clear draft", but it doesn't work...

[quirrc]

That is a shortcut for the red cross button near green icons of loading/saving drafts, it deletes the manually saved draft file from disk.

[vanushah]

Okay. Then where is "New Draft" button?
Or how do I quickly clear draft's "Subject" and "Text" fields?

PS I'm sorry for my poor English..

[quirrc]

draft here means file, not text fields in the client. to clear text fields use reset button (check if it is enabled in options/general)

[saveyoursanity]

Hiya. I know this isn't really a support forum for Semagic, but I was hoping you'd be able to help me out here anyway. This also might be a bug, I'm not sure:

I use iTunes, and prior to installing Winamp I had Semagic detecting the music I was playing just fine. Now it doesn't, and in the status bar it says "Player: Winamp" when I try to detect. That's not my music player, and it's not even installed anymore. How can I fix this?

[quirrc]

that means that plugin in itunes for music detection emulates winamp so old clients that supported only winamp can detect music in itunes. the error it only if it does not detect music.

[saveyoursanity]

It isn't detecting anything.

[quirrc]

disable detection via plugin in options/music in semagic and enable via com. get the latest release if that will not help http://sourceforge.net/project/showfiles.php?group_id=84783