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.

It is possible to live on that, there are people who live on less than it. Personally all of it went to supplementing my Mom’s income so we could survive.

There are plenty of entry level jobs in India that offer those kinds of wages. There are more that offer less.

Yes, it’s exploitative.

I’m from India so these numbers might be a bit weird. My yearly comp has basically gone like this from 2017 to 2023

$0.7k -> $3.6k -> $4.8k -> $20k

Have you seen all the people just stuffing their profile README full of random graphics and stats and badges

Ohhhh, this site is a great find. Exploring all the articles right now. Thanks!

Unfortunately, no one can be told what a monad is. You have to see it for yourself (then you won’t be able to explain it to anyone)

eBPF is something that I’ve been exploring recently for work. I was quite blown away when I realized the true potential. I did find it difficult to get started, and while this article is a good introduction, some example code or hands on would be nice to have

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.

How often do a few nanoseconds in the inner loop matter?

It doesn’t matter until you need it. And when you need it, it’s the difference between life and death

I’ll be sure to read it when you do :)

OTOH, the more pythonic one will probably perform worse, but I’m not familiar enough with Python internals to make that claim without benchmarks.

I’ll try it out and add the data in the article

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.

Haha this is exactly me. That habit of losing the knowledge rapidly post investigation is something I’m trying to break, and that’s part of the reason I banged out this blog post immediately after my itch was satisfied.

The “I have to tell people about this NOW” vibe also carried me through completing my website (just so I could publish this blog post)

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"
      }
    }
  ]
}

Glad you liked it! Thanks for reading ❤️