• 1 Post
  • 751 Comments
Joined 4 months ago
cake
Cake day: March 3rd, 2024

help-circle
  • That’s not how that works.

    NFT is issued determining ownership to a property. Property sells, another NFT is issued, tied to the original one to maintain a chain of ownership. Issuance of a second NFT for a sale to a new owner would depend on authorization by the previous NFT holder. Lienholder information could also be stored, and linked to a mortgage NFT with payment history.

    The “NF” part of that stands for “non-fungible.” As in, once created, cannot be changed.


  • One of the things blockchain could do is become a digital proof of ownership, augmenting or replacing things like property deeds and car titles. We already agree that a written record of ownership of such things is legally binding (even if the writing is stored digitally), but transfer of that ownership to another person is still a very manual process. Imagine an NFT that represents ownership of your house, and when you want to sell your house, you transfer that NFT to someone else’s custody - adding their ownership information to it. It would record the entire chain of ownership, and specific details about the piece of property involved.






  • Let me see what I can do.

    A “debtor” is a company or person who owes money. I would assume that by “corporation,” they mean “the ‘corporation’ which is both you and not you.” So let’s call that “Someone who owes money.”

    A “creditor” is a company or person to whom money is owed.

    I believe that “individual agent” is referring back to the “person,” while the “straw man” is the imaginary magical –

    You know, fuck it, I can’t even.



  • For the passers-by, in very simple terms:

    A switch maintains a list of the IPs and MAC addresses of devices attached to it (ARP [Address Resolution Protocol] table). When a packet comes into the switch for a specific destination IP, the switch looks up on the ARP table where that destination IP can be found, and only sends the packet out on the port the destination device (or next hop towards that device) is connected to.

    A hub doesn’t do any of that. Every packet that comes into the hub gets sent out of every port on the hub, to every device connected to the hub. It’s on the connected devices’ to discard packets that aren’t addressed to them. On anything but a very small and relatively slow network, this would create an unnecessarily large amount of traffic, not to mention the security issue around sending packets to devices they’re not addressed to.











  • Nougat@fedia.iotoLinux@lemmy.mlWhy do you still hate Windows?
    link
    fedilink
    arrow-up
    3
    arrow-down
    3
    ·
    4 days ago

    The PIN is stored locally on the machine only. It doesn’t get synced with anything anywhere. It’s actually much safer to use a PIN for authentication because it’s four digits that you (well, maybe not you) don’t have to write down, and the only time it works is on the physical machine. The user account password can be long and/or complex, but if you’re only ever authenticating at the keyboard, all you have to remember is the PIN.