Re:15,000 lines of verified cryptography now in Python
by madars on Saturday April 19, 2025 @01:01AM
(#43734322)
After seeing "Jigar Kumar" cognitive exploits on xz mailing list a maintainer would be excused (and I'd even say, encouraged) to just ignore pressure tactics altogether. It's an open source project - if it works great, if it breaks, you get to keep both pieces.
Re:15,000 lines of verified cryptography now in Python
by throwaway519 on Saturday April 19, 2025 @03:19AM
(#43734803)
To the non-technical founder, this is doing something.
They will not move to ~~mocking up~~ sketching a wireframe of something.
Re:15,000 lines of verified cryptography now in Python
by aftbit on Saturday April 19, 2025 @11:50AM
(#43737215)
>Do you really think the maintainers don't understand that "doesn't work with Python 3.13" isn't going to affect tons of people?
I had trouble parsing this sentence. Claude simplified it for me as follows. AI to the rescue!
"Do you really think the maintainers fail to realize that Python 3.13 compatibility issues will affect many people?"
There's some bozo asking "any news? I cant downgrade because another lib requirement" just two days after the maintainer wrote several paragraphs explaining how difficult it is to make it work with Python 3.13. This adds no value for anyone and is just noise. Anyone interested in actual useful information (workarounds, pointers on how to help) has to wade though a firehose of useless nonsense to get at anything remotely useful. Any seriously discussions of maintainers wanting to discuss things is constantly interrupted by the seagulls from Finding Nemo: "fix? fix? fix? fix? fix?""
Never mind the demanding nature of some people in that thread.
Just upvote. That's why this entire feature was added.