Skip to content

Instantly share code, notes, and snippets.

👨‍💻
Back to business

Evgeny Zborovsky yuv4ik

👨‍💻
Back to business
Block or report user

Report or block yuv4ik

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@yuv4ik
yuv4ik / README.md
Last active Nov 9, 2018
PCL@.NET Standard
View README.md
@PurpleBooth
PurpleBooth / README-Template.md
Last active Sep 17, 2019
A template to make good README.md
View README-Template.md

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

@luca-barbieri
luca-barbieri / Facebook.cs
Last active Feb 16, 2018
Facebook Login button for Xamarin Forms
View Facebook.cs
// This code has been placed in the public domain.
// NO WARRANTY OF ANY KIND
// WORK IN PROGRESS AND ONLY LIMITED TESTING, MIGHT BE PARTIALLY BROKEN
// Note that you need to setup both your iOS and Android projects to include your app id and so on for this to actually work (see the Facebook docs for each platform)
// Common
public class FacebookLoginEventArgs : EventArgs
{
@subudeepak
subudeepak / WebSockets.md
Last active Sep 17, 2019
The problems and some security implications of websockets - Cross-site WebSockets Scripting (XSWS)
View WebSockets.md

WebSockets - An Introduction

WebSockets is a modern HTML5 standard which makes communication between client and server a lot more simpler than ever. We are all familiar with the technology of sockets. Sockets have been fundamental to network communication for a long time but usually the communication over the browser has been restricted. The general restrictions

  • The server used to have a permanent listener while the client (aka browser) was not designated any fixed listener for a more long term connection. Hence, every communication was restricted to the client demanding and the server responding.
  • This meant that unless the client requested for a particular resource, the server was unable to push such a resource to the client.
  • This was detrimental since the client is then forced to check with the server at regular intervals. This meant a lot of libraries focused on optimizing asynchronous calls and identifying the response of asynchronous calls. Notably t
@irazasyed
irazasyed / homebrew-permissions-issue.md
Last active Sep 17, 2019
Homebrew: Permissions Denied Issue Fix (OS X / macOS)
View homebrew-permissions-issue.md

Homebrew Permissions Denied Issues Solution

sudo chown -R $(whoami) $(brew --prefix)/*

@stephenhardy
stephenhardy / git-clearHistory
Created Apr 26, 2013
Steps to clear out the history of a git/github repository
View git-clearHistory
-- Remove the history from
rm -rf .git
-- recreate the repos from the current content only
git init
git add .
git commit -m "Initial commit"
-- push to the github remote repos ensuring you overwrite history
git remote add origin git@github.com:<YOUR ACCOUNT>/<YOUR REPOS>.git
@CristinaSolana
CristinaSolana / gist:1885435
Created Feb 22, 2012
Keeping a fork up to date
View gist:1885435

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
You can’t perform that action at this time.