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.

The emoji guy is giving Shrek a blowjob

deleted by creator

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”)

The law will then say E2EE is forbidden. And then the next step is making Telegram as a prime example to strip out E2EE because “Look how many bad guys we can catch without E2EE”.

I wish it has more element like CnC Renegade or Battlefield. This is quite an interesting game experiment

I see. I’ve skimmed the docs and indeed see that it supports a lot of IDP with what looks to me some env var. And thanks for answering another question of what their auth library is since that is a lot to support.

Can you give the gist of it?

There aren’t enough swear-words in the English language, so now I’ll have to call you perkeleen vittupää just to express my disgust and frustration with this crap.

Beautiful

Same could be said for any other distro. I think his point is that when shit just works, nothing makes a difference between distro. Be it Arch, Debian, Ubuntu, Mint, Fedora, Gentoo

Maybe depending on how far you take it. A CPU instruction is different from hardware to hardware, but a function signature would stay the same no matter the underlying architecture. If we want to go through that logic then an interpreter can be thought of as a form of emulator.

Yeah, hence is-“number”. But we were talking about regex are we. A number representation can use digits but it can also not. Much like how you make a number using the word “elf”.

Alright, maybe you misunderstood the term digits with numbers. When parsing a digit, you do not attach semantic yet to the building blocks. A \d regex parser does not care that the string “555” is not equivalent to “VVV”. All it cares about is that there is the digit “5” or “V”. In the same vein, regex parser should not try to parse IV as a single symbol.

As I said, a digit is a symbol. Much like how we use letters to compose words, digits are used to construct numbers. When you start to repeat or reuse the symbol then it is no longer a singular symbol (what regex \d does). Hence my comments on why arabic script are one of the understandable debates since i18n is a valid concern as much as a11y is.

Yeah, but “elf” are not digits. Digits are a symbol abstracted from the language itself. Does 5 and V convey different meanings in the context of digits? And yeah, I can see why they would argue about the implementation because inclusivity is important. Especially when designing a language implementation. If you are designing it wrong, it will be very hard to extend it in the future. But for application level implementation, go nuts.

So the only valid digits are arabic numbers but arabic script numbers are not a valid digit? If we want programming to be inclusive then doesn’t that make sense to also include the arabic script number?

Hey, don’t kinkshame man. Just look at those stupid sexy v-bind

Dude, his point is that if you did not implement partial rendering on a big file, the browser will have to work extra hard to render that shit. Not to mention if you add any interactivity on the client side like variable highlighting that needs to be context aware for each language… that basically turns your browser into VSCode, at that point just launch the browser based vscode using the . shortcut.

It’s not a matter of the server side of things but rather on the client side of things.