Hashids.net VS DevToPosts

If you're just doing this to avoid Insecure Direct Object Reference (IDOR) problems, then perhaps something like Hashids might be a better choice?

I'm gonna be using this Library https://github.com/ullmark/hashids.net to encode the BIGINT into a string and decode the string back into the BIGINT within my web application.

If you can use a string, then Markus Ullmark's hashids.net library would be a good place to start.

You could use this approach along with this package https://github.com/ullmark/hashids.net

Hashids helps you to convert a number Id to a string, this can make your app a little more secure hiding the actual id or related key of your DB when the data is requested by an API.

Guids are nice, but there’s the option of hashids too. While it’s not advertised as a security mechanism, it does mask the integer and make things harder to guess

Another way to solve enumeration attacks is to use a two-way hashing algorithm to convert your auto-incrementing integer IDs to a hash of arbitrary length. This is essentially what YouTube is doing with their video IDs and it's a low-CPU, low-complexity solution that prevents/severely deters enumeration attacks.

Here is one such library for C# https://github.com/ullmark/hashids.net

ullmark/hashids.net: A small .NET package to generate YouTube-like hashes from one or many numbers. (github.com)

Nota 💡: Como costumbre, el código fuente: DevToPosts/AspireDashboard/OpenTelemetryExample · isaacOjeda/DevToPosts (github.com)