![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Testing posting using JLJ
Mar. 13th, 2009 02:19 amTesting a post using the JLJ command line client. ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
cheyinka pointed it out to me. It's going to take some getting used to to remember all the commands, but I'm kinda liking the idea of having a command line client, running from anywhere without needing to worry about crossplatform interface issues.
cheyinka pointed it out to me. It's going to take some getting used to to remember all the commands, but I'm kinda liking the idea of having a command line client, running from anywhere without needing to worry about crossplatform interface issues.Test centering in 1-column bloggish
Mar. 13th, 2008 03:45 pmblah
(p align="center")
(div align="center")
(center)
Testing centering in 1-column bloggish.
(div style="text-align: center")
(p align="center")
Testing centering in 1-column bloggish.
(div align="center")
Testing centering in 1-column bloggish.
(center)
(div style="text-align: center")
Testing centering in 1-column bloggish.
Firefox 3 on Mac OSX
Feb. 16th, 2008 09:32 pmI'm trying out Firefox 3(.0b3) right now! I decided to download it on a whim; I was hoping that it would be less of a memory hog than Firefox 2. Because trying to run that plus Aptana (Ruby IDE) at the same time was bogging down my system horribly. For the record, it seems to be running more smoothly, but the test may not be fair since most of my extensions were disabled for being incompatible *g*
I love the new features, including the improved downloads interface, additional interfaces (such as the new Applications item, which is the filetype-to-action mapping) and what look to be better error messages. One of my favorite things is that there is now a shortcut for the JavaScript console. It may not seem like much, but the inefficient way to open the JavaScript console has always been one of those little things that irritated me to no end.
It is somewhat strange to see the form controls be styled like Safari's. And the window is a darker gray than I'm used to. I am not enamoured, but I guess I'll get used to them.
There are a few rough spots; sometimes the rendering is weird and elements show up in the wrong place on the page (the header for Vertigo does this often on the Explore page). Also, the cmd+shift+T shortcut does not seem to always work; I often have to use the menu instead. I'm hoping that these kinks will be worked out by the time it makes it to release.
I'm excited about their moving the preferences storage backend to SQLite instead of writing to the textfile (prefs.js) only when closing the browser properly. I think this affects the values saved by Greasemonkey as well; if so, then that means I won't lose the data from the current session if the browser suddenly crashes. I am almost tempted to try to crash something so I can test :-)
I'm also excited about the improved search and bookmarking (with tags) functions -- searching through the address bar brings up results based on the address, the page title, bookmarks, bookmark tags, and I'm finding it pretty useful. (For example, when doing Support work, I can just type "entryprops" and get the URL I want, instead of having to type "livejournal.com/admi...", selecting whatever URL comes up, then deleting the end and triggering autocomplete again with "entr..."). There's also apparently auto-resume for downloads, though I have not tested it yet.
I love the new features, including the improved downloads interface, additional interfaces (such as the new Applications item, which is the filetype-to-action mapping) and what look to be better error messages. One of my favorite things is that there is now a shortcut for the JavaScript console. It may not seem like much, but the inefficient way to open the JavaScript console has always been one of those little things that irritated me to no end.
It is somewhat strange to see the form controls be styled like Safari's. And the window is a darker gray than I'm used to. I am not enamoured, but I guess I'll get used to them.
There are a few rough spots; sometimes the rendering is weird and elements show up in the wrong place on the page (the header for Vertigo does this often on the Explore page). Also, the cmd+shift+T shortcut does not seem to always work; I often have to use the menu instead. I'm hoping that these kinks will be worked out by the time it makes it to release.
I'm excited about their moving the preferences storage backend to SQLite instead of writing to the textfile (prefs.js) only when closing the browser properly. I think this affects the values saved by Greasemonkey as well; if so, then that means I won't lose the data from the current session if the browser suddenly crashes. I am almost tempted to try to crash something so I can test :-)
I'm also excited about the improved search and bookmarking (with tags) functions -- searching through the address bar brings up results based on the address, the page title, bookmarks, bookmark tags, and I'm finding it pretty useful. (For example, when doing Support work, I can just type "entryprops" and get the URL I want, instead of having to type "livejournal.com/admi...", selecting whatever URL comes up, then deleting the end and triggering autocomplete again with "entr..."). There's also apparently auto-resume for downloads, though I have not tested it yet.
Must provide entry text?
Feb. 7th, 2008 01:01 pmError: There was an error processing your request: Must provide entry text.
Cause: high security settings while in RTE
Browsers + conditions:
IE7:
IE6:
Other browsers:
Solutions:
Note: when I investigated, I got a popup saying, "Your brower's security settings could limit some features of this editor. You must enable the option 'Run ActiveX controls and plug-ins.' You may experience and notice missing features." But no users have reported this. This means there may be another setting which controls the pop-up, or there may be another setting that is preventing the JavaScript from working properly even though JavaScript itself is enabled. However, solutions/workarounds remain the same, I believe.
I believe there's a stock that handles this, sans the "make HTML your default editor, if you can't enable ActiveX" section.
Cause: high security settings while in RTE
Browsers + conditions:
IE7:
- RTE
- no autosaved draft (because that fills in the entry text; in fact, I think that this means that it will post your autosaved draft, not any additional text you fill in)
- with active scripting enabled (so that noscript doesn't kick in, and you still see the form controls) -- under security tab
- with ActiveX disabled (so that the RTE doesn't actually do anything) -- under security tab
IE6:
- don't know the exact settings, but probably a similar combination
Other browsers:
- unknown. Have there been reports of this in Firefox/Opera/Safari?
Solutions:
- modify browser security settings; make sure LiveJournal is allowed to run active scripting, ActiveX
- default editor to HTML (http://www.livejournal.com/settings/?tag=editor)
Note: when I investigated, I got a popup saying, "Your brower's security settings could limit some features of this editor. You must enable the option 'Run ActiveX controls and plug-ins.' You may experience and notice missing features." But no users have reported this. This means there may be another setting which controls the pop-up, or there may be another setting that is preventing the JavaScript from working properly even though JavaScript itself is enabled. However, solutions/workarounds remain the same, I believe.
I believe there's a stock that handles this, sans the "make HTML your default editor, if you can't enable ActiveX" section.
Trying out Twitter
Dec. 13th, 2007 02:34 amAbby convinced me, and I have a Twitter... thing.
I think I like it. It basically lets me indulge in one-way whining in tiny bursts (words stolen from murklins :-)), without having to think too much.
I started in the afternoon by posting to it from GMail chat, but it seemed a bit awkward to have to switch to the browser all the time. Plus, the notifications wouldn't work. After I got home, I tried out Bitlbee onexor674's recommendation, and now I'm able to post from IRC (irssi, which I'm logged into via Ciaran's server all the time, anyway!)
What would make it perfect would be if I could post a digest of my Twitter stuff as a backdated entry on my LJ, but I'm running into problems with the Perl modules (reflected on the last few items of my feed hah). I wonder what XML::RSS::Tools does, and whether I can rewrite the twitter2lj.pl script to not use it? (My other alternative is to run it as a cron job from a web server, but it needs additional modules, and I'd have to ask first.)
I think I like it. It basically lets me indulge in one-way whining in tiny bursts (words stolen from murklins :-)), without having to think too much.
I started in the afternoon by posting to it from GMail chat, but it seemed a bit awkward to have to switch to the browser all the time. Plus, the notifications wouldn't work. After I got home, I tried out Bitlbee on
exor674's recommendation, and now I'm able to post from IRC (irssi, which I'm logged into via Ciaran's server all the time, anyway!)What would make it perfect would be if I could post a digest of my Twitter stuff as a backdated entry on my LJ, but I'm running into problems with the Perl modules (reflected on the last few items of my feed hah). I wonder what XML::RSS::Tools does, and whether I can rewrite the twitter2lj.pl script to not use it? (My other alternative is to run it as a cron job from a web server, but it needs additional modules, and I'd have to ask first.)
Investigated all four issues while I was logged in to LJ and as both logged in and logged out of Photobucket.
( four different issues with inserting images via RTE: diagnostic work, error messages, all that dull stuff )
More context in the headers themselves. Urgh, I'm too lazy to dig around PB to figure out what's going on (not even sure I can? Dig around, I mean. Also figure out what's going on)
'Kay, I think at this point, I need to update the RT ticket about being unable to paste images using photobucket, and possibly file another one about the "OK" button's appearance being delayed, and another one about the "please type image url" popup. And then uh. Possibly IC where necessary, but tomorrow. Think I need to stop work on this particular issue for today. Need a night's rest before I can whip this into shape to make coherent ICs, reports, etc. Here's to hoping I don't forget :P
Also, must remember to find out whether anyone else is experiencing the same problem (more to the point, if not everyone is experiencing this problem, then why?)
( four different issues with inserting images via RTE: diagnostic work, error messages, all that dull stuff )
More context in the headers themselves. Urgh, I'm too lazy to dig around PB to figure out what's going on (not even sure I can? Dig around, I mean. Also figure out what's going on)
'Kay, I think at this point, I need to update the RT ticket about being unable to paste images using photobucket, and possibly file another one about the "OK" button's appearance being delayed, and another one about the "please type image url" popup. And then uh. Possibly IC where necessary, but tomorrow. Think I need to stop work on this particular issue for today. Need a night's rest before I can whip this into shape to make coherent ICs, reports, etc. Here's to hoping I don't forget :P
Also, must remember to find out whether anyone else is experiencing the same problem (more to the point, if not everyone is experiencing this problem, then why?)
"Range: bytes=0-307199"
Jul. 31st, 2007 01:06 amI find it interesting that servers respond to the Range header in so many different ways.
My newest toy is a simple Perl script which I wrote to test why certain feeds can't be syndicated on LJ. I've only had a chance to use it twice, but both times the feed couldn't be created because the Range header makes the remote server return 206 (Partial Content) instead of 200 (OK), and each server had a different idea of how it should serve up partial content. And to confuse things even more, some servers return 200(OK) even when the Range header is specified.
First request I tried it with, the remote server returned the feed as a gzipped stream. Second request I tried it with, the server couldn't handle a byte range beyond a certain size (the size of the feed, maybe?); anything larger than that, and it returned 416 (Requested Range Not Satisfiable). I know that the problems with Bad Behaviour are also caused by the range header, but I am not certain about the specifics, other than that it's rejecting the requests because the byte range starts with a 0.
I really should drop this, since there's literally nothing I can do about any of it and there are more productive things I could be doing right now. But. Maybe I'll just check out one more feed if another request about failed feed creation comes in, even if finding out what's wrong isn't likely to help get the feed syndicated.
Enough synning for today! I'm jumping ahead of myself again. I have yet to answer a feed change request where the answer is a simple "yep, valid. Feed changed"; I should get on that soon ;)
My newest toy is a simple Perl script which I wrote to test why certain feeds can't be syndicated on LJ. I've only had a chance to use it twice, but both times the feed couldn't be created because the Range header makes the remote server return 206 (Partial Content) instead of 200 (OK), and each server had a different idea of how it should serve up partial content. And to confuse things even more, some servers return 200(OK) even when the Range header is specified.
First request I tried it with, the remote server returned the feed as a gzipped stream. Second request I tried it with, the server couldn't handle a byte range beyond a certain size (the size of the feed, maybe?); anything larger than that, and it returned 416 (Requested Range Not Satisfiable). I know that the problems with Bad Behaviour are also caused by the range header, but I am not certain about the specifics, other than that it's rejecting the requests because the byte range starts with a 0.
I really should drop this, since there's literally nothing I can do about any of it and there are more productive things I could be doing right now. But. Maybe I'll just check out one more feed if another request about failed feed creation comes in, even if finding out what's wrong isn't likely to help get the feed syndicated.
Enough synning for today! I'm jumping ahead of myself again. I have yet to answer a feed change request where the answer is a simple "yep, valid. Feed changed"; I should get on that soon ;)
Yay, I know how to make my journal reliably crash in IE.
(This is a temporary thing.)
ETA:
A demonstration of crashing
( linkspam: some of these things may stop some versions of IE from crashing )
(This is a temporary thing.)
ETA:
A demonstration of crashing
( linkspam: some of these things may stop some versions of IE from crashing )
crash IE, crash
Jul. 15th, 2007 09:36 amA-b
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
русский текст
Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
русский текст
Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?
Poll time!
Jun. 13th, 2007 06:33 am[Poll #1002098][Poll #1002098]
Oh neat. Changing your vote in a poll sends another notification.
(Please note that the poll below doesn't work.)
Oh neat. Changing your vote in a poll sends another notification.
(Please note that the poll below doesn't work.)
More update.bml stuff
Dec. 21st, 2006 01:30 amIn case anyone wants to comment on the script but doesn't feel comfortable doing so on us.o, here is a good place. I'm assuming that anyone who wants to use that script has an LJ account, since the script itself is made to work with LJ!
---
Because it seems fitting, here's a script (not written by me!) which restores the appearance and formatting of the old update.bml page.
Also, I've finally posted the script to add a tagslist to update.bml. There's an easter egg in there of a sorts -- didn't bother to remove my uglification code, but it can't be activated unless you know the exact steps.
Ah, the stupid thing is that my script is not compatible with the first one, so unless someone (else) is willing to figure out how to fix that, you'll have to choose one or the other.
The information below is outdated; most updated info is in the script itself and probably also in the extended description over at us.o.
( Rough docu for my script. This text is also found within the script itself )
---
Because it seems fitting, here's a script (not written by me!) which restores the appearance and formatting of the old update.bml page.
Also, I've finally posted the script to add a tagslist to update.bml. There's an easter egg in there of a sorts -- didn't bother to remove my uglification code, but it can't be activated unless you know the exact steps.
Ah, the stupid thing is that my script is not compatible with the first one, so unless someone (else) is willing to figure out how to fix that, you'll have to choose one or the other.
The information below is outdated; most updated info is in the script itself and probably also in the extended description over at us.o.
( Rough docu for my script. This text is also found within the script itself )
