Apresenta??o da nova Graph API do Facebook, esta que classifica e relaciona o conte¨²do da rede social em forma de um grafo contendo objects e connections e seus correlacionamentos
An introduction to Facebook Graph API and OAuth 2. This presentation covers basic example of Facebook Graph API, and including how OAuth 2 client-side flow works.
The document contains instructions for a bot to log in to various websites, create blog posts or bookmarks, and validate the results. It logs into sites like blog.com, alplist.com, url.org, and folkd.com. It creates posts and bookmarks, setting title, body, tags, and submitting. It checks for errors or success messages and gets the URL of the created post.
The Flash Facebook Cookbook - FlashMidlandsJames Ford
?
This document provides an overview of the Facebook Graph API. It begins with an introduction to the Graph API and what kind of data is available through it, with or without authentication. It then discusses the data structures and objects in the Graph API, including the different types of objects and how they are connected. The document also covers how to connect to the Graph API from JavaScript and ActionScript and discusses methods for retrieving, posting, and modifying data programmatically through the Graph API.
The fb:request-form tag creates a form that sends requests or invitations to selected Facebook users. It allows selecting multiple friends using tags like fb:multi-friend-selector. Required attributes include type, content, and optional attributes like invite. Form data like selected friend IDs is returned via POST variables. Examples demonstrate how to structure the form and handle submissions across different platforms.
The document summarizes the Twitter API and how to integrate it with PHP. It includes sections on the various Twitter API methods for timelines, statuses, users, lists, direct messages, spam reporting, saved searches, OAuth authentication and more. It also provides code examples for functions to get latest trends, display data in arrays, show a user's friends and followers, post a tweet, make URLs shorter with Bitly, get a user's last status, and linkify URLs in text.
Intro to developing for @twitterapi (updated)Raffi Krikorian
?
A short primer on how to develop for the Twitter API.
This is the newly edited version of http://www.slideshare.net/raffikrikorian/intro-to-developing-for-twitterapi
This document provides an overview of the Twitter API and how to develop applications using it. It discusses the main API endpoints including the REST API, Search API, and Streaming API. It also covers authenticating via OAuth, common libraries, rate limiting, and tools for interacting with the API like twurl and the Twitter developer console.
The Identity Problem of the Web and how to solve itBastian Hofmann
?
The document discusses identity on the web and potential solutions. It describes issues with having separate identities and passwords for different services. It then summarizes various single sign-on solutions like Microsoft Live ID, Facebook Connect, and OpenID. OpenID is explained in more detail, covering how it works and its limitations. OAuth is also summarized. The document argues that a simpler specification building on OAuth 2.0 that is easier to implement could help solve the identity problem on the web.
This document discusses Twitter's APIs for adding location information to tweets. It describes using services like myloc.me to add locations to tweets, setting a user's profile location, and Twitter's geotagging API which allows adding location meta-data without reducing tweet character count. It also outlines Twitter's trends API for accessing global and location-specific trending topics.
The document discusses building REST APIs and describes the principles of REST. It outlines the goals of building a REST API as a platform for innovation, long term stability, availability, uniform access, and low development costs. It describes using hypermedia and hyperlinks to navigate between resources and build stateless, cacheable APIs. The document provides examples of describing resources with XML or JSON, finding and retrieving single or multiple resources, and linking between related resources to build a RESTful workflow.
This document describes how to use personal links and PHP echo functions to track affiliate traffic and leads. It provides two solutions:
1. Driving affiliate traffic to your own affiliate hoplink. Personal links are created for each affiliate using their CB nickname as a unique ID. PHP echo prints the affiliate ID in the hoplink to track sales. Leads are tracked by adding a hidden "affid" field to the email form that gets auto-filled with the affiliate ID.
2. Driving affiliate traffic for your own CB product. This works the same way but prints the affiliate ID in the hoplink as the affiliate instead of just the ID. Commissions can be offered on both leads and product sales.
This document provides a list of over 800 link sources that can be used to build link wheels and structures for SEO purposes. It describes different types of link wheels and structures like link chains, closed link wheels, open link wheels, and random link wheels. It then lists hundreds of blog platforms, RSS directories, social bookmarking sites, forums, and other sites that can be used to build links and boost ranking. The goal is to pass link power from these various sites to a "Money site" to help it rank higher in search results.
The document provides an overview of the Facebook JavaScript SDK. It discusses loading and initializing the SDK, using it to check login status and perform login, subscribing to events, and making API calls to Facebook for user data and to post to Facebook. The SDK enables using Facebook features like the Like button and Login in websites and accessing the Graph API and FQL from JavaScript.
The document describes Socialtext's history and products from 2001-2010. It traces Socialtext's evolution from early wiki and collaboration tools to enterprise social software including dashboards, blogs, spreadsheets, and mobile apps. Key acquisitions and partnerships along the way include Google Spreadsheets, Twitter, and Facebook.
A few people like to say that passwords are dead, but the reality is far from it. First of all, we can't get rid of passwords entirely, because the alternatives all suck: physical tokens are easy to lose and retina scans are pretty creepy. What we should focus on is eliminating site-specific passwords.
Mozilla Persona was introduced at OSDC last year, but a number of new things have been added to it since. But more importantly, it's still the best shot we have at a decentralized web-wide identity system that works for average users and doesn't violate their privacy.
So I'm back to show you what's new and to talk about what organizations can gain from adding native support on their domain. It's time to solve the password problem on the web.
Overview of three Yahoo! Technologies. Build your Own Search Service (BOSS), Yahoo! Query Language (YQL) and the Yahoo! Application Platform (YAP) for the University of South Carolina
CIS13: Identity Tech Overview: Less Pain, More GainCloudIDSummit
?
Tim Bray, Developer Advocate, Google
Identity is tricky, and the penalties for getting it wrong are severe. Good news: technologies are surfacing that reduce developer pain while improving user experience. This talk highlights those technologies and introduces a framework, starting from your unique combination of constraints, users and platforms, to help you figure out which technologies and policies will work for you.
The Mobile Internet is Bigger Than You ThinkJason Grigsby
?
Presentation given at a Software Association of Oregon event. Overview of mobile technology space, challenges for app developers, and the opportunity.
Includes some slides from the EXCELLENT Morgan Stanley report on the Mobile Internet:
http://www.morganstanley.com/institutional/techresearch/mobile_internet_report122009.html
In fact, the title is borrowed from Mary Meeker's presentation at Web 2.0 Summit. It is my theme for 2010.
The document discusses how mobile technology is transforming journalism and media. Some key points:
- Mobile devices are the most important communication technology since the printing press.
- Mobile is the 7th mass media, with over 4.6 billion mobile subscribers worldwide, more than half the planet.
- Mobile represents a disruptive technology that is changing how media companies operate and distribute news/content.
- Usage of mobile internet and apps like Opera Mini are growing dramatically, showing people increasingly consuming media on mobile.
Building Consistent RESTful APIs in a high-performance environmentLinkedIn
?
This document discusses building consistent RESTful APIs in a high-performance environment. It provides examples of LinkedIn's RESTful APIs and how they follow best practices like having a domain model foundation and allowing flexible, fine-grained requests and responses. The document also discusses how LinkedIn uses an incentive system to encourage API partners to optimize their usage in a way that reduces costs for both LinkedIn and the partners.
1. The document discusses Facebook Login and the Open Graph protocol. It explains how to implement Facebook Login on a website by adding a Facebook app, obtaining app credentials, redirecting users to Facebook for login, and exchanging tokens to obtain long-lived access tokens.
2. It also covers how the Open Graph protocol allows websites to provide metadata so that content shared to Facebook is enriched with things like images, titles, and descriptions from the page.
3. The document provides code examples and links to Facebook developer documentation for implementing Facebook Login and integrating with the Open Graph.
The document discusses the Open Graph API and Facebook Graph API. It provides information on social plugins, like buttons and comments that can be added to websites. It also describes how different types of Facebook data, such as users, pages, events etc. can be accessed programmatically through unique URLs. Finally, it covers authentication methods for the APIs including OAuth 2.0 and the older REST API.
The document provides an overview of Facebook's API capabilities and the different types of applications that can be developed using the Facebook API. It discusses how the Facebook API allows developers to access user profile information, friends, photos, and groups. It also describes the different types of Facebook applications that can be built, including external web applications, external desktop applications, and internal Facebook applications. The document then provides examples of code for retrieving user data from Facebook and displaying it on an ASP.NET application page.
Facebook API for Developers : Introducing the Facebook PlatformWildan Maulana
?
The document summarizes the Facebook platform for application developers. It covers the history of Facebook and introduces the main elements that make up the Facebook Platform, including the REST API, Facebook Query Language (FQL), Facebook JavaScript (FBJS), and client libraries. Facebook launched its platform in 2007 to enable third-party applications to integrate with Facebook and access user data and features through these application programming interfaces and software development kits.
Managing your Business APIs is using WSO2 API Manager WSO2
?
This document discusses managing business APIs using WSO2 API Manager. It covers transforming web services, data feeds, and external APIs into business APIs. It then discusses managing, monitoring, securing, scaling, and controlling business APIs. It also covers analyzing and identifying business patterns from API usage data using tools like WSO2 Business Activity Monitor. The goal is to explain how WSO2 API Manager can help manage the full lifecycle of business APIs.
This document provides an overview of the Twitter API and how to develop applications using it. It discusses the main API endpoints including the REST API, Search API, and Streaming API. It also covers authenticating via OAuth, common libraries, rate limiting, and tools for interacting with the API like twurl and the Twitter developer console.
The Identity Problem of the Web and how to solve itBastian Hofmann
?
The document discusses identity on the web and potential solutions. It describes issues with having separate identities and passwords for different services. It then summarizes various single sign-on solutions like Microsoft Live ID, Facebook Connect, and OpenID. OpenID is explained in more detail, covering how it works and its limitations. OAuth is also summarized. The document argues that a simpler specification building on OAuth 2.0 that is easier to implement could help solve the identity problem on the web.
This document discusses Twitter's APIs for adding location information to tweets. It describes using services like myloc.me to add locations to tweets, setting a user's profile location, and Twitter's geotagging API which allows adding location meta-data without reducing tweet character count. It also outlines Twitter's trends API for accessing global and location-specific trending topics.
The document discusses building REST APIs and describes the principles of REST. It outlines the goals of building a REST API as a platform for innovation, long term stability, availability, uniform access, and low development costs. It describes using hypermedia and hyperlinks to navigate between resources and build stateless, cacheable APIs. The document provides examples of describing resources with XML or JSON, finding and retrieving single or multiple resources, and linking between related resources to build a RESTful workflow.
This document describes how to use personal links and PHP echo functions to track affiliate traffic and leads. It provides two solutions:
1. Driving affiliate traffic to your own affiliate hoplink. Personal links are created for each affiliate using their CB nickname as a unique ID. PHP echo prints the affiliate ID in the hoplink to track sales. Leads are tracked by adding a hidden "affid" field to the email form that gets auto-filled with the affiliate ID.
2. Driving affiliate traffic for your own CB product. This works the same way but prints the affiliate ID in the hoplink as the affiliate instead of just the ID. Commissions can be offered on both leads and product sales.
This document provides a list of over 800 link sources that can be used to build link wheels and structures for SEO purposes. It describes different types of link wheels and structures like link chains, closed link wheels, open link wheels, and random link wheels. It then lists hundreds of blog platforms, RSS directories, social bookmarking sites, forums, and other sites that can be used to build links and boost ranking. The goal is to pass link power from these various sites to a "Money site" to help it rank higher in search results.
The document provides an overview of the Facebook JavaScript SDK. It discusses loading and initializing the SDK, using it to check login status and perform login, subscribing to events, and making API calls to Facebook for user data and to post to Facebook. The SDK enables using Facebook features like the Like button and Login in websites and accessing the Graph API and FQL from JavaScript.
The document describes Socialtext's history and products from 2001-2010. It traces Socialtext's evolution from early wiki and collaboration tools to enterprise social software including dashboards, blogs, spreadsheets, and mobile apps. Key acquisitions and partnerships along the way include Google Spreadsheets, Twitter, and Facebook.
A few people like to say that passwords are dead, but the reality is far from it. First of all, we can't get rid of passwords entirely, because the alternatives all suck: physical tokens are easy to lose and retina scans are pretty creepy. What we should focus on is eliminating site-specific passwords.
Mozilla Persona was introduced at OSDC last year, but a number of new things have been added to it since. But more importantly, it's still the best shot we have at a decentralized web-wide identity system that works for average users and doesn't violate their privacy.
So I'm back to show you what's new and to talk about what organizations can gain from adding native support on their domain. It's time to solve the password problem on the web.
Overview of three Yahoo! Technologies. Build your Own Search Service (BOSS), Yahoo! Query Language (YQL) and the Yahoo! Application Platform (YAP) for the University of South Carolina
CIS13: Identity Tech Overview: Less Pain, More GainCloudIDSummit
?
Tim Bray, Developer Advocate, Google
Identity is tricky, and the penalties for getting it wrong are severe. Good news: technologies are surfacing that reduce developer pain while improving user experience. This talk highlights those technologies and introduces a framework, starting from your unique combination of constraints, users and platforms, to help you figure out which technologies and policies will work for you.
The Mobile Internet is Bigger Than You ThinkJason Grigsby
?
Presentation given at a Software Association of Oregon event. Overview of mobile technology space, challenges for app developers, and the opportunity.
Includes some slides from the EXCELLENT Morgan Stanley report on the Mobile Internet:
http://www.morganstanley.com/institutional/techresearch/mobile_internet_report122009.html
In fact, the title is borrowed from Mary Meeker's presentation at Web 2.0 Summit. It is my theme for 2010.
The document discusses how mobile technology is transforming journalism and media. Some key points:
- Mobile devices are the most important communication technology since the printing press.
- Mobile is the 7th mass media, with over 4.6 billion mobile subscribers worldwide, more than half the planet.
- Mobile represents a disruptive technology that is changing how media companies operate and distribute news/content.
- Usage of mobile internet and apps like Opera Mini are growing dramatically, showing people increasingly consuming media on mobile.
Building Consistent RESTful APIs in a high-performance environmentLinkedIn
?
This document discusses building consistent RESTful APIs in a high-performance environment. It provides examples of LinkedIn's RESTful APIs and how they follow best practices like having a domain model foundation and allowing flexible, fine-grained requests and responses. The document also discusses how LinkedIn uses an incentive system to encourage API partners to optimize their usage in a way that reduces costs for both LinkedIn and the partners.
1. The document discusses Facebook Login and the Open Graph protocol. It explains how to implement Facebook Login on a website by adding a Facebook app, obtaining app credentials, redirecting users to Facebook for login, and exchanging tokens to obtain long-lived access tokens.
2. It also covers how the Open Graph protocol allows websites to provide metadata so that content shared to Facebook is enriched with things like images, titles, and descriptions from the page.
3. The document provides code examples and links to Facebook developer documentation for implementing Facebook Login and integrating with the Open Graph.
The document discusses the Open Graph API and Facebook Graph API. It provides information on social plugins, like buttons and comments that can be added to websites. It also describes how different types of Facebook data, such as users, pages, events etc. can be accessed programmatically through unique URLs. Finally, it covers authentication methods for the APIs including OAuth 2.0 and the older REST API.
The document provides an overview of Facebook's API capabilities and the different types of applications that can be developed using the Facebook API. It discusses how the Facebook API allows developers to access user profile information, friends, photos, and groups. It also describes the different types of Facebook applications that can be built, including external web applications, external desktop applications, and internal Facebook applications. The document then provides examples of code for retrieving user data from Facebook and displaying it on an ASP.NET application page.
Facebook API for Developers : Introducing the Facebook PlatformWildan Maulana
?
The document summarizes the Facebook platform for application developers. It covers the history of Facebook and introduces the main elements that make up the Facebook Platform, including the REST API, Facebook Query Language (FQL), Facebook JavaScript (FBJS), and client libraries. Facebook launched its platform in 2007 to enable third-party applications to integrate with Facebook and access user data and features through these application programming interfaces and software development kits.
Managing your Business APIs is using WSO2 API Manager WSO2
?
This document discusses managing business APIs using WSO2 API Manager. It covers transforming web services, data feeds, and external APIs into business APIs. It then discusses managing, monitoring, securing, scaling, and controlling business APIs. It also covers analyzing and identifying business patterns from API usage data using tools like WSO2 Business Activity Monitor. The goal is to explain how WSO2 API Manager can help manage the full lifecycle of business APIs.
O documento fornece uma vis?o geral do Gerenciador de Neg¨®cios do Facebook, que permite que empresas gerenciem suas P¨¢ginas, contas de an¨²ncios e permiss?es em um ¨²nico lugar. O Gerenciador de Neg¨®cios ajuda a reduzir o tempo gasto com logins compartilhados e permiss?es, al¨¦m de fornecer maior controle sobre quem tem acesso aos ativos da empresa.
Este ¨¦ um material desenvolvido pelo Facebook para divulga??o da ferramenta Gerenciador de Neg¨®cios e est¨¢ sendo utilizado como material de apoio no blog KaueKGG.com.br na s¨¦rie de publica??es sobre o Business Manager.
Confira em http://kauekgg.com.br/business-manager
Dokumen tersebut membahas pengantar mengenai JSON (JavaScript Object Notation), yaitu format pertukaran data ringan yang banyak digunakan untuk mentransmisikan data terstruktur melalui jaringan. JSON dirancang berdasarkan subset bahasa JavaScript dan memungkinkan representasi struktur data sederhana seperti objek dan array. Dokumen tersebut juga menjelaskan contoh sintaks JSON dan beberapa pranala terkait.
Tutorial ini menjelaskan cara mengkonsumsi Facebook API untuk mengambil dan memposting data profil pengguna. Langkahnya adalah membuat aplikasi Facebook, menyiapkan hosting virtual, menginstal library Facebook PHP SDK menggunakan Composer, dan mengkoding konsumsi API untuk halaman login dan profil pengguna.
The Facebook Open Stream API allows third-party developers to access and display Facebook users' activity streams within their own applications. Developers can filter and remix streams to show status updates, photos, videos, notes, likes, and comments. The API includes a live stream widget that can be embedded to display streams on app canvases, profile tabs, or external websites using simple code. Developers must consider authentication, stream permissions, and methods for reading and publishing stream stories when using the Open Stream API.
Pengembangan Mobile Learning (Android) dengan eXeLearning dan PhoneGap BuildWahyu Purnomo
?
Cara mudah membuat konten mobile learning berbasis Android dengan eXeLearning dan PhoneGap build
disampaikan pada Kuliah Umum Media Pembelajaran di FKIP Unisma, bersama Dr. Sri Wahyuni, M.Pd
Januari 2014
The document discusses Facebook Open Graph authentication and permissions. It provides information on obtaining access tokens, requesting additional permissions from users, and making requests to the Graph API using access tokens. It also includes charts detailing properties and connections for various Graph API objects like events, comments, albums, and more.
Participating websites with Facebook Connect will be able to display information personalized to your interests ¡ª without requiring you to sign in at that website or provide it with any information.
The document discusses Facebook's Open Graph and how it allows any object like companies, brands, products, content or ideas to be part of the social graph. It outlines social plugins like the Like button, activity feed, and recommendations that allow sites to integrate with Facebook. It encourages companies to "stake their claim" and leverage the Open Graph to gain earned social media through likes, shares and recommendations which have a potential 135x multiplier effect. It also notes the benefits of enhanced search results if a company starts their Facebook Search Optimization and the importance of the Facebook news feed, where likes allow opting users into the stream.
Building Serverless Applications with Microsoft Graph - ECS 2018Dragan Panjkov
?
This document discusses Microsoft Graph and permissions for accessing user and organizational data through the Graph API. It explains that users can consent to applications accessing their own data, while administrators can consent on behalf of all users. It also provides examples of Graph API URLs and parameters for querying resources and outlines ways to implement user and application permissions to obtain access to data through the Graph API.
OAuth is a standard protocol for authorization that avoids directly sharing usernames and passwords between applications. It allows applications to request and receive limited access to a user's data without giving out their credentials. The OAuth protocol defines authorization flows for different use cases and allows applications to request different scopes of access. Facebook implements OAuth to allow third-party applications to access user data on Facebook in a secure manner by using access tokens rather than credentials.
Social networks integration using node js:
1. OAuth2
2. API consumption
3. everyauth vs. passport.js
the demo code can be found under my github repo - https://github.com/orkaplan/social-demo
This document summarizes the Douban API and authentication methods. It describes Douban as a social networking site focused on books, movies, music and more. It then outlines the different Douban APIs available and how third-party apps can integrate and be powered by the Douban API. Finally, it details the different OAuth 2.0 authentication flows including client-side, server-side, and native app flows for obtaining access tokens to make requests to the Douban API on behalf of a user.
This document provides an overview of OAuth and OAuth2 authentication protocols. It discusses the key components of OAuth including the resource owner, client, authorization server and access tokens. It explains the OAuth workflow and signature process. It also covers OAuth2 improvements like removing the need for cryptography and access tokens being short-lived. Finally, it discusses implementations of OAuth in Ruby using gems like OAuth and Faraday as well as OmniAuth for multi-provider authentication in Rails applications.
I used to dislike OAuth (Open Standard for Authentication): how do I implement it? In this slideshow, we delve into consuming it with the Google APIs. We go first into the background and then step-by-step through the process. Follow along today!
This document summarizes a Flutter meetup in Tokyo, including discussions on changing the app launcher icon and name in Flutter apps, developing Flutter packages and plugins, and a new Flutter plugin called flutter_launcher_name that allows changing the launcher name. Links and resources are provided for modifying app icons and names, developing packages, and the GitHub repo for the flutter_launcher_name plugin.
Integrating OAuth and Social Login Into WordpressWilliam Tam
?
My presentation at #wpnyc WordCampNYC 2016. An overview of how OAuth works (mostly OAuth2), and techniques for integrating it in plugins, themes, and as part of 'social login' for websites.
The document discusses Facebook integration for a travel application built with CakePHP. It provides an overview of key integration points including the Connect button, profile pictures, and publishing actions to Facebook. It also outlines the application structure, installing the Facebook PHP library, configuring the application, and implementing specific controllers and views for Facebook authentication and authorization.
The document provides an overview of the history and development of OAuth standards for authorization. It describes some of the issues with early implementations that prompted the creation of OAuth 1.0, including services storing user passwords and lack of ability to revoke access. OAuth 1.0 introduced signatures to address these issues. OAuth 2.0 replaced signatures with HTTPS and defines common flows for different use cases, including authorization code, implicit, password, and client credentials grants.
Firefox Sync allows users to sync bookmarks, tabs, passwords and other data between devices. The document discusses setting up a local instance of Firefox Sync using Python and the Mercurial source code repository. It provides instructions for installing dependencies, running the Sync server on port 5000, and making a patch to fix an error binding parameters to SQLite.
Leveraging Rails to Build Facebook AppsDavid Keener
?
This presentation is a distillation of some of the practical tactics that David Keener's development team at MetroStar Systems has used to create highly successful FaceBook applications using Rails, including real-life systems like PollCast, Iran Voices and the Votridea Contest Platform. FaceBook is the world's largest social network, with over 500 million members.
This document discusses OAuth 2.0 and its use for API security. It describes the key concepts in OAuth including the roles of clients, resource owners, authorization servers, and resource servers. It explains the authorization code, implicit, resource owner password credentials, and client credentials grant types. It also covers refresh tokens, token introspection, and token revocation, including examples of how these concepts work together to securely authenticate users and grant access to protected resources.
OAuth is an open standard for authentication that allows users to log into third party applications using their existing credentials from another service, without having to expose their password. OEmbed is a format for converting URLs into embeddable rich content like photos or videos. It allows websites to display content from other sites without having to manually embed HTML or write custom code. Both standards aim to simplify authentication and content embedding while keeping users' data and identities secure.
The document discusses social design and the Facebook platform. It provides tips for using Open Graph tags and actions like Like, Send, and Share to optimize content distribution and engagement. It also covers connecting apps to Facebook for identity, personalization using social context, and driving distribution by making sharing easy. The goal is to identify users, add value at key touchpoints, and enable contribution back to the social graph.
Plugins on OnDemand with Remote Apps - Atlassian Summit 2012 Atlassian
?
The document discusses how remote apps allow developers to integrate third party applications into Atlassian's OnDemand service. Remote apps use a simple descriptor file to register the app and define things like permissions, pages, and macros. This avoids the complexity of developing plugins and allows apps to be built using any programming language. Examples are provided of how to create a Lucidchart diagramming app using remote apps.
O documento discute oportunidades para times de data science em empresas, incluindo melhorar recomenda??es de conte¨²do e material para usu¨¢rios, otimizar a produ??o de v¨ªdeos, apoiar design e UX, e analisar dados para apoiar o neg¨®cio e tomar decis?es. Tamb¨¦m menciona a import?ncia de times de data science trabalharem pr¨®ximos aos neg¨®cios e terem habilidades semelhantes a times de devOps.
m¨¦tricas para produtos e times ¨¢geisFagner Moura
?
Com p¨²blico diverso (QA, dev, neg¨®cio e atendimento), a id¨¦ia foi apresentar os valores por tr¨¢s do movimento ¨¢gil, suas vertentes e como o sistema envolvido, o time, pode ser guiado a tomar melhores decis?es baseando-se em dados.
O documento discute como Scrum pode ser usado para mais do que apenas gerenciamento de projetos ¨¢geis, permitindo a descoberta, gera??o de conhecimento e inova??o respons¨¢vel atrav¨¦s de experimenta??o e aprendizado constante. Ele tamb¨¦m explora como princ¨ªpios de outras metodologias como Lean e Kanban podem ser incorporados ao Scrum para aprimorar ainda mais os processos de desenvolvimento.
The document discusses various types of app extensions for iOS, including today widgets, share extensions, action extensions, photo editing extensions, document provider extensions, custom keyboards, and how to implement them. It notes that extensions add contextualized functionality beyond the core app, are disabled by default, and communicate with the containing app indirectly through defined extension points and the NSExtensionContext class.
O documento discute a concorr¨ºncia no iOS, comparando as abordagens usando a biblioteca Grand Central Dispatch (GCD) e NSOperations. A GCD fornece filas globais e personalizadas para executar tarefas de forma ass¨ªncrona e concorrente. NSOperations usa a GCD por tr¨¢s dos panos para gerenciar opera??es de forma KVO compliant. Blocks s?o recomendados para implementar tarefas concorrentes de forma concisa e segura.
Couchbase is a distributed key-value NoSQL database that was released in 2010 and is used by companies like Heroku and Zynga. It uses a simple and fast binary/ascii protocol like Memcached and provides features like easy node management, automatic rebalancing without downtime, throughput that scales linearly, and a nice admin interface. It has an asynchronous persistence architecture with temporary data and "hot keys" stored in memory. It also supports vbucket mapping, a proxy called Moxy for protocol conversion, and dynamic reconfiguration. Couchbase is simple, fast and elastic with no schema required, easy configuration, and quick start times. It promises low latency and no application waiting with multi-threaded and asynchronous processing.
O documento descreve o Redmine, uma ferramenta de desenvolvimento colaborativo que permite controlar documentos, wiki, newsletters, status de tarefas e gerenciamento de vers?o em um ¨²nico lugar, com foco nos tickets de projeto - permitindo verificar pend¨ºncias, atualizar andamentos e finalizar tickets. A documenta??o ¨¦ importante para garantir a qualidade ou evitar perda de tempo.
31. server side flow
App try to access OAuth Dialog
Facebook (App Authorization)
OAuth Dialog
(User Authentication)
curl -F 'client_id=113391995351148'
-F 'redirect_uri=http://facebook-buraco-debug.jogatina.com.....'
https://www.facebook.com/dialog/oauth
32. server side flow
App try to access OAuth Dialog
Facebook (App Authorization)
OAuth Dialog
(User Authentication)
curl -F 'client_id=113391995351148'
-F 'redirect_uri=http://facebook-buraco-debug.jogatina.com.....'
-F 'scope=email, read_stream'
https://www.facebook.com/dialog/oauth
33. server side flow
App try to access OAuth Dialog
Facebook (App Authorization)
OAuth Dialog
(User Authentication)
Cookie not found, show OAuth Dialog (facebook layout)
34. server side flow
App try to access OAuth Dialog
Facebook (App Authorization)
OAuth Dialog
(User Authentication)
goes to App authorization directly
35. server side flow
OAuth Dialog HTTP 302
(App Authorization) (redirect_url param)
OAuth Dialog
User Authentication)
don?t allow !
redirect with some params like: error_reason, error, etc.
36. server side flow
OAuth Dialog HTTP 302
(App Authorization) (redirect_url param)
OAuth Dialog
User Authentication)
allow !
redirect with authorization code param
43. client side flow
HTTP 302
HTTP request
(redirect_url param)
Pass URI fragment with access_token
http://jogatina.com....#access_token=gzZ666a..&expires_in=64090