Still, I’d be lying if I said we don’t occasionally wince when we see someone using our services in a less-than-ideal way. It’s completely understandable, mind you: the problem of figuring out who represents a given citizen is tougher than you might think. But we hate to think that anyone is getting bad information about which office to call — talking to the people who represent you should be simple and easy! Since this comes up with some frequency, it’s probably worth talking about the nature of these problems and how to avoid them.

TL;DR: Looking up congressional districts by zip code is inherently problematic. Our latitude/longitude-based API methods are much more accurate, and should be used whenever possible.

The first complication is probably obvious: zip codes and congressional districts aren’t the same thing. A zip code can span more than one district (or even more than one state!), so if you want to support zip lookups for your users, you’ll have to support cases where more than one matching district is returned. Our API accounts for this, but it’s important that your code do so, too. We err on the side of returning inclusive results when a zip might belong to multiple congressional districts.

Unfortunately, things are actually more complicated than that. Most people don’t realize it, but zip codes describe postal delivery routes — the actual routes that mail carriers travel — not geographically bounded areas. Zip codes are lines, in other words, while congressional districts are polygons. This means that mapping zips to congressional districts is an inherently imperfect process. The government uses something called a zip code tabulation area (ZCTA) to approximate the geographic footprint of a given zip as a polygon, and this is what we use to map zip codes to congressional districts. But it really is just an approximation — it’s far from perfect.

It’s much better to skip the zip code step entirely and simply look up your location against the congressional district shapefiles published by the Census Bureau using a precise geographic coordinate pair instead of a hazy, vague zip code. Thanks to the Chicago Tribune News App Team’s excellent Boundary Service project, we offer exactly this capability. If you can, we strongly encourage you to get a precise latitude/longitude pair from your users (either by geolocating them or geocoding their full address), then use it to determine their representatives.

“But what about house.gov’s ZIP+4 congressional lookup tool?” I hear you asking. It’s true, many House offices use this tool to determine who your representative is (and whether you’re allowed to email them). Unfortunately, just because this tool is on an official site doesn’t mean it’s perfect. Here in the Labs, Kaitlin (who lives in Maryland) can’t write her representative because the ZIP+4 tool gives incorrect results. Besides, not that many people know their full nine-digit ZIP+4 code.

So if you can, use latitude/longitude pairs. If you can’t, and have to depend on zips, we’ll supply results that are very, very good — but not as good as real coordinates would allow.

Original Source

Imagine if you could only get data from an API when things have changed or there is new data? Well, you do not have to imagine anymore, the Facebook Graph API now supports HTTP ETags. ETags support on the Facebook Platform can help you reduce bandwidth consumption and client-side overhead by suppressing output when making Graph API calls. In addition, clients (especially mobile devices on slow connections) can increase performance and reduce data usage when calling the Graph API with ETags.

This is how it works:

1. When you make a Graph API call, the response header includes ETag with a value that is the hash of the data returned in the API call. Pull this ETag value and use in Step-2.
2. Next time you make the same API call, include the If-None-Match request header with ETag value pulled from step-1 for this API call.
3. If the data hasn’t changed, the response status code would be 304 – Not Modified and no data is returned.
4. If the data has changed since last pull, the data is returned as usual with a new ETag. Pull the new ETag value and use for subsequent calls.

Note: While ETags help reduce the data traffic, the If-None-Match GET will still count against the throttling limits for your app and must not be performed at a frequent rate. We recommend only do it for data that doesn’t change frequently like user’s friends, likes, photo albums, photos etc. Do not use it for news feed, messages etc.

The ETag is calculated using the entire response from the API call including its formatting. Developers should be aware that the formatting of API response output may be impacted by the user agent string. Therefore, calls originating from the same client should keep the user agent consistent between calls.

Example:

Install Firebug and Modify Headers add-ons on Firefox.

Fetching user’s friends: https://graph.facebook.com/me/friends?access_token=<token> returns friends data in JSON output and ETag in the response header. You can quickly test by visiting the Graph API Doc and clicking on the Friends sample link that auto generates access token for the session user and makes this API call.

Next create the If-None-Match request header in the Modify Header add-on tool with the ETag value pulled from the Firebug. Make sure the header is enabled (green lit).

