![Avatar](/_next/image?url=https%3A%2F%2Finfosec.pub%2Fpictrs%2Fimage%2F671e3303-3972-453b-bfb7-55c5d2402d6b.jpeg&w=3840&q=75)
![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
owl
Cool picture
Somehow reminds me of the matrix.
When you visit a website your browser speaks with the server in http. It is structured in requests and responses. You request a text, you get it. You request to upload an image, it is done. Very useful, but what if you wanted to get a live feed of things. Imagine you wanted to chat. You could send many requests always asking “is there a new message?” and always getting “no”. That’s not good, with a websocket your webbrowser and the server establish a live connection. Now they can send and receive small pieces of information. For chatting, games, auctions and many other things websockets are useful.
I don’t know a lot about this, but I would guess a normal user would like a message, that says something along the lines of “404, couldn’t find what you were looking for.” The status code and the links back to itself as well as the 13 MBs of noise should probably not irritate them. Hidden links should also not irritate normal users.
Is this a real photo? Do they always have a flag on top?