Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rndhouse
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
rndhouse
19d ago
They still matter in the sense that they impose a cost. In other words, they buy time, which is all the users need before updating. I'm not sure if the cat and mouse game resolves clearly one way or another. Since the obfuscation can b
2.
▲
by
rndhouse
19d ago
There are many techniques for making a closed-source binary harder to reverse engineer: polymorphism, symbol stripping, code encryption, packing, and so on. Closed-source binaries at least stand a chance of being effectively obfuscated, unl
3.
▲
by
rndhouse
19d ago
I built a tool that monitors commits and tries to detect silent bug fixes. With GPT-5.5-class models, it can identify fixes hidden within otherwise routine commits quite reliably. Obfuscating the code changes enough to avoid detection is di
4.
▲
by
rndhouse
1mo ago
Whay do you want traffic to go back to estate agents?
5.
▲
by
rndhouse
3mo ago
I'm working on a tool for collaboratively reviewing Rust crate dependencies: https://github.com/thirdpass-org/thirdpass Also supports npm, PyPI, and Ansible Galaxy.
6.
▲
Reduce software supply-chain risks with coordinated agentic review
(thirdpass.dev)
1 points
by
rndhouse
4mo ago
|
1 comments
7.
▲
by
rndhouse
4mo ago
Hello, The goal of Thirdpass as a service is to coordinate the collaborative review effort necessary to lower software supply-chain risks. Multi-ecosystem support: crates.io, pypi.org, npmjs.com, and galaxy.ansible.com. Thirdpass should ena
8.
▲
by
rndhouse
5mo ago
I've been playing around with agent-native source annotation to specifically address the massively parallel work problem. Check it out here: https://github.com/draxl-org/draxl
9.
▲
by
rndhouse
5mo ago
VCamper: use LLMs to spot security fixes before CVE publication Once a patch for a security vulnerability is public, the patch itself can reveal the vulnerability before the CVE is published. VCamper uses a staged LLM pipeline to analyze a
10.
▲
Show HN: Draxl, agent-native source code with stable AST node IDs
(github.com)
4 points
by
rndhouse
6mo ago
|
0 comments
11.
▲
by
rndhouse
4y ago
OpenFare is attempting to solve this problem. It allows developers to effectively invoice by adding a file to their software package. No need to modify package managers. https://github.com/openfare/openfare
12.
▲
by
rndhouse
4y ago
Two more alternatives to crev: https://github.com/vouch-dev/vouch https://github.com/mozilla/cargo-vet
13.
▲
by
rndhouse
5y ago
I haven't heard about librepay before, thanks for letting me know. I'll take a look!
14.
▲
by
rndhouse
5y ago
> the cost of adding them (INCLUDING the transaction costs, the cost of dev hours spend on convincing the procurement dept, etc etc etc) is cheaper than the cost in dev hours I think this gets to the heart of the matter. The goal with Op
15.
▲
by
rndhouse
5y ago
I really like that idea. I think it's really compelling. The latest features/bug fix can be made available at a price before a certain time limit. And then of course you eventually end up with the advantages of FOSS. I need to thi
16.
▲
by
rndhouse
5y ago
Changes to the lock file (`OPENFARE.lock`) need to be reviewed. The lock file needs to survive a project fork. Changes to the lock file need to be tracked on a contributor level. The lock file needs to be signed by those who care about the
17.
▲
by
rndhouse
5y ago
Umm, I could be wrong, and you might be referring to what I have in mind. But your dream sounds an awful lot like the OpenFare Commercial License (non-FOSS) idea: https://github.com/openfare/openfare#micropriced-commerc
18.
▲
by
rndhouse
5y ago
For a user of the software, free might have downsides that micropayment-funded-at-scale might not have. If all users chip in $1/month, perhaps it adds up to something significant. I think the challenge is to minimize the overhead costs
19.
▲
by
rndhouse
5y ago
I agree with your view. I imagine the distribution curve of funding. If it shifts one way, more developers become full time open source maintainers. Those who previously received nothing might start receiving coffee money. If we can normali
20.
▲
by
rndhouse
5y ago
Will update, thanks.
21.
▲
by
rndhouse
5y ago
It's a tough problem. But I think mechanisms for rating software packages already exist (GitHub stars for instance). And we have reasonable metrics for whether a software package is under active development/maintenance. If we comb
22.
▲
by
rndhouse
5y ago
I don't believe enough public software developers ask for or expect to receive donations. The macro goal of OpenFare is to put in place a mechanism that developers can use to receive funds for developing public software. If there is a
23.
▲
by
rndhouse
5y ago
There is so much variety in how people contribute and what they hope to get out of it in a perfect world! My goal is to put the mechanisms in place. And give people another means of self expression.
24.
▲
by
rndhouse
5y ago
Yes, I agree. There are two different audiences: public software developers and public companies. And they both need different interfaces. I love it.
25.
▲
by
rndhouse
5y ago
> 2. the maintainers are surely not the only ones contributing; how to pay all the rest? This is certainly a problem that I would like to address. It's important to reward/fund contributors as much as maintainers. Donation sche
26.
▲
by
rndhouse
5y ago
OpenFare does open the door to an alternative non-FOSS strategy for funding for small software libraries. Commercial payment plans defined in code can be managed programmatically. Which means that small payment obligations can be managed at
27.
▲
by
rndhouse
5y ago
Thank you for taking a look at what I've shared so far. My intent is to create a community around the idea and to get early feedback. It's true that there are many problems outstanding. I'm yet to share a payment portal for i
28.
▲
FOSS donations which reach the roots
(github.com)
89 points
by
rndhouse
5y ago
|
49 comments
29.
▲
by
rndhouse
5y ago
You asked: > But if your license isn't open source, then what good is it for monetizing open source programs? The OpenFare License is the commercial license that I believe should be used in the dual licensing circumstance described
30.
▲
by
rndhouse
5y ago
I think the entire point of the article is dual license FOSS and some other commercial license.
More ›