Now call the friend Graph API again – https://graph.facebook.com/me/friends?access_token=<token>. Note that the API returns no data and the status code is ‘304- Not Modified’:

PHP Code Example:

The php code demonstrates ETags while fetching user’s friends. The code pulls the ETag from the response header and then call the same API again while passing the ETag value in the If-None-Match request header. Notice that the response for the second call is 304 – Not Modified.

  <?php

    $app_id = 'YOUR_APP_ID';
    $app_secret = 'YOUR_APP_SECRET';
    $my_url = 'YOUR_REDIRECT_URL';

    $code = $_REQUEST["code"];

    echo '<html><body>';

    // Auth the app using the server side OAuth 2.0
    if(!$code) {
        // get permission from the user to publish to their page.
        $dialog_url = "http://www.facebook.com/dialog/oauth?client_id="
         . $app_id . "&redirect_uri=" . urlencode($my_url);
        echo('<script>top.location.href="' . $dialog_url . '";</script>');
    } else {
        // get access token for the user
        $token_url = "https://graph.facebook.com/oauth/access_token?"
         . "client_id=" . $app_id
         . "&redirect_uri=" . urlencode($my_url)
         . "&client_secret=" . $app_secret
         . "&code=" . $code;
        $access_token = file_get_contents($token_url);

        // get user's friends now we have the access token
        $friend_url = 'https://graph.facebook.com/me/friends?' .
                    $access_token;

        // initialize curl if not yet initialized
        if (!$ch) {
          $ch = curl_init();
        }

        /*
         * Disable the 'Expect: 100-continue' behaviour. This causes CURL
         * to wait for 2 seconds if the server does not support this
         * header.
         */
        curl_setopt($ch, CURLOPT_HTTPHEADER, 'Expect:');
        // set the URL to Graph API URL
        curl_setopt($ch, CURLOPT_URL, $friend_url);
        // we want header in the output
        curl_setopt($ch, CURLOPT_HEADER, true);
        // but do not display the curl output
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        // execute the curl and get the info
        $response = curl_exec($ch);
        $info = curl_getinfo($ch);

        // extract the http code, header and body
        $http_code = $info['http_code'];
        $headers = substr($response, 0, $info['header_size']);
        $body = substr($response, -$info['download_content_length']);

        // convert header string into an associate array and extract the ETag
        $headers_arr = http_parse_headers($headers);
        $etag = $headers_arr['Etag'];

        echo '<a href="' . $friend_url . '"/>' . $friend_url .
                '</a/> <br /><br />';
        echo 'HTTP Code: ' . $http_code . '<br />';
        echo 'ETag: ' . $etag . '<br /><br />';

        /*
         * Execute the same API curl call while passing the
         * ETag value in If-None-Match request header
         */
        echo 'Executing the same API call with request header <br/>
                <b/>If-None-Match: '. $etag . '</b/>
                returns : <br/><br/>';
        curl_setopt($ch, CURLOPT_HTTPHEADER, array('If-None-Match: ' .
                    $etag));
        $result = curl_exec($ch);
        $http_code = curl_getinfo( $ch, CURLINFO_HTTP_CODE );

        echo 'HTTP Code: ' . $http_code . '<br />';

        curl_close($ch);

    }
    echo '</body> </html>';

    /*
     * Function to convert header string into associative array
     * Source - http://php.net/manual/en/function.http-parse-headers.php
     */

     function http_parse_headers( $header )
     {
        $retVal = array();
        $fields = explode("\r\n", preg_replace('/\x0D\x0A[\x09\x20]+/',
                    ' ', $header));
        foreach( $fields as $field ) {
            if( preg_match('/([^:]+): (.+)/m', $field, $match) ) {
                $match[1] = preg_replace('/(?<=^|[\x09\x20\x2D])./e',
                        'strtoupper("")', strtolower(trim($match[1])));
                if( isset($retVal[$match[1]]) ) {
                    $retVal[$match[1]] = array($retVal[$match[1]],
                                $match[2]);
                } else {
                    $retVal[$match[1]] = trim($match[2]);
                }
            }
        }
        return $retVal;
     }
  ?>

Sample Code Output:

https://graph.facebook.com/me/friends?access_token=<access_token>

HTTP Code: 200
ETag: "84a290085a1bb6df44534ac017bfed800c407a15"

