Making the client open source means its auditable by the public. Making a server open source doesn't mean anything because you don't know if the host you're talking to is actually running that code.
You think extroverts are incapable of observing and listening?
What you did not create, you have not understood.
So just because I didn't write a book means I could never understand it from reading it? Are editors useless in the world of book publishing? Then what is the point of code review?
You act as if my LLM-assisted prototyping implies I made no decisions and didn't read any code. That's obviously a terrible way to use LLMs.
How do you determine what is genuine, and who holds the keys to digital signing?
Ah yes, collective decision making, so easy, especially with strangers.
I use dufs. Copyparty seems good too.
I do grind my beans haha.
It's been this way for at least a decade.
If you need a whole meeting to explain what's going on in your PR then it's already too complicated, IMO. That explanation should be done as a combination of PR description, commit messages, documentation, comments, and the code itself.
Everyone will forget a meeting. The stuff I described will pay dividends for future maintainers.
The meetings should happen at design and planning phase.
Your Git requires a regular flagellation to function properly.
tatterdemalion
0 post score0 comment score
On Cryptad's security page, they say:
This is the trust requirement I am trying to avoid by making the browser extension open source and independently verifiable.