01MV2-to-MV3 Side-by-Side ReplayHacker NewsAfter Chrome removed the installation channel for legacy MV2 extensions, maintainers are less worried about whether they can rewrite an API than whether an MV3 release quietly stops blocking a class of requests on a real page. MV2 and MV3 are two generations of Chrome extension rules. Teams upload the old package still in production and the new package awaiting release, then select the pages, login states, and click flows that best represent real user behavior. The product launches two isolated browsers and has the old and new versions shadow-run the same sequence: opening tabs, switching accounts, visiting dynamic pages, triggering network requests, and changing permission states. It aligns page outputs, request logs, storage changes, and console output from both sides. When results diverge, the report stops at the first differing action and includes the trigger conditions, relevant APIs, and a runnable minimal reproduction script. Maintainers can save a flow after a fix as a regression case and rerun it automatically on code submission. The first release focuses on network requests and background tasks common to ad blockers, script managers, and privacy extensions; it does not attempt to design a team’s entire migration plan. Its output is a list of behavioral differences that engineers can immediately reproduce and fix.View detailsHide details
When migrating an extension to MV3, replay real browser flows side by side to pinpoint the exact step where the new version loses behavior the old version had.
After Chrome removed the installation channel for legacy MV2 extensions, maintainers are less worried about whether they can rewrite an API than whether an MV3 release quietly stops blocking a class of requests on a real page. MV2 and MV3 are two generations of Chrome extension rules. Teams upload the old package still in production and the new package awaiting release, then select the pages, login states, and click flows that best represent real user behavior.
The product launches two isolated browsers and has the old and new versions shadow-run the same sequence: opening tabs, switching accounts, visiting dynamic pages, triggering network requests, and changing permission states. It aligns page outputs, request logs, storage changes, and console output from both sides. When results diverge, the report stops at the first differing action and includes the trigger conditions, relevant APIs, and a runnable minimal reproduction script.
Maintainers can save a flow after a fix as a regression case and rerun it automatically on code submission. The first release focuses on network requests and background tasks common to ad blockers, script managers, and privacy extensions; it does not attempt to design a team’s entire migration plan. Its output is a list of behavioral differences that engineers can immediately reproduce and fix.
Who it is for
Small teams still maintaining ad-blocking, script-management, or privacy extensions. It is most useful just before an MV3 candidate package is submitted to the Chrome Web Store, or immediately after a migration fix is merged. At that point, unit tests usually pass, but teams worry about behavioral drift after login-state changes, on dynamic pages, or during permission changes. The on-call maintainer needs differences they can reproduce directly, not another migration checklist.
Smallest useful version
Use Playwright to control two isolated persistent browser profiles, loading one unpacked package into each. The initial dual-run setup pins both to the same Chrome 138 baseline and enables the official retention policy. Recorded actions cover only navigation, clicks, account switching, and permission changes. A collection layer uses Playwright events and CDP to capture DOM summaries, requests, console output, and storage snapshots. The aligner compares at action boundaries rather than seeking pixel-perfect page matches. Reports lead with the first divergence, then generate a rerunnable Playwright case. Once the versions match, the MV3 package gets a standalone smoke test in current Chromium.
Why now
On August 31, 2026, the Chrome Web Store removed all remaining MV2 extensions. Installed legacy versions can no longer be updated or reinstalled, making maintainers more urgent to catch silent MV3 behavior regressions before release.
Strongest counterargument
Dynamic sites can create a high volume of false differences. Ad rotation, A/B tests, timestamps, and API responses may diverge before the extension does. Normalize too aggressively and genuine missed blocking may disappear. Login flows also involve CAPTCHAs, two-factor authentication, and expired sessions, so replay stability directly affects report credibility. The legacy runner must remain pinned to Chrome 138; maintaining an outdated browser and a high-risk sandbox is not easy over time. Extension packages and login states are sensitive as well, so isolation, key destruction, and local deployment raise delivery costs. If the first-divergence report produces frequent false positives, engineers will quickly return to manual retesting.
Signal, observation time, and sources
hacker_news observation: Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO; observed 2026-09-01T00:33:19.377Z.
Manifest V2 support timeline — Chrome’s official timeline states that all remaining MV2 extensions were removed from the Chrome Web Store on August 31, 2026. Installed versions can no longer be updated, and once removed, cannot be reinstalled. Chrome 138 is the last version to support MV2 with the ExtensionManifestV2Availability policy.
Chrome extensions — Playwright’s official documentation states that Chrome extensions must run in persistent Chromium contexts. It demonstrates loading unpacked extensions, accessing MV3 service workers, and reusing extension contexts through test fixtures.
Test Chrome Extensions on Playwright tests in BrowserStack Automate — BrowserStack’s official documentation states that Automate can upload zipped extension packages through its REST API and load them in Playwright sessions. Its examples include network logs and session-result viewing.
02A Company Knowledge Base That Resolves ConflictsHacker NewsWhen an employee asks the company AI, “Can I expense a rideshare on a business trip?” the hardest case is when it retrieves two valid documents with opposite answers. After a team connects policy pages, shared documents, and internal announcements, the product identifies the original sentences behind its answer and checks their effective dates, applicable departments, and owners. Rather than hiding the conflict, the answer page first presents a provisional explanation with citations. If the two provisions genuinely cannot coexist, the system turns the employee’s original question into a single adjudication card and sends it to the owner of that policy. Next to the original sentence, the owner simply chooses which rule to retain, specifies the conditions under which it applies, or enters a new unified policy. The confirmed result is written back to the knowledge base immediately, while the old passage is marked retired or pending revision. The next employee who asks will no longer receive the same contradictory material. Managers can also see which policies repeatedly cause disputes and which owners have been slow to respond. The first version handles conflicts among written policies; it does not interpret the law for a company or let the model decide benefits, compensation, or disciplinary matters. Each real question becomes an opportunity to close a knowledge gap that has gone unmaintained for years.View detailsHide details
When company policies conflict, employees get a cited provisional answer first, while the smallest possible adjudication task goes to the responsible owner.
When an employee asks the company AI, “Can I expense a rideshare on a business trip?” the hardest case is when it retrieves two valid documents with opposite answers. After a team connects policy pages, shared documents, and internal announcements, the product identifies the original sentences behind its answer and checks their effective dates, applicable departments, and owners. Rather than hiding the conflict, the answer page first presents a provisional explanation with citations.
If the two provisions genuinely cannot coexist, the system turns the employee’s original question into a single adjudication card and sends it to the owner of that policy. Next to the original sentence, the owner simply chooses which rule to retain, specifies the conditions under which it applies, or enters a new unified policy. The confirmed result is written back to the knowledge base immediately, while the old passage is marked retired or pending revision. The next employee who asks will no longer receive the same contradictory material.
Managers can also see which policies repeatedly cause disputes and which owners have been slow to respond. The first version handles conflicts among written policies; it does not interpret the law for a company or let the model decide benefits, compensation, or disciplinary matters. Each real question becomes an opportunity to close a knowledge gap that has gone unmaintained for years.
Who it is for
Mid-sized companies that have already connected policy pages, shared drives, and internal announcements to an AI system. Employees need an actionable answer immediately before filing an expense, requesting leave, or ordering equipment; waiting for HR delays the task, while blindly trusting the model can cause harm. Knowledge owners need a way to turn scattered follow-up questions into manageable revision work.
Smallest useful version
Start with travel, expense, and leave policies, which often contain dates and scope conditions. Connect one document source and one question entry point while preserving source permissions and version numbers. During parsing, extract titles, original sentences, publication dates, departments, and owners. Once retrieval returns candidate passages, assess conflicts only among provisions that answer the same question. When a contradiction is detected, withhold a definitive answer and show both citations with a provisional explanation. Adjudication cards should allow only three actions: retain a provision, limit its applicability, or enter a unified policy. Write results first to a separate override layer, then update source documents through controlled tasks.
Why now
On August 31, a Launch HN post introduced Almanac’s enterprise knowledge AI; as recorded on September 1, it had 44 points, 41 comments, and ranked 16th. The discussion makes it easier for teams to move beyond “Can we find it?” toward how to answer and correct conflicts across multiple materials.
Strongest counterargument
Policy documents often lack effective dates, applicable departments, and clear owners, so conflict detection may stall on missing metadata. Semantically similar language does not necessarily mean opposite policies, and false positives could burden owners with invalid adjudications. Permissions and version control in source systems also constrain automated write-backs, while an override layer could become another source of truth. If owners do not act promptly, provisional explanations may persist indefinitely. Incorrect guidance on benefits, compensation, or discipline could also trigger employment disputes. The product needs complete citations, approval records, and a human fallback; otherwise, one wrong adjudication could erode employee trust.
Signal, observation time, and sources
hacker_news observation: Launch HN: Almanac (YC S26) – AI that knows your company; observed 2026-09-01T00:33:19.377Z.
Launch HN: Almanac (YC S26) – AI that knows your company — A post titled “Launch HN: Almanac (YC S26) – AI that knows your company” was created on August 31, 2026, at 15:34 UTC. A snapshot taken on September 1, 2026, at 00:33 UTC recorded 44 points, 41 comments, and rank 16.
Almanac — the agent with a company brain — Almanac’s official site says it maintains a sourced company wiki in which every line can be traced back to its original source; when users correct a page, the system applies that correction in later work.
Keep content accurate with Guru’s SME verification workflow — Guru’s official materials state that every knowledge card has a verification status, date, and assigned verifier; the system supports review reminders, queues for unverified items, expert handling, and feedback on problematic text.
Citations - Glean Help Center — Glean’s official materials state that enterprise knowledge answers can display citations and locate the supporting passages; citations honor existing access permissions. Its search index continuously processes content updates, deletions, and permission changes.
03FX-MIC Performance Gesture PatchesProduct HuntWhen performers first get a programmable microphone they can squeeze or shake, they can usually connect it to effects but struggle to create gestures that work reliably in rehearsal. This marketplace turns movement arrangements already proven by sound engineers, lighting designers, and artists into installable patches: a hard squeeze triggers distortion, a light shake switches harmonies, and a rotation controls lighting brightness. Each patch specifies compatible devices, required plug-ins, and the performance sections it suits. After connecting the microphone, users enter rehearsal mode. Brief on-screen animations show how to apply force, while audio and vibration cues indicate whether they have crossed a threshold. They can try the arrangement against recordings of a chorus, monologue, or transition and see gesture curves, effect changes, and lighting routes. If accidental triggers occur too often, the product recommends adjusting sensitivity or replacing a high-risk action with a gesture that requires a long-press confirmation. When a patch pack is purchased, its device routing, thresholds, and demo clips load together. Artists can save their own revisions and tag the songs they apply to. The first release supports a small set of compatible microphones and commonly used audio software, with a focus on making a gesture reliably repeatable in the rehearsal room. It sells not a screenshot of settings, but a movement arrangement ready for the stage.View detailsHide details
A marketplace where performers can rehearse and install stage-ready FX-MIC gesture patches that pair microphone movements with effects and lighting routes.
When performers first get a programmable microphone they can squeeze or shake, they can usually connect it to effects but struggle to create gestures that work reliably in rehearsal. This marketplace turns movement arrangements already proven by sound engineers, lighting designers, and artists into installable patches: a hard squeeze triggers distortion, a light shake switches harmonies, and a rotation controls lighting brightness. Each patch specifies compatible devices, required plug-ins, and the performance sections it suits.
After connecting the microphone, users enter rehearsal mode. Brief on-screen animations show how to apply force, while audio and vibration cues indicate whether they have crossed a threshold. They can try the arrangement against recordings of a chorus, monologue, or transition and see gesture curves, effect changes, and lighting routes. If accidental triggers occur too often, the product recommends adjusting sensitivity or replacing a high-risk action with a gesture that requires a long-press confirmation.
When a patch pack is purchased, its device routing, thresholds, and demo clips load together. Artists can save their own revisions and tag the songs they apply to. The first release supports a small set of compatible microphones and commonly used audio software, with a focus on making a gesture reliably repeatable in the rehearsal room. It sells not a screenshot of settings, but a movement arrangement ready for the stage.
Who it is for
The core users are independent singers, DJs, hosts, and live electronic artists who already own an FX-MIC. They look for gesture ideas during a first rehearsal for a new song, a tour changeover, or a last-minute rearrangement, when rehearsal time for trial and error is limited and parameter screenshots cannot show how to apply force. Sound engineers also need to hand tested configurations to the next performer without re-explaining them at every show.
Smallest useful version
A desktop app can use Tauri to read the FX-MIC mounted drive. The device exposes config.json and four WAV slots, making import, validation, and one-click installation a practical starting point. JSON Schema and Ajv can check effect names, parameter ranges, and modulation targets, while audio files are preflighted against the official format and size rules. The rehearsal page should first record the line output and annotate gesture prompts and effect changes. For lighting, export only a MIDI or OSC routing list; do not claim that the microphone directly controls lights. Because raw gesture curves and device vibration have no public interface, the first version should not use them for automated assessment.
Why now
As of September 1, EP–2350 FX–MIC ranks No. 2 in Product Hunt’s new-product feed. By bringing handle controls, shaking, and JSON presets to a handheld microphone, it will lead more new users to the rehearsal problem of being able to change parameters but not reliably reproduce a movement.
Strongest counterargument
The device currently exposes config.json and a file-copy workflow, but no real-time gesture-data interface. The system cannot reliably establish whether a shake matches a demonstration gesture; it can only estimate from the resulting audio. Rotary control and device vibration are not documented official capabilities either. Including them in a patch would create compatibility promises that cannot be kept. Gain, latency, and feedback across different sound-reinforcement chains also change how thresholds feel. One accidental trigger can play the wrong sample or suddenly add distortion, quickly eroding trust onstage. The team would also need to keep testing firmware, audio software, and lighting routes, with support costs growing alongside the compatibility matrix.
EP–2350 FX–MIC — Input snapshot: as of September 1, 2026, EP–2350 FX–MIC ranked No. 2 in Product Hunt’s new-product feed. The page describes it as a programmable microphone that can be squeezed, shaken, and played.
EP–2350 FX–MIC User Guide — The official guide confirms support for four sample slots, config.json, custom effect chains, handle modulation, shake modulation, and LFOs. Files are written through a USB-C mounted drive, and JSON syntax errors may prevent the device from booting. The guide does not list rotational gestures, a real-time gesture-data interface, device vibration, or a lighting-control interface.
Max for Live — Ableton’s official documentation confirms that Max for Live can create and install custom devices and extend hardware control through the Live API. Live also supports mapping external MIDI control data to controllable parameters.
Ableton Live | MaxforLive | Synth Patch Store — Isotonik Studios sells patches, control devices, effects, and sound packs for Ableton Live, Max for Live, and a range of music hardware, and features work by independent developers.
04Offline Video On-Deck QueueRedditKaraoke hosts, teachers, and event video operators are often handed the next song or another clip before the current video has finished. They cannot interrupt the full-screen output, yet must browse folders, remember the order of requests, and make a rushed switch at the end. This offline player moves on-deck work to a separate sidebar while the current video keeps playing. Hosts can search local files, preview thumbnails, and add multiple videos in succession. Each queued item is a draggable card showing file duration, audio tracks, and estimated playback time. A last-minute request can be marked as a one-time insert: it plays after the current clip, then the player automatically returns to the original queue. To skip a segment, the operator changes only the queue, without risking the projected image. Files likely to fail playback are flagged before their turn, leaving time to swap in backup material. After an event, the queue can be exported as a reusable playlist or retained as a record of who requested which clip and when. The first release starts with local folders and common video formats, with no streaming song requests or cloud collaboration. It addresses a specific live-use problem: handling a steady flow of next-video requests calmly while one offline computer keeps playing video.View detailsHide details
While one local video plays, a separate on-deck queue lets operators search, order, and temporarily insert multiple files, then continues automatically through the queue.
Karaoke hosts, teachers, and event video operators are often handed the next song or another clip before the current video has finished. They cannot interrupt the full-screen output, yet must browse folders, remember the order of requests, and make a rushed switch at the end. This offline player moves on-deck work to a separate sidebar while the current video keeps playing. Hosts can search local files, preview thumbnails, and add multiple videos in succession.
Each queued item is a draggable card showing file duration, audio tracks, and estimated playback time. A last-minute request can be marked as a one-time insert: it plays after the current clip, then the player automatically returns to the original queue. To skip a segment, the operator changes only the queue, without risking the projected image. Files likely to fail playback are flagged before their turn, leaving time to swap in backup material.
After an event, the queue can be exported as a reusable playlist or retained as a record of who requested which clip and when. The first release starts with local folders and common video formats, with no streaming song requests or cloud collaboration. It addresses a specific live-use problem: handling a steady flow of next-video requests calmly while one offline computer keeps playing video.
Who it is for
The primary users are karaoke hosts, classroom teachers, and small-event video operators. They need an on-deck sidebar when a video is already output full-screen and someone hands them the next clip. Opening a new file directly can interrupt the image, while managing the order from memory can cause clips to be missed. Remote and touchscreen use also demands few controls and an unambiguous sequence.
Smallest useful version
Build the first release as a landscape Android app in Kotlin and Jetpack Compose, with a playback area and fixed on-deck sidebar. Use Media3 ExoPlayer as the playback engine; it supports adding, moving, removing, and replacing items during playback. Let the app read user-selected local files through system directory permissions. Keep the original queue and one-time inserts as separate business-layer state rather than merging them into one list. Read thumbnails and durations one file at a time in the background, checking files that are about to play first. Exclude streaming, accounts, and cloud sync; export playlists as local files first.
Why now
A September 1, 2026 post in r/androidapps asked whether multiple local videos could be queued while the current video is playing. When recorded that day, the comments had not identified an existing solution, leaving an unmet need for an editable offline on-deck queue.
Strongest counterargument
Recognizing a local file does not guarantee smooth playback at an event. Unusual containers, corrupted files, or hardware-decoding differences may only surface when playback switches. Checking every file in advance adds battery use, waiting time, and cache-management overhead. If a one-time insert resumes at the wrong position, the rest of the queue shifts out of order. Full-screen output and sidebar focus must also be isolated, or remote-control buttons may accidentally trigger playback controls. When event logs include requester information, users must be able to disable and clear them. Unless recovery from failures is simple enough, this kind of tool will struggle to earn trust in live settings.
Signal, observation time, and sources
community_demand observation: Video Player with Reserve Next Video function?; observed 2026-09-01T00:36:00.185Z.
Video Player with Reserve Next Video function? — A post dated September 1, 2026 asks whether users can search for and queue multiple local videos while the current video is playing; it explicitly does not require online features, and no comments had offered an existing solution when the page was recorded.
Playlists | Android media — Media3 ExoPlayer playlists can dynamically add, move, remove, and replace media items during playback; moving the current item does not interrupt playback.
mpv Reference Manual — mpv’s loadfile command supports append, insert-next, and insert-at; it also provides playlist move and remove commands, plus JSON IPC for external control.
Settings/Media/Videos — Kodi can add selected videos to a temporary playlist and access it through the sidebar; it can also extract video details including duration, audio tracks, and codecs.
05Festival Camp Extension NetworkHacker NewsAt desert festivals, camping gatherings, and other large temporary events, mobile service is often unreliable, and attendees may not want to watch their screens all day. Organizers can place weatherproof public phones at camp entrances, water stations, and beside stages, then connect them with solar power and a local mesh network. Each camp or landmark gets a short extension, so visitors can walk to the nearest phone and call a friend’s location. When placing a call, the screen first shows which phones are near the recipient’s camp, then routes the call to the selected extension. If the recipient is away, the caller leaves a callback arrangement—such as, “Meet me at the East Gate phone at 9 tonight”—rather than sharing personal location data. The recipient can call back to that physical phone, while the system retains the call time and meeting point, giving separated people a way to reunite without relying on a mobile phone. An organizer dashboard uses a site map to manage phone locations, extension numbers, and battery levels, and the full kit can be packed up and moved to the next event afterward. The first deployments would serve clearly bounded camps and fixed landmarks, not emergency-response dispatch. It reimagines the public phone for temporary events as social infrastructure for making plans and checking in.View detailsHide details
At temporary gatherings with no reliable cell service, public extensions let people reach camps and arrange callbacks at specific physical meeting points.
At desert festivals, camping gatherings, and other large temporary events, mobile service is often unreliable, and attendees may not want to watch their screens all day. Organizers can place weatherproof public phones at camp entrances, water stations, and beside stages, then connect them with solar power and a local mesh network. Each camp or landmark gets a short extension, so visitors can walk to the nearest phone and call a friend’s location.
When placing a call, the screen first shows which phones are near the recipient’s camp, then routes the call to the selected extension. If the recipient is away, the caller leaves a callback arrangement—such as, “Meet me at the East Gate phone at 9 tonight”—rather than sharing personal location data. The recipient can call back to that physical phone, while the system retains the call time and meeting point, giving separated people a way to reunite without relying on a mobile phone.
An organizer dashboard uses a site map to manage phone locations, extension numbers, and battery levels, and the full kit can be packed up and moved to the next event afterward. The first deployments would serve clearly bounded camps and fixed landmarks, not emergency-response dispatch. It reimagines the public phone for temporary events as social infrastructure for making plans and checking in.
Who it is for
Camp leads, event operations teams, and volunteers at desert festivals and large camping events. It matters most when a group has scattered and needs to change plans, check in, or find someone. Phones may have no signal or no battery, and attendees may not want to keep checking a screen. A public extension at a fixed landmark is usable even for people who cannot configure wireless equipment.
Smallest useful version
Build the endpoints from weatherproof analog phones, ATAs, and an on-site Wi-Fi mesh network. Deploy Asterisk locally at the event and register each phone as a SIP extension. Its call routing, extension logic, and voicemail can support short-code calling and missed-call messages. Store callback arrangements separately as structured records containing only the call time, waiting phone, and expiration time. The first version does not connect to the public telephone network or use personal accounts. The dashboard provides only a site map, endpoint status, battery levels, and extension configuration. Each endpoint also needs a local configuration cache so brief dashboard outages do not prevent dialing.
Why now
On August 31, 2026, Playa Phone reached Hacker News; as recorded on September 1, it ranked first with 475 points and 175 comments. The event was still underway, and official guidance warns that mobile communication on-site is unreliable; a single Playa Phone hangs up after six unanswered rings.
Strongest counterargument
A weatherproof enclosure is only the beginning. Dust, intense sun, cold nights, and repeated drops will continually wear down keypads, handsets, and connectors. Insufficient solar power can first take isolated nodes offline, then make users think the whole network has failed. Stage noise can reduce speech intelligibility, while queues constrain the capacity of any one phone. If expired missed-call records are not cleared, they can send people to places that have already been vacated. Anything that looks like a phone may be treated as an emergency contact point. On-site signage, automated prompts, and operational inspections are therefore essential.
Playa Phone | Hacker News — The input snapshot shows that the Playa Phone post was created on August 31, 2026; as recorded on September 1, 2026, it ranked first with 475 points and 175 comments.
Playa Phone — The project page says the phone is available during Burning Man week. It uses internet calling and offers free outbound calls of up to five minutes; busy lines return a busy signal, and the phone hangs up after six unanswered rings.
Features Available in Asterisk — Asterisk officially lists capabilities including traditional PBX functions, call routing, flexible extension logic, and voicemail, which can underpin on-site short codes and missed-call messages.
When a bird passes through the yard, it automatically combines fragmented footage from multiple security cameras into one recognizable visit replay.A local box reads footage from backyard security cameras and combines fragmented triggers across multiple cameras into a single bird visit. Users receive only likely species, visit duration, and a concise replay; raw video never needs to be uploaded.
Two-Player Pips Puzzle
Other
After finishing the daily Pips, invite a friend to solve a short puzzle together using different sets of clues.Pips is a logic game where players place dominoes in a grid according to number rules. Two friends each receive half of the necessary clues and must use limited markings and communication to arrive at the same solution within five minutes.
When local AI jobs queue up, it automatically enlists idle office Macs to run them in parallel overnight and return the results.When local AI jobs pile up, idle Apple-silicon Macs around the office temporarily form a compute pool after hours. Jobs are split according to each machine’s memory, then merged and returned automatically in the morning, with caches cleared.
When handing a CLI to non-technical colleagues, developers can publish both terminal and cross-platform desktop versions from a single command definition.Developers write a command definition once to generate both a terminal command and a cross-platform desktop form. Each click can be copied as an equivalent command, and the two interfaces automatically cross-check their results.
For a last-minute special occasion, friends pool clothes and coordinate try-ons, borrowing, and returns directly.When they need an outfit for a wedding or themed party at short notice, users send trusted friends their size and occasion. Each friend lends one item, and the product assembles an outfit while coordinating try-ons and returns.