CoreyCole

# 0 is too far from ` ;)
set -g base-index 1

# Automatically set window title
set-window-option -g automatic-rename on
set-option -g set-titles on

#set -g default-terminal screen-256color
set -g status-keys vi
set -g history-limit 10000

CoreyCole

### INSTALLATION NOTES ###
# 1. Install Homebrew (https://github.com/mxcl/homebrew)
# 2. brew install zsh
# 3. Install OhMyZsh (https://github.com/robbyrussell/oh-my-zsh)
# 4. brew install reattach-to-user-namespace --wrap-pbcopy-pbpaste && brew link reattach-to-user-namespace
# 5. Install iTerm2
# 6. In iTerm2 preferences for your profile set:
#      Character Encoding: Unicode (UTF-8)
#      Report Terminal Type: xterm-256color
# 7. Put itunesartist and itunestrack into PATH

CoreyCole

[18-08-21 11:25:18.728] NativeScript debugger was not able to get inspector socket port., Error: NativeScript debugger was not able to get inspector socket port.
at Errors.fail (/Users/corey/.npm-global/lib/node_modules/nativescript/lib/common/errors.js:125:28)
at IOSDebugService.<anonymous> (/Users/corey/.npm-global/lib/node_modules/nativescript/lib/services/ios-debug-service.js:233:30)
at Generator.next (<anonymous>)
at fulfilled (/Users/corey/.npm-global/lib/node_modules/nativescript/lib/services/ios-debug-service.js:4:58)
at <anonymous>
[18-08-21 11:25:18.737] (CLI) (node:21116) UnhandledPromiseRejectionWarning: Error: Cannot connect to device socket. The error message is NativeScript debugger was not able to get inspector socket port.
at Errors.fail (/Users/corey/.npm-global/lib/node_modules/nativescript/lib/common/errors.js:125:28)
at Errors.failWithoutHelp (/Users/corey/.npm-global/lib/node_modules/nativescript/lib/common/errors.js:135:21)
at SocketProxyFactory.<anonymous> (/Users/corey/.npm-global/lib

CoreyCole

[18-08-21 11:21:36.348] NativeScript Sidekick version: 1.12.0-v.2018.8.14.2
[18-08-21 11:21:37.012] Dependencies versions: NodeJS: 8.11.1, npm: 5.6.0, NativeScript CLI: 4.2.2.
[18-08-21 11:21:37.046] Checking for updates...
[18-08-21 11:21:37.215] No updates available.
[18-08-21 11:21:38.129] (CLI) Using NativeScript CLI located in /Users/corey/.npm-global/lib/node_modules/nativescript
[18-08-21 11:21:38.903] (CLI) Searching for devices...
[18-08-21 11:21:39.238] Loaded CLI extension nativescript-cloud, version 1.13.0.
[18-08-21 11:21:39.241] Loaded CLI extension nativescript-starter-kits, version 0.3.4.
[18-08-21 11:21:43.591] The user Corey Cole  logged in.
[18-08-21 11:21:47.924] Devices service initialized.

CoreyCole

Keybase proof

I hereby claim:

• I am coreycole on github.
• I am coreycole (https://keybase.io/coreycole) on keybase.
• I have a public key ASDPblmT8KXriULPAmcRJA_FImur-Qin96cGYf1MLx3n4go

To claim this, I am signing this object:

CoreyCole

static void
handle_media_stream (GstPad * pad, GstElement * pipe, const char *convert_name,
    const char *sink_name)
{
  GstPad *qpad, *rtp_sink, *rtp_src, *rtcp_src, *rtp_udp_sink, *rtcp_udp_sink;
  GstElement *q, *conv, *resample, *opusenc, *rtpopuspay, *rtpbin, *rtp_udpsink, *rtcp_udpsink;
  GstPadLinkReturn ret;
  gchar *rtpopuspay_string, *rtp_udpsink_string, *rtcp_udpsink_string;

  g_print ("Trying to handle stream with %s ! %s", convert_name, sink_name);

CoreyCole

static gboolean
start_pipeline (void)
{
  GstStateChangeReturn ret;
  GError *error = NULL;
  // GstCaps *audio_caps;
  // GstWebRTCRTPTransceiver *trans = NULL;
  // GArray *transceivers = NULL;

  pipe1 =

CoreyCole

Below is the architecture I’d use for a multiplayer todo app with Leptos + Datastar + Axum SSE.

The important design choice: Leptos renders typed server-side HTML components. Datastar owns browser events and DOM patching. Axum owns routes, mutations, and SSE streams. Do not hydrate the same DOM subtree with Leptos WASM and then also morph it with Datastar.

Datastar’s model fits this well because it patches HTML elements from the backend using SSE and morphing, so the backend can stay the source of truth. ([Datastar][1]) The Rust SDK has Axum integration and PatchElements/PatchSignals primitives. ([Docs.rs][2]) Leptos supports SSR, and its Axum integration exists for server-side apps, but in this guide we are using Leptos mostly as a typed HTML renderer rather than a hydrated client framework. ([Leptos Book][3])

---

Goal