Description | Command |
---|---|
Start a new session with session name | screen -S <session_name> |
List running sessions / screens | screen -ls |
Attach to a running session | screen -x |
Attach to a running session with name | screen -r |
#!/usr/bin/env python3 | |
# encoding: utf-8 | |
"""Use instead of `python3 -m http.server` when you need CORS""" | |
from http.server import HTTPServer, SimpleHTTPRequestHandler | |
class CORSRequestHandler(SimpleHTTPRequestHandler): | |
def end_headers(self): | |
self.send_header('Access-Control-Allow-Origin', '*') |
mesh.traverseAncestors(function (parent) { | |
parent.updateMatrixWorld(true); | |
}) | |
var worldScale = mesh.getWorldScale(); | |
var worldRotation = mesh.getWorldQuaternion(); | |
var boxWidth: json.userData.size[0] * worldScale.x; | |
var boxHeight: json.userData.size[1] * worldScale.y; | |
var boxDepth: json.userData.size[2] * worldScale.z; |
<h1 class="shimmer">Some Shimmer Text</h1> | |
<style> | |
@import url('http://fonts.googleapis.com/css?family=Alegreya+Sans:300'); | |
body{ | |
background: #000; | |
} | |
.shimmer{ | |
/* styling stuff */ | |
font-family:"Alegreya Sans"; |
Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.
And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.
If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
I hereby claim:
- I am jb0gie on github.
- I am j_b0gie (https://keybase.io/j_b0gie) on keybase.
- I have a public key ASAcIngHjIQTTo8DGqifsQPgKRvTjTpMp-mkKi2e-8UVswo
To claim this, I am signing this object:
When compiling client files to webassembly, usually you'll end up with both .js and .wasm files.
By default, most webservers don't know about the wasm MIME type.
You'll likely see the following error:
wasm streaming compile failed: TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.
Here is how to add the wasm MIME type (on linux systems, apache + nginx):
Open /etc/mime.types You'll see two columns, media type on the left, file type on the right Add the line application/wasm wasm
using UnityEngine; | |
public class DistanceJoint3D : MonoBehaviour { | |
public Transform ConnectedRigidbody; | |
public bool DetermineDistanceOnStart = true; | |
public float Distance; | |
public float Spring = 0.1f; | |
public float Damper = 5f; |
I've been deceiving you all. I had you believe that Svelte was a UI framework β unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.
But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.
Svelte is a language.
Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?
A few projects that have answered this question:
A quick cheatsheet of useful snippet for Flutter
A widget is the basic type of controller in Flutter Material.
There are two type of basic Widget we can extend our classes: StatefulWidget
or StatelessWidget
.
StatefulWidget are all the widget that interally have a dynamic value that can change during usage. It can receive an input value in the constructor or reference to functions. You need to create two classes like: