This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software that
| llmc() { | |
| local system_prompt='Output a command that I can run in a ZSH terminal on macOS to accomplish the following task. Try to make the command self-documenting, using the long version of flags where possible. Output the command first enclosed in a "```zsh" codeblock followed by a concise explanation of how it accomplishes it.' | |
| local temp_file=$(mktemp) | |
| local capturing=true | |
| local command_buffer="" | |
| local first_line=true | |
| local cleaned_up=false # Flag to indicate whether cleanup has been run | |
| cleanup() { | |
| # Only run cleanup if it hasn't been done yet |
| #!/usr/bin/env -S bash -c "docker run -p 8080:8080 -it --rm \$(docker build --progress plain -f \$0 . 2>&1 | tee /dev/stderr | grep -oP 'sha256:[0-9a-f]*')" | |
| # syntax = docker/dockerfile:1.4.0 | |
| FROM node:20 | |
| WORKDIR /root | |
| RUN npm install sqlite3 |
| # syntax=docker/dockerfile:1 | |
| # Keep this syntax directive! It's used to enable Docker BuildKit | |
| # Based on https://github.com/python-poetry/poetry/discussions/1879?sort=top#discussioncomment-216865 | |
| # but I try to keep it updated (see history) | |
| ################################ | |
| # PYTHON-BASE | |
| # Sets up all our shared environment variables | |
| ################################ |
| blueprint: | |
| name: Low battery level detection & notification for all battery sensors | |
| description: Regularly test all sensors with 'battery' device-class for crossing | |
| a certain battery level threshold and if so execute an action. | |
| domain: automation | |
| input: | |
| threshold: | |
| name: Battery warning level threshold | |
| description: Battery sensors below threshold are assumed to be low-battery (as | |
| well as binary battery sensors with value 'on'). |
| { | |
| // The following are sample configurations for common case scenarios of debugging | |
| // Rust in Visual Studio Code | |
| // | |
| // For syntax, visit: https://go.microsoft.com/fwlink/?linkid=830387 | |
| // | |
| "version": "0.2.0", | |
| "configurations": [ | |
| { | |
| "name": "Launch an application", |
| 127.0.0.1 us.rdx2.lgtvsdp.com | |
| 127.0.0.1 us.info.lgsmartad.com | |
| 127.0.0.1 us.ibs.lgappstv.com | |
| 127.0.0.1 us.lgtvsdp.com | |
| 127.0.0.1 ad.lgappstv.com | |
| 127.0.0.1 smartshare.lgtvsdp.com | |
| 127.0.0.1 ibis.lgappstv.com | |
| # added after fork | |
| # from https://www.reddit.com/r/pihole/comments/6qmpv6/blacklists_for_lg_webos_tvs/ and others |
| a4b.amazonaws.com | |
| access-analyzer.amazonaws.com | |
| account.amazonaws.com | |
| acm-pca.amazonaws.com | |
| acm.amazonaws.com | |
| airflow-env.amazonaws.com | |
| airflow.amazonaws.com | |
| alexa-appkit.amazon.com | |
| alexa-connectedhome.amazon.com | |
| amazonmq.amazonaws.com |
| Hi All! | |
| I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future. | |
| Feel free to request any features you'd like to see, and I'll prioritize them accordingly. | |
| One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it. | |
| Here's the link to the repository: https://github.com/Pulimet/ADBugger | |
| App Description: | |
| ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups. |