Webby is a “web link” information script by speechless, whereby it display titles and other relevant information from links given in irc channels. It can also be used to test and contstruct regular expression in channel.

My only concern is the network spamfilter; Z:lines, and the ‘non-safe_search’ on the script.

Example:

< Solitary_Scar > @webby www.debian.org
< bot > Debian — The Universal Operating System (http://tinyurl.com/dqx8 )( 200; text/html; iso8859-1; 14791 bytes )
< bot > Debian GNU/Linux is a free distribution of the GNU/Linux operating system. It is maintained and updated through the work of many users who volunteer their time and effort.

Example2:

< Solitary_Scar > @webby www.coffeegeeksvslinuxgeeks.net
< bot > webby: Couldn’t open socket: host is unreachable (http://www.coffeegeeksvslinuxgeeks.net )

Webby will start working tomorrow Nov 21th, for private channels.

Si deseas que tu URL sea más corto y publicar cómodamente en Twitter,  accede los siguientes links:

http://tinyurl.com/

http://tinyurl.com/create.php

Dans la série “et si j’essayais de coder ça”, voici une fonction PHP qui donne l’adresse redirigée à partir d’une URL. C’est pas clair ? En gros, vous lui donnez une URL bit.ly, tinyurl ou autre, et elle vous donne l’adresse originale. Ça devrait maintenant être plus clair

Pour la petite histoire, c’est un tweet de @jdenoy qui m’a donné l’envie de coder cette fonction et la voici :

function get_redirection($address) {
  $url=parse_url($address);
  if(!isset($url['scheme'])) $url['scheme']='http';
  if(!isset($url['port'  ])) $url['port'  ]=80;
  if(!isset($url['path'  ])) $url['path'  ]='/';

  if($url['scheme']!='http') return FALSE;

  $fp=fsockopen($url['host'],$url['port'],$errno,$errstr,30);
  if(!$fp) return FALSE;

  $out ="GET ".$url['path']." HTTP/1.1\r\n";
  $out.="Host: ".$url['host']."\r\n";
  $out.="Connection: Close\r\n\r\n";

  fwrite($fp,$out);
  $response="";
  while(!feof($fp)) $response.=fgets($fp,4096);
  fclose($fp);

  $lines=explode("\r\n",$response);
  if(strpos($lines[0],"301")===FALSE and strpos($lines[0],"302")===FALSE) return FALSE;

  foreach($lines as $line) {
    if(substr($line,0,10)=="Location: ") return substr($line,10);
    if($line=="") return FALSE;
  }

  return FALSE;
}

print get_redirection("http://bit.ly/3eg1ua");

Le principe consiste à consulter l’entête de réponse, d’y détecter s’il s’agit d’une redirection (code 301 ou 302) et alors de retrouver la nouvelle adresse (ligne “Location:”). Ça m’a permis aussi de découvrir la fonction parse_url qui est bien pratique dans mon cas

Well it doesn’t exist yet, but should – Google’s answer to TinyURL.com – the Google URL shortener.

Why should Google enter the URL shortening business?

I think a better question is: “Why not?’

If anyone could and should be in the url shortening business its Google.

Having a shortened url under a custom domain extension like .Google (dot.Google – custom brand name domain extensions will become available next year) would create more visitor traffic and page views which in turn would create more advertising inventory for Google to offer to Adwords advertisers.

Making the new Google’s shortened url service available to Blogger accounts would be a good place to start.

As it stands now, everytime a Blogger account holder wants to share their blog post, Google’s Blogger service generates a rather lengthy and unwieldy Google domain address.

Google Blogger Follow Share

Assuming the blog’s title is more than a single word, this renders most Official Google blog posts incapable of being shared directly with Twitter because of Twitter’s 140 character limit.

Share This Post

More often than not, Google Blogger account posts’ title and domain addresses far exceed the 140 characters available for sharing a blog post directly with Twitter.

Thus, the Google domain address has to be shortened which is an inconvenience to say the least.

Google then shortens their domain’s address to one other than the Google’s brand – the Bit.ly brand.

Share Blogger With Twitter

This process then requires opening a new browser window, copying and pasting the Blogger address into Bit.ly – what a pain in the browser!

Bit.ly is a great service but there is no reason why Google couldn’t make this whole process several steps shorter while retaining a bunch of traffic that was their’s to begin with.

To take this a step further – why doesn’t Google just co-opt the best form and functionality the url shortening industry has to offer and then distribute its shiny new TinyURL shortening service to all Google account holders through their Google Accounts dashboards?

Google Accounts URL Shortener

Between offering the new Google url shortening service to Blogger and Google Account holders, Google would surely realize the birth of a signicant new traffic generating property – the shortened Google URL.

Un’altra funzione importante e innovativa dell’ultima versione di msn è quella di poter inserire link nel messaggio personale per condividere il proprio sito web o qualsiasi altra cosa on-line con i propri amici. Ma quì sorge il nostro problema, quando inseriamo un nostro link troppo lungo questo viene tagliato per questioni di spazio nel client, quindi come possiamo fare per aggirare l’ostacolo?…Semplice basta usufruire del servizio offertoci da TinyURL disponibile qui. Inseriamo il nostro link e clicchiamo su “Make TinyURL” ed in pochi secondi abbiamo il nostro link abbreviato. Questo servizio può comunque essere sfruttato anche nei siti web o forum quando si deve inserire un link di un immagine ecc.

So sad! One day cli.gs was a thriving little business and the next day, well… someone or something apparently abused their program and now they are banned by Facebook. Note to self: It could happens to any of us!!

Here are my personal choices for alternatives. Just choose one and keep on pinging:
http://tr.im/: Includes bells & whistles
http://notlong.com: Includes bells & whistles
http://tinyurl.com/: Basic

And, if this is all Greek to you, check out the free ebook, Sane Social Networking in 15 Minutes a Day.

Cách đây khoảng 2 năm, tôi biết đến một dịch vụ “mới toanh” (lúc đó) là tinypaste, thấy nó rất hay nên có giới thiệu trên eChip. Tinyurl thì giúp bạn thu gọn link, còn tinypaste ? – rất độc đáo, nó giúp bạn thu gọn một đoạn text. Nói rõ hơn là bạn sẽ được cung cấp một đường link ngắn gọn để dẫn đến một đoạn text, ví dụ : http://tinypaste.com/9bd0814 , nếu bạn thấy đường dẫn đó quá dài thì có thể dùng tinyurl hay bit.ly để….thu gọn tiếp, haha.
Hôm nay tôi có dịp quay lại trang tinypaste thì thấy nó có nhiều cải tiến so với hồi đó :
Đọc tiếp… »

So I’ve fallen behind on some of my work.   I’ve been busy with some other school projects.  This means the list I’ve whittled down last week has grown considerably large again.

• Consider creating a Twitter account in conjunction with your blog (not considering doing)
• Comment on another student’s blog
• Watch online lectures/readings
• Complete lab by Friday
• Watch two online lectures
• Read document on Mercurial
• Read up on GCC
• Read the How to Make
• Build Firefox
• Pick a project
• Complete the Initial Project Plan

While that list doesn’t look too much larger than last time, falling behind on readings isn’t too fun because you then have to do double the amount of readings.  As like last time, I’ve crossed off all the things I’ve done so far.  Let’s do a run down.

I’ve crossed off joining Twitter, even though I really haven’t joined.  I’m not too into the whole Twitter system.  While I understand that it may have closed some doors to a certain part of the community, I don’t think it’s expressly needed.  I believe I have access to what I need with the blogs, wikis and IRC channels.  I’m not too fond of Twitter so there will be no alerts following me.  If you really wish to follow me, you can just use the feeds on my blog as this is where I’ll be publishing the important parts of my work and life.

I’m always willing to leave a comment on a blog post that interests me.  It’s part of the whole blogging community.  I know it’s nice receiving feedback on what you’ve written, so it’s only natural to do so when you’re inspired by what someone’s written.  I did this on a blog post that a colleague of mine did.  I was initially on the fence about what project to work on.  I couldn’t decide on whether to help with Processing.js or to stick to my C/C++ programming background and work on some bugs there.  I was also thinking of working on the mobile side of Mozilla with Fennec.  Carlos‘ blog post gave me what it was I was I needed.  It was the inspiration to work on something new and innovative.  Also, the courage to learn a new language and a new style of coding.  So with that, I was able to cross two items off my list.  I put my name down for Processing.js!

I finished my lab, albeit a little late, with the help of buddhatron through IRC.  My page on the CDOT wiki is now updated.  In the process, I was able to use pastebin and tinyurl as was part of the learning experience for the lab.

Now, the rest of my catching up had to do with a lot of reading and watching online lectures.  My first online lecture, about the Mozilla Community, would cause my Firefox browser to crash.  I was able to start it up at school but couldn’t at home because I hadn’t downloaded and installed Quicktime.  I talked to David about it and he said he was switching the video formats.  So hopefully, I’ll be able to see it soon.

The next online lecture I watched was called “Learning to be at the festival.”  It was a lecture given by David Humphrey and it’s a great summary for what he’s been trying to teach us during the first couple weeks of this course.  The best way to learn in the environment of the Open Source Community is to just jump right in and get your hands dirty.  You learn through experience.  It’s a great lecture for anyone apprehensive about the course work and project, which I’m sure most of us are.

I watched this week’s lectures as well.  They were not as interesting to me.  They were How the Mozilla Build Works by J. Paul Reed and Mozilla’s Build System by Ted Mielczarek.  As you can guess, they were both about Mozilla’s build system and how it works behind the scenes.  I couldn’t run the video for preed’s lecture so I just listened to the sound recording.  Unfortunately, I couldn’t follow along too well because the slides posted aren’t available anymore.  Ted’s video lecture was better, in terms of being able to access it.  However, I noticed that I wasn’t paying attention too much to either lecture.  While I can understand that being knowledgeable in what you’re diving into is important, I just wasn’t interested in the behind the scenes work.  For me, it’s kind of like Discovery channel’s How It’s Made.  It just wasn’t very interesting.  I sat through them though, not absorbing all too much.

The stuff I haven’t crossed out, I’m in the process of doing.  I was in the middle of going through the GCC reading, when I spotted another blog post that inspired me to just dive right in.  So I decided to take the first plunge and while writing this blog I was downloading and installing my virtual machine courtesy of VirtualBox.  I, then, downloaded Fedora to install on the vm.  It’s now running smoothly in the background, minus the fact that I can’t change the resolution past 800×600.  Anyone have suggestions or is this the limitation of a vm?  Anyway, I’m going to start on Mercurial and then try to build Mozilla.  I’ll update more later!

آپلود فایل در Bit.ly + سبقت Bit.ly از TinyURL

Bit.ly یکی از محبوبترین سرویس کوتاه کننده‌ی URL بر روی وب، با توافقی که با yFrog (سایت به اشتراک گذاری فایل‌های چندرسانه‌ای)به عمل آورد، قابلیت کوتاه کردن سریع آدرس تصاویر و دیگر فایل‌ها را به امکانات خود افزود.

این بدان معناست که Bit.ly در واقع عمل آپلود و به اشتراک گذاری فایل‌ها و سپس کوتاه کردن آدرس را با هم تافیق کرده است و دیگر برای به اشتراک گذاری فایل‌ها نیاز به وبسایت دیگری نخواهیم داشت.

اما نکته مهم آنکه در حال حاضر Bit.ly محدودیتی برای فایل‌های آپلودی در نظر گرفته است و آن‌ها را به فایل‌هایی با پسوندهای jpg, png, gif, bmp, tiff, swf, flv, pdf, mp4, mov, avi محدود کرده است.

پیش‌بینی می‌شود با اضافه شدن این قابلیت، گرایش به Bit.ly نسبت سایر وبسایت‌های مشابه نظیر TinyURL به شدت افزایش یابد. همچنان که این روند رشد از مدت‌ها قبل شروع شده بود.

You all know the shorten URL web apps, they exist for a long time now, but they sure have become a must use app if you are using Twitter. And Twitter itself made the choice of their favorite shorten URL site: http://bit.ly/ . But this last one has one interesting, new and even shorter option to use it: http://j.mp/.

J.mp gives you two extra chars to use with your tweets, and will represent from now on, that everyone that uses j.mp can have a 1.4% length increase in their tweets. Yes, I know, those stats doesn’t sound like a big deal to you, but isn’t cool to have a even shorter option for your URLs?

Bit.ly and j.mp are both products from Betaworks group, that is having an important growth from last May: Since then, Twitter replaced TinyUrl with Bit.ly as its built-in short URL service.

I’ve been always grateful with these shorten URLs apps, did you ever ask to you what would Twitter be without the shorten URLs?

For those of us who Twitter allot using their BlackBerry (can’t you tell which smartphones a brotha favors?) trying to shorten a url and post a new tweet, or retweet is challenging. Let me show how I USE to do it:

1. type in the url address I want to shorten on my desktop Internet explorer
2. copy the url
3. go to tinyurl and shorten the url
4. copy the shortened url
5. send myself an email with the new url pasted in my subject
6. open up the email on my blackberry
7. copy the new url
8. open the ubertwitter app
9. paste the new url in my message, and send tweet

Well thanks to the folks over at the Crackberry Forums, I have found (and dowloaded) the life-saving little app called Bit.lify. This FREE (a brotha loves free) BlackBerry application enables you to shorten AND copy (or email, or text) any url from your phone, using your phone’s browser – no need to mess with trying to go to an url shortener website on your computer (or phone) copy, shorten, copy again, and paste again.

Here are my new steps:
1. type in the url address on my phone’s browser
2. click the BB menu button, and select “bit.lify” in the menu
3. select copy from the list of choices
4. open ubertwitter app
5. paste the new url in my message, and send tweet

Just about half of the steps are gone! This is a MUST-HAVE app for die hard BlackBerry/Twitter users!

For more information and to download Bit.lify, go to ubiquitoussystems.com

Bit.ly

A couple weeks ago  I talked about Tr.im the url shortner. This time I am talking about Bit.ly no they are not closing or closed then reopen  Don’t give them idea’s. But no Bit.ly has grown beyond expections .  Twitter changed it’s default Url Shortener earlier this year from the tinyurl.com to bit.ly. CBS uses them and they have become very popular in use.  So are competeing in a very large Url Shortening Market like against Tr.im so they are in a very large market that once again is free thing that goes will with twitter use And them being the default on twitter if you don’t use a different shortener brings them many uses. Like Tinyurl was and they are still doing well.  One of the reasons why Twitter picked Bit.ly was Tinyurl.com takes more charaters then Bit.ly and twitter you need that extra room for those 140 charter limits.So Bitly is the king now but so was tinyurl so  we’ll se what happens next. I think Twitter needs to make their own. So does Facebook since many of their users also use Url Shorteners.

Bagi yang hobi ngeblog mungkin sering melihat link yang awalanya tinyurl.com, bit.ly DLL, nah kali ini saya akan memberikan tips cara decode Melihat link tinyurl yang asli, jadi kita dapat melihat link affiliasi yang biasanya berada di balik banner2 di suatu blog tanpa harus ikut affiliasi dari yang menawarkan, tapi kasihan juga yah udah capek-capek tapi yang ikut langsung ke situsnya tanpa perantara yang punya blog :lol

Sebenarnya banyak situs yang dapat melakukan decode terhadap link tinyurl, tetapi kali ini saya hanya membahas satu saja, sebab hasil yang di dapat juga masih yang itu-itu juga kok. Berikut caranya:

- pertama dan utama anda masuk ke sini http://longurl.org/
- setelah itu pada kolom isian yang seperti gambar dibawah masukan link yang ingin di lihat sumber aslinya, sebagai contoh saya memasukan link “http://bit.ly/cCcob” dan klik tombol “expand”

- nah setelah proses selesai dilakukan kita dapat melihat apasih isi di balik http://bit.ly/cCcob itu tadi, lihat bambar di bawah!

Saya kira sampai disini sudah selesai tugas kita untuk menterjemahkan sulapan tinyurl. Apa bila tulisan yang saya buat ini merasa ada yang dirugikan saya minta maaf, sebenarnya bukan itu tujuan postingan ini , saya membuat postingan hanya untuk menjaga-jaga apabila kita mendapatkan atau diberikan oleh seseorang link tinyurl kita tahu apakah itu mengarah kesitus spam yang mengandung virus dan dapat merugikan kita. Selamat mencoba.

Twitter ha deciso che verrà messo un filtro per bloccare quei link che portano a siti contenenti malware. Questa decisione è stata presa a seguito di diversi episodi spiacevoli avvenuti nella breve storia dell’uccellino più famoso del mondo. Sta di fatto che da adesso, chiunque voglia inserire all’interno della propria twittata un collegamento ad un sito con dei malware, comparirà il messaggio “Oops! Il tuo tweet conteneva un URL di un noto sito di malware”. Sembra una storia a lieto fine, ma non è tutto oro quello che luccica. Perchè il meccanismo funziona, ma solo con la navigazione via browser (e quindi non con i cellulari), ma soprattutto non funziona se i collegamenti vengono accorciati da altri siti come tinyurl. Insomma, si può fare di meglio..