| Settings on Twidere: | |
| API URL Format: https://your-host/[DOMAIN.]twitter.com/ | |
| Uncheck "Same OAuth signing URL" | |
| Uncheck "No verion suffix" | |
| Password login recommended. |
| # <type>: (If applied, this commit will...) <subject> (Max 50 char) | |
| # |<---- Using a Maximum Of 50 Characters ---->| | |
| # Explain why this change is being made | |
| # |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| | |
| # Provide links or keys to any relevant tickets, articles or other resources | |
| # Example: Github issue #23 |
| // ==UserScript== | |
| // @name Steam Queue Auto Discoverer | |
| // @description Discover the Steam queue three times to get the sale cards | |
| // @version 2.3.0 | |
| // @namespace https://gist.github.com/xPaw/73f8ae2031b4e528abf7 | |
| // @icon https://store.steampowered.com/favicon.ico | |
| // @match https://store.steampowered.com/explore* | |
| // @grant none | |
| // ==/UserScript== |
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
Note: There is a lot of information here, but if I have provided a link, it is probably something you should click on and read. OAuth is a complex enough subject on it's own, and hacking these two services together only adds to it.
Even so, I have found Firebase's API to be simpler than almost any other OAuth solution I have explored. When all is said and done, the important bits of code related to authentication is actually less than 10 lines. If you have ever tried to implement your own OAuth flow before, you know how amazing that is.
In the end, it may be worth using Firebase for authentication, even if that's the ONLY thing you use it for.
| doctype xml | |
| set_content_type('text/xml') | |
| date_format = "%Y-%m-%dT%H:%M:%S+00:00" | |
| posts = get_data(type="post", status=['public', 'secret'], limit=300) | |
| // | |
| This is a XML sitemap file. Which is supported by many search engines like Google. | |
| You can find more information about XML sitemap on `http://sitemaps.org`. |
| /** | |
| * Adapted from https://gist.github.com/hdragomir/8f00ce2581795fd7b1b7 | |
| * This version tries to load the font from localStorage. If it's not there it simply adds a link to the stylesheet | |
| * and ajaxes the contents in on load. This makes an extra request. But adding the stylesheet link renders quicker than | |
| * waiting for a response to the ajax request and then injecting the contents into a style tag, hopefully minimising the | |
| * FOUT you get when you view http://www.theguardian.com/ and http://www.smashingmagazine.com. | |
| */ | |
| (function () { | |
| "use strict"; | |
| // Once cached the css file is stored on the client forever. To invalidate the cache change this URL. |
Maintaining even a small mongodb application in production requires regular backups of remotely stored data. MongoDB gives you three ways to acomplish it. In this post I'm using monogodump command for creating a backup and mongorestore for recreating the data.
The purpose of this writing is to provide a simple way of periodic database dumps from a remote server to a Dropbox cloud storage.
Remember that for using
mongodumpyou have to have amongodprocess running.
Suppose that you want make a backup of your books database.
To create a dump use mongodump -d books -o which will result in a book folder containing bson files with all collections.
| <?php namespace GM\WWWPostThumbnail; | |
| /** | |
| * Plugin Name: WWW Post Thumbnail | |
| * Description: Allow to use an external image url as featured image. | |
| * Plugin URI: https://gist.github.com/Giuseppe-Mazzapica/928bc22e5f49a654cf7c | |
| * Author: Giuseppe Mazzapica | |
| * Author URI: https://github.com/Giuseppe-Mazzapica | |
| * License: MIT | |
| * Version: 0.1.0 | |
| * |
| ################################## | |
| # WORDPRESS NGINX CONFIGURATIONS | |
| ################################## | |
| # /etc/nginx/wordpress.conf | |
| # | |
| # Contains a common configuration for use by nginx on a WordPress | |
| # installation. This file should be included in any WordPress site | |
| # nginx virtual host config located in sites-available with the following line: | |
| # | |
| # include /etc/nginx/wordpress.config; |