soul VS Nest

Mastodon was a platform that came to mind where each instance is run individually by a person or an organization and each instance gets to decide how they want to moderate it.

Although users get to choose which instance to join depending on their tastes, they have to sign up for a new account each time on each instance and potentially lose their followers if their account get’s banned in any of these instances.

So I’ve decided to build Soul, which is an external OAuth-based identity provider built specifically for social media in mind. It comes with several user management and user connections management features that can allow one’s “digital soul” to exist in various platforms as long as they integrate with Soul.

Soul is still in a really early stage of development but it is open source and constantly looking for new opportunities to improve. Please give it a shot and try building a social media platform on top of Soul to tap on it’s existing users (though not a lot at the moment, but I hope it’ll grow)."

Check out our site here: https://www.soul-network.com/ and main Github repo here: https://github.com/soul-project/soul

"With Elon Musk’s takeover of Twitter, I began to question if transferring ownership of a centralized platform to another is really the solution to true freedom of speech.

Mastodon was a platform that came to mind where each instance is run individually by a person or an organization and each instance gets to decide how they want to moderate it.

Although users get to choose which instance to join depending on their tastes, they have to sign up for a new account each time on each instance and potentially lose their followers if their account get’s banned in any of these instances.

So I’ve decided to build *Soul*, which is an external OAuth-based identity provider built specifically for social media in mind. It comes with several user management and user connections management features that can allow one’s “digital soul” to exist in various platforms as long as they integrate with Soul.

Soul is still in a really early stage of development but it is open source and constantly looking for new opportunities to improve. Please give it a shot and try building a social media platform on top of Soul to tap on it’s existing users (though not a lot at the moment, but I hope it’ll grow)."

Check out our site here: https://www.soul-network.com/ and main Github repo here: https://github.com/soul-project/soul

Want to add the authenticator to your social media, just integrate your platform with soul. Here is my Github: https://github.com/soul-project/soul

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/