jmathai

# Title: Smart-TV Blocklist for Pi-hole
# Version: 15December2021v1
# Description: This is a blocklist to block smart-TVs sending metadata back home, sometimes with the added benefit of blocking interface ads for apps and movie services.
# Please help with collecting domains!
# It could occur that the TV fails to receive new updates, or that other apps or services no longer work. Please report such an incident.
# Make sure to also use the extra RegEx list at https://perflyst.github.io/PiHoleBlocklist/regex.list, which helps remove regional LG ad domains among other things.

# Panasonic Viera & panny tv
0077777700140002.myhomescreen.tv
cert-test.sandbox.google.com

jmathai

Getting Elodie running on Synology DSM

• Install python
• Install pip
• Install virtualenv
• Install virtualenvwrapper
• Install git (server) through DSM Package Manager
• Install perl through DSM Package Manager
• Install exiftool through CPHub (https://www.cphub.net/?id=40&pid=609)
• Clone elodie from Github (https://github.com/jmathai/elodie)

jmathai

const HomeAssistant = require( 'homeassistant' );
const Pino          = require( 'pino' );

const config   = require( 'config' );
const hass     = new HomeAssistant( config.get( 'home_assistant' ) );
const imessage = require( 'osa-imessage' );
const logger   = Pino();

// TODO package this better
const bridge = {

jmathai

#!/bin/bash

# Ease staging of files

for i in $(git status | grep -A 10000 "not updated" | grep modified) ; do 
  if [ -f $i ] ; then 
    git diff $i; 
    echo -n "Add this to stage? [y/n]: "; 
    read ans; 
    if [ "$ans" == "y" ] ; then 

jmathai

<?php
/*
 * This is a sample function that guarantees unique URLs for frontend assets.
 *  Images for example.
 *  Include this and your users will never re-download an asset they already 
 *    have just just because you push a new build.
 *  If including this in your stylesheet then you should set this up in you
 *    should be using something like Amazon Cloud Front to cache a static
 *    version of it.
 */

jmathai

/**
 * This Joule is a serverless dynamic DNS system using Lambda and Route53.
 */

// We have to require the aws-sdk and immediately set the credentials.
// If we instantiate the Route53 object first then it assumes the role assigned to the lambda function.
var AWS = require('aws-sdk');
if(process.env.AWS_KEY !== '' && process.env.AWS_SECRET !== '') {
  AWS.config.update({accessKeyId: process.env.AWS_KEY, secretAccessKey: process.env.AWS_SECRET});
}

jmathai

# username = your Joule username
# joule_name = the name of your Joule (probably joule-node-dynamic-dns)
# test.example.com. = the domain you'd like to use for DDNS (with a trailing .)
# a_secret_you_chose = the string you chose as your secret for your Joule

./client.sh username joule_name test.example.com. a_secret_you_chose

# Output if IP address hasn't changed
# {"status": "success", "message": "No change in IP address detected."}
#

jmathai

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1458757563000",
            "Effect": "Allow",
            "Action": [
                "route53:ChangeResourceRecordSets",
                "route53:ListHostedZones"
            ],

jmathai

git clone https://github.com/joulehq/joule-node-boilerplate.git
cd joule-node-boilerplate/src
cp events.json-sample events.json
npm i
npm test

> joule-boilerplate@0.0.1 test /Users/jaisenmathai/joule-node-boilerplate/src
> node ./node_modules/joule-node-local/index.js

{ headers: { Status: '200 OK', 'Content-Type': 'application/json' },

jmathai

var Response = require('joule-node-response');

exports.handler = function(event, context) {
  var response = new Response();
  response.setContext(context);
  var name = event.name || 'World';
  var greeting = 'Hello, ' + name + '.';

  var result = {
    "message": greeting