@joe why would anyone want to use HTTP to browse the Web?
-
@joe why would anyone want to use HTTP to browse the Web? why not have a different protocol for every single website?
-
@joe why would anyone want to use HTTP to browse the Web? why not have a different protocol for every single website?
@trwnh@mastodon.social Except that you can access every website with any competent web browser and it will broadly work the same across all of them, but if you want to use the YouTube clone with your Mastodon account, you can't, you have to either re-register or look at knock-off YouTube with a Twitter UI, which is just silly.
-
@trwnh@mastodon.social Except that you can access every website with any competent web browser and it will broadly work the same across all of them, but if you want to use the YouTube clone with your Mastodon account, you can't, you have to either re-register or look at knock-off YouTube with a Twitter UI, which is just silly.
@joe you're right, it is silly
i mean it's possible, but it shouldn't be the only way of doing things.
there's a standardized API that lets you hand off your activity to an "outbox" for further delivery... and barely anyone uses it. hence the frustration of this thread. everyone just builds monoliths instead, containing the sum total of an entire mail server and an entire web browser. everyone insists on basically building outlook or thunderbird except without a separate email server involved.