Executing the same API call with request header If-None-Match: "84a290085a1bb6df44534ac017bfed800c407a15" returns : 

HTTP Code: 304

Original Source

Video:

Original Source

As always, the Mac development community has come to the rescue with some amazing tools that completely take the effort out of the process. Follow along as we take a look at five great apps that will help you work with LESS, Sass, Stylus and even some non-CSS languages like CoffeeScript and HAML.

What Is a CSS Preprocessor?

A CSS preprocessor is a tool that makes writing CSS easier, more flexible and arguably even more fun. Some purists despise preprocessors and wouldn’t dream of using them, but others, such as the folks at Twitter, have used them as the cornerstone for massive frameworks that rapidly speed up web development.

Typically, a CSS preprocessor adds some interesting functionality to CSS such as variables, mixins, functions, nesting, etc. Some even seek to dramatically redefine the CSS syntax so it’s quicker and easier to write. Developers differ on which preprocessor is the best, but ultimately the output is plain old CSS so which you want to use comes down to a matter of preference. Here are the three current forerunners in this area:

• LESS - The dynamic stylesheet language
• Sass - Syntactically Awesome Stylesheets
• Stylus - Expressive, dynamic, robust CSS

As I mentioned in the introduction, there are several Mac apps that make working with CSS preprocessors much easier and more enjoyable. Let’s take a look.

Five Apps to Process Your Files

LESS.app

LESS.app is a little older and narrower than some of the other options on the market today but it still works perfectly for all your LESS projects. LESS used to require a ruby implementation but these days it uses a .js file to automatically compile your code in the browser.

However, for live sites, you’ll still want to use the resulting CSS in its pure form. This requires you to view the source in the browser and copy/paste the code, which is definitely not ideal. With LESS.app, all of your .less files are automatically compiled and output to a .css file. LESS watches your project folder so as you make changes, everything is kept perfectly in sync.

Price: Free
Supported Languages: LESS

LESS.app

Crunch!

While most of the apps on this list are aimed at simply compiling files, the Crunch! AIR app goes one step further and is actually a full blown text editor specifically created for LESS. With it, you can write in LESS with full syntax highlighting, organize your code libraries and of course, automatically compile your .less files to .css files.

The app’s UI is unique and attractive and despite the fact that I’m not typically a fan of AIR apps, I really enjoy using Crunch! to write LESS. Even if you don’t like LESS, it’s a decent free CSS editor!

Price: Free
Supported Languages: LESS

Crunch!

LiveReload

LiveReload is a really useful utility that just about every web developer should have, whether you’re working with alternate CSS syntaxes or not. It sits in your menu bar and watches a folder for changes in the files. If a file is updated, it automatically refreshes your browser so you get an up to date look at your page without hitting Command+R every ten seconds.

The beauty is that it goes beyond refreshing the browser and actually processes any code that needs it. For instance, CoffeeScript files are output to JavaScript and Sass files are output to CSS. No word yet on how much it will cost when it finally releases but for now you can enjoy the beta completely free.

Price: Free (during beta)
Supported Languages: CoffeeScript, SASS/SCSS, LESS, Stylus, HAML and Jade

LiveReload

Codekit

The developers of the LESS.app above have moved on to a new project, it’s very similar in nature with a lot more “wow” thrown in. Codekit not only watches and compiles your LESS files, it also handles your Sass, Stylus and CoffeeScript files. Like LiveReload, it automatically reloads your browser when any files are updated.

It doesn’t stop there though, it goes one step further and allows you to set up frameworks that you can easily reuse in new projects without copying your code. And that’s still not all! As one final trick it can even optimize all the images in your project so that everything stays nice and speedy. Impressive no?

Price: Free (during beta)
Supported Languages: CoffeeScript, SASS/SCSS, LESS, and Stylus

Codekit

Compass.app

Compass is an open-source CSS Authoring Framework that is built on Sass. It contains a ton of useful tools such as pre-built CSS3 mixins and it’s easy to extend to suit your own needs.

The Compass.app is a Sass compiler specially built for use with the Compass framework. It compiles your code, reloads your browser and works perfectly with all your favorite Compass extenstions.

Price: $7
Supported Languages: Sass

Compass.app

Commenter Additions

Our commenters have pointed out a few great apps that should be added to this list. Here they are:

