Skip to content

Instantly share code, notes, and snippets.

@raucao
raucao / uri.js
Created September 6, 2012 10:14 — forked from jlong/uri.js
URI Parsing with Javascript
var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";
parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port; // => "3000"
parser.pathname; // => "/pathname/"
parser.search; // => "?search=test"
parser.hash; // => "#hash"
parser.host; // => "example.com:3000"
@raucao
raucao / my.css
Created January 6, 2015 15:50 — forked from anonymous/my.css
background: linear-gradient(270deg, #219f7e, #3d9cd1);
background-size: 400% 400%;
-webkit-animation: AnimationName 30s ease infinite;
-moz-animation: AnimationName 30s ease infinite;
-o-animation: AnimationName 30s ease infinite;
animation: AnimationName 30s ease infinite;
@-webkit-keyframes AnimationName {
    0%{background-position:0% 50%}
    50%{background-position:100% 50%}
    100%{background-position:0% 50%}
@raucao
raucao / wifi.json
Last active January 22, 2016 17:58 — forked from beanieboi/wifi.json
Hackerbeach Wifi Passwords
{
"places": [
{
"name": "Surf Shak",
"SSID": "Bar Surf",
"password": "shak2525"
},
{
"name": "Hostal Rutamar",
"SSID": "HOSTAL RUTAMAR",
@raucao
raucao / mastodon_backup.sh
Created January 21, 2018 17:23 — forked from nolanlawson/mastodon_backup.sh
Script to back up a Mastodon instance
#!/usr/bin/env bash
#
# Make a backup file of a Mastodon instance. The backup file is a TGZ containing
# the Postgres dump as well as the /public/system (media) files and the
# .env.production file. For loading the dump file contents, see:
# https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Migration-guide.md
#
# Usage: ./mastodon_backup.sh my_dump_file.tgz
#
# Advanced usage: MASTODON_LIVE_DIRECTORY=/path/to/live ./mastodon_backup.sh my_dump_file.tgz

A/V calls in Conversations

Here are some short notes for server admins and developers of other XMPP clients.

Notes for server admins

Most calls will require server side assistence. Depending on the network it might be enough to have a STUN server for Conversations to learn your external IP and punch a hole in the NAT. On some, more restrictive, networks however this isn’t enough and Conversations will need a TURN server. TURN servers are used to proxy the entire (encrypted) traffic through the server. (In my initial testing this was often the case when mobile networks were involved.)

To ensure best possible user experience in all situations server admins should set up both.