Well, ease of use I suppose. Just look at us capable of using basically anything as an energy source. Imagine a machine that is not finicky on how they got their energy. The problem for any such machine will always be efficiency. You cannot do more work than the energy that you put in a system. Such machines will need a stomach that is capable of processing "food" at the same/greater speed that it is spending its energy. Not to mention we usually use machine for heavy, energy intensive task, so I doubt such stomach will be useful for any meaningful machine.
bitfucker
joined 8 months ago
I think the commenter mean using artificial stomach for machinery to convert food into energy that the machine can use
Hmmm, yeah it gets harder to associate it with physical reality when user generated content is introduced. Maybe an archival of said content is mandated but then again, who is going to serve the archive. In the case of youtube, it would be almost impossible
Huh, the difference is that a website is not akin to a public park but privately owned park with or without entrance fee. The owner is nice enough to open the park and let you do whatever you want for free with the cleaning and maintenance is paid by the owner, but when the park is closed, would you still say the owner should still be forced to maintain it?
The transport is usually TCP/IP tho. But nowadays QUIC is trying to make it UDP. HTTP is specifically an Application Layer Protocol from OSI model
The thing is, it does exists a way to convert grpc protobuf to json one
It usually goes down like this on some security heavy system: It does not know that a queue is missing. It does however know that it cannot access that queue. When an error is thrown on a secure system, usually the first thing to check is the privilege. If the queue does not exist, so does the privilege to access said queue hence the first error being thrown.
Hoo boy, can't wait until someone brings a bag of flour to the plane as a threat
The emoji guy is giving Shrek a blowjob
Yeah, but as you said, it is highly dependent on the implementation. Theoretically it is possible that the user is also seeding the previously downloaded/streamed chunk (via WebRTC for example if using a browser). That reminds me of a madlad that stores data on a ping packet (see suckerpinch channel on youtube, specifically his video titled "Harder Drive")
Well, remember the news when one of those fucker even continue the procedure despite the patient SCREAMING in pain and he just doesn't care?