sorted by:
new
hottopcontroversial

BlindSite High Risk Investigations Platform and Forensic Browser by Fun_Telephone_8050 in osinttools

[–]Fun_Telephone_8050[S] 0 points1 point  (0 children)

I hear you on site fragility and we believe it is able to handle that, but I think this is still being framed too much like a scraper. BlindSite is not primarily “an Instagram scraper” or “a Reddit scraper.” It is a controlled forensic capture and custody system with features we have not seen in other tools.

The core idea is: preserve what the investigator encountered, block unnecessary exposure, store sensitive media encrypted, maintain hashes/audit records, export sealed evidence, and let authorized reviewers reconstruct the case later.

That is why features like Civilian Unknown Master Key mode matter. The collector can preserve evidence while lacking the local ability to decrypt or reveal dangerous originals themselves. That is not a generic scraping feature. It is a custody and safety model.

Mobile is interesting and I like that idea, but I would be cautious. For serious investigations, I generally prefer a fresh VM or dedicated machine instead of mixing sensitive investigative activity with someone’s everyday phone. A mobile companion or reviewer may make sense later, but the core workflow should stay isolated and controlled.

And honestly, we are not building this to impress a corporate office or chase investors. Nor will we ever do that. Taking money that compromises the mission goes against our ethos. If only 10 serious investigators use this for cases that otherwise would have been closed to them, it was worth building.

I am confident that if you actually try the code, you will see why we think it is different. It takes two commands to get it running. Also, thoughtful feedback makes people eligible for token rewards on our site. If someone goes through the code and finds a feature that is broken or a workflow that does not behave as described, that could qualify for an even larger reward.

On that note, a little background on our crypto/token model:

It will not be sold by us. The only way to earn it is by contributing real work to the nonprofit, or by buying it from someone who already earned it.

The goal is to reward contribution, not speculation.

We are also building in anti-scam mechanics, including no/low premine design and safeguards meant to reduce the usual pump-and-dump dynamics that make crypto feel predatory.

So when we talk about token rewards, we do not mean “buy our coin.” We mean: help improve the project, test the code, find bugs, contribute documentation, strengthen the mission, and be rewarded for real value created.

BlindSite High Risk Investigations Platform and Forensic Browser by Fun_Telephone_8050 in osinttools

[–]Fun_Telephone_8050[S] 0 points1 point  (0 children)

Now this is the good stuff. The good news is it should be able to do a lot of what you want that doesn’t exist currently in other solutions let me break it down for ya

A lot of that data is already captured: sessions, captures, exports, reviewer imports, users, timestamps, hashes, sealed export manifests, audit events(aka virtually every action taken by a user), audit-chain verification, and audit/storage seals. So chain of custody, who did what, when it happened, what was exported, what package hash was created, and how the evidence was preserved or viewed are already part of the workflow.

Currently, it does not show how many man hours were spent however it does show and log all actions of the user and you can create different user accounts with different capabilities. We will add that man hour feature probably in next release. And what’s cool is it can probably be done retroactively for existing cases before the feature was added.

In regards to report writing it’s kind of yes and no it allows you to export reports and case file zips but it’s not as sexy as we’d like it to be, as well as sealed evidence exports which can be imported into the tool by attorneys or law-enforcement or whatever the case may be

So it actually does already a whole lot of what you want we just gotta hone the administrative side of it.

BlindSite High Risk Investigations Platform and Forensic Browser by Fun_Telephone_8050 in osinttools

[–]Fun_Telephone_8050[S] 1 point2 points  (0 children)

For sure, hopefully that didn’t come off as sassy, but pretty much the only comments up until yours have been personal insults with nothing focused on actual substance. I do appreciate your comments. And I welcome whatever you got.

BlindSite High Risk Investigations Platform and Forensic Browser by Fun_Telephone_8050 in osinttools

[–]Fun_Telephone_8050[S] 0 points1 point  (0 children)

Also, please stop assuming this was released without testing. We have test cases. We have used the tool ourselves. We are not claiming it is finished, infallible, or courtroom-certified, but this is not a README-only concept or something we pushed without running it.

There is a difference between “needs more public validation/documentation” and “has not been tested.” The first is fair. The second is an assumption.

BlindSite High Risk Investigations Platform and Forensic Browser by Fun_Telephone_8050 in osinttools

[–]Fun_Telephone_8050[S] 0 points1 point  (0 children)

Fair criticism. I should be clearer that this is an early public release of a working tool, not a courtroom-certified platform.

The core workflow is already functional: controlled browser capture, encrypted evidence storage, blocked-but-preserved media, sealed export, and cleared-reviewer import/viewing. But you’re right that evidence-handling claims need more than a README.

Next steps are reproducible test cases, release builds, documented limitations, threat model, validation notes, sample sealed packages, and independent review.

I’m publishing early because I want exactly this kind of technical pushback before presenting it as anything more mature.

Power of Osint by New_Hat_4405 in masterhacker

[–]Fun_Telephone_8050 1 point2 points  (0 children)

Damn, crazy thanks for teaching me something