𝙲𝚑𝚊𝚒𝚛𝚖𝚊𝚗 𝙼𝚎𝚘𝚠

  • 0 Posts
  • 165 Comments
Joined 11 months ago
cake
Cake day: August 16th, 2023

help-circle
  • 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?















  • Aaand here’s your misunderstanding.

    All messages detected by whatever algorithm/AI the provider implemented are sent to the authorities. The proposal specifically says that even if there is some doubt, the messages should be sent. Family photo or CSAM? Send it. Is it a raunchy text to a partner or might one of them be underage? Not 100% sure? Send it. The proposal is very explicit in this.

    Providers are additionally required to review a susbet of the messages sent over, for tweaking w.r.t. false positives. They do not do a manual review as an additional check before the messages are sent to the authorities.

    If I send a letter to someone, the law forbids anyone from opening the letter if they’re not the intended recipient. E2E encryption ensures the same for digital communication. It’s why I know that Zuckerberg can’t read my messages, and neither can the people from Signal (metadata analysis is a different thing of course). But with this chat control proposal, suddenly they, as well as the authorities, would be able to read a part of the messages. This is why it’s an unacceptable breach of privacy.

    Thankfully this nonsensical proposal didn’t get a majority.






  • Have you never worked on a large distributed system before? There are good reasons not to use integer ids:

    • Generating ids on multiple machines is a hassle and requires careful configuration, which is not necessary when using uuid/cuid2 or something.
    • Ids have to be generated by the database, which is a huge degradation of overall system performance. If the application can generate the id, then the database insert is not a blocking operation anymore and you can just continue.
    • The performance difference is highly negligible, as it’s massively outweighed by fetching rows for example. With a proper database design, the difference is anywhere between 1-5%. If that makes the difference for your application, you’ve already made poor design decisions elsewhere that are far more important.

    We use prefixed incrementing base63 uuids. It’s highly performant and we can generate it in the application, saving a lot of time in many processes because we don’t have to wait for the database anymore.

    I’m sure doing int indexes over strings was once considered the gold standard but that’s not been true for years now. Yes, it’s slightly better for database performance. No, it’s not better overall for a slew of reasons, including system performance.