| // ==UserScript== | |
| // @name SOJM | |
| // @namespace salembeats | |
| // @version 2.16 | |
| // @description Compare your earnings to the crowd, to tell whether it's "Slow, Or Just Me?" | |
| // @author Cuyler Stuwe (salembeats) | |
| // @include https://worker.mturk.com/dashboard* | |
| // ==/UserScript== | |
| const globals = { |
I’m looking for any tips or tricks for making chrome headless mode less detectable. Here is what I’ve done so far:
Set my args as follows:
const run = (async () => {
const args = [
'--no-sandbox',
'--disable-setuid-sandbox',
'--disable-infobars',
| { | |
| "global": { | |
| "check_for_updates_on_startup": true, | |
| "show_in_menu_bar": false, | |
| "show_profile_name_in_menu_bar": false | |
| }, | |
| "profiles": [ | |
| { | |
| "complex_modifications": { | |
| "parameters": { |
| /** | |
| * A LocalStorage-based mutex. Guarantees¹ that only one browser window will be | |
| * able to execute the code inside the callback at a time. | |
| * | |
| * Based on the Alur and Taubenfeld fast lock | |
| * (http://www.cs.rochester.edu/research/synchronization/pseudocode/fastlock.html) | |
| * with an added timeout to ensure there will be eventual progress in the event | |
| * that a window is closed in the middle of the callback. | |
| * | |
| * 1. The guarantee assumes that the algorithm is correctly implemented. |
| let clickStream = Rx.Observable.fromEvent(document.getElementById('link'), 'click'); | |
| clickStream | |
| .buffer(clickStream.debounce(250)) | |
| .map(list => list.length) | |
| .filter(x => x === 2) | |
| .subscribe(() => { | |
| console.log('doubleclick'); | |
| }) |
| /* bling.js */ | |
| window.$ = document.querySelectorAll.bind(document); | |
| Node.prototype.on = window.on = function (name, fn) { | |
| this.addEventListener(name, fn); | |
| } | |
| NodeList.prototype.__proto__ = Array.prototype; |
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com, example2.com, and example1.com/images on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
