Gist 562766

100%

✓ Published0🌍 Public

Last edited Sep 2, 2010

Created on Sep 2, 2010

This example demonstrates a command-line workflow for authenticating a Twitter user via OAuth and displaying their rate-limit status. It shows the authorization URL, prompts for a PIN, and exchanges it for an access token using the `twitter_oauth` gem. The script then outputs the rate-limit data as YAML and prints the token and secret. It relies on the `TwitterOAuth::Client` class and the `request_token`, `authorize`, and `rate_limit_status` methods, with user input handled through standard input.

AI-generated description

Similar vizzes

Loading thumbnail…

Anthropic OAuth CLI - Simplified Claude Code spoof demo

This demo shows a simplified Claude Code spoof that impersonates Anthropic's OAuth flow to harvest user authorization codes. The Python script defines an `AnthropicOAuth` class that generates PKCE challenges, constructs an authorization URL pointing to claude.ai, and exchanges returned codes for access and refresh tokens via the console.anthropic.com token endpoint. It uses the `requests` library for HTTP calls and stores credentials in a local JSON file with restricted permissions, mimicking legitimate CLI authentication behavior.

JJastor11

57% match

Loading thumbnail…

Gist d3be7947ba494f0cc785ad4ff966f6d5

This example demonstrates a workflow for collecting and structuring Twitter data through the streaming API. It uses the `tweepy` library to authenticate and open a live stream, filtering tweets by specified terms or hashtags, and saving each raw tweet as a JSON line to a file. The code then reads that file back, parses each tweet, and extracts selected fields into a nested list, including the text, user handle, favorite and retweet counts, timestamp, follower count, and language. Finally, it organizes the data into a structured pandas DataFrame with corresponding column names, preparing it for further analysis or visualization.

GGeorgeMcIntire

57% match

Loading thumbnail…

Gist 525907

This Ruby code defines an OmniAuth strategy for authenticating users with Google via OAuth, then retrieves basic profile information from the Google Contacts feed. It uses the `omniauth/oauth` library and the `multi_json` gem to parse the JSON response from `http://www.google.com/m8/feeds/contacts/default/full?max-results=1&alt=json`. The strategy extracts the user’s email and name from the feed’s `id` and `author` fields, falling back to the email if the name is unknown. It overrides the request phase to include a scope parameter for the contacts feed.

XXXX

56% match

Loading thumbnail…

Gist 173470

This visualization displays the difference between the friend lists of two Twitter accounts, showing which users are followed by the second account but not the first. The output reveals a list of screen names representing accounts unique to that second follow set. The example works as a Ruby script that leverages the `twitter` gem, using the `Twitter::HTTPAuth` and `Twitter::Base` classes to authenticate with two separate account credentials. It fetches friends for each account via the `friends` method, extracts screen names with a `proc` filter, and computes the set difference between the two arrays.

TTBD

56% match

Loading thumbnail…

Gist 850654

This example shows how to test authorization and role-protected attribute updates in a Rails controller using RSpec. It verifies that a user cannot edit another user’s profile, can change their own given name, and cannot modify their role field, with assertions on flash messages, response codes, and assigned attributes. The code uses Devise::TestHelpers to sign in a factory-built user, and RSpec’s `describe`, `context`, and `it` blocks to structure the test cases.

VVortex

55% match

Loading thumbnail…

Gist 360936

This example demonstrates a Tumblr API client in Ruby, showing how to fetch and model blog posts through a `Post` class that wraps raw post data in a `Hashie::Mash`. The code reveals the workflow of querying the Tumblr API via HTTParty, with support for pagination, post-type filtering, and direct lookup by ID. The visualization highlights the library’s role as an interface layer, not a rendering tool, as it contains no charting or drawing logic—instead, it focuses on data retrieval and object mapping. The example is purely code-based, with no visual output, emphasizing the API’s data-access patterns rather than graphical representation.

DDylanFM

55% match

Loading thumbnail…

Gist 189433

This visualization shows a Ruby data fixture that defines user account attributes for a test suite. It uses the Machinist library’s `User.fix` block to generate randomized login names, emails, and passwords via regex-based `unique` generators, along with nested `Character.make` factories. The code specifies constraints like password confirmation, character count limits, and a boolean agreement flag, demonstrating how to construct realistic test data without a rendering API.

XXXX

55% match

Loading thumbnail…

Gist 706255

This example shows a server-side Ruby on Rails configuration that adjusts OmniAuth’s URL generation for production environments. It overrides the `full_host` method inside the `OmniAuth::Strategy` module to strip the path and query from the incoming request URL, force the port to 443 for HTTPS or 80 for HTTP, and return the cleaned absolute URI. The code uses Ruby’s `URI.parse` and the `request.url` helper to rebuild the host string. No data visualization is present; the snippet is purely an authentication-related code patch.

XXXX

55% match