Neon

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

Neon AI

I built an AI content engine that turns one piece of content into posts for 9 platforms — fully automated with n8n

What it does: You give it any input — a blog URL, a YouTube video, raw text, or just a topic — and it generates optimized posts for 9 platforms at once: Instagram, Twitter/X, LinkedIn, Facebook, TikTok, Reddit, Pinterest, Twitter threads, and email newsletters. Each output is tailored to the platform (hashtags for IG, hooks for TikTok, professional tone for LinkedIn, etc.). It also auto-generates images for visual platforms like Instagram, Facebook, and Pinterest,using AI. Other features: - Topic Research — scans Google, Reddit, YouTube, and news sources, then uses an LLM to identify trending subtopics before generating content - Auto-Discover — if you don't even have a topic, it searches what's trending right now (optionally filtered by niche) and picks the hottest one - Cinematic Ad — upload any photo, pick a style (cinematic, luxury, neon, retro, minimal, natural), and Gemini transforms it into a professional-looking ad - Multi-LLM support — works with Mistral, Groq, OpenAI, Anthropic, and Gemini - History — every generation is saved, exportable as CSV The n8n automation (this is where it gets fun): I connected the whole thing to an n8n workflow so it runs on autopilot: 1. Schedule Trigger — fires daily (or whatever frequency) 2. Google Sheets — reads a row with a topic (or "auto" to let AI pick a trending topic) 3. HTTP Request — hits my /api/auto-generate endpoint, which auto-detects the input type (URL, YouTube link, topic, or "auto") and generates everything 4. Code node — parses the response and extracts each platform's content 5. Google Drive — uploads generated images 6. Update Sheets — marks the row as done with status and links The API handles niche filtering too — so if my sheet says the topic is "auto" and the niche column says "AI", it'll specifically find trending AI topics instead of random viral stuff. Error handling: HTTP Request has retry on fail (2 retries), error outputs route to a separate branch that marks the sheet row as "failed" with the error message, and a global error workflow emails me if anything breaks. Tech stack: - FastAPI backend, vanilla JS frontend - Hosted on Railway - Google Gemini for image generation and cinematic ads - HuggingFace FLUX.1 for platform images - SerpAPI + Reddit + YouTube + NewsAPI for research - SQLite for history - n8n for workflow automation It's not perfect yet — rate limits on free tiers are real — but it's been saving me hours every week. Happy to answer questions. https://preview.redd.it/f8d3ogk3nktg1.png?width=888&format=png&auto=webp&s=dcd3d5e90facd54314f40e799b32cab979dae4bf https://preview.redd.it/j8zl07llmktg1.png?width=946&format=png&auto=webp&s=5c78c12a223d6357cccaed59371e97d5fe4787f5 https://preview.redd.it/5cjas6hkmktg1.png?width=891&format=png&auto=webp&s=288c6964061f531af63fb9717652bececfb63072 https://preview.redd.it/k7e89belmktg1.png?width=1057&format=png&auto=webp&s=8b6cb15cfa267d90a697ba03aed848166976d921 https://preview.redd.it/3w3l70tlmktg1.png?width=1794&format=png&auto=webp&s=6de10434f588b1bf16ae02f542afd770eaa23c3f https://preview.redd.it/a40rh1canktg1.png?width=1920&format=png&auto=webp&s=1d2414c7e653a5f01f12a21a43e69bd4fb4b99ed submitted by /u/emprendedorjoven [link] [comments]

I made a game where you center a div. The threshold is 0.0001px. Nobody has ever won.

I built "Can You Center This Div?" for the DEV April Fools 2026 challenge. https://preview.redd.it/x28bvuc80etg1.png?width=3840&format=png&auto=webp&s=b15647824686c7739dee573b480804281e6976b3 You drag a div to the center of the screen. That's it. The catch: the success threshold is 0.0001 pixels, roughly 5,000x smaller than a single pixel on a Retina display. The global success counter reads 0. It has always read 0. The whole thing is wrapped in a JARVIS-style HUD with real-time deviation readouts, a logarithmic precision meter, a global leaderboard, radar sweep with live player blips, and an "Earth Scale" that translates your pixel miss to real-world distance. Miss by 3px? That's 49,000km on Earth. Congrats, you missed by more than the circumference. Other features: - 2,500+ quotes based on how far off you are - Share cards for every platform (1080x1080 PNG) - Hidden 418 teapot easter egg (3D particle cloud with steam) - Anti-cheat that rejects suspiciously close submissions with HTTP 418 - Light and dark mode - Open source Stack: Next.js 16, React 19, TypeScript, Neon Postgres (serverless), pure CSS for 90% of the visuals. No animation libraries. Game logic is a single custom hook. GitHub: github.com/raxxostudios/center-this-div Try it: center-this-div.vercel.app The anti-value proposition: this app takes the most solved problem in CSS and makes it unsolvable. Happy April Fools. The joke is your CSS skills. submitted by /u/norm_cgi [link] [comments]

