My First Blog #Blog1

 Here I begin this new journey! ✌

So I will be posting blogs every week. The topics will be regarding Latest Technologies like Machine Learning, Software Development, Data Science, etc. I am writing this blog so that I can track my progress and keep myself updated regularly. Also if someone reads my blog and finds it helpful will be another achievement for me. 

I will be posting a blog once a week on Monday. Before that, I will research different news, blogs, videos, etc., and will try to combine them in one place. So that anyone including me would find it useful and inspiring as well. My main motive through these blogs is to help me stay focused and consistent in my work life. 

I will also be posting my projects and will share my work life and what I learned from that project and what more improvements could have been done to make the project more interesting and helpful to the community. 

With that note, Let's begin today's blog.

Let's talk about GitHub

Token authentication requirements for Git operations

In July, GitHub announced its intent to require the use of token-based authentication for all authenticated Git operations. From Aug 13, 2021, they will no longer accept account passwords when authenticating Git operations on GitHub.com.

After seeing this, I stopped using a normal HTTP clone in the git terminal, and I switched to SSH keys with GitHub, where I don't require any password in the terminal to push my work on GitHub. 

Now the question arises of how the Workflow will get affected?

• First will affect the command line Git Access.
• Desktop applications that use Git.
• Any apps that have access Git repo on GitHub.com directly using your GitHub password.

But the following users remain unaffected by this change:

• Users who have two-factor authentication enabled in their account, are already required to use token- or SSH-based authentication (I had it from the beginning).
• If the user has GitHub Enterprise Server, no such announcement has been made to their on-premises offering changes.
• If the user maintains a GitHub App. Then for your kind information, GitHub apps do not support any password authentication.  

So, What to do next?

• If you are using a password to authenticate Git operations with Github, you must switch using a personal access token over HTTPS(I would recommend this) or SSH key by August 13, 2021, to avoid any disruption.
• For integrators, the user must authenticate integrations using the web or device authorization flows by August 13, 2021, to avoid any disruption. For more info, see Authorizing OAuth Apps and the announcement on the developer blog in Github.

Why am I posting it?

Few days before I received a mail regarding this update from GitHub, there I came to know about it and thought to share it with you guys. So, if you are a GitHub user, you must have received an email from GitHub. I would recommend you guys to take your actions as soon as possible.  

What about React JS 18...

What's up with React 🙅

The React team is working on the React 18 release, which will be their next major version.

They have already published a React 18 alpha so that library authors can try it and provide feedback.

Basically, the goal of the React 18 Working Group is to prepare the ecosystem for a smooth, gradual adoption of React 18 by existing applications and libraries. The main working group is hosted on GitHub Discussions and is available for the public to read. 

That's it for today, will post next week again with some amazing topics, and projects