You're viewing ![[personal profile]](http://s.dreamwidth.org/img/silk/identity/user.png){kind=small} marcmagus's journalCreate a Dreamwidth Account Learn More | Reload page in: light style |
cesyWhen did Dreamwidth sneak the "Quote" button into the comment editor?
I'm still not all that big on application-in-your-browser type stuff, but this gets points for making a tool that directly addresses a common task one might want to perform and makes it easier for the user. Go Dreamwidth devteam.
LJ's comment notification is broken and seems to be getting worse, not better, as time passes. If they don't fix it soon, I may turn off comments at LJ and direct everybody to Dreamwidth [something I've been considering anyway to consolidate discussion].
If I did so, I hope the comment count and direct link to mode=reply would suffice to not be too much of a pain for people to comment.
I've said a few times that the reason I'm at Dreamwidth and expect in the long-run to migrate as much as possible to Dreamwidth is that they seem to be doing a lot of things right that LiveJournal and most other things I've encountered does wrong.
The first of these was splitting "friends" into "access" and "subscription", so you can track the entries of somebody without giving them trust permission to your private entries, or give somebody trust permission to view your private entries without having to see all of their entries.
Now they've released the alpha version of one of the other huge things I've been claiming for years these sites need: reading filters. It's a paid user only feature, which is a little disappointing, but they say you'll be able to filter on tags! I hope this will begin the death of "I have these filters, let me know if you want on/off them" stuff that, while it serves a valuable purpose, has always felt like a horrid hack of a misuse of technology because the proper technology didn't exist. Instead, I hope to see "I regularly use the following tags; feel free to filter any out you don't want to see."
I don't really have enough readership that I expect this to be terribly relevant, but I'd like to set an example. I try to tag all of my content appropriately, but I know I can be a bit haphazard about it. I am officially soliciting suggestions for tags which I may not have thought of but should use. I would also welcome suggestions for past posts I've made which should be tagged differently.
( Current Tags )
This morning as I was lying in bed trying to wake up, I was thinking about a poll I kind of wanted to post here, but which I couldn't because, of course, that's a paid account feature on both Dreamwidth and LiveJournal.
Much to my surprise, I was just going through my email Inbox and discovered that someone has given me a month's paid time at Dreamwidth. Thank you, anonymous benefactor!
Of course, in the intervening couple of hours, I'd forgotten what I wanted to poll people about. Maybe it will come back to me.
Dreamwidth has finally rolled out an option to customize the footer which appears when you crosspost with comments disabled. Testing out my customization to demonstrate it does what I want it to.
The word "comment" should function as a direct link to post a comment for those who want it.
Feedback would be highly welcome.
[Edit: fixing link in footer]
[Edit 2: copying code for small font size from original.]
Thanks to a comment and link from ![[livejournal.com profile]](http://s.dreamwidth.org/img/external/lj-userinfo.gif)
pw201, the script maintainer, on my last post about the script, I've gotten the LJ New Comments GreaseMonkey script working correctly in Opera, and, further, working correctly in Opera with DreamWidth as well!
First, for full functionality in Opera using LiveJournal:
Replace your GreaseMonkey Library Emulation script with mair_aw's modified version available here.
Modify the New Comments script as described in my prior entry on the topic.
If you want to get DreamWidth working as well, you'll have to do a bit of extra work. Mair gave me the clue, that you need to get the GM emulation to set the correct domain in its cookies so the data can be retrieved again. Here are patches to both scripts to enable this. (I really need to get someplace to stick this sort of thing.)
For DreamWidth:
Comments/suggestions welcome.
( Patches )
Dreamwidth has just given me another two (2) invite codes.
Same deal again, first two people who respond to this post over at Dreamwidth who I can identify as real people I know get the codes. I'll edit the post with the number of remaining codes so people don't waste time asking for what I don't have. [Although if somebody needs a code when I don't have any, I'd be happy to put in a request.]
I have zero (0) codes remaining.
[Those went quick.]
Following the suggestion in response to my support request, I've made a quick patch to JLJ and am posting this test post to see if it works correctly.
A correct fix would probably require taking a look at the API documentation for the &ver= field and taking a look at JLJ; I suspect that said setting should only be set if the current locale is a Unicode locale, rather than always turning it on as I currently am, but I'd want to know how it's defined to be sure.
Anyway, here's the test text again, using the full toolchain with patched jlj; hopefully for the last time.
The problem was presumably due to an extended character in either the name "Métro Bis" or the dessert "Crème Brulèe", possibly the name "Métro Bis" being present in the post title.
If it works, I'll be crossposting to LJ to confirm correct encoding there.
Edit: Confirmed, I can edit this entry and crosspost it.
I have two (2) invite codes [all gone] for Dreamwidth, which I'd be happy to share with any of my friends who is interested.
I'll give them to the first two respondents who are people I actually know [just in case...]. I'm turning off comments on the LJ crosspost of this just to reduce ambiguity; if you're [likely] reading on LJ and want a code, please click through and leave a comment using OpenID.
At the request of Dreamwidth support, I'm making a batch of posts to try to narrow down the possible source of the encoding problem I encountered last week.
The problem was presumably due to an extended character in either the name "Métro Bis" or the dessert "Crème Brulèe", possibly the name "Métro Bis" being present in the post title.
Test 5 removes vim from the toolchain.
Posted using jlj+nano in rxvt-unicode with $LANG=en_US.utf8 and $LC_ALL=en_US.utf8
At the request of Dreamwidth support, I'm making a batch of posts to try to narrow down the possible source of the encoding problem I encountered last week.
The problem was presumably due to an extended character in either the name "Métro Bis" or the dessert "Crème Brulèe", possibly in the name "Métro Bis" being present in the post title.
This second test is using the full toolchain but removing the extended character from the post subject, to test my recent pet theory that this may be involved.
At the request of Dreamwidth support, I'm making a batch of posts to try to narrow down the possible source of the encoding problem I encountered last week.
The problem was presumably due to an extended character in either the name "Métro Bis" or the dessert "Crème Brulèe", possibly in the name "Métro Bis" being present in the post title.
This first test is using my normal toolchain to confirm that I can make a test post which reproduces the problem. After this will be a series of posts eliminating one aspect or another to see if the source of the problem can be narrowed down.
The LJ New Comments script for Greasemonkey is really cool. It keeps track of which comments you've already read, and gives handy keyboard shortcuts to jump to the [n]ext/[p]revious new comment.
It works with Dreamwidth, too.
( Opera )
Kudos to Dreamwidth for setting up their crossposter right. It correctly automatically converts their <cut> and <user> tags to <lj-cut> and <lj user=""> tags appropriately when crossposting to LiveJournal. A minor detail, but well done.
I've joined the small horde of people who are sufficiently interested in Dreamwidth to go take a look and open an account. This post is being posted to Dreamwidth, and should be automatically crossposted to LiveJournal as well.
Having read through a lot of their documentation, I find the Dreamwidth project promising because it reads to me as though they have learned a lot of lessons from both the mistakes and successes of LiveJournal. Their [meh, this sounds like an advertisement...oh well] commitment to openness, sustainability, and community is something I appreciate. The tools they've already put in place seem like a good demonstration that they mean it and are competent to deliver.
Unless something goes wrong, I expect to post like this from now on. At some point, it's possible I will disable comments on the LiveJournal crosspost (I'm still thinking about this...not giving comment counts and requiring an extra click for LJ users is annoying, but fractured comments are also annoying, and at least DW's OpenID support seems solid.). I probably won't turn off the crossposting entirely.
The biggest feature which encourages me to move to Dreamwidth is their decision to separate the concepts of "Subscribe" and "Access" [jumbled together on LiveJournal under the unfortunate name of "friends"]. This is something I've been quietly complaining about for as long as I can remember here on LJ, and it gives me hope that DW gets it.
[P.S. I'm hoping to post a little more frequently, health permitting. Hopefully I can do so and be interesting about it.]
[Edit: fixed failure to use Markdown correctly]
[Edit: it turns out crossposting via client isn't supported yet; you either have to post through the website or edit the post once it hits DW and tell it to crosspost manually. Irritating; I might look into configuring JLJ to double-post or something.]