Switched from MCPs to CLIs for Claude Code and honestly never going back

I went pretty hard on MCPs at first. Set up a bunch of them, thought I was doing things “the right way.” But after actually using them for a bit… it just got frustrating. Claude would mess up parameters, auth would randomly break, stuff would time out. And everything felt slower than it should be. Once I started using CLIs. Turns out Claude is genuinely excellent with them. Makes sense, it's been trained on years of shell scripts, docs, Stack Overflow answers, GitHub issues. It knows the flags, it knows the edge cases, it composes commands in ways that would take me 20 minutes to figure out. With MCPs I felt like I was constraining it. With CLIs I jactually just get out of the way. Here's what I'm actually running day to day: gh (GitHub CLI) — PRs, issues, code search, all of it. --json flag with --jq for precise output. Claude chains these beautifully. Create issue → assign → open PR → request review, etc. Ripgrep - Fast code search across large repos. Way better than grep. Claude uses it constantly to find symbols, trace usage, and navigate unfamiliar codebases. composio — Universal CLI for connecting agents to numerous tools with managed auth. Lets you access APIs, MCPs, and integrations from one interface without wiring everything yourself. stripe — Webhook testing, event triggering, log tailing. --output json makes it agent-friendly. Saved me from having to babysit payment flows manually. supabase — Local dev, DB management, edge functions. Claude knows this one really well. supabase start + a few db commands and your whole local environment is up. vercel — Deploy, env vars, domain management. Token-based auth means no browser dance. Claude just runs vercel --token $TOKEN and it works. sentry-cli — Release management, source maps, log tailing. --format json throughout. I use this for Claude to diagnose errors without me copy-pasting stack traces. neon — Postgres branch management from terminal. Underrated one. Claude can spin up a branch, test a migration, and tear it down. Huge for not wrecking prod. I've been putting together a list of CLIs that actually work well with Claude Code (structured output, non-interactive mode, API key auth, the things that matter for agents) Would love to know any other clis that you've been using in your daily workflows, or if you've built any personal tools. I will add it here. I’ve been putting together a longer list here with install + auth notes if that’s useful: https://github.com/ComposioHQ/awesome-agent-clis submitted by /u/geekeek123 [link] [comments]

I built MAGI — a Claude Code plugin that spawns 3 adversarial AI agents (inspired by Evangelion) to review your code, designs, and decisions

