Self taught developer

Previously known as @yourstruly@dataterm.digital

Come hang out with me on Mastodon

Check out my blog, where I write about what I have learned

  • 11 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle







  • I agree that from a completeness point of view, the official manual is better (I’ve linked it at the bottom of my post as well), however I’d love to hear your specific thoughts about why you feel this particular article is not good- I’ve tried to include fully interactive examples for the most common tasks I find myself doing with jq everyday. This feedback will help me improve my own skills as well, so I would appreciate it very much.









  • The scenario is not ficticious. It’s taken straight from my first job, but I had to leave out specific details. The application being developed had something to do with DRM, so that might explain the weird requirements.

    The lesson is that sometimes business will require you to force users to update their version, and/or enable specific features for specific subsets of users. So you should have such a mechanism in place before it is required, otherwise you will end up doing hacky things like breaking the server to do what needs to be done.

    Systems such as these are actually fairly common in enterprise, but since it was my first job, I had not planned ahead for this because I had no idea.













  • You are right that it does feel a little roundabout. My understanding is that webfinger converts from the username to the user profile url and image. This is useful during federation, and for generic fedi/activitypub clients because different Fedi software maps usernames and profiles differently.

    For example, user@lemmy.instance will reside at lemmy.instance/u/user, while user @mastodon.instance will reside at mastodon.instance/user.

    Fom some poking around, it seems that Lemmy does not properly support sending the profile image on Webfinger because I wasn’t able to do it using the rel parameters that are mentioned in the spec.



  • Hey Thanks for reading, and I’m glad you found it interesting.

    To my understanding, Webfinger provides a standard API for discovering the user profile details no matter the software running on the node.

    For example,

    $ curl https://programming.dev/.well-known/webfinger\?resource\=acct:snowe@programming.dev | jq
    {
      "subject": "acct:snowe@programming.dev",
      "links": [
        {
          "rel": "http://webfinger.net/rel/profile-page",
          "type": "text/html",
          "href": "https://programming.dev/u/snowe"
        },
        {
          "rel": "self",
          "type": "application/activity+json",
          "href": "https://programming.dev/u/snowe",
          "properties": {
            "https://www.w3.org/ns/activitystreams#type": "Person"
          }
        }
      ]
    }