Not sure but that sounds like you have a problem with your Git installation (or a dependency of Git). Maybe a reinstallation can solve that.

If you are thinking about transitioning an organization to open source, pricing and vendor lock-in are generally good arguments.

If you are thinking about helping individuals transition, that's a bit more difficult. Pricing could still work, but is not always that effective. It boils down to the willingness to try something new.

In both cases projects with good documentation and a healthy community also helps, but if the open alternative lacks features, it's a though sell.

Mine happened when I watched Paolo Perrota's Git courses on Pluralsight. That's when it clicked for me.

https://www.docs.bsky.app/blog/feature-bridgyfed

I think single account ActivityPub implementations are addressing a weakness of the Fediverse: one's identity (handle, username) is tied to an instance they have no control over. If that instance shuts down users lose everything. With a single account instance, you take that control back. And since it doesn't need to scale the architecture can be much simpler and can be deployed to much cheaper infrastructure.

The demo was not straightforward, though. And I didn't quite get how a user can follow Mastodon users, for example.

I wasn't aware of that. I guess it was thought to be a mod driven community. Anyway... Cool question. I hope we will see some creative solutions here.

Please also consider posting to !challenges@programming.dev

The longest I worked for a company is around 6-7 years.

As long as you get the opportunities to develop your skills in the areas you want (so that they are still relevant in the job market) and there is a good team around you, it doesn't make sense to change jobs just to change jobs. It's generally difficult to get a meaningful salary increase without a job change and that's the main reason most people are looking for new jobs, I think.

This sounds more like a Github question.

Apart from the historical value, the most important part of this article now is the "Note of reflection" added 10 years after it's inception:

If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.

I don't think this work flow is relevant any more even for teams that don't do CD, to be honest. It was a messy work flow to begin with and I haven't seen it applied successfully in practice.

As far as I know, the correct way of handling authentication for a desktop applications is using OAuth and "Authentication Code with PKCE" flow. This way, you won't have to store the password at all.

But Lemmy doesn't support OAuth as of now. So, if you want users to be able to use the application without entering credentials, you will have two options:

1. Store the password under current user
2. Store the token you receive after the login (the token doesn't expire)

Lemmy may decide to expire tokens in the future (that's the correct thing to do, in my opinion).

I would add Ars Technica to that list and call it a day.

For programming I follow YouTube channels of the conferences relevant for my tech stack (YouTube natively supports RSS). They are generally 1 hour talks but it's a great way to stay up to date.