kintar

pm disable-user --user 0 com.samsung.android.bixby.agent

pm disable-user --user 0 com.samsung.android.bixby.es.globalaction

pm disable-user --user 0 com.samsung.android.bixbyvision.framework

pm disable-user --user 0 com.samsung.android.bixby.wakeup

pm disable-user --user 0 com.samsung.android.bixby.plmsync

kintar

// ==UserScript==
// @name         YouTube - Hide Live Chat
// @namespace    http://tampermonkey.net/
// @version      1.0
// @description  Hide live chat by default on live streams
// @author       LM
// @match        https://www.youtube.com/watch*
// @run-at       document-end
// @grant        none
// ==/UserScript==

kintar

#!/usr/bin/env fish

if ! set -q PICO_SDK_PATH
    echo "PIC_SDK_PATH is not set"
end

if ! set -q argv[1]
    set scriptName = (status --current-filename)
    echo ""
    echo "-----------------------------------------------------------------"

kintar

### Keybase proof

I hereby claim:

  * I am kintar on github.
  * I am kintar (https://keybase.io/kintar) on keybase.
  * I have a public key whose fingerprint is F48E 61A3 40E0 473C BBC4  BE96 2AF7 AB1F 4E82 C922

To claim this, I am signing this object:

kintar

The way I like to think of git is like little boxes with code in them.
You write all of your code, and put it in a box and put a post-it note
on the box that says "main". This is what happens when you first create
a git repository.

Then you decide you're going to make changes,  You work on some code but
get interrupted. So you put all of your changes in a new box and a
post-it on there called "in-progress", then tie a piece of string from
the "main" box to the "in progress" box to remind you what you were
making changes to.  This is what happens when you do a `git clone` to