Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I'm Archiving Picocrypt

github.com

Post reply on HN
Print view View original

111–120 of 159 posts

Re: I'm Archiving Picocrypt

#111

Post by kannanvijayan »

immibis wrote: post #79
uludag wrote: post #65

I've felt similar to the author, a sort of despair that the only point of writing software now is to prop up the valuation of AI companies, that quality no longer matters, etc. Then I realized that nothings stopping me from writing software how I want and feel is best . I've stopped using LLMs completely and couldn't be happier. I'm not even struggling at work or feeling like I'm behind. I work on a number of persona…

This is also a good opportunity to remember that MIT is not a strong enough open source license, and if you want to prevent corporations making money off your work, make it AGPL or even SSPL, plus a statement that AI training creates a derivative work (the latter may or may not have any legal effect). MIT is a donation of your labour to corporations. With a stronger license, at least they're more likely to contribute…

Tangentially, I wonder if logins and click-throughs can help address this on the legal front.

If you set up a login flow with a click through that explicitly sets the terms of access, specifying no cost for access by a person, and some large cost for access by AI.

Stepping past this prompt into the content would require an AI to either lie, committing both fraud and unauthorized access of content.. or behave truthfully, opting in the proprietor of the API to the associated costs.

In either case, the site operator can then go after the company doing the scraping to collect the fees as specified in the copyright contract (and perhaps some additional delta of punitive fines if content was accessed fraudulently).

Re: I'm Archiving Picocrypt

#112

Post by dingnuts »

stoneyhrm1 wrote: post #90

I understand the author's sentiment but industries don't exist solely because somebody wants them to. I mean, sure, hobbies can exist, but you won't be paid well (or even at all) to work with them. Software engineering pays because companies want people to develop software. It pays so well because it's hard, but the coding portion is become easier. Vibe coding and AI is here to stay, the author can choose to ignore i…

it's not LLMs vs typing for loops by hand. It's LLMs vs snippets and traditional cheap, pattern based code generation, find and replace, and traditional refactoring tools

those are still faster and cheaper and more predictable than an LLM in many cases

Re: I'm Archiving Picocrypt

#113

Post by devheart »

blenderob wrote: post #101

I'm starting to feel kinda old and out of the loop. Could someone please explain the conversational style of this post? It begins with a prompt directed at Gemini, followed by what appears to be an AI-generated response. Are these actual AI responses or is the developer writing their parting message in a whimsical way? I'm genuinely confused. Help much appreciated!

He posted a conversation with Gemini, including his real posts and then Gemini's responses.

Re: I'm Archiving Picocrypt

#115

Post by IncreasePosts »

hakavlad wrote: post #110
Tepix wrote: post #99

The (current) last commend by hakavlad (same as hakavlad on HN perhaps?): @HACKERALERT Your decision may be somewhat irresponsible towards those who donated to the audit. That audit was one year ago. The money didn't go towards the author. The source continues to be available. The author doesn't own you zilch.

>The money didn't go towards the author. Perhaps many would have refused to donate if they knew that the project would be archived in a year. Collecting for audit and then archiving the project is, in a way, a violation of expectations.

Did they perform the audit? That is what is important.

The more and more you start modifying code after the audit, the more and more useless the audit becomes.

Re: I'm Archiving Picocrypt

#116

Post by pythonaut_16 »

immibis wrote: post #79
uludag wrote: post #65

I've felt similar to the author, a sort of despair that the only point of writing software now is to prop up the valuation of AI companies, that quality no longer matters, etc. Then I realized that nothings stopping me from writing software how I want and feel is best . I've stopped using LLMs completely and couldn't be happier. I'm not even struggling at work or feeling like I'm behind. I work on a number of persona…

This is also a good opportunity to remember that MIT is not a strong enough open source license, and if you want to prevent corporations making money off your work, make it AGPL or even SSPL, plus a statement that AI training creates a derivative work (the latter may or may not have any legal effect). MIT is a donation of your labour to corporations. With a stronger license, at least they're more likely to contribute…

Alternatively MIT does exactly what it says it does. It's up to you as an author whether you like those terms or if you'd prefer GPL, AGPL, or SSPL.

If you want a permissive license MIT is perfectly reasonable. If you want more restrictions or stronger copy-left then don't pick MIT.

Re: I'm Archiving Picocrypt

#117

Post by hakavlad »

IncreasePosts wrote: post #115
hakavlad wrote: post #110

Earlier quoted context omitted.

>The money didn't go towards the author. Perhaps many would have refused to donate if they knew that the project would be archived in a year. Collecting for audit and then archiving the project is, in a way, a violation of expectations.

Did they perform the audit? That is what is important. The more and more you start modifying code after the audit, the more and more useless the audit becomes.

Yes, they performed.

Re: I'm Archiving Picocrypt

#118

Post by axus »

rowanG077 wrote: post #105
Tepix wrote: post #99

The (current) last commend by hakavlad (same as hakavlad on HN perhaps?): @HACKERALERT Your decision may be somewhat irresponsible towards those who donated to the audit. That audit was one year ago. The money didn't go towards the author. The source continues to be available. The author doesn't own you zilch.

Yes, I found this a profoundly weird comment. The audited code will be forever available and audited.

Human beings are weird, and donations aren't always based on reason. I say it's better to discuss the feelings than worry about disapproval.

Surely a recent audit only increases the odds of someone assuming responsibility for a fork. Knowing there is a solid baseline to proceed from.

Re: I'm Archiving Picocrypt

#119

Post by mproud »

neom wrote: post #37

https://github.com/Picocrypt/Picocrypt/issues/134#issuecomme... This to me is the crux of the whole thing. Almost like a knitter throwing away their needles because they saw a loom.

As a complete outsider looking at this, without additional context, I just have a hard time believing there aren’t more reasons, they’re just not willing to share them:

* I’m not passionate about it anymore

* I’m tired

* I want to repurpose my free time

* I’m not adding enough value compared to other options now available

In the end, it’s pointless to argue about why someone feels the way they do. If they are firm on their stance, don’t waste anybody’s time, no matter how irrational their argument is. Give up trying to be right.

Probably this guy should have just stopped engaging directly with some of the dialogue, but the fact that he is exploring the idea of trying to hand it off in some manner tells me he really does care about the project.

Re: I'm Archiving Picocrypt

#120

Post by rollcat »

tromp wrote: post #67

How does "a very small (hence Pico), very simple, yet very secure encryption tool" come to depend on OpenGL, threatening its future on MacOS?

Immediate mode UI toolkits are designed for pluggable backends, some even can discover the appropriate backend at runtime. If you're writing a game, you're expected to (and actually, you must) build your own integration.

ImGUI and Nuklear each have 20+ backends in their repos: https://github.com/ocornut/imgui/tree/master/backends> https://github.com/Immediate-Mode-UI/Nuklear/tree/master/dem...>

Post reply on HN