| [ | |
| { | |
| "id": "f64fc2c05427d1ff", | |
| "type": "mqtt in", | |
| "z": "329ba4b7632a95c8", | |
| "name": "BlueIris/+/alert-image-b64", | |
| "topic": "BlueIris/+/alert-image-b64", | |
| "qos": "2", | |
| "datatype": "json", | |
| "broker": "e811c8eb637d26a5", |
| { | |
| "message": message, | |
| "data": { | |
| "clickAction": "http://cameras.vpn.d.sb:81/ui3.htm?maximize=1&tab=alerts&cam=" & original_payload.camera & "&rec=" & original_payload.id, | |
| "image": "/media/local/alerts/" & image_filename, | |
| "actions": [{ | |
| "action": "URI", | |
| "title": "Live View", | |
| "uri": "http://cameras.vpn.d.sb:81/ui3.htm?maximize=1&cam=" & original_payload.camera | |
| }, { |
This is an example of how to use the Google Drive file picker and Google Drive API to retrieve files from Google Drive using pure JavaScript. At the time of writing (14th July 2013), Google have good examples for using these two APIs separately, but no documentation on using them together.
Note that this is just sample code, designed to be concise to demonstrate the API. In a production environment, you should include more error handling.
See a demo at http://stuff.dan.cx/js/filepicker/google/
| # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # | |
| # Yet-Another-Bench-Script # | |
| # v2024-01-01 # | |
| # https://github.com/masonr/yet-another-bench-script # | |
| # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## # | |
| Sun Feb 18 01:52:40 PM PST 2024 | |
| Basic System Information: | |
| --------------------------------- |
| # /etc/nginx/snippets/wordpress/common.conf | |
| index index.php; | |
| # Deny all attempts to access hidden files such as .htaccess, .htpasswd, .DS_Store (Mac). | |
| location ~ /\. { | |
| deny all; | |
| } | |
| # Block PHP files in uploads, content, and includes directory. | |
| location ~* /(?:uploads|files|wp-content|wp-includes)/.*\.php$ { |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Example Page</title> | |
| </head> | |
| <body> | |
| <p>This page uses the favicon as a progress bar. Try clicking the button.</p> | |
| <button onclick="run()">Do something</button> | |
| <script> |
| const {img, ...otherPayloadFields} = msg.payload; | |
| const objectsToFilter = new Set([ | |
| 'ball', | |
| 'sports ball', | |
| 'horse', | |
| 'book', | |
| 'suitcase', | |
| ]); | |
| let formattedObjectNames = 'Nothing'; |
This Gist contains some scripts for Tinc, in order to configure the routing tables for a remote subnet on Windows (ie. if a remote system wants to expose an entire subnet over the VPN). Tinc does not configure the routing tables by default, which is why these scripts are needed. See the mailing list thread here: https://www.tinc-vpn.org/pipermail/tinc/2018-December/005340.html
Place the files in the Tinc network directory (eg. C:\Program Files\Tinc\netname\) and change $interface in functions.ps1 to match the name of the Tinc interface configured in tinc.conf
| We are writing to let you know about a bug we recently discovered and fixed in Slack's Shared Invite Link functionality. This | |
| feature allows you to create a link that will permit anyone to join your Slack workspace; it is an alternative to inviting | |
| people one-by-one via email to become workspace members. You are receiving this email because you created and/or revoked one | |
| of these links for your workspace between April 17, 2017 and July 17, 2022. We'll go into detail about this security issue below. | |
| Important things first, though: We have no reason to believe that anyone was able to obtain your plaintext password because | |
| of this vulnerability. However, for the sake of caution, we have reset your Slack password. You will need to set a new Slack | |
| password before you can login again. | |
| Now, for some technical details — feel free to skip the next two paragraphs if that doesn't interest you. When you're |
| zigbee2mqtt: | |
| container_name: zigbee2mqtt | |
| restart: unless-stopped | |
| image: koenkk/zigbee2mqtt:latest | |
| volumes: | |
| - /var/local/docker/zigbee2mqtt:/app/data | |
| - /run/udev:/run/udev:ro | |
| ports: | |
| - 8080:8080 | |
| environment: |