I was about to ask if there wasn't an alcatel or bell labs logo like that, turns out it's the first in the blog post :-P

their card design could use larger text, I think. isn't that too small to read comfortably even from around 1m?

also, one name per line, that's going to work well

while I suppose Kiefer Sutherland doesn't work for them, there's still plenty of room for complications, so I hope they did check that one well, or that it has been in use already. (e.g. are they doing tr ' ' '\n', or do they at least take care that connecting components don't take a line of their own?)

On the other hand, if someone has a long name and some lines of it end up printed over or under the logo, well, it might be seen as realistic CSS?

the best they could come up with is lucent? yeesh

straws will be grassed 2024

gumo

uhm

oh well

good (ugt) morning :)

Hi

so I read rfc 9114

aka HTTP/3

So because of their inability to realize that http was never designed for the bullshit they pushed in http/2 they decided well http doesn't NEED to be a TCP/IP protocol anymore.. quic is udp

and then consider DNS.. so in the end we will trade tcp http and udp dns for quic udp http with dns over http which is over quic a udp protocol

and all for streaming social netflix pocket telescreens

it's like they finally realized the "web" aka http shouldn't have been used for all this it should have been a new protocol on the internet EXCEPT they think they have some claim to define the web and restrict the broader internet of protocols.. and they only get proven right when others go along with it..

its like the people who control the browsers call the shots.. so why why why are all of US not involved in that..

or simply do the same trick twice.. end run whatwg with a new working group putting out first the old working standards reaffirming them and then working on actually evolving THOSE standards

like what was the plan until sometime mid-2008

it would be best to do it now while the web is still world and wide

cause in a udp http whatwg world nothing existing can ever be relied on to continue to exist or.. work off a god damned cell phone

It's a real problem for me.. I read things and have feelings about them leading to forming opinions..

UDP works well for A/V, where you don't mind one lost packet every now and then

it's horrible for everything else

exactly

Unless you love corrupted photos, corrupted executables, and text files missing large chunks of content (or documents that will not open at all because the section with the metadata never arrived)

but you would say "well, let's add error correction and retransmission to the protocol", and oh my, you've already reinvented TCP

TCP-over-UDP

tomman: the modern web doesn't need localstorage so downloads like that outside drm protected webmedia is really besides the point and actively harmful to the web..

i mean

just needs moar JavaScript

that will likely be the thing

i am prophasising again and that's never good

uh did anyone ask for more javascript?

well I have the solution it just has little chance of succeeding broadly but it sure would be great.. Fork HTTPS as the Hypertext Document Protocol CA certs work per normal but plain http cases are covered by allowing self-signed certs to verify connection integrety but like http not authinticity/identity .. and that's stage 1.. Stage 2 is redefining HTTP into a rich XML protocol but its still tcp/ip the xml enabled version would use a single header

to denote if content was embedded in the main xml response or appended

there's this neat thing from Macromedia, well, now Adobe

it has ECMAscript in it

action script was better

tomman: it des work well for A/V, but it doesn't need http to be reimplemented on top of it, or does it?

I've used TV over UDP broadcast in the past, worked quite well

njsg: it's not the web i know and it isn't the web that was promised by anything other than sqinting real hard at a bullet point list and half of them are only valid because the new thing just happens to carry the same name

I even have a name for the new standards body The Web Hypertext Document Technology Working Group or WHDTWG (wood-twig)