I have done it zero times, and I am definitely a Human man.

No idea what this is all about, but received is spelt incorrectly.

Nah just shove it through in random patterns like a hundred times. It works well enough.

I tried to get something on iPhone once, added credit to my account using one of those vouchers you can get from the store. I was able to add the credit, but it refused to allow me to purchase anything without adding payment details.

Get a Steam Deck, and you can press the power button whenever you want to stop playing and it puts the system on standby. Press it again and it powers on in a couple seconds right where you left it.

Damn, not sure I’m a fan of any of this. I left Arch because I didn’t want to be on Rolling release any more, and really liked what Nobara was offering for the out of the box experience.

Brave is super sketchy, and not sure about putting in yet another thing to handle updates (replacing plasma-discover and gnome-software).

I’m wondering if its worth forking it to remove some of these changes.

Because SEO is a game, and those with the mist shit that matches what Google wants is rewarded with a higher ranking.

What about Deskflow? Worked pretty well for me.

Proxmox is definitely on its way to become a viable replacement for sure. There’s also OpenShift from Red Hat which could be worth a look at as well.

The end goal is to try and have a web app that is usable on both desktop and mobile, I would use what I learn from this simple app to hopefully get something bigger going.

I have nothing specifically against JS I just was (somewhat ignorantly) hoping I could avoid it altogether. I also don’t like having to double up on defining classes, one for backend and one for frontend. I tried React and it really felt like I was wasting my time redefining stuff that I had already defined in my backend.

In my previous attempt, I basically had 3 definitions. The database definition, the Rust definition, then the frontend (JS).

Armosaur, more like Armsaresmall! Amirite?

OK, that’s fine. Just means I’d need to think more about how stuff is implemented. I’m thinking like input fields for date and time selection etc. Could be an interesting challenge for sure.

Surely its all been done before ha ha

I think I’m going to go this route - Leptos + HTMX. I’ll see how far this gets me without any JS. What type of interactivity do you think might require JS? I assume I should be able to do form validation etc without it?

OK, guess I’ll avoid WASM for now then. Someone else mentioned HTMX and pair that with Leptos, I should be able to get away with no JS.

All good, yea its because I need crowdsec installed on the proxy as well - not just the bouncer - in order to actually send the logs to Opnsense.

I ended up having some weird performance issues so I pulled it all out for now and will revisit another time.

How do you find working with it? Especially the debugging side?

OK, I was hoping to have it usable with JS disabled entirely, but that sounds impossible based on what you and others are saying. At least I can level my expectations somewhat before diving in.

Really? I thought part of the attraction for WASM was that it could be native code without needing JS. That’s good to know though. Thanks.

With the bouncer setup, I assume I need to pass in where to look for logs or something for those to be passed into the lapi? I followed this CrowdSec and Nginx Proxy Manager , as far as I can tell everything is connected an running, I have crowdsec running on OpnSense via the plugin - it appears to be healthy as per the CrowdSec Console.

npm  | [nginx       ] nginx: [error] [lua] crowdsec.lua:62: init(): error loading captcha plugin: no recaptcha site key provided, can't use recaptcha       
npm  | [nginx       ] nginx: [error] [lua] ban.lua:37: new(): BAN_TEMPLATE_PATH and REDIRECT_LOCATION variable are empty, will return HTTP 403 for ban decisions
npm  | [nginx       ] nginx: [alert] [lua] crowdsec_openresty.conf:5):11: [Crowdsec] Initialisation done                                                    
npm  | [supervisor  ] starting service 'app'...                                                                                                             
npm  | [app         ] [5/5/2025] [11:26:30 PM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite                                               
npm  | [supervisor  ] all services started.

Cheers, I’ve since discovered that’s is “bouncers” that I want on the endpoints I.e on my Nginx Proxy Manager. I’ll just use the LAPI on the Opnsense box for now I think.