Gianfranco P gianpaj

2023 update

ℹ️ Please note this research is from 2016 when Opera has first added their browser "VPN", even before the "Chinese deal" was closed. They have since introduced some real VPN apps but this below is not about them.

🕵️ Some folks also like to use this article to show a proof that the Opera browser is a spyware or that Opera sells all your data to 3rd parties or something like that. This article here doesn't say anything like that.

When setting up (that's immediately when user enables it in settings) Opera VPN sends few API requests to https://api.surfeasy.com to obtain credentials and proxy IPs, see below, also see The Oprah Proxy.

The browser then talks to a proxy de0.opera-proxy.net (when VPN location is set to Germany), it's IP address can only be resolved from within Opera when VPN is on, it's 185.108.219.42 (or similar, see below). It's an HTTP/S proxy which requires auth.

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

To run on ios:

Install XCode (recommended) or XCode command line tools by xcode-select --install
Into XCode settings, go to "Downloads" tab and download iOS 9.2 emulator
Compile native app and run it on simulator via npm run ios

To run on Android:

Set up Android environment
Create emulator via npm run android-emulator-create
Run emulator via npm run android-emulator
Compile native code and run it on emulator via npm run android

	{
	"name": "flow",
	"version": "1.0.0",
	"main": "index.js",
	"license": "MIT",
	"scripts": {
	"start": "npm-run-all --parallel styles:watch browsersync",
	"styles:watch": "node-sass --watch style.scss style.css",
	"browsersync": "browser-sync start --server --files \".html, .js, *.css\""
	},

	//
	// Quick & Dirty Google Cloud Storage emulator for tests. Requires
	// `stream-buffers` from npm. Use it like this:
	//
	// `new MockStorage().bucket('my-bucket').file('my_file').createWriteStream()`
	//

	class MockStorage {
	buckets: {[name: string]: MockBucket};

	{
	"presets": [
	"react",
	"es2015"
	],
	"sourceMaps": "inline",
	"retainLines": true
	}

	import { expect } from 'chai';
	import superagent from 'superagent';
	import mockSuperagent from 'superagent-mock';
	import * as Errors from '../../../common/utils/errors';

	// Under test.
	import login from './login';

	describe(`login api`), () => {
	const serverEndPoint = `http://foobar.com/login`;

	# Sample Nginx config with sane caching settings for modern web development
	#
	# Motivation:
	# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
	# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
	# and juicy version of your assets available.
	# At some point, however, you want to show your work to testers, your boss or your client.
	# After you implemented and deployed their feedback, they reload the testing page – and report
	# the exact same issues as before! What happened? Of course, they did not have developer tools
	# open, and of course, they did not empty their caches before navigating to your site.

	module.exports = (string) => {
	return string.replace(/([a-z0-9]\|(?=[A-Z]))([A-Z])/g, '$1-$2').toLowerCase();
	};