Login

u/Large-Cress900

Update on Zap Browser: just released v0.3.6-beta.
▲ 1 r/IMadeThis

Update on Zap Browser: just released v0.3.6-beta.

A few weeks ago I shared the first beta here while experimenting with the idea of a browser built around Nostr, Lightning and privacy-first workflows.

Since then the project evolved a lot faster than expected.

This new release adds:

  • built-in update checker
  • multi-theme engine
  • improved popup/interstitial blocking
  • overlay ad cleanup
  • improved NIP-07 permission handling
  • automated Linux + Windows releases

Now shipping:

  • AppImage
  • deb
  • rpm
  • Windows installer
  • portable builds

Still beta, but the project is starting to feel much more stable and usable compared to the early builds.

Really appreciate all the feedback people gave on the previous post — a lot of fixes and ideas came directly from community comments and GitHub issues.

Repo:
https://github.com/shadowbipnode/Zap-Browser

u/Large-Cress900 — 2 hours ago
▲ 2 r/LocalLLM

I’ve been experimenting with running operational/sysadmin AI workflows entirely through local Ollama models instead of cloud APIs, mainly for privacy/self-hosted reasons.

Honestly, I expected it to be mostly a gimmick… but I’m starting to think local models are becoming surprisingly usable for real infrastructure tasks.

Some workflows I tested locally with Ollama:

  • log analysis
  • command generation
  • config generation
  • troubleshooting flows
  • script generation
  • operational risk/rollback suggestions
  • Docker/systemd/nginx-oriented diagnostics

The interesting part is that the value doesn’t seem to come from “chatting with AI”, but from structured operational workflows:

  • assumptions
  • rollback steps
  • verification commands
  • risk awareness
  • environment-aware outputs

That feels much more useful than generic “AI assistant” conversations.

I’m curious how many people here are already using local models for actual ops/sysadmin workflows instead of just experimenting.

Questions:

  • which local models are working best for you?
  • are 3B/7B models already enough for practical infra tasks?
  • where do local models still fail badly?
  • do you trust them for production-adjacent workflows yet?

For context, I tested mostly with Ollama on Linux using lightweight local models rather than huge GPU-heavy setups.

reddit.com
u/Large-Cress900 — 8 days ago
▲ 4 r/linuxadmin+3 crossposts

I just released v1.3.0-beta and the project changed quite a lot since the original post.

Biggest change:
I moved away from the idea of making “just another AI chatbot wrapper”.

The goal now is building something closer to an infrastructure-aware Linux operational assistant.

New features include:

  • structured troubleshooting output
  • rollback + verification workflows
  • confidence/risk analysis
  • Docker/systemd environment detection
  • operationally-aware diagnostics
  • redesigned UI inspired by modern infra tools
  • integrated GitHub update checker

The AI now tries to reason differently depending on the detected environment instead of generating generic answers.

For example:
Docker-related issues now generate Docker-oriented operational workflows instead of random Linux suggestions.

Still beta, but the project is becoming much more serious and useful than the first versions.

Would genuinely appreciate more testing and criticism from Linux/sysadmin/self-hosted users.

GitHub:
https://github.com/shadowbipnode/sysai-assistant

u/Large-Cress900 — 5 days ago
▲ 1 r/browsers

I've been building an open source desktop browser (Electron + Chromium) focused on privacy — built-in adblock, WebRTC block, UA rotation, no extensions needed. Early Linux beta.

I want to share it here to get feedback from people who actually care about browsers, not to promote a product. Is that the kind of post this sub welcomes, or should I take it elsewhere?

Happy to follow any rules — just didn't want to post without asking first.

reddit.com
u/Large-Cress900 — 10 days ago
▲ 13 r/Bitcoin+1 crossposts

I wanted a browser where I could pay Lightning invoices without switching apps or installing extensions. So I built one.

Zap Browser is an open source Electron browser with a native NWC wallet. You paste your nostr+walletconnect:// string once and you're done — pay invoices, receive, check balance, all from the browser toolbar.

Lightning stack:

  • NWC (Nostr Wallet Connect) over real WebSocket — NIP-47 ECDH encrypted
  • Compatible with LNbits, Alby, Zeus, Mutiny, Breez, Phoenix
  • Works with self-hosted LNbits behind nginx (tested and running)
  • Pay Lightning invoices directly from any page
  • Receive: generate invoice from the wallet panel
  • Disconnect/reconnect at any time

Why it matters for LN node runners: If you run your own LNbits or LND, you can connect Zap Browser to your node. No third party custodian. Your keys, your node, your browser.

Also included:

  • Cashu ecash wallet (multi-mint)
  • Nostr NIP-07 native signer (automatic login on Nostr apps)
  • 106k adblock + WebRTC leak prevention

Download (Linux): https://github.com/shadowbipnode/Zap-Browser/releases/tag/v0.3.3

Early beta — happy to take feedback from node runners. What NWC features would be most useful to you?

u/Large-Cress900 — 10 days ago