Home Assistant users with LG washers, fridges, and AC units are getting their LG accounts temporarily banned because the popular community integration's polling looks like 'automated script usage,' breaking their automations. They want their appliances to keep working locally without risking a cloud account lockout. This is the appliance sibling of the broader manufacturer-lockdown trend, aimed at white-goods owners rather than car owners.
builder note This is a cat-and-mouse game against a manufacturer who can change the rules, so do not sell a polished consumer app that LG can brick overnight. The defensible play is a respectful, rate-limited, official-API-first bridge (or local LAN where it exists) sold to the HA crowd as 'won't get your account banned,' and treat ongoing maintenance as the actual product.
landscape (3 existing solutions)
Every path to controlling an LG appliance still routes through LG's cloud, which is now actively hostile to third-party polling. There is no reliable local or sanctioned-API route that exposes full appliance features without gambling your account, and Matter does not fill the gap.
LG ThinQ official cloud app / API Cloud-only and the source of the bans. The official developer API exists but is gated and oriented to vendors, not hobbyists wanting full local control of their own machine. Matter / Home Assistant native LG's Matter support covers only a thin slice of appliance functionality (on/off, basic status), not the cycle/notification/diagnostic detail people actually automate around. sources (1)
smart-homelocal-firsthome-assistantappliancesanti-cloud-lockin
eIDAS 2.0 forces EU relying parties to accept EU Digital Identity Wallet logins (OID4VP) by January 2027, and developers are now asking for it in the tools they actually run. Keycloak, the default self-hosted identity server, has no native support, and the alternatives are enterprise identity platforms. The opening is a Clerk/Auth0-style, low-friction 'accept an EU wallet credential' drop-in for small teams.
builder note Do not try to out-walt.id on the full credential lifecycle. The wedge is purely the verifier/relying-party side ('accept an EU wallet login') packaged for people who currently use Clerk/Auth0/Keycloak, with the regulatory deadline as your built-in urgency.
landscape (3 existing solutions)
The protocol layer exists and the big vendors sell it, but everything is pitched at banks and governments. The gap is a cheap, maintained, indie-friendly verifier (especially a first-class Keycloak path) so a two-person EU SaaS can become wallet-ready before the 2027 deadline without buying an identity platform.
walt.id Community Stack / SDK Full OID4VP/OID4VCI SDK, but it is an infrastructure stack you adopt and operate, aimed at organizations, not a five-minute 'add a login button' for a side project. sources (1)
eidas2eudi-walletoid4vpidentitykeycloak
Experienced engineers say their main watering holes (HN especially) have turned into AI marketing feeds, and deep technical writing no longer surfaces. They want a place that discovers and discusses substantive, human-made tech content without drowning in LLM hype. The demand is for curation and discovery, not another generic forum.
builder note The trap is building yet another forum and hoping people show up. The actual unmet need is curation/discovery (the 'what's worth reading this week' problem), so start as a ruthlessly curated reader/digest with a small human editorial hand, not an empty Reddit clone waiting on network effects.
landscape (3 existing solutions)
The same 'where do I go instead of HN' question keeps recurring with no satisfying answer. Every alternative is either invite-walled and tiny (Lobsters, Tildes) or just another algorithmic aggregator. Nobody owns 'open, well-moderated, discovery-first, AI-light, and usable on a phone' at once.
Lobsters (lobste.rs) Repeatedly named as the closest thing, but invite-only, deliberately small, link-list only, no real mobile app, and discovery is thin beyond the front page. Tildes Invite-only and tiny by design. Calmer than HN but too small to function as a discovery engine for the broad tech-content firehose. RNKFlow An aggregator pitched directly in the thread; the OP flagged poor mobile usability and it is an algorithmic feed, not a curated/community layer. sources (2)
communitycontent-discoveryanti-ai-slopcurationrss