veilgen
Joined 1 year ago
Joined 1 year ago
Would be interesting to see how it compares to static analysis tools like mypy or linters—does it catch edge cases they might miss? Nice work!
The technical approach is also fascinating—using static Parquet files on R2 instead of a traditional database keeps costs low while maintaining accessibility via SQL and DuckDB. Offloading computation to GitHub Actions is a clever way to handle large-scale processing efficiently.
It'll be interesting to see how this evolves, especially with the potential addition of traffic-aware travel times. Great work!
On the other hand, it could be useful for users who want to maintain a consistent archive of their content across platforms. But the question remains: should platforms allow this kind of timestamp manipulation?
1. Install a Better Dictionary: Firefox allows you to install custom dictionaries. You can search for dictionaries that might be more comprehensive or suited to your needs, such as specialized dictionaries for slang, names, or specific topics. To do this:
Go to Firefox Settings > Language > Choose a Dictionary.
Install additional dictionaries from the available list or download them from reputable sources.
2. Add Words to the Dictionary: If it’s not recognizing common words, you can manually add them to Firefox’s dictionary. Simply right-click on the word that’s flagged as incorrect and choose “Add to Dictionary.”
3. Enable Third-Party Extensions: There are extensions available for Firefox like Grammarly or LanguageTool that offer more accurate spell checking and even grammar suggestions. They can integrate cloud-based checks similar to Chrome's approach.
4. Consider Cloud-Based Spell Checkers: If you don’t mind sending data to a cloud service, using third-party spell checkers (like the ones mentioned above) can offer better performance. They can work across browsers, so it’s a similar experience to what you had with Chrome.
Unfortunately, Firefox doesn’t have the same advanced cloud integration for spell checking as Chrome, but these options might help make the experience better!
Regarding machine learning, it's definitely something we've been exploring. Integrating ML could allow the synthetic data to adapt more dynamically to evolving detection systems. This approach could help ensure that the generated data continues to evade detection as detection mechanisms become more sophisticated. We're excited to see how this technology can evolve and improve with time
I’ve been working on Veilgen, a tool designed to generate fully synthetic, encrypted fake data for security testing and red teaming. Unlike real or scraped data, Veilgen creates randomized structured data, making it ideal for:
Testing AI-driven detection systems without exposing real data. Simulating SSRF/RCE payloads with obfuscated and encrypted inputs. Eypassing security filters using structured yet unpredictable fake data. Running on Android/Linux with optional root features for deeper security analysis.
Since modern security systems rely heavily on AI-based anomaly detection, traditional evasion techniques are becoming less effective. How do you approach generating fake data for testing? What’s the biggest challenge in bypassing detection systems?
Would love to hear your feedback
Projects that naturally spark discussions tend to:
1. Solve a pressing problem—People talk about tools that significantly impact their workflows.
2. Have strong storytelling—A compelling narrative around the project’s origin, challenges, or breakthroughs makes it more shareable.
3. Engage actively in relevant communities—Posting insightful content on HN, Reddit, and Twitter (not just announcements) can help.
4. Encourage contributions beyond code—If the project welcomes blog posts, case studies, and integrations, it creates more discussion opportunities.
Have you tried running AMAs or writing deep-dive articles about the project’s internals and use cases? That often sparks technical conversations beyond GitHub.
One question: How do you handle prompt drift over time? As models evolve, prompt effectiveness can degrade—do you provide any automated testing or monitoring to detect when a deployed prompt needs adjustment?
Looking forward to exploring Portkey’s capabilities.