GitHub Trending: Today — Electerm, DNS Blocklists, Novu

Today's shortlist: electerm/electerm — terminal and SSH/SFTP/RDP/VNC client (+40 stars); hagezi/dns-blocklists — DNS filtering lists for ads, tracking, and malicious domains (+46 stars); novuhq/novu — notification infrastructure for agents and products (+36 stars).

electerm/electerm — one desktop for remote systems

For developers and operators who routinely cross SSH, file transfer, serial, and desktop-remote protocols, electerm/electerm puts those clients behind one cross-platform interface. Its issue tracker tells the more useful adoption story: connection reliability, RDP behavior, and Windows display bugs are active concerns rather than a polished abstraction one can install and forget.

The discussion search found no direct fresh thread about the project itself; most retrieved HN material was about Electron's macOS performance. That absence is a reminder to evaluate the client on its own protocols and platforms, not merely on the framework argument surrounding it.

hagezi/dns-blocklists — DNS filtering that stays editable

Hagezi DNS Blocklists targets people running Pi-hole, AdGuard, or a filtering DNS service who want maintained domain lists for ads, tracking, phishing, scams, and malware. The project’s current issues include AI-generated phishing sites, fake music stores, and false-positive allow requests: the list is a continuing editorial operation, not a static security download.

Bluesky users describe the lists as well maintained and recommend specific variants for phones and private DNS setups. That practical recommendation is more meaningful than a generic popularity signal: users are selecting a trade-off between filtering coverage and the risk of blocking something legitimate.

novuhq/novu — notification delivery as product infrastructure

novuhq/novu is for teams that need one system to orchestrate email, push, SMS, chat integrations, and an in-product inbox. Its value is not a new delivery channel but centralizing preference, routing, and presentation work that otherwise spreads across vendors and application code.

A previous HN thread asked the question that remains decisive for infrastructure like this: who is running it at high volume? Current issue discussions include inbox rendering and connection failures, while Bluesky users specifically praise the embeddable inbox and customizable push payloads.

The boundary is the product

These three repositories are not trying to invent a new workflow. They make a familiar boundary configurable: remote access, name resolution, and user communication. The useful test is correspondingly plain—adopt the one where owning that boundary saves more operational complexity than it creates.