?

Log in

No account? Create an account
LiveJournal Client Discussions [entries|archive|friends|userinfo]
LiveJournal Client Discussions

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

302: lj_dev [Oct. 10th, 2007|02:22 pm]
LiveJournal Client Discussions

burr86
In the interests of consolidating all LiveJournal development-related discussion, we're going to be closing down this community. The same conversations we've been having here can instead be posted to lj_dev.

lj_dev will be the place for everything related to LiveJournal/FotoBilder development topics. This includes both the code itself, client development, as well as installing the code. So, feel free to join the community and participate. :)
linkpost comment

Plain text to LJ [Oct. 5th, 2007|10:01 pm]
LiveJournal Client Discussions

indybrittney12
[mood |frustratedfrustrated]

I have an old blog from xanga that's in html/plain text and I want to move it over here. Which client would be the best to do this? I also want to post it on LJ as the original date that I posted it in my old blog so an easy way to change the date would be nice too.  
linkpost comment

ljKlient 0.2.0 Preview Release 1 [Oct. 3rd, 2007|11:00 pm]
LiveJournal Client Discussions

ralesk
[mood |accomplishedaccomplished]

Today marks another milestone in the development of ljKlient — as the first preview of the 0.2 series is released.  Please go to the project website to download the package.

Feature review and a tutorialCollapse )
link7 comments|post comment

LJ-Sec updated to v0.60 [Sep. 17th, 2007|05:38 pm]
LiveJournal Client Discussions

soundwave106
LJ-Sec is a bulk journal entry management tool. It allows you to bulk change post security, delete posts, find and replace items, and repost journal entries to other LJ-compatible servers. LJ-Sec has been updated to version 0.60 today.

This adds several features:

  • Community management. Finally, you can use this to back up and repost communities!

    Caveat: Livejournal obviously won't let you repost or edit some other person's entry as anybody other than yourself, so LJ-Sec treats these entries differently. Read the documentation for more information.

  • Configurations. Configurations can now be loaded and saved, which makes managing multiple journals easier. A new configuration manager brings forth many settings previously hidden.

  • Other changes:

    You can override the default behavior in regards to the cache that stores journal entries, and utilize your own file. Again, this makes managing multiple journals easier.

    You can now disable the "resynchronize on login" feature if you want.

    New options for selecting posts: "Select inverse" and "Select My Entries Only" (the later option is mainly for community management)

    Resynchronization should now show a bit less of those "server retries" errors.




    LJ-Sec now requires the .NET framework version 2.0. IE 5.0 is also required. All posts also must be in Unicode in order for LJ-Sec to sync right (you can convert older posts here).

    Backing up your journal using a tool like LJArchive is strongly recommended before using LJ-Sec.

    Find the download for LJ-Sec at http://www.mp3vcr.com/ljsec/.
  • link5 comments|post comment

    (no subject) [Aug. 31st, 2007|11:38 am]
    LiveJournal Client Discussions

    bridgetwannabe
    Hi all, I was wondering if anyone knows of an LJ client that also allows you to view/manage comments to journal entries. I have a couple differerent journals and find it cumbersome to have to be constantly logging out/logging in to work with comments.

    Thanks in advance!!
    link1 comment|post comment

    if you want bots to cache, make the resources cacheable! [Aug. 30th, 2007|08:07 pm]
    LiveJournal Client Discussions
    snej
    LiveJournal's bot policy page says:

    "You are encouraged to cache the results of your bot's requests, which saves us bandwidth and CPU time. Bots making repeated requests on the same resource (URL) in a short amount of time will be blocked."

    However, the HTTP responses LiveJournal sends for FOAF data are, per the heuristics in RFC 2616, nearly uncacheable. They don't include Last-Modified or Expires headers. There's sort of a cognitive disconnect going on here.
    $ curl -I http://frank.livejournal.com/data/foaf
    HTTP/1.0 200 OK
    Date: Thu, 30 Aug 2007 22:27:28 GMT
    Server: Apache
    Cache-Control: private, proxy-revalidate
    Vary: Accept-Encoding
    Content-length: 45098
    Keep-Alive: timeout=30, max=100
    Connection: keep-alive
    Content-Type: application/rdf+xml; charset=utf-8

    Clearly a custom application can cache the data however it wants. But it would be a lot more convenient if we could take advantage of HTTP-level caching support in web client frameworks. I've just spent much of the day struggling with such a framework, trying in vain to convince it to cache FOAF resources so I didn't have to re-invent the wheel. :-/
    linkpost comment

    Community Cross-posting Software [Aug. 27th, 2007|08:50 pm]
    LiveJournal Client Discussions

    njyoder
    What Windows-compatible software (or server-based software that interoperates with Windows-compatible software) allows for easy cross-posting to multiple personal journals and/or communities? Which also allow you to easily edit the cross-posted post and have changes reflected in all of the journals it was posted in? Do any also allow you to automatically add a list of all journals it was cross-posted to?

    Cross-posted.
    link5 comments|post comment

    Speed [Aug. 26th, 2007|10:37 pm]
    LiveJournal Client Discussions

    ralesk
    [mood |curiouscurious]

    Probably slightly off-topic.  Something I noticed in the last couple weeks is that whenever I try to log in with ljklient, it takes ages to get a reply from the server — so much that it takes around a minute to log in to the service.  I haven’t changed a thing in my code, and one of my translators mentions the same problem, so I wonder what’s going on.

    Anyone have a clue?


    EDIT.

    Okay, it was the whole AAAA lookup mess as usual.  I’m really glad that linux is daft like that, using AAAA lookups even when I have no ipv6 enabled.  Strangely enough, there’s a proper reply right away when I dig for the AAAA record of www.livejournal.com — yet ljKlient tries four times, every 5 seconds, until it finally gives up and does an A record lookup.

    A solution would be if LiveJournal were available on ipv6 :P  I’ll try to figure out how to stop Python from doing this until then…


    EDIT.

    Wireshark to the rescue!  Using my ISP or OpenDNS makes them fire back empty responses as proper, and then the software tries on “A” pretty quickly — my router however tries to be helpful by immediately looking it up on “A” once “AAAA” failed, and replies with a PTR: “18.177.9.204.in-addr.arpa: type PTR, class IN, www.livejournal.com” which apparently is too confusing to something in my system.  Fun.

    So, well, back on topic — if you use ljKlient and it’s ridiculously slow for you at logging in… set your nameservers in /etc/resolv.conf to OpenDNS’s addresses.  Should help a lot.

    linkpost comment

    (no subject) [Aug. 21st, 2007|09:01 am]
    LiveJournal Client Discussions
    half_my_own_man
    Is there a client that would change all or selected posts to friends-only?

    --Okay, I see LJSec does for your personal journal, but how about for a community that I run?  Even if it's just for my posts in that community?
    link2 comments|post comment

    Read blogs [Aug. 15th, 2007|01:49 am]
    LiveJournal Client Discussions
    traider_dev
    Hello!
    I want write a program that will read livejournal blogs. I found this doc http://www.livejournal.com/doc/server/ljp.csp.xml-rpc.getevents.html, but it says that user must log in to read blogs, that is, user must have an account. So... Is there any way to read blogs without logging?

    Translated by Google =)
    link3 comments|post comment

    navigation
    [ viewing | most recent entries ]
    [ go | earlier ]