A less infuriating SSH experience.
▲ 3 r/DevLK+2 crossposts

A less infuriating SSH experience.

Mankind deserves a less infuriating SSH Experience...

Edit: People keeps asking what's infuriating in ssh, it's the delay. Typing Delay is infuriating. And yes most of you who are living in developed countries does not experience these but the few who are working from countries like Sri Lanka, will definitely experience this delay.

And yeah, you probably already guessed how: a normal SSH session does a full round trip per keystroke you type, wait for the server to echo it back, watch it appear. FlashSSH does the line editing locally, so typing, history, autosuggestions and tab-completion are all instant. It only touches the network once... when you press Enter.

Even for full-screen stuff (vim, tmux, btop…) where it hands over a real PTY, it does mosh-style predictive echo: your keystrokes show up immediately in grey and turn white the moment the server confirms them same idea as mosh, minus the full terminal emulator. And it decides whether prediction is actually helping at runtime instead of guessing from the program name, so it works in sessions it's never heard of.

Best part: anything that needs a terminal but isn't on the known list just works now. A plain exec that fails with a "needs a terminal" error gets transparently re-run under a PTY (or you force it with a ! prefix). No allowlist editing.

One-line install, C on libssh, MIT. Still early tell me what breaks:

Direct Install:

curl -fsSL https://raw.githubusercontent.com/z3r0n3br4instorm/FlashSSH/main/install.sh | sh
github.com
u/__z3r0_0n3__ — 2 days ago

Zed for OpenGL 3.3

Hi Everyone!,

I created this fork of zed to work with OpenGL 3.3 backends. Mainly because I'm daily driving this old macbook pro on Arch Linux with intel HD3000 graphics as a hobby project and I wanted to use zed with it.

Anyways, here's the repo if anyone wants to check it out: https://github.com/z3r0n3br4instorm/zed/tree/gl33-backend

And here's the Pre-Compiled binary for Linux

https://drive.google.com/file/d/1BwfKQZ244XbmhXzCnXNBHm9PPlfuZTIr/view?usp=drive_link

reddit.com
u/__z3r0_0n3__ — 4 days ago
▲ 3 r/DevLK+1 crossposts

ACI (Abstract Coding Interface) an alpha VS Code extension where a local LLM "compiles" pseudocode blocks into real code (looking for feedback)

