Hello All! I am working on a test server at the moment, and I am working towards a safer app. It was suggested to me by a robot (not lary ;-) ) that gates, validation rules, and assuring certain actions (edit or delete) are gates based on permissions - is a good approach but could be stronger. two points are: my ids are guessable , and, internal ID references - if exposed, easier for malicious actors. So when editing a user, or an industry, the id is guessable and therefore a weak spot. So, a couple of options exist for me, one would be encrypting IDs, and the other is to add a policy which I mostly understand. more suggestions include Encryption at Rest, which is new to me. I did some quick research and saw that the encrypted IDs take up more space, and that led me to wonder about uuids (which are not as guessable and also take up space). so this long winded question comes round to the point: if you were setting up a new system, and you could start from scratch, would you go with UUIDs, or sequential numbers and try to encrypt them? Or another solution altogether when it comes to IDs in livewire?

Cool!

Solving a "it works on my machine" problem: unknown unknown -> known unknown -> known known -> solution!