Hey everyone, I built a Claude Code plugin called MAGI that brings multi-perspective analysis to your workflow. Instead of getting a single opinion from Claude, MAGI launches three independent sub-agents in parallel — each analyzing the same problem through a completely different lens — then synthesizes their verdicts via weighted majority vote. The concept comes from Neon Genesis Evangelion. In the anime, NERV operates three supercomputers called the MAGI (Melchior, Balthasar, Caspar), each containing a copy of their creator's personality filtered through a different aspect of her identity. Decisions require 2-of-3 consensus. I adapted that architecture for software engineering. The Three Agents Agent Role What it focuses on Melchior (Scientist) Technical rigor Correctness, algorithmic efficiency, type safety, test coverage Balthasar (Pragmatist) Practicality Readability, maintainability, team impact, time-to-ship, reversibility Caspar (Critic) Adversarial red-team Edge cases, security holes, failure modes, hidden assumptions, scaling cliffs Each agent analyzes independently (no agent sees the others' output), produces a structured JSON verdict with findings sorted by severity, and the synthesis engine computes a weighted consensus. How voting works Verdicts are weighted: approve = +1, conditional = +0.5, reject = -1. The score determines the consensus: STRONG GO — All three approve GO WITH CAVEATS — Majority approves but conditions exist HOLD — Majority rejects STRONG NO-GO — All three reject The key insight: disagreement between agents is a feature, not a failure. When Melchior approves but Caspar rejects, you've surfaced a genuine tension between correctness and risk. That's exactly the kind of thing you want to catch before shipping. Three modes code-review — Reviews code or diffs with line-specific findings design — Evaluates architecture decisions, migration plans, trade-offs analysis — General problem analysis ("should we use Redis or Postgres for this?") Example output +==================================================+ | MAGI SYSTEM -- VERDICT | +==================================================+ | Melchior (Scientist): APPROVE (90%) | | Balthasar (Pragmatist): CONDITIONAL (85%) | | Caspar (Critic): REJECT (78%) | +==================================================+ | CONSENSUS: GO WITH CAVEATS | +==================================================+ ## Key Findings [!!!] [CRITICAL] SQL injection in query builder (from melchior, caspar) [!!] [WARNING] Missing retry logic for API calls (from balthasar) [i] [INFO] Consider adding request timeout (from caspar) The report includes the full dissenting opinion (Caspar's argument against), conditions for approval, and specific recommended actions from each agent. Technical details Agents run in parallel via asyncio + claude -p — total time is the slowest agent, not the sum 109 tests passing (pytest), linted with ruff, type-checked with mypy Degraded mode: if one agent fails, synthesis continues with 2/3 Fallback mode: works without claude -p by simulating perspectives sequentially Complexity gate: trivial questions skip the full 3-agent system Python 3.9+, dual-licensed MIT/Apache-2.0 Install claude --plugin-dir /path/to/magi Or symlink for auto-discovery: mkdir -p .claude/skills ln -s ../../skills/magi .claude/skills/magi GitHub: https://github.com/BolivarTech/magi Full technical documentation (including the Evangelion-to-software mapping) is in docs/MAGI-System-Documentation.md. I'd love to hear feedback. If you try it and the three agents unanimously approve your code on the first try... your code is either perfect or Caspar's prompt needs tuning. submitted by /u/jbolivarg [link] [comments]

Built a voice dictation app entirely with Claude Code. 4 months in, 326 stars.

VoiceFlow runs Whisper locally for voice dictation. Hold a hotkey, speak, text shows up at your cursor. No cloud, no accounts. I built it with Claude Code and the repo has a CLAUDE.md documenting what was AI-assisted. Some of you might remember the first version I posted here in December. It was Windows-only, kind of rough, and I was mostly using it to dump context into Claude faster. Since then it has been 4 months, 10 releases, and 326 GitHub stars. It runs on Linux now too. The Linux port took about 3 days with Opus 4.6. Claude wrote the evdev hotkey capture code and I had never touched evdev before, worked on the first try. Same with AppImage packaging and CUDA library probing, stuff I had no experience with and it just handled it. PySide6 on Wayland was a different story. Transparency, compositing, multi-monitor detection, Claude kept suggesting fixes that sounded right but did not actually work. I ended up in the Qt docs for those. Clipboard was similar, the wl-copy vs xclip vs pyperclip situation on Linux is a mess and Claude's first pass was a catch-all abstraction that broke on half the setups. I had to be very specific: only wl-copy, only Wayland, fall back to wtype. After 4 months on this project, the thing I keep coming back to is that Claude Code works best when I hand it existing code and say "make this work on a different platform." When the problem is more open-ended it tends to guess confidently and get it wrong. Also set up GitHub Actions this week so both Windows and Linux builds are automated now. Caught a glibc bug from user reports that was breaking the AppImage on Fedora and KDE Neon, fixed it and shipped v1.4.0 within two days. 326 stars, MIT licensed, still free. Demo: https://i.redd.it/59rbyzplc87g1.gif Site: https://get-voice-flow.vercel.app/ Repo: https://github.com/infiniV/VoiceFlow submitted by /u/raww2222 [link] [comments]

How I wired Claude Code into Linear, Discord, and Vercel for a 30-day solo build