Repo: [https://github.com/z3r0n3br4instorm/AbstractCodingInterface](https://github.com/z3r0n3br4instorm/AbstractCodingInterface)

Hey all,

I've been tinkering on a side project called ACI (Abstract Coding Interface) and wanted to share it here, mostly to get some early feedback since it's very much an alpha release.

The idea:

you write high-level pseudocode in a small language called PSyx (`.aci` files), and a small (1b, 3b, 7b etc.) local LLM (via Ollama, llama.cpp, LM Studio, etc.) compiles it into actual source code, block by block, streamed into a file next to your spec. Tested with \`deepseek-coder:6.7b\`. The pseudocode stays as the "source of truth," and editing one function only recompiles that function instead of regenerating the whole file.

Example:

```

FUNC-START greet

INPUT name as string

IF name is empty

DISPLAY Hello, World!

DISPLAY Hello, name

FUNC-END

```

Save it as `greet.aci`, and ACI opens `greet.py` next to it with the compiled output.

Why I built it / where it might actually be useful:

- Language migration / porting: since the spec is language-agnostic pseudocode, in theory you could re-target the same `.aci` file to a different `aci.targetLanguage` and get a re-implementation, useful if you're prototyping logic once and need it in multiple languages.

- Keeping intent readable: for logic-heavy functions, the pseudocode ends up being a lighter-weight "spec" than a full docstring, and it stays in sync with the code since it's literally what generated it.

- Local-first AI coding : no API keys, no cloud calls, everything runs against your own local model — appealing if you want AI-assisted coding without sending code out.

- Incremental compiles: because only the edited block gets recompiled, it avoids the "regenerate the whole file and hope nothing broke" problem you get with a lot of AI codegen tools.

I want to be upfront that these are the use cases I *think* it's good for, not ones I've rigorously validated — it's a young project and I haven't stress-tested it against real-world codebases yet, so take the above as hypotheses rather than proven wins.

Where it's at right now:

- Genuinely early/alpha, expect rough edges and missing features

- Currently only available as a VS Code extension (installable via `.vsix`)

- A Zed editor version is in the works, not out yet

- Local-model only for now (no cloud backends wired in)

Would love thoughts, criticism, or feature requests.

u/__z3r0_0n3__ — 23 days ago
▲ 13 r/foss+2 crossposts

I made a webcam-based auto-brightness tool for Linux (Hypridle integration)

https://reddit.com/link/1v2osto/video/v62f8lgr8meh1/player

https://github.com/z3r0n3br4instorm/AutoBrightnessLinux

My laptop doesn't have an ambient light sensor, and I was sick of squinting at 100% brightness in a dark room or getting blinded at max brightness near a window. So I wrote a small Python tool that uses the webcam instead of dedicated hardware.

It grabs a frame, does a bit of weighted luminance + percentile analysis on the center region (to avoid getting thrown off by a bright window in the corner or a dark hoodie filling half the frame), and maps that to a brightness percentage via brightnessctl. There's smoothing baked in so it doesn't yank your screen between values every time you glance away.

It's built to slot into Hypridle on idle-timeout and resume it re-samples the room and adjusts both screen and keyboard backlight (keyboard scales to ~20% of screen brightness). No daemon, no polling loop eating CPU in the background — it just fires when hypridle tells it to.

Still early (v0.0.1), Python + OpenCV, Hyprland-specific for now but the core brightness logic doesn't care what compositor you're on happy to take PRs for other idle daemons.

Repo's here if you want to poke at it: https://github.com/z3r0n3br4instorm/AutoBrightnessLinux

Feedback, roasts, and "why didn't you just use X" comments all welcome.

reddit.com
u/__z3r0_0n3__ — 30 days ago
▲ 3 r/OpenCoreLegacyPatcher+1 crossposts

Dead display after sleeping my 13inch 2011 MacBook pro

I bought this used early 2011 13 inch MacBook pro to daily drive it. I kinda did something stupid to be honest, I initially installed Sonoma with OCLP, it was working fine but not smooth, so I decided to dual boot it with Catalina, with dosdude1's Catalina patcher. Then I installed Snow leopard as well. So it had three operating systems. I removed Sonoma after a while and had been using Catalina for like a week now. 

I have to mention this as well, when I tried to install a RAM card to the bottom slot & It didn't boot, sometimes it boots but crash in the OS or 3/4th of the boot progress. Also when I put pressure on the CPU area it manages to be on the OS for a while before crashing again. Eventually I gave up and now it only has a single stick of 8GB RAM on the top slot.

Circleling back to the main issue, I left my laptop idle on my table today, I went out came back to a black screen, I thought it might've been sleeping I tried waking up, nothing happened so I force turned it off (I have a secondary HDD installed in a caddy I heard the HDD stopping when I did that). Then when I boot it back up the display doesn't work, no backlight or image. But it boots up because I can see the keyboard backlight gets initialized and I can blindly enter password and do a `sudo reboot` which will actually reboot the laptop. I tried blindly booting to the snow leopard entry, somehow that initializes the backlight, but no image is showing up. When I boot it to Snowleopard and reboot, when the laptop turns back on the backlight initializes. But if I do a PRAM reset, backlight doesn't initialize again. 

Bear in mind I'm booting Snowleopard from the opencore menu. So I tried resetting PRAM and booting a clean Snowleopard installation from my other SSD which will turn on the backlight on boot but when I reboot the backlight is not turning on again. Currently I don't have a mini display port adapter so I don't know if the display output works,

reddit.com
u/__z3r0_0n3__ — 1 month ago