I get your concern about this meme being racist, but not everything is about race. The stock photo of two adults passing a baby and the picture from a cartoon depicting a woman throwing a baby just so happened to be of different races. IMO that’s not racist.
Please stop. It’s not intentional. Stop basing your judgment on people and actions with an acute view of their skin color. Just see two sets of people. Thanks.
In a world where there is racism, acting like racist themes don’t exist only helps prolong it.
One set of of people here was drawn white (and responsible with a child), the other was drawn black (and irresponsible). That’s worth critiquing, intentional or not.
Acting racist doesn’t mean you are literally Satan, it means you are acting racist. Not stopping after people point it out and acting defensive and in denial is worse than thoughtlessly doing something racist, being told off and then correcting
Would you feel better about this if it was a stock photo of a white woman yeeting their baby rather than using a comic? A comic that the meme maker didn’t create? Should the meme maker recolor the baby and woman white to make things better for you? This isn’t racist because one of the meme images happens to be of black people.
What do you mean interception is at a different layer? You can capture at any layer as long as the payload isn't encrypted, and if it is, you still get layers 1 through 4 (Physical, Link, Network, and Transport).
actually, do yeet the baby if you have an application with different needs. for example, if you want to play a game, you’re better off yeeting 60 babies a second and just hope that whoever is on the side catches enough of them to get a smooth stream of babies, than making sure every baby is handed gently to the next person and get the whole line clogged up the moment anything disrupts it. if you just use the yeetomatic 3000 you’re always getting fresh babies on the other end, a few might just be dropped in the process
No, instead of using TLS for encryption (like most TCP traffic) UDP will use things like DTLS and SIP
Or if you’re asking about the actual transport it’s more like TCP is going to your friend’s house and calling your mom to let her know you’re there vs UDP is going to their house and not calling.
No no, it's not "broadcasted". It still has a fixed sender and receiver IP address, but UDP doesn't verify whether the receiver got the data or not. You can implement that over UDP, but you have to do it yourself.
With TCP, the packet will retransmitted automatically if the receiver didn't tell the sender "yep, I got it".
You'd have to be somewhere in the route from A to B to intercept it. But TCP is no different in that regard.
TCP is connection based so both sides need to agree to connect before data is exchanged. UDP is connectionless, so it will send data from A to B (and vice versa) regardless of if the other side is available.
The benefit is that you don’t need to wait for verification from the user that they got the packet before you can send the next group of packets. If you’re, say, watching a stream, it’s not important that you received the packets because that’s just a few skipped frames or a second of lag, whereas the tradeoff on overhead is pretty big.
TCP is more important with like file downloads where it’s okay if it takes a couple hours to get a really big file as long as that file isn’t corrupted or missing any data.
Nah, tcp still yeats the baby, it just verifies that it was caught unbruised, or at all. If it wasn’t that’s ok. Try again. Yeet the baby’s little sister
Add comment