I built a full-stack product in 30 days of evenings and weekends. Solo. Using Claude Code as my pair programmer, wired into Linear for ticket tracking and Discord for build notifications. The result: [VGC Team Report](https://pokemonvgcteamreport.com) — a team report builder for competitive Pokemon (VGC). Players paste their teams and get detailed breakdowns with matchup plans, damage calcs, speed tiers, and shareable reports. This post is about the workflow — specifically how I connected Claude Code to Linear and Discord to create a one-person development pipeline that actually ships. ## The Numbers - 274 commits in 30 days - ~42,000 lines of TypeScript - 25 features tracked and shipped via Linear - 66 React components, 41 API routes, 22 custom hooks - Auth (Clerk), database (Neon Postgres), PWA, i18n in 7 languages - Continuously deployed on Vercel ## The Stack - **Next.js 16** (App Router) - **React 19** - **TypeScript** (strict mode) - **Tailwind CSS v4** - **Clerk** for auth - **Neon** for serverless Postgres - **Vercel** for hosting and deploys - **Linear** for ticket tracking - **Discord** for build notifications - **Claude Code** as the AI development partner ## The Workflow: Linear -> Claude -> Discord -> Vercel This is what a typical session looks like: 1. Claude runs `linear_get_in_progress` to check my Linear board for tickets 2. Picks the highest priority ticket (bugs first, always) 3. Reads relevant files and implements the feature or fix 4. Runs `tsc --noEmit && npm run build` — if it fails, Claude fixes the errors 5. Commits with the ticket ID: `VGC-42: Add speed tier chart` 6. Pushes to main 7. Posts a comment on the Linear ticket via GraphQL — commit URL + changed files 8. Moves the ticket to In Review 9. Calls `discord_notify_build` — posts an embed to Discord #builds with the commit, changed file list, and deploy status 10. Vercel auto-deploys from main 11. Moves to the next ticket This isn't hypothetical. I wrote a `linear.sh` bash script with functions that Claude calls directly: - `linear_get_in_progress` — queries Linear GraphQL for In Progress tickets - `linear_move_issue` — moves a ticket to a new state - `linear_comment_with_changes` — posts a comment with the commit link and changed files - `discord_notify_build` — sends a Discord embed with commit info and deploy status Claude calls these via bash. The whole flow — implement, verify, commit, update Linear, notify Discord — happens in one session without me touching any of those systems. ## The CLAUDE.md Operating Manual The key to making this work is a `CLAUDE.md` file at the repo root. Claude reads it at the start of every session. Mine contains: **Git strategy:** - Trunk-based development — push direct to main for routine work - Feature branches only for large or risky changes - `npx tsc --noEmit && npm run build` before every push — non-negotiable **Linear workflow:** - The exact state IDs for "In Progress" and "In Review" - How to query for tickets, implement them, commit with the VGC-XX prefix - How to post the commit comment and move the ticket state - Rule: bug tickets are always worked on first, regardless of priority number **Discord notifications:** - The `discord_notify_build` function format - Different embeds for direct-to-main pushes vs PR flows **Failure handling:** - Build fails → fix and retry, never push broken code - Linear API fails → still commit and push, note the failure to the user - Production breaks → `git revert`, push to main, notify Discord, move ticket back **Code conventions:** - Follow existing patterns, no drive-by refactors - Commit messages: `VGC-XX: description` for tracked work This file is the single most valuable thing in the project. Every session starts with full context. No re-explaining, no drift, no "can you check the codebase structure?" ## Automated Monitoring Beyond the dev workflow, I set up two Vercel cron jobs: - **Daily (9 AM):** Site health check, stale ticket scan, SEO audit, DB health — posts alerts to Discord only if something's wrong - **Weekly (Friday 5 PM):** Linear progress digest, user growth, dependency updates — always posts a summary to Discord These run on Vercel's free tier. Real-time uptime monitoring is handled by UptimeRobot with 5-minute pings. ## What Worked **Trunk-based development with type-checking gates.** Every push to main auto-deploys on Vercel. The gatekeeper is `tsc --noEmit && npm run build`. The feedback loop is minutes, not days. **Linear ticket traceability.** Every commit links back to a ticket. Every ticket has a comment with the commit URL and changed files. When something breaks, I trace it to the exact change and the exact intent. **Discord as an audit trail.** Every build posts to #builds. It sounds like overkill for a solo project, but scrolling through the channel to see what shipped this week is genuinely useful. **The CLAUDE.md as living infrastructure.** I update it whenever the workflow changes. New conventions, new failure modes, new

Ungefragt Ausführungen

submitted by /u/Sea_Fruit5986 [link] [comments]

MCP server that lets AI create animated SVGs from scratch

hey, I just shipped this and looking for feedback. nakkas is an MCP server where AI is the artist. you describe what you want, AI constructs the full config (shapes, gradients, animations, filters), and the server renders clean animated SVG. some things it can do: animated logos, loading spinners, data visualizations scatter fields, radial patterns, grid layouts parametric curves (rose, spiral, heart, superformula) 15 filter presets (glow, neon, glitch, chromatic aberration...) CSS @ keyframes + SMIL animations, zero JavaScript works in anywhere SVG renders. npx nakkas@latest I would love to see what you make with it. you can share examples in github discussions. repo: https://github.com/arikusi/nakkas npm: https://www.npmjs.com/package/nakkas submitted by /u/Niacinflushy [link] [comments]

I built a free H-1B visa intelligence tool almost entirely with Claude Code — from ETL pipeline to production

I'm a solo dev who built https://www.h1b.guru - a free tool that turns raw US Department of Labor disclosure data into actionable intelligence for H-1B job seekers. The entire stack was built with Claude Code as my pair programmer. What it does: Search 800K+ LCA filings and PERM records with filters (employer, location, job title, wage level) Sponsor profiles showing filing stats, approval rates, wage distributions, and green card activity Salary benchmarking by occupation and state "Ask Guru" — an AI chat that answers natural language questions about the data (e.g., "Find cap-exempt companies in Delaware") The stack (all built with Claude Code): Python ETL pipeline that ingests raw DOL Excel files, does entity reconciliation on messy employer names, and loads into Neon Postgres FastAPI backend with async Postgres queries Next.js 14 frontend deployed on Vercel How Claude Code helped: The biggest win was the ETL pipeline. DOL data is messy — employer names have dozens of spelling variations, LCA and PERM filings have no shared key, and there are subtle data nuances (e.g., one LCA can cover multiple workers, amended filings inflate counts). Claude Code helped me build the probabilistic entity matching, the pipeline orchestrator with resume capability, and all the edge-case handling I would have spent weeks figuring out alone. On the frontend, Claude Code basically built the entire UI — filter modals, infinite scroll, responsive tables, the sidebar, dark mode. I'd describe what I wanted and iterate. Most features went from idea to deployed in a single session. The API layer was similar — Claude Code wrote the parameterized SQL generation for Ask Intel (LLM generates a query spec, not raw SQL, to avoid injection), the streaming SSE architecture, and all the sponsor stats aggregation queries. I'm not a frontend dev by background, so Claude Code turning my rough descriptions into polished React components was the difference between this shipping and sitting in a Jupyter notebook. Free to use - no signup, no paywall. Just go to https://www.h1b.guru and search. Happy to answer questions about the build process or how Claude Code handled specific parts. I can't believe the speed with which you can build things now. Took me 2 days to do the hard work and 2 more to figure out how to market. Check this out www.h1b.guru especially if you are an international and going through F1 or H1. https://preview.redd.it/829ynzxqxbqg1.png?width=788&format=png&auto=webp&s=86e701e3c49767b11c428bba11fb804729aa1cdc submitted by /u/pvertigo [link] [comments]

Text Adventure Games Skill for Claude Desktop

I've been working on a text adventure game engine that runs entirely inside Claude Desktop as a skill. No servers, no app, no code to run — just install the skill and say "play a text adventure." What it does: Full RPG mechanics — d20 system, D&D 5e, GURPS Lite, Pathfinder 2e, Shadowrun 5e, or a narrative engine with no dice Everything renders inside Claude's widget system — styled scenes, interactive buttons, stat panels, maps, shops, social encounters, combat 3D dice rendered with Three.js — actual polyhedra (d4 tetrahedron through d20 icosahedron) with tumble animations and proper opposite-face numbering 19 expansion modules — ship systems, crew management, star charts, procedural world generation, AI-powered NPC dialogue, lore encyclopaedia, and more 12 visual styles — from "Station" (the dark sci-fi default) to Parchment, Neon, Brutalist, Art Deco, Ink Wash, Stained Glass, and others. Each completely changes the look without touching game logic 5 narrative output styles — Master Storyteller, Noir Detective, Pulp Adventure, Gothic Horror, Sci-Fi Narrator. Each changes how the story is written Story architect module that tracks plotlines, foreshadowing, consequence chains, and dramatic pacing behind the scenes World history generation — the GM builds epochs, power structures, and cultural details before your adventure even starts .save.md files — portable saves you can download and resume in any conversation .lore.md files — author your own adventures OR export your world for someone else to play. Your character becomes a historical figure in their game https://preview.redd.it/5f15x2hma6qg1.png?width=1369&format=png&auto=webp&s=149b744638cc471a9df0615c55a41da145534068 https://preview.redd.it/foxsoqppa6qg1.png?width=1364&format=png&auto=webp&s=65bc936dc123fe8bb5ed4102adab3a7f60eaa8fa https://preview.redd.it/0ra2gi4ua6qg1.png?width=1374&format=png&auto=webp&s=bb7d4835b7ebe0cf5184410335b0c384c6e3ee2f https://preview.redd.it/lxmliv40b6qg1.png?width=1371&format=png&auto=webp&s=9df857a9d45837a819c1445a6d96faa60ca55f12 https://preview.redd.it/jlyvzv92b6qg1.png?width=1366&format=png&auto=webp&s=88a018bdc91252d7906c5c73110ad14936e08c25 How to install: Download text-adventure.zip from the repo Open Claude Desktop → Customise Claude → Skills → Add Skill → drop in the zip Say "play a text adventure" The output styles (narrative voice) are separate .md files you can use to further adjust the style, or use your own. Links: GitHub: https://github.com/GaZmagik/text-adventure-games The whole thing is freely available — no licence restrictions Built with Claude Code (Opus 4.6). The skill itself is ~400KB of markdown — no code, no build step, just instructions that Claude follows to run the game. submitted by /u/gazmagik [link] [comments]

Wrote a SIMD Compiler in 12K Lines of Rust

I kept hitting the same problem: Write Python → profile → find hot loop → rewrite in C → fight ctypes → debug pointers → finally get 5× speedup. Then repeat next week. So I built Eä. Eä is a compiler for SIMD kernels: - write a small .ea file - run one command - call it from Python like a normal function But it runs at native vectorized speed. Example: import ea kernel = ea.load("fma.ea") result = kernel.fma_f32x8(a, b, c, out) # 6.6× faster than NumPy Benchmarks are from a fairly simple setup, but I tried to keep things fair and reproducible. No ctypes. No header files. No build system. The compiler generates: - shared library - Python wrapper - (also Rust, C++, PyTorch, CMake bindings) Targets: - x86-64 (AVX2 / AVX-512) - AArch64 (NEON) Whole compiler: - ~12k lines of Rust - 475 tests The main idea: the compiler handles all the "glue code" so you can focus only on the kernel. That turned out to matter more than SIMD itself. I'm not a compiler engineer. I don't have a CS degree. I'm the kind of person who has ideas and wants to see if they work. What changed is the tooling. I built Eä with the help of AI models. Claude for the heavy lifting, my own judgment for the architecture and design decisions. The hard rules came from me (learned the painful way from the first attempt). The implementation speed came from having a capable coding assistant. --- Full write-up (design, desugaring, binding generation, etc): https://petlukk.github.io/eacompute/blog/12k-lines-of-rust.html submitted by /u/Acceptable_Analyst45 [link] [comments]

claude ain’t flawless remember

I showed it a simple question and it labels an element with an electronic configuration of 2,8 to be Argon when it’s actually Neon. This is middle school knowledge and Claude Sonnet 4.6 messed this up. Hiccups happen tho. submitted by /u/Stunning_Draft7685 [link] [comments]

🔥 burnmeter - Built an MCP to quickly ask Claude "what's my burn this month?" instead of logging into 12 dashboards

Hey! 👋 I built an MCP server that aggregates infrastructure costs across Vercel, Railway, Neon, OpenAI, Anthropic, and more. You just ask "what's my burn this month?" and get a full breakdown across your stack in seconds. No new dashboard. No extra tab. Just ask Claude. Free, open source, runs locally. Check it out: [mpalermiti.github.io/burnmeter](http://mpalermiti.github.io/burnmeter) Still early — would love to hear from anyone building that finds this helpful. Feedback welcome.  submitted by /u/mpMSFT [link] [comments]