Nire Bryce

@NireBryce

reality is the battlefield

she/they (pl)
breadthcharge.net/

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.

Nire Bryce @NireBryce8/28/2023, 7:38 PM

it seems so assinine that we still connect with webapps with either servicename.example.com or example.com:port/servicename

you need to jump through hoops to do rdns to shunt various subdomains to various services (if they all run on the same port, which they usually do, because it's a webapp), or have ugly port stuff

but it could easily be example.com/servicename, no fiddling with ports, just point it at the fuckin thing. how is there no workaround that isn't literally 30 years old.

all I want to do is navigate to things where I say they are, not care about what port they're listening to or setting up even more infrastructure just to do what it's supposed to.

the web as it stands is fairly unsuitable for hosting applications without an ops department or a few weeks of hobby time to burn, and that's kinda sad

You must log in to comment.

in reply to @NireBryce's post:

cat @catball8/28/2023, 7:43 PM

god, yeah, having to reverse proxy stuff sucks

it shows that it was built for serving non-interactive documents from a single server based on a directory tree, and everything since then has been hacked on top in various nonstandard ways :(

Nire Bryce @NireBryce8/28/2023, 7:46 PM

that's what infuriates me with it though -- just let me access apps as documents, its not like javascript cares where it's served from. it can even be a docker container, just have the entry-point be there.

cat @catball8/28/2023, 9:02 PM

oh, gotcha. would that be like CGI bin? because I'd kinda love a performant cgi bin

Nire Bryce @NireBryce8/29/2023, 12:03 AM

yeah, or like, ports in reverse (my request opens a socket, which you connect to to pull me into wherever it actually lives/runs)

but cgi-bin would be cool.

cat @catball8/29/2023, 2:56 AM

would you need something that deterministically does that (like some 5-tuple consistent hash load balancer), or like some system that tracks the state of sessions and maps them to backends?

cat @catball8/29/2023, 2:57 AM

jk i think this goes back to having middleware and/or netops again

cat @catball8/29/2023, 2:58 AM

computers are a lot harder when you have a lot of them

Raymond Neilson @deltavee8/29/2023, 1:15 AM

In the old days, you could do that kind of thing, sure - but you're at the mercy of the same-origin rule. So are all those webapps you want to run on the same origin, they all think they have the cookie and storage and CSP namespaces all to themselves, and they absolutely will trip over each other and fuck each other over.

There is always something playing traffic cop in the middle of all this shit, because if there isn't then everything blows itself up (or worse, lets everyone have a party on your domain).

(Also ftr yes, javascript can care very much about where it's loaded from. Blame the cryptominers and ransomware for making the web a paranoid shitfest.)

Nire Bryce @NireBryce8/29/2023, 2:09 AM

yeah, but right now the home use is have ppl learn 9 things they will use once a year at most to deploy a new thing, which makes it really hard to actually help anyone in ways that won't bite me in 3 months unfortunately

Raymond Neilson @deltavee8/29/2023, 2:53 AM

I think there's absolutely room to make better tools for DNS, especially rDNS. I think there's a fucking hole the size of a carrier for something simple to deploy a bunch of webapps. But there is always some reverse proxy hiding eldritch complexity, even if you prefer top-level routes to subdomains (note: subdomains are better on every single axis, from security to composability to actually configuring the webapp in question without a thousand URL rewrite rules, except for the extra DNS management overhead).

I guess mostly I'm saying there's always gonna be a bunch of magic, let's not make things less secure because you want one flavor of magic over another?

Nire Bryce @NireBryce8/29/2023, 5:35 AM

:yeah:

Pinned Tags