• SimpLESS – A free and simple LESS compiler.
• Scout – An open source, free compiler for Compass and Sass.

Conclusion

No matter which CSS preprocessor you favor, the tools above will help you compile your code and perform various other functions with almost zero work on your part. Considering that most of them are completely free, you might as well give these apps a shot and see what you think!

Have you used these or any other similar apps? Leave a comment and let us know!

Original Source

Code for America, a non-profit which tries to bring the people and the power of the internet into government, has received a $1.5 million grant from Google.

Code for America launched this year to help governments become more transparent, connected, and efficient by connecting web developers with people who deliver city services. Earlier this year, Code for America debuted its inaugural fellowship program, which pairs technologists with leading cities to help them innovate.

In 2011, 19 fellows worked with 3 cities to develop over 21 applications, which are now being reused across the country and around the world. And the non-profit has also brought on Greylock Partner and former Mozilla CEO John Lilly and Tumblr VP and former White House and Google staffer Andrew McLaughlin to its Board of Directors. Other backers include the John S and James L Knight Foundation, the Ford Foundation, and the Open Society Foundation.

With the new funding, the organization is also launching two new programs (a Civic Startup Incubator and a Volunteer Engagement Platform). The seed accelerator, which has raised initial funding from Kauffman Foundation, will launch in the Spring of 2012 to help foster sustainable businesses that can become the next generation of government vendors.

In 2012, Code for America will also roll out an online platform to connect civic hackers and others with each other locally, and to reuse and remix civic apps in their cities.

Original Source

PhoneGap is a “wrapper” that developers use to turn Web applications built through HTML5 and Javascript into native applications for mobile platforms such as iOS and Android. Terms of the acquisition were not announced. Essentially what Adobe has done is to distance itself from the problems it has created with Flash on mobile and align itself with the hottest mobile developers in the ecosystem.

Sponsor

PhoneGap itself will continue to be open source. PhoneGap Build, which includes proprietary code, will be how Adobe monetizes the Nitobi acquisition. Yet, let’s get one thing straight here – this is about talent as much as it is about code.

Adobe has been left out in the cold ever since Apple decided that it would not support Flash for iOS. Android finally got on board the Flash wagon with version 2.2 Frozen Yogurt but the fact of the matter is that Flash does not run well on mobile devices anywhere.

In a press release, Adobe said that it work to make contributions to the HTML5 community and work with open source projects like WebKit and JQuery. Adobe will take a big step in game development across platforms with PhoneGap at its back and will finally have a firm way into to the native application ecosystem that it has been mostly shut out of the last couple of years.

Once the acquisition closes at the end of October and PhoneGap furthers its application with the Apache Software Foundation, PhoneGap will likely cease to exist as a brand. It will then become Apache branded, with “Apache DeviceReady” the early name being kicked around.

Is this good news? Both Nitobi and Adobe are excited and the fact that PhoneGap will remain open source through Apache means that most developers will hardly see a change. If you are a PhoneGap Build customer, you are going to be sending your check to Adobe now instead of Nitobi. Let us know you thoughts in the comments.

Discuss

Original Source

The Facebook Marketing Series is supported by Buddy Media. Power your connections and turn fans and into real connections when you run technology powered by Buddy Media. Download Buddy Media’s free guide for Successful Retail Social Posting to learn how to drive results with your social postings.

Businesses rely on Facebook to increase brand awareness, build community and strengthen customer service (for starters).

But how can companies effectively leverage Facebook to amplify new product launches? We spoke with some companies — large and small — that used Facebook to effectively introduce products to the marketplace and generate new sales.

1. Build a Targeted Audience

To ensure that time spent online is time well spent, businesses must focus on building and cultivating a targeted audience. Start by defining your audience and developing a strategy to attract that demographic to the Facebook Page. A content strategy, social giveaways and Facebook ads can help companies reach the right people.

As sneakpeeq co-founder and president Henry Kim says, “We learned that if you get the right audience to share your product in the beginning — and getting this audience excited about your company is a giant step — you can do this with little money. Be creative. Where else can you get an instant audience for your company?”

A growing Facebook community is also an evolving community. Sheri Wallace, who works with Dandelion, seller of eco-friendly baby products, notes: “The community at 10,000 fans is not the same as it was at 2,000.” She adds that keeping in touch with the parents has been crucial to increased growth and to the success of newly launched products.

