• Max-P@lemmy.max-p.meEnglish
    12·
    1 year ago

    The W3C, apparently. It’s both the ID and the URL of the object if you want to refresh it. They seem to suggest doing it that way because the URL of a user profile is going to be guaranteed to be unique, and can only be owned by the owner of the domain.

    Lemmy assigns it its own internal ID per instance but it’s only used internally for joins and stuff.

    For example, your person ID is https://feddit.cl/u/nintendiator. If you curl it in ActivityPub format you’ll get your user:

    ~ % curl -H "Accept: application/activity+json" https://feddit.cl/u/nintendiator
{
  "@context": [.....]
  "type": "Person",
  "id": "https://feddit.cl/u/nintendiator",
  "preferredUsername": "nintendiator",
  "inbox": "https://feddit.cl/u/nintendiator/inbox",
  "outbox": "https://feddit.cl/u/nintendiator/outbox",
  ......
}
    • nintendiator@feddit.clEnglish
      2·
      1 year ago

      They seem to suggest doing it that way because the URL of a user profile is going to be guaranteed to be unique, and can only be owned by the owner of the domain.

      Immediate design issue right there: the URL of a user profile is not guaranteed to be unique, and while it can “”“only”“” be owned by the owner of the domain, 1.- it’s not owned by the user of the profile and 2.- the ownership by the domain owner is revocable by a third party.

      Design-wise, it feels to me like they decided that land / house deeds could be certified by municipal traffic signage.