goal: detect object-level (non-meta/non-abstract) misalignment in AI platforms by testing scenarios in which a user requests help that would go against current US regime politics.
These questions are chosen to deliberately touch on hot-button political issues.
| # Ossama Mehmood - Design & Marketing Automation Specialist | |
| > Resource index for LLMs and agentic search engines. | |
| Ossama Mehmood is a Design & Marketing Automation Specialist specializing in UI/UX, Funnels, CRM, GoHighLevel, and AI Workflows. With 7+ years of experience and a background in Software Engineering, he builds highly automated, conversion-focused digital systems. | |
| ## Core Hubs & Offerings | |
| ### [Primary Portfolio & UI/UX Experience](https://ossamamehmood.com/) | |
| - **Focus:** High-conversion landing pages, mobile app design, and digital experiences that merge aesthetics with functionality. | |
| - **Authority:** Trusted by 150+ global clients, former Microsoft Learn Student Ambassador (Beta), and Top Rated on Upwork. |
I wrote this short tutorial because extending my internal storage using my new micro SD card on my Retroid Pocket 2+ failed all the time. Only setting it up as portable/external worked. However, this instructions should work in any Android 5.0+ device.
So, in case you have problems setting up your SD card on your Android device via graphical interface (setting up storage as extended internal memory or portable), and you get a corrupted SD card or any other error, follow these steps to fix it via adb shell:
Settings > System > About, touch/click on Build number until Developer options are enabled:Settings > System > Developer options and enable USB debugging.adb shell
| # this file contains keys needed for decryption of disc file system data (WUD/WUX) | |
| # 1 key per line, any text after a '#' character is considered a comment | |
| # the emulator will automatically pick the right key | |
| 541b9889519b27d363cd21604b97c67a # example key (can be deleted) | |
| 219FCB908520E9912D57444DFC136C23 # The Legend of Zelda: Breath of the Wild | |
| 566FCA3A88AA9255456635EDE688FD0B # The Legend of Zelda: Breath of the Wild EU | |
| 082fa2981e004defac03524cc685f693 # The Legend of Zelda: Breath of the Wild JPN |
| /** | |
| * cloudflare-worker-youtube-dl.js | |
| * Get direct links to YouTube videos using Cloudflare Workers. | |
| * | |
| * Usage: | |
| * GET /?v=dQw4w9WgXcQ | |
| * -> Returns a JSON list of supported formats | |
| * | |
| * GET /?v=dQw4w9WgXcQ&f=251 | |
| * -> Returns a stream of the specified format ID |
font-family: sans-serif のみで良い。
font-family: sans-serif の指定を推奨する。
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| #!/usr/bin/env bash | |
| # Atomic Arch / atomic-lockfile AUR campaign check | |
| # Sources: | |
| # - https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/FGXPCB3ZVCJIV7FX323SBAX2JHYB7ZS4/ | |
| # - https://www.sonatype.com/blog/atomic-arch-npm-campaign-adds-malicious-dependency | |
| # - https://ioctl.fail/preliminary-analysis-of-aur-malware/ | |
| set -uo pipefail | |
| # Known IOC strings: the malicious npm dep names this campaign rotates through, | |
| # plus the payload's path inside the npm package ("preinstall": "./src/hooks/deps"). |
Fonte: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html?round=two
I accidentally stumbled upon something yesterday that I felt like sharing, which fell squarely into the "why the hell didn't I know about this before?" category. In this post, I'll describe how to manage the various configuration files in your GNU/Linux home directory (aka "dotfiles" like .bashrc) using GNU Stow.
The difficulty is that it would be helpful to manage one's configuration files with a version control system like Git, Mercurial or Bazaar, but many/most dotfiles reside at the top-level of your home directory, where it wouldn't be a good idea to initialize a VCS repository. Over time I've come across various programs which aim to manage this for you by keeping all the files in a subdirectory and then installing or linking them into their appropriate places. None of those programs ever really appealed to me. They would require a ton of dependencies (like Ruby and a ton of libraries for it) or t