Skip to content

Rewrite of the code#72

Open
neiltalap wants to merge 9 commits intomainfrom
rewrite
Open

Rewrite of the code#72
neiltalap wants to merge 9 commits intomainfrom
rewrite

Conversation

@neiltalap
Copy link
Copy Markdown
Member

As mentioned before it's a one pile of shit. I will slowly rewrite the codebase into what we need to have.

glenv1ew
glenv1ew previously approved these changes Apr 2, 2026
Copy link
Copy Markdown
Collaborator

@glenv1ew glenv1ew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@daniliuskosmaches daniliuskosmaches left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, why did we renamed our project from CLoaq to Synnapse?

@neiltalap
Copy link
Copy Markdown
Member Author

okay, why did we renamed our project from CLoaq to Synnapse?

Wasn't marketable or sellable. Simple as that. And you can't exactly sell some questionable anonymity tool to people, it doesn't solve too many problems.

Instead we will focus on "Pod to pod communication between clusters and endpoints without network boundaries. " It is for kubernetes, but it is much more sensible for me, and you long term.

The LICENSE has changed to agplv3 too.

I am sorry for these sudden movements, but it is what it is.

@daniliuskosmaches
Copy link
Copy Markdown
Contributor

daniliuskosmaches commented Apr 2, 2026

okay, why did we renamed our project from CLoaq to Synnapse?

Wasn't marketable or sellable. Simple as that. And you can't exactly sell some questionable anonymity tool to people, it doesn't solve too many problems.

Instead we will focus on "Pod to pod communication between clusters and endpoints without network boundaries. " It is for kubernetes, but it is much more sensible for me, and you long term.

The LICENSE has changed to agplv3 too.

I am sorry for these sudden movements, but it is what it is.

No problem dude, we can continue to work if you want you can make another repo for pod to pod communication and at least me can continue to contrubution for the projects, because maybe in the future our old idea will be very good for the future problem

@neiltalap
Copy link
Copy Markdown
Member Author

neiltalap commented Apr 2, 2026

okay, why did we renamed our project from CLoaq to Synnapse?

Wasn't marketable or sellable. Simple as that. And you can't exactly sell some questionable anonymity tool to people, it doesn't solve too many problems.
Instead we will focus on "Pod to pod communication between clusters and endpoints without network boundaries. " It is for kubernetes, but it is much more sensible for me, and you long term.
The LICENSE has changed to agplv3 too.
I am sorry for these sudden movements, but it is what it is.

No problem dude, we can continue to work if you want you can make another repo for pod to pod communication and at least me can continue to contrubution for the projects, because maybe in the future our old idea will be very good for the future problem

Bruv, it's not good for my reputation or business to do that kind of thing. I got you, I give you full permission to fork it into its own thing, but being practical is above that for me here. It is hard for me to mentally and philosophically decide to work on Cloaq at all, and what we have with Synapse here is what aligns with me.

Because we/I can monetize it eventually and it falls into an area of my expertise, I am an infra engineer.

But if you want to keep on going with Cloaq, you can fork the specific commit point you need, and then I will grant you full ownership of the code.

It sounds nice in theory, but bruv, world doesn't operate on kind wishes. If you have no plans to monetize, what will happen is that you will not be able to do so.

I initially started this as a fun project, then with time I started to have serious plans around this. But what I came to realize along the way is that this simply doesn't work for me, that's the conclusion that I have come to.

@neiltalap
Copy link
Copy Markdown
Member Author

okay, why did we renamed our project from CLoaq to Synnapse?

Wasn't marketable or sellable. Simple as that. And you can't exactly sell some questionable anonymity tool to people, it doesn't solve too many problems.
Instead we will focus on "Pod to pod communication between clusters and endpoints without network boundaries. " It is for kubernetes, but it is much more sensible for me, and you long term.
The LICENSE has changed to agplv3 too.
I am sorry for these sudden movements, but it is what it is.

No problem dude, we can continue to work if you want you can make another repo for pod to pod communication and at least me can continue to contrubution for the projects, because maybe in the future our old idea will be very good for the future problem

@glenv1ew @m3nt0l-dta if you are willing can you give Gaukhar a task? Or @daniliuskosmaches you can give her a task too, something easy. Just give her one, don't give her many.

@daniliuskosmaches
Copy link
Copy Markdown
Contributor

okay, why did we renamed our project from CLoaq to Synnapse?

Wasn't marketable or sellable. Simple as that. And you can't exactly sell some questionable anonymity tool to people, it doesn't solve too many problems.
Instead we will focus on "Pod to pod communication between clusters and endpoints without network boundaries. " It is for kubernetes, but it is much more sensible for me, and you long term.
The LICENSE has changed to agplv3 too.
I am sorry for these sudden movements, but it is what it is.

No problem dude, we can continue to work if you want you can make another repo for pod to pod communication and at least me can continue to contrubution for the projects, because maybe in the future our old idea will be very good for the future problem

Bruv, it's not good for my reputation or business to do that kind of thing. I got you, I give you full permission to fork it into its own thing, but being practical is above that for me here. It is hard for me to mentally and philosophically decide to work on Cloaq at all, and what we have with Synapse here is what aligns with me.

Because we/I can monetize it eventually and it falls into an area of my expertise, I am an infra engineer.

But if you want to keep on going with Cloaq, you can fork the specific commit point you need, and then I will grant you full ownership of the code.

It sounds nice in theory, but bruv, world doesn't operate on kind wishes. If you have no plans to monetize, what will happen is that you will not be able to do so.

I initially started this as a fun project, then with time I started to have serious plans around this. But what I came to realize along the way is that this simply doesn't work for me, that's the conclusion that I have come to.

Okay, I got you man

@daniliuskosmaches
Copy link
Copy Markdown
Contributor

okay, why did we renamed our project from CLoaq to Synnapse?

Wasn't marketable or sellable. Simple as that. And you can't exactly sell some questionable anonymity tool to people, it doesn't solve too many problems.
Instead we will focus on "Pod to pod communication between clusters and endpoints without network boundaries. " It is for kubernetes, but it is much more sensible for me, and you long term.
The LICENSE has changed to agplv3 too.
I am sorry for these sudden movements, but it is what it is.

No problem dude, we can continue to work if you want you can make another repo for pod to pod communication and at least me can continue to contrubution for the projects, because maybe in the future our old idea will be very good for the future problem

@glenv1ew @m3nt0l-dta if you are willing can you give Gaukhar a task? Or @daniliuskosmaches you can give her a task too, something easy. Just give her one, don't give her many.

Nah, I dont think that she will do it, Im very sure she will use chagpt without any ideas what will happen, BTW the project is going to be restructured and the old forks will be no good and im also can not fully review the code on golang

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants