Huddled Masses » Web http://huddledmasses.org You can do more than breathe for free... Sat, 28 Jan 2012 21:37:20 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Convert Twitter users into FriendFeed Imaginary Friends! http://huddledmasses.org/convert-twitter-users-into-friendfeed-imaginary-friends/ http://huddledmasses.org/convert-twitter-users-into-friendfeed-imaginary-friends/#comments Sat, 16 May 2009 20:15:47 +0000 Joel 'Jaykul' Bennett http://joelbennett.net/?p=1170 So a lot of people seem to be taking the latest missteps by Twitter’s management (and the accompanying admission of bad design) as an opportunity to try out some alternatives. Many of them seem to be coming over to FriendFeed (which has been better than Twitter for a long time, but nevermind that) ... so I thought I’d update and release a PowerShell 2.0 script I wrote to create imaginary friends out of your friends that stay on Twitter.

The first part of it is a WatiN script (that automates your browser) called New-ImaginaryFriend which takes three parameters: a name for the imaginary friend, a url for an avatar for the friend, and a HashTable… Of course, we sort-of cheat by using the HashTable … it’s basically a bunch of key-value pairs of remote services and user names. You can use it to add twitter ID’s like twitter="jsnover" or blogs like blog="http://HuddledMasses.org/" etc. You can even add multiple sources (eg: twitter + diigo, two blogs, etc) to a single new imaginary friend 8) ...

This script is done using WatiN because the FriendFeed API doesn’t support creating imaginary friends yet, and as a result it’s slow, and requires IE (and doesn’t seem to work very well with IE8 — at least, I couldn’t get it to set the avatars using IE 8 on Windows 7, so I commented out the avatar part of the next-to-last line).

The other part of the script is a pair of functions: the first is Get-FriendFeedFriends which retrieves profile information for all your friends in a slick format that includes all their services and such … you may find other uses for this later ;-) , the second is Get-TwitterFriends … Both have an -Exclude parameter so you can pass it a list of people to ignore.

When you put these three functions together, you can just import the FriendFeed module, and start creating friends (don’t forget this version of the scripts only works with IE6 or IE7 for the purpose of avatars, as WatiN can’t seem to set the file upload value in IE8 yet).


