Where is the server source code itself?

[MarianoFacundoArch]

Hi,
Where is the server source code itself that this API interacts with?
Thanks.

[abrahamjuliot]

It's private.

[MarianoFacundoArch]

Is there any reason for keeping it private?
What do we don't want to leak to the outside world?

[abrahamjuliot]

The main reason is we don't want this used as a fingerprinting library. The goal is to promote research and education. If sharing the server-side code catches interest, it can be discussed here. But, it's not likely to be presented beyond the process and brief snippets.

[gongchandang49]

@abrahamjuliot Linking with #292 as I think it's related – goals of the project aside, speaking only about handling volume of requests, why not open source the server in a different repo? That way, anyone could host a public backend for this or their own instance, and would help alleviate the costs of this project while maintaining functionality.

On a side note, I don't get the point of gatekeeping stuff "because we don't want to create a fingerprinting library". If you don't want to create it, just don't. Most people won't care either. But is it really worth it to hinder development of this project just because there exists the possibility of someone using it for a different purpose than you initially planned? 🤔 Not too sure about that. Just my two cents.

[abrahamjuliot]

I will give it more thought. Your input is appreciated. Might run some of it via local/session storage and let the developer experiment with it.