Mobile-Detect VS UUID

You can use PHP projects like https://github.com/serbanghita/Mobile-Detect to make checks on your server but it will generate false positives in some cases. I've implemented that in custom widgets to deliver different content. Until know no complaints :-) But it is not implemented in Elementor by default so you'll need PHP knowledge to create a custom widget. Then you can output different posts for different devices. If you can't do that: you have to use the switches

I've been using this: http://mobiledetect.net/

This challenge is commonly tackled with a device detection library on the backend like MobileDetect (this one is in PHP, but ports exist to a variety of backend languages).

If you really can’t make your website responsive, then there’s a great php library here http://mobiledetect.net

I personally use mobiledetect to detect the visitor's device type.

Use composer require mobiledetect/mobiledetectlibto use MobileDetect.

I'd recommend using either Ramsey/uuid or generating a random number using random_bytes(32) then compressing it. 32 bits of randomness should be sufficient for most programs.

Of course, theoretical math and applied math often work out differently. Here's a thread with a guy claiming his team's software is running into "Several hundred [UUID] collisions per day"

Or just use a library.

I'll leave this here https://github.com/ramsey/uuid/issues/80

Not really in the realm of “thousands” of runs, but UUID collisions are possible and have been observed multiple times after only 1 million generations due to unknown reasons.

There's also the risk of bad randomness sources and/or bugs.

One popular UUID library got a bug report stating: "We are generating about 1M UUID4 a day, and we are getting several hundred collisions a day". And so they were; turned out to be a bug/weird interaction between the OpenSSL library they were using for randomness and forking. (Details here, although it was all fixed years ago of course: https://github.com/ramsey/uuid/issues/80)

On paper, you should never, ever, ever see a collision when generating a mere million v4 UUIDs a day, much less hundreds of collisions. But that doesn't mean it can't happen!

This is also an interesting bit of analysis; comes from a company that processed a lot of UUIDs generated in browsers, checked, and discovered about 5 collisions per million UUIDs. Again, not what you'd naively expect! (Turned out to be mostly driven by misbehaving crawlers.) https://medium.com/teads-engineering/generating-uuids-at-sca...

just make sure you have everything configured correctly on your system if using UUIDs:

https://github.com/ramsey/uuid/issues/80

In the types of systems that need UUIDs there is probably no easy way to check for collisions. The prospect of mystery data corruption with no ability to trace it down frightens the hell out of me.

The only reason that issue was reported is because someone was actually doing the collision checking. That's not going to be the norm in UUID systems. Think about it.

In theory the risk of collision is so small it can be written off, but implementations can have bugs.