What happens if a mistake was made and an NFT is erroneously issued (for example to the wrong person)?

What happens if the owner dies? How is the NFT transferred then?

Who checks that the original NFT was issued correctly?

What about properties that are split? What happens if the split isn't represented in the NFT correctly (e.g. due to an error)?

The whole non-fungible part can be a problem, not a solution. It very, very rarely happens that ownership of a property is contested. It happens quite often that a mistake is made during a property transfer/sale that needs to be corrected. How do NFTs deal with this, and are they a solution to a non-issue?

People seem to be downvoting you but you're absolutely right. Languages are dynamic and evolve all the time. The language "rules" are merely descriptive; they explain how most people use the language, and if you want to make sure everyone can understand you it's best to follow them.

Even then there's some wiggle-room. Take the gif/jif pronunciation debate, it was coined as "jif" but the majority of people switched to "gif". So (depending on the dictionary you own) it will often either list just "gif" as correct, or list both as equally valid pronunciations (which given the sizeable minority for "jif" seems like the correct approach imo). All the gift/giraffe/creator-says-x is just fluff and noy actually all that relevant.

The PR had some issues regarding files that were pushed that shouldn't have been, adding refactors that should have been in separate PRs, etc...

Though the main reason is that Signal doesn't consider this issue a part of their threat model.

The Right Honourable Member of Parliament Sir Keir Rodney Starmer, Knight of the Most Honourable Order of the Bath, King's Council to His Royal Majesty Charles the Third, by the Grace of God of the United Kingdom of Great Britain and Northern Ireland and of His other Realms and Territories, King, Head of the Commonwealth, Defender of the Faith, Lord of Mann, Prime Minister of the United Kingdom of Great Britain and Northern Ireland.

Anything less is offensive and requires a licence.

It's Base62 actually, misremembered that. It's to avoid some special characters iirc. And no, performance is fine.

We're using this: https://github.com/TheArchitectDev/Architect.Identities

It's gonna make fiat obsolete. Any day now!

Glad to see things will improve in the US!

Dude, he's literally got a mushroom head. He is the fat knob.

https://github.com/TheArchitectDev/Architect.Identities

Here's the package one of our former developers created. It has some advantages and some drawbacks, but overall it's been quite a treat to work with!

Bless you.

At the company I work at we use UUIDv7 but base63 encoded I believe. This gives you fairly short ids (16 chars iirc, it includes lowercase letters) that are also sortable.

Hitler was too big of a pussy unfortunately.