Import-Module FriendFeed
## Get any twitter friends who aren't on friendfeed
## Make sure you use FriendFeed's built in "add all your twitter friends" first
$twits = Get-TwitterFriends `
         -Nickname jaykul
         -Exclude $(Get-FriendFeedFriends jaykul | select -expand twitter)

## Add them to friend feed
foreach($twit in $twits) {
   New-ImaginaryFriend $twit.name @{twitter=$twit.screen_name} $twit.profile_image_url
}

You can download all of the required modules at once (7z), or grab the latest versions of them from PoshCode: FriendFeed, HttpRest, and WatiN … but if you do that, you’ll still need to get the binaries separately :-/

Reblog this post [with Zemanta]
]]> http://huddledmasses.org/convert-twitter-users-into-friendfeed-imaginary-friends/feed/ 2 Get-Web (Another round of wget for PowerShell) http://huddledmasses.org/get-web-another-round-of-wget-for-powershell/ http://huddledmasses.org/get-web-another-round-of-wget-for-powershell/#comments Fri, 02 May 2008 02:08:08 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/?p=520 Well, after multiple attempts at a wget PowerShell script (the last one works very well for downloading web pages, files, as long as you don’t need to send post parameters or anything like that) ... I found myself writing a script last week that included a custom HTTP POST function as well as using some prior functionality I wrote (ConvertFrom-Html) to convert HTML files to XML documents — which PowerShell can deal with nicely.

So I’ve taken my Huddled.Html code and worked it in together with a few extra bits … and I’m releasing it under the new name “PoshHttp” (which has the sole benefit of being short, in the case when you need to type the full command names, like: PoshHttp\Get-Web.

In lieu of providing proper documentation for this, there’s a script below which shows off some of the features of the Get-Web cmdlet … but first, you’re going to want to download PoshHttp and I can give you a basic overview.

Get-Web

Downloads a file from the web URI, optionally passing POST or GET parameters which it accepts as a Hashtable. If the resulting file is an xml or html file, it converts it to XML and outputs it as an XmlDocument object. If they are not, it saves them to file, and outputs the FileInfo object.

  • Plain will prevent the conversion to xml
  • Save will force saving to file (either xml or binaries)
  • Path lets you specify the file name/path (normally, it selects a path based on what you’re downloading).
  • Force will prevent it from asking if you want to overwrite files

ConvertFrom-Html

Converts HTML to XML. I’ll eventually tweak this so it supports passing it a file path and even saving the xml in-place on the original file … but for now you can use it on a stream of text, like this: (Get-Content file.html | ConvertFrom-Html).save( "file.xml" ). Note that it outputs an xmldocument object … you can get the xml as text to the console using Get_OuterXml().

ConvertTo-Hashtable

Converts a url-style query string or NameValueCollection into a Hashtable. It’s mainly to make it easier to use the Get-Web in cases where you’re getting the URL or POST data from elsewhere.

Here’s a script with a few example uses of Get-Web:


## Find the url of the image (download an html file as an xmldocument)
$ImgURL = (Get-Web http://dilbert.com/fast/).html.body.div.img.src

if($Host.Name -eq "PoshConsole") {
      #In PoshConsole, show it inline
      $ImgUrl | Out-WPF -source "<Image Height='174' Source='{Binding Path=AbsoluteUri}' xmlns='http://schemas.microsoft.com/winfx/2006/xaml/presentation' />"
} else {
   ## Use Get-Web to download an image (it's saved to file by default), and open it in my default viewer
   ## When Get-Web saves a file, it outputs the [FileInfo] which can be invoked with &
   &(Get-Web "http://dilbert.com$ImgURL" -force)
}

###################################################################################################
## Determine the language of a snippet of text (5 words minimum for best results)
function Resolve-Language([string]$text) {
   ## This time, we're using Get-Web with POST parameters ...
   return (Get-Web "http://www.xrce.xerox.com/cgi-bin/mltt/LanguageGuesser" -Post (@{Text=$text})
          ).SelectSingleNode("//font")."#text".Trim()
}

###################################################################################################
## Translate text to English ... This is obviously reworkable as a general translation tool
## But I don't have much use for that, since I only speak Spanish, English, and code ...
function Get-English([string]$text,[string]$FromLanguage) {
   if(!$FromLanguage) {
      $FromLanguage = Resolve-Language $text
   }
   $post = @{text=$text}
   switch($FromLanguage) {
      "Arabic"       { $post["langpair"] = "ar|en" }
      "Chinese"      { $post["langpair"] = "zh|en" }
      "Dutch"        { $post["langpair"] = "nl|en" }
      "French"       { $post["langpair"] = "fr|en" }
      "German"       { $post["langpair"] = "de|en" }
      "Greek"        { $post["langpair"] = "el|en" }
      "Italian"      { $post["langpair"] = "it|en" }
      "Japanese"     { $post["langpair"] = "ja|en" }
      "Korean"       { $post["langpair"] = "ko|en" }
      "Portuguese"   { $post["langpair"] = "pt|en" }
      "Russian"      { $post["langpair"] = "ru|en" }
      "Spanish"      { $post["langpair"] = "es|en" }
      default { return "Sorry, but I can't translate $FromLanguage" }
   }
   
   ## Using Get-Web with POST parameters ... nothing remarkable, but it's just nice with the previous function ...
   return (Get-Web "http://www.google.com/translate_t" -Post $post
          ).SelectSingleNode("//div[@id='result_box']")."#text".Trim()
}


####################################
## Figure out the real url behind those shortened forms
function Resolve-URL([string[]]$urls) {
   [regex]$snip  = "(?:https?://)?(?:snurl|snipr|snipurl)\.com/([^?/ ]*)\b"
   [regex]$tiny  = "(?:https?://)?TinyURL.com/([^?/ ]*)\b"
   [regex]$isgd  = "(?:https?://)?is.gd/([^?/ ]*)\b"
   [regex]$twurl = "(?:https?://)?twurl.nl/([^?/ ]*)\b"

   switch -regex ($urls) {
      $snip {
         ## Notice that {{ Get-Web ... -plain }} returns plain text, not an xml doc
         write-output $snip.Replace( $_, (Get-Web "http://snipurl.com/resolveurl?id=$($snip.match( $_ ).groups[1].value)" -plain))
      }
      $tiny {
         ## GET parameters this time ...
         $doc = Get-Web "http://tinyurl.com/preview.php" -Get @{num=$tiny.match( $_ ).groups[1].value}
         write-output $tiny.Replace( $_, "$($doc.SelectSingleNode(""//a[@id='redirecturl']"").href)" )
      }
      $isgd {
         $doc = Get-Web "http://is.gd/$($isgd.match( $_ ).groups[1].value)-"
         write-output $isgd.Replace( $_, "$($doc.SelectSingleNode(""//div[@id='main']/p/a"").href)")
      }
      $twurl {
         $doc = Get-Web "http://tweetburner.com/links/$($twurl.match( $_ ).groups[1].value)"
         write-output $twurl.Replace($_, "$($doc.selectsingleNode(""//div[@id='main-content']/p/a"").href)" )
      }
      default { write-output $_ }
   }
}
]]> http://huddledmasses.org/get-web-another-round-of-wget-for-powershell/feed/ 1 If I were versioning the web … http://huddledmasses.org/if-i-were-versioning-the-web/ http://huddledmasses.org/if-i-were-versioning-the-web/#comments Mon, 11 Feb 2008 20:58:13 +0000 Joel 'Jaykul' Bennett http://HuddledMasses.org/if-i-were-versioning-the-web/ This “Web 2.0” nonsense is still ridiculous, and I thought I’d just throw this out there to express my annoyance. The one thing you’ll notice here is that at no point do we get a new version just because you started using the same old tech for different purposes. Water does not become Water 2.0 just because you use it to wash your car instead of drinking it, nor because you put it in bottles and pretend it’s worth it’s weight in gasoline. Neither does the web get a new version just because some corporate muckety-muck discovered blogging, nor even when someone finally notices XmlHttpRequest and dreams up a new acronym for “fetching data from a webservice via a javascript in a web page”. What we can do is change the version number when we make a significant change in the underlying technologies.

  • HTML = 1.0
  • Client-Side Script (Js/Vbs) = 2.0
  • Style Sheets = 2.5
  • Server-Side Scripting (Perl/Php/etc)= 3.0
  • Server-Side Databases = 3.5 (the first real web apps — apps that didn’t just manipulate something you already has)
  • XML and XmlHttpRequest (partial page reloads) = 4.0
  • The single-browser web (Netscape dies and the web becomes a uniform platform of IE5 compatible sites). = 4.1

And at some future point in time …

  • Client-Side Databases = 5.0 (this is in the HTML5 spec released this month)
  • Rise of MicroFormats = 6.0 (this is where microformats emerge as recognized standards)
  • Social Web = 7.0

In the Social Web, browsers become true portals, with integrated identity management, instant messaging, contact management and feed aggregation. Micro-formats are one of the supported standards, and browsers can parse them and store and track their information. When you comment on a website, your OpenID is tracked with a microformat vcard, plus your browser offers to ping your OpenId enabled tracking service so your friends can follow a central feed of all your comments and forum participation across the whole web (based on your anonymous OpenID). All of this happens without third party plugins that nobody installs.

So yeah … Web 2.0? The Social Web? No. I think not.

]]> http://huddledmasses.org/if-i-were-versioning-the-web/feed/ 1