Recently I finally start to C-X M-x to do text scaling, the typing is hard even as near 2 decades user of Emacs.

But I will still consider to release it anyways

And I am also very grateful that tailscale implement some workaround for systems such as apple-based OS with core APIs built into the open source code, thus if you really need you can just look the open source code and doing accordingly, though it really need some research work.

For the long term if they really do not want to open source the core client code (which I do not believe at the moment), I think support a fully open source coordinator and open source client based on the fork will still be doable.

I’m an indie developer and heavy Tailscale user. I built NovaAccess because I needed reliable SSH access to my tailnet on iOS without breaking other VPNs.

On iOS, the official Tailscale app requires VPN entitlements, which means you can’t run it alongside another VPN. That was a deal-breaker for my workflow. NovaAccess uses libtailscale directly, so it works without requesting VPN permissions and can coexist with any VPN you’re already using.

What NovaAccess does:

Native SSH terminal for tailnet hosts (SwiftTerm, not WebKit)

Auto-discovery of tailnet nodes

SSH key management

Optional support for custom login servers / Headscale

In the latest update (v1.1.0), I focused heavily on terminal UX and reliability:

Reworked terminal core and accessory keyboard

Better session resume after backgrounding

UI redesign to make daily ops faster

There’s also a Pro tier for people managing multiple tailnets or doing heavier ops:

Multi-tailnet switching

In-tailnet server monitoring

Internal web access

SFTP file management

The free tier is fully usable for SSH access.

I built this primarily for myself and am now trying to see if it’s useful to others.

Feedback (especially critical) is very welcome.

App Store link:

https://apps.apple.com/us/app/novaaccess-tailnet-tools/id674...

For the Tailscale and SwiftTerm core dependencies we use, we also have the fork OpenSourced on GitHub:

https://github.com/GalaxNet-Ltd/SwiftTerm https://github.com/GalaxNet-Ltd/libtailscale

Comments URL: https://news.ycombinator.com/item?id=46886288

Points: 1

# Comments: 0

Seems Miguel’s velox point a new idea, leveraging the wry and use ffi to go, and rewrite some tooling.

I hope I will have the spare time and energy to give a try…

I can understand that put UDP payload into a single HTTP stream, at least when QUIC transport is in use, there is no UDP in TCP case.

The Source Address/Port in the UDP payload message serve as key to handle to the tunnel client if I understand correctly?

And I also being shocked that Cisco Switch goes to reboot loop with this DNS order issue.

I have a folder which is controlled by Git, the folder contains various markdown files as my personal knowledge base and work planning files (It's a long story that I have gradually migrate from EverNote->OneNote->Obsidian->plain markdown files + Git), last time I tried to wire a Local LLM API(using LMStudio) to claude code/open code, and use the agent to analyze some documents, but the result is not quite good, either can't find the files or answer quality is bad.

Seems this machine is more powerful than it, definitely attractive to me for a physical aarch64 self host runner.

this is the second MCP i added, quit impressive.

Merry christmas!

Merry Christmas to everyone.

Since I do not make this node public accessable, so no worry for AI web crawlers:)