• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle











  • Yeah, I wasn’t arguing, just thinking out loud too. I think the whole decentralised aspect of the fediverse means that ownership has to have a cryptographic answer because there’s no central source of truth that everyone can agree on.

    I think moving accounts is a little easier than you think, apart from who gets to say that something should move. It’d be better to have a “pull” than something like the “push” solution that currently exists on Mastodon - there you can forward an account to a new place, as long as the old instance exists and cooperates (big ifs).

    I’m mostly thinking about moving accounts (+ communities) in the case of when an instance suddenly vanishes.


  • Posts and comments have a canonical URL (i.e. the original submission’s URL that’s linked to via the Fediverse pentagram), so that can be used as a foreign key when comparing.

    I think identify claiming would need to have been designed into the original spec with something like a public/private key for account ownership to allow moving of related data in a safe way, or e.g. editing a post from a different instance than originally posted it.



  • The line breaks haven’t worked, here’s it formatted correctly:

    Explanation: it’s mostly due to how js does type conversion.

    For the Ls, it’s:

    • [] is an empty array
    • ![] is treated as false
    • combining a boolean with the empty array returns “false” as a string (so true + [] = “true”, false + [] = “false”)
    • ! + [] is treated as true
    • ! + [] + ! + [] is treated as 2 since true + true = 1 + 1 = 2
    • so you have “false”[2], which is l

    for the o it’s:

    • [] is an empty array
    • [] + {} returns “[object Object]” as a string ({} + [] returns 0)
    • ![] is false
    • !![] is true
    • +!![] casts it to an integer
    • so that part is “[object Object]”[1], which returns “o”-