Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cele domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/hughmcguire/hughmcguire.net/wp-includes/functions.php on line 6121

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":556,"date":"2008-04-09T11:38:40","date_gmt":"2008-04-09T15:38:40","guid":{"rendered":"https:\/\/hughmcguire.net\/2008\/04\/09\/twitter-delicious-twitticious\/"},"modified":"2008-04-10T11:30:35","modified_gmt":"2008-04-10T15:30:35","slug":"twitter-delicious-twitticious","status":"publish","type":"post","link":"https:\/\/hughmcguire.net\/2008\/04\/09\/twitter-delicious-twitticious\/","title":{"rendered":"twitter + delicious -> twitticious"},"content":{"rendered":"

One of the things I’ve been lamenting about twitter<\/a> is that it’s replaced del.icio.us<\/a> as the “place where I put interesting links” … ie. links my friends might be interested in. This means that I don’t really have a good, structured repository of links like I used to have with delicious. The problem is that twitter and delicious do a similar thing – let you share information – from a totally different philosophical starting point. <\/p>\n

Delicious is a database designed to collect and organize URLs, which you can also share. <\/p>\n

Twitter is a conversational tool, that also allows you to share URLs. <\/p>\n

So delicious is built as an organizable archive; while twitter is built as an ephemeral transmission device.<\/p>\n

But what I’ve found is that I want to do both: transmit interesting links, but *also* archive them for future reference. So I want to link the two services. I asked on Twitter if anyone knew how; Jordan (blog<\/a> – twitter<\/a>) pointed me to twitticious<\/a> (review<\/a>), by Alex Girard<\/a> which, I think, does exactly<\/s> what I want, unfortunately with some problems, but the meat of what I want twitticious does:<\/p>\n

1. I post a URL to twitter, with a bit of text
\n2. twitticious then sends that post to delicious, with the twit text as the title, and the URL as the URL<\/p>\n

I now am able to transmit my twits, and archive the URLs in a nicely structured\/able database.<\/p>\n

It’s so simple. And all you have to do to get it to work is:
\n-give twitticious your twitter name
\n-give twitticious your delicious name\/password (hopefully not<\/s>probably too much of a security threat).<\/p>\n

Problem 1: the delicious entries aren’t tagged, so you have to do that in a separate step.
\nPotential Solution: have twitticious automatically tag: “from:twitter” … so I can easily find & tag those entries<\/p>\n

Problem 2: twitticious uses the twitter’s tinyurl as the URL it posts to delicious
\nPotential solution: could the true URL be extracted and posted instead? <\/p>\n

Problem 3: Apparently it can’t be turned off
\nPotential Solution: you could just change your delicious pw, and that should do the trick, I think. <\/p>\n

UPDATE: Problem 4: The password thing. Probably too much of a security threat.
\nPotential solution: I don’t know.<\/p>\n

(PS what do you think gives the CIA more information: my Facebook account or my del.icio.us account?)<\/p>\n","protected":false},"excerpt":{"rendered":"

One of the things I’ve been lamenting about twitter is that it’s replaced del.icio.us as the “place where I put interesting links” … ie. links…<\/p>\n