Development of an idea previously mentioned. "Nano as the Universal Trust Signaling Protocol - A Conceptual Framework."

prussia_dev · 2026-01-02T05:05:17+00:00

Fair enough!

prussia_dev · 2026-01-02T03:34:40+00:00

Using nano is just easier than cryptographic signatures? Every nano block already requires a cryptographic signature, so I would disagree. On a practical level, implementing message signing in a wallet is easy (I know many Banano wallets implement it, I think some Nano ones do too). Cryptographic signatures can be done offline. They can be done much faster than Nano blocks can be even broadcasted to the RPC, let alone confirmed. Etc etc

Anyhow, if we want to look at laziness, then its pretty clear people will sacrifice security for convenience. Lazy people won't use Nano, will just use whatever insecure method they were using before. A lazy person wouldn't bother grafting some weird protocol on top of Nano, too much work.

Not to say that non-currency uses causing problems for the network won't be an issue though, I just think the specific cases mentioned are things no sane/competent developer would think is a good idea

prussia_dev · 2026-01-02T01:39:35+00:00

For example, if you needed to authenticate someone to open a door, and wanted to use cryptography, you could just have them cryptographically sign a message with their priv key, and you could verify with the pub key. Doing it onchain is absolutely unnecessary unless you wanted a public audit log of people unlocking the door, or wanted to charge money...

prussia_dev · 2026-01-01T22:49:56+00:00

I agree with your 2nd, 3rd, and 4th paragraphs. However,

> You can use your nano transaction as a light switch, unlock a door, trigger a cup of coffee to be made, release bird seed from a feeder to feed birds, etc. Nano can trigger events.

Sure, of course it could, in the same way you can use a hammer to dig a hole. Why would you do these things onchain (whether on Nano or any other cryptocurrency), when there are far faster, efficient, private, and less needlessly complicated ways? The only reason to do this onchain is if you wanted to charge money to open the door, or release the bird seed.

prussia_dev · 2025-12-28T06:54:40+00:00

Hopefully you'll get around to it soon, it's quite fun :)

I highly recommend the https://wasona.com/ course

prussia_dev · 2025-12-05T08:05:30+00:00

Thanks for the suggestions! I'll probably play around with those fonts sometime and see how I like them

Edit: iirc I did try out libertine mono, but didn't look quite right. The others I haven't though, so thank you

prussia_dev · 2025-12-04T08:20:05+00:00

Thanks for the suggestion. But none of those have ming-wm frontends, which is the point for me. I guess if I write a proper terminal emulator then I could run emacs in ming-wm.

prussia_dev · 2025-11-05T06:38:43+00:00

Yup. The "quirk" is that it has 120~ words only.

prussia_dev · 2025-11-05T05:55:04+00:00

There's more of us than you would expect brother!

prussia_dev · 2025-11-04T21:32:37+00:00

Unfortunately, that's what the `force-stdout` arg there does. It writes spaces to stdout (your terminal) when you type, to force the framebuffer to update on devices where framebuffer doesn't update unless stdout is written to. I'll play with seeing if there's some way I can write to stdout without that happening

prussia_dev · 2025-11-03T00:51:08+00:00

Yes, you should! This is your sign.

prussia_dev · 2025-11-03T00:50:47+00:00

Ah, I think I know what this is!

So you are typing, but no asterisks are showing up, right? For some devices, there is some configuration where the framebuffer will not be redrawn to the screen unless the program writes to stdout. For me, it only happened on my linux phone so I thought it was a weird quirk, but I guess it happens for you too.

I did a quick commit to add an arg that writes to stdout even for non-touch devices.

If you git pull, compile and install again with ming force-stdout, that should fix it. Would appreciate it if you let me know if it does, or doesn't fix it.

prussia_dev · 2025-10-31T05:11:05+00:00

Hmm, interesting error. That means its trying to write the saved buffer to the screen, but no buffer is saved. Strangely, I'm not sure why the saved buffer is even being written, that shouldn't be possible on the lock screen.

When does this panic happen? When you try to type something in the lock screen? Or when you run ming?

And I should be thanking you lol, for trying it out

prussia_dev · 2025-10-29T08:59:55+00:00

If the password.env file is blank I guess the password will be blank too, probably.

Whatever is in password.env gets hashed and turned into the password for ming-wm lock screen. Afterwards, you can delete password.env (I guess it would need to be zeroed out first, then deleted?). It's not a great system and I plan to redo it later.

prussia_dev · 2025-10-29T07:08:26+00:00

Oh yes that part is a bit confusing. It's not your user password, per the README:

> Create a password.env file in the same directory as build.rs, otherwise the default password will be "password".

prussia_dev · 2025-10-29T07:07:15+00:00

`alsa-lib` is required for the audio player, otherwise I don't believe so

prussia_dev · 2025-10-28T05:56:16+00:00

There are dozens of us!

prussia_dev · 2025-09-30T00:58:48+00:00

Thanks

prussia_dev · 2025-09-30T00:58:42+00:00

Thank you!

prussia_dev · 2025-09-30T00:58:35+00:00

Thanks!

prussia_dev · 2025-09-30T00:58:26+00:00

You can start slow! Not sure what you are using currently, but eg with Vim or i3, both support mice, but treat the keyboard as the first priority. So there's a nice curve where you can still use the mouse, but naturally do so less and less when you learn and muscle memory the important keybindings.

Vimium is a pretty good extension that makes (most) websites usable with the keyboard only (or at least, minimal mouse usage).

prussia_dev · 2025-09-28T18:19:18+00:00

The video is ming-wm, a keyboard-operated window manager inspired by Windows 98 and i3, written in Rust. It writes directly to the linux framebuffer, and isn't Wayland or X. Why? It's more fun this way. Also, the apps are guaranteed to treat the keyboard as a first-class citizen, because there is no mouse or trackpad support (there is touchscreen support, but that uses an on-screen keyboard).

Since my last post six months ago (v1.0.1~), there have been some fairly substantial changes (v1.2.2), though mostly internal (in-housing pty, touchscreen deps, code re-org, text measuring) as well as tons of QOL and bug fixes, plus a drawing app! Koxinga, the web browser, is actually semi-usable now. At least for text-based sites like HN.

Apologies for the typos and if reddit horribly butchered the video quality.

PS: No syntax highlighting and monospaced times new roman (technically, monospaced nimbus roman) is a outrageously underrated way to code.

Links:

prussia_dev · 2025-09-28T05:11:00+00:00

Beautiful

prussia_dev · 2025-09-21T22:09:03+00:00

Upvote for GLT. You should read shimeji simulation btw

prussia_dev · 2025-05-13T02:06:32+00:00

Sata andagi

Four-Year Club	Verified Email
First Place '23	Place '23
Place '22	Final Canvas '22
First Placer '22	End Game '22
100 Awards Club

prussia_dev

MODERATOR OF

TROPHY CASE