says: My aim with the FossyTweets
Code Snippet I used
---++ Your name here
showlink="Tweet to me!"
Why not [[http://twitter.com/YOUR USER NAME HERE][follow me]] on Twitter?
Ideas, comments, suggestions: please write them here. Sign and date your comments if you don't mind.
The referenced blogger.js script hardcodes the ID of the ul element to which the output will be written. A modified version of the callback can be written so the ID of the ul element to be customized. I've written a prototype but I seem to be running up against this bug
. -- IsaacLin
- 02 Dec 2008 - 03:04
and created a temporary sample page, FossyTweets
that makes use of it. Note that the way the bug I seem to be encountering
manifests itself, the page seems to work the very first time it is loaded, and then subsequent loads will fail. This seems to be due to a caching problem by Twitter. (Technical details: The initial response seems to be cached with the callback instead of just the JSON data structure, so the subsequent response has nested callbacks.) -- IsaacLin
- 03 Dec 2008 - 15:06
The bug report says the bug has been resolved, and it seems to work, so I've replaced the FossyTweets
page with the implementation from the sandbox version. Note I intentionally did not put a table of contents on the page: with all of the sections closed, I thought the headings were already easily skimmed, and the table of contents would look redundant. I realize that with some sections left open, a table of contents would be more useful. I'm not sure which is the more likely use case: I believe I would tend to close a section after reading it, as this reduces the amount of scrolling I need to do on the page. -- IsaacLin
- 04 Dec 2008 - 00:42
Isaac, thanks very much! There’s a virtual beer in this for you.
- 4 December 2008 - 10:29
This wiki app seems to be out of order. I can't see any tweet updates at all. Anybody able to fix?
- 11 Nov 2010
seems to do just fine.
- 11 Nov 2010