Nothing comes to mind. DRM literally means digital rights management and unless you wanted to be petty, like blocking a certain person from using your app, then DRM for something free is not something that I can think of a use case for.
Nothing comes to mind. DRM literally means digital rights management and unless you wanted to be petty, like blocking a certain person from using your app, then DRM for something free is not something that I can think of a use case for.
Enforcing payment comes to mind without resorting to in-app purchase or any account creation. A lot of desktop software is a good example of those. Sure, you can still have cracks and whatnot, but then again, that’s not the point. Might as well ask what is the point of Denuvo. That is a whole other discussion.
Yes, that’s my point. Android “doesn’t” have to use Google Play Store, but it is convenient. Other store fronts exist like F-droid and many vendor specific one. Google just provide the DRM mechanism like steam does provide DRM via steamworks
What I mean by that is, this is just an API/SDK for app developers to use. Google does not enforce the use of such things. Much like steam does not force the use of their drm for example (please note the difference between the marketplace and the drm). App developers can always choose how they make and distribute their app.
Ehh, this is basically just another form of DRM. No different than you having a Steam and GOG model. You can make your apps using DRM and enforce certain constraints
ROG Ally
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.
I wanted OpenSAGE to mature more quickly so modders of CnC can have a field day with it. This looks like a nice in-between for me
I never understood this argument. Why does having common first letter bad? If you mean subjectively then sure, it may not be for everyone, but objectively?
Then Promise.all is for you!
Eh, we can argue about language all we want but at the end of the day if it is still the same code just with a different branding, someone will be bound to automate the process eventually. It’s FOSS, if someone is willing to put in the works to enable people who think the brand name is a hindrance for their change then more power for them no? We even change master/slave terminology in CS and many other field for the same reason (linguistic)
Yeah, a fair point
To be fair, if the fork sole purpose is to just re-label the software and make people that have irks because of the name start to use the software, who are we to judge?
Just as a heads up, sometimes the pattern is not that easy for computer to brute force. As an example, my old password contains a birth date but with an alternating shift making them a combination of digit and symbol.
You jest but it can happen when what the docs says doesn’t reflect the implementation. And also, that’s what we call bugs.