fingerprintjs VS sourcegraph

It may not be common, but I did find these (fairly popular projects) which don't appear to allow production usage:

https://github.com/fingerprintjs/fingerprintjs

For this test, I used a variety of device ID and fingerprinting apps, but it turned out that using only one was sufficient. The results you can see in the table below are from Fingerprint OSS Demo app - the same company made this that's behind the powerful https://fingerprint.com. Instead of posting the actual ID values, I replaced them with single-letter representations. All profiles are exactly identical aside from what is in the Setup column.

They already somewhat have.

View the demo in normal mode at https://fingerprint.com/ and then open it again in Incognito

Probably through fingerprinting. There was a post here about https://fingerprint.com/ not too long ago. Go there and press the "View Live demo" button. Now do the same thing in a private browsing window. There's a good chance it'll still know it's you. The best thing you can do is to set the resistfingerpinting option, as mentioned by others, but still this doesn't work 100% of the time.

I am not sure about the state of Goanna's randomization tech, but I know that they don't implement spoofing / randomization for a number of variables that are used by fingerprinters, like hardware concurrency. For example, Firefox's impl includes the following code:

https://fingerprint.com/

I also tried setting privacy.resistFingerprinting = true in Firefox, but it's sad to see that most websites become unusable (most sites using canvas just render a green/purple mess), zooming in Google Maps is basically broken (skips several levels at a time), and like others have mentioned dark mode and time zones also stop working.

What a mess the (somewhat private) web is nowadays. The more I think about it, the more I am convinced legislating privacy is the only way out of this arms race we seem to be losing.

Sourcegraph | REMOTE | Full-Time | Machine Learning Engineer, Developer Advocate, Enterprise Product Manager, Technical Advisor | https://sourcegraph.com

Sourcegraph is a code AI platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

That's pretty much what https://sourcegraph.com/ are selling, is it not?

- https://sourcegraph.com is pivoting and building a copilot application (named Cody). This is pretty good, since sourcegraph is great at understanding your code

While a readable Dockerfile can work as documentation, there are a few caveats:

* the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image.

* I still need a way to notify me of updates; if the Dockerfile just wgets a binary, this doesn't help me.

* The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)

We use Sourcegraph, which is a tool that searches through code in repositories. We leverage this tool in order to understand the adoption curve of our components across all of Reddit. We have a dashboard for each of the platforms to compare the inclusion of RPL components over legacy components. These insights are helpful for us to make informed decisions on how we continue to drive RPL adoption. We love seeing the green line go up and the red line go down!

SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a...

https://github.com/sourcegraph/sourcegraph/commit/3cd931ef54... has some additional information, but not a lot.

https://github.com/sourcegraph/sourcegraph/issues/53528#issu... appears to be a comment from someone in the project laying out why they've changed.

As a general rule with open source projects it basically depends on whether they had a contributor licence agreement.

Sourcegraph appear to have had one:

https://github.com/sourcegraph/sourcegraph/blob/main/CONTRIB...

So presumably they nailed this down.

Exactly my thoughts. I am using the Homebrew version of Sourcegraph, which I presume to be quite dead [1]. I do this because there was no packaged version of the Sourcegraph OSS. I would happily use the OSS version instead otherwise.

[1]: https://github.com/sourcegraph/sourcegraph/discussions/54589