2. Reward Existing Community Members

As Nike Golf launched a new golf ball during the Master’s Tournament, it offered a select number of limited edition green swoosh 20XI balls to Facebook fans in three time-based giveaways in the days leading up to the tournament. The giveaway occurred several weeks before the 20XI balls were available in retail stores, so the public did not yet have access to the product.

In addition to giving away a small number of golf balls, Nike Golf also offered a free shipping promotional code as a “consolation prize.” According to Brian Carter, digital marketing manager for Nike Golf, the launch doubled interaction rates and led to a significant increase in impressions. Most notably, the revenue generated from the campaign’s promotional code was six times the cost to run the campaign.

3. Create Clear Landing Pages & Calls to Action

In some cases, Facebook can function like a traditional website landing page. Transparent Corp, a software company that exclusively sells its products online, has used Facebook Page tabs to create “condensed and easily sharable versions of the landing pages for new software products,” according to Aaron Smyk, the company’s director of social media and marketing.

Smyk offers the following tips to create effective landing pages within Facebook:

• Account for design restrictions. The section of a Facebook page that you can control and design is a fixed width of 520 pixels. Additionally, if the design extends beyond 800 pixels in height, a horizontal scroll bar will be automatically inserted into the design, which can take away from the overall aesthetic and functionality. For a cleaner, smoother integration, plan on a height of 800 pixels or less.
• Keep navigation options extremely simple or rely on the existing left menu to navigate between pages. During the design process, remember that the custom part will be surrounded by Facebook’s existing navigational options.
• Include clear calls to action. What do you want the user to do when they land on your page? Make sure that’s abundantly clear for a user. Smyk suggested, “Include clear links on the landing page for your new product that allow users to move forward in learning more about your product, or purchasing it. You don’t want these pages to be dead ends. All the typical ‘call to action’ rules still apply here.”

4. Solicit Feedback to Fine-Tune the Product

If a business has effectively built a Facebook following that resembles the target market, this network can be a major research and development asset. Ask for feedback, design input and functionality requests. If you’re launching a product with a beta testing period, ask the Facebook community for volunteers.

5. Leverage Geotargeting Features

If the product announcement includes a soft launch targeting specific cities, take advantage of Facebook’s geotargeting tools, including ads and customized status updates.

Facebook ads can be targeted by state, city or zip code. But, don’t stop there. Dig deeper to create a more targeted, cost-efficient, effective campaign. For example, if your product appeals to people who work in a specific industry, research the major players in that space and target the ad to people who work at those companies and live in the city you’re trying to dig into.

But, sneakpeeq’s Kim warns, “Be smart about spending money on Facebook. Do a lot of testing and find out what works. Start small and when you find something that works, keep doing it and on a broader scale.”

In addition to geotargeting ads, posts can be directed toward certain locations. Just click the button underneath the status box to customize who can see the update. The default setting is “public,” but page admins can select a country and then specify states or cities.

6. Make a Splash with Creative Giveaways

In 2009, Little Debbie used the launch of the new Little Debbie Chocolate Cupcakes as a centerpiece of the brand’s entrance into Facebook. The product launch included:

• Share-A-Thon Giveaway. Fans could enter to win a new two-seater Smart Car (as featured in the Little Debbie TV ads) and other weekly and monthly prizes.
• Million Cupcake Giveaway. To celebrate National Cupcake Day, Little Debbie gave away 125,000 boxes of the new cupcakes — totaling 1 million cupcakes — to randomly selected fans who had entered the Share-A-Thon Giveaway.
• “Cupcake Cars” were driven across the United States, distributing samples and posting photo galleries to Facebook and Flickr.

According to David Griner, director of digital content for Luckie & Co., the agency that helped Little Debbie develop and implement these campaigns, Facebook continues to be a major components of their product launch strategy. “With each launch, we feature the new products on Facebook, solicit fan feedback and offer occasional giveaways to encourage sampling. Since the cupcake launch, we’ve doubled the Facebook audience to more than 1 million Likes, thanks largely to giveaways and other promotions that help fans feel engaged with the brand.”

Companies want to get creative with giveaways, but as Kim notes, it’s important to stay true to the brand and use giveaways as a learning opportunity. “Everything we gave away was something we were already selling or planning to sell on sneakpeeq in terms of product/brands. We also used the launch on Facebook to educate consumers about what sneakpeeq is — a social shopping site with a twist.”

What advice can you offer to companies who want to incorporate Facebook into their product launch? Let us know in the comments below.

The Facebook Marketing Series is supported by Buddy Media. Power your connections and turn fans and into real connections when you run technology powered by Buddy Media. Download Buddy Media’s free guide for Successful Retail Social Posting to learn how to drive results with your social postings.

More About: Facebook, Facebook Marketing Series, features, mashable, product launch

Original Source

A nasty security bug in Skype‘s iOS app can lead to users’ personal information being stolen.

The cross-site scripting (XSS) vulnerability, demonstrated in the video below, is present in Skype 3.0.1 and earlier versions of Skype’s iOS app.

It lets an attacker create malicious JavaScript code that runs when the user views a text message in Skype’s chat window. The code can be used to access any file that the Skype app itself has access to, including the address book on your iPhone.

The technical explanation of the bug can be found here.

Skype is aware of the issue and is working on a fix. “We are working hard to fix this reported issue in our next planned release, which we hope to roll out imminently,” Skype said in a statement.

[via Superevr]

More About: hack, hackers, security, Skype, vulnerability

Original Source

Google's powerful Web browser Chrome has unveiled a release that brings us all a little closer to univseral Web development.

The release came with two new technologies: Web Audio API, a feature that brings some advanced audio capabilities to JavaScript, and Native Client, which allows for execution of C and C++ code within the browser. Oh, and it also seemingly erases the divide between Web and native apps.

Originally, these features had been released on the beta channel back in August, but they are now a prominent part of the Chrome experience.

Web Audio API will help developers add in audio effects to JavaScript programming that will allow them to have a little more fun with "cool" sounds, as opposed to just playing back simple files. These only appear on browsers that support Web Audio API.

It's safe to say that most developers are going to be more interested in the offical release of Native Client, which makes it possible for all Chrome users to run applications that have been written in either C or C++ securely inside their browser. It works through the use of an API Google calls "Pepper" that provides HTML5 bindings for C and C++. When Native Client apps use Pepper, they will be provdied with a set of interfaces that equip them with the necessary bindings, allowing developers to leverage their proficiency and knowledge of the native code and pump out portable, high performance Web apps.

Google says that they have plans to eventually make Native Client available to other browers as a plugin. This could pave the way for cloud-based applications to execute desktop-level codes that could be run on Google Chrome, more or less eradicating the line between Web/cloud and desktop applications.

In addtion to these two major overhauls, Google's update also presents some improvements for Mac OS X Lion users, which, as I'm sure they'll tell you, isn't the most Chrome-friendly OS available. These include fixing crash bugs and adding some "visual polish," like the new Lion scrollbars and support for full-screen mode.

Original Source

The new version of QR Card Us separates the QR link itself from the ‘hard card,’ or physical business card, so that customers can buy standalone QR Cards – mobile-friendly Web pages from which contact info can be saved – without worrying about their physical cards becoming outdated. It also adds Organizations, which allow a moderator to manage QR Cards for a company, club or any kind of group. Finally, the update adds Notes, which lets users attach any kind of text note about a new contact to their saved info.

Sponsor

An annual $15 fee provides ongoing support for the QR Card, which can be updated anytime, to which the QR code is a permanent link. Buying a standalone QR Card allows customers to put their code wherever they want, such as their own branded materials. Customers can also purchase ‘hard cards,’ or physical business cards, for a one-time printing fee, alongside the $15 annual charge for the Web-based card. Customers can order new hard cards without affecting the subscription for the Web card.

While QR Card Us provides color, layout and typography choices for both the physical and Web cards, many prospective customers requested more control over their own brand. Thanks to the power of Web-based communication, the flexibility of the small team and the online core of QR Card Us, Spearhead Dev was able to iterate quickly to respond to these concerns within a week.

To learn more about QR Card Us, check out our initial post, in which 19-year-old co-founder Michael Schade describes his vision of “making technology accessible for everyone.” Also make sure to visit their website at qrcard.us.

We’ve also covered lots of different ways mobile Web technologies have been applied to business and personal networking, which you can explore here.

Have you ever used a mobile business card reader for networking? Tell us about it in the comments.

Discuss

Original Source