Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
akerl_
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
151.
▲
by
akerl_
4mo ago
Somebody appears to be cataloging the documents, including the TRO, here: https://www.reddit.com/r/RecklessBen/comments/1tqrdei/compla... The TRO applies to "co-Defendants (including DOES 1-15), the
152.
▲
by
akerl_
4mo ago
How many people have to star your repo before it's no longer yours?
153.
▲
A Post-Quantum Future for Let's Encrypt
(letsencrypt.org)
4 points
by
akerl_
4mo ago
|
0 comments
154.
▲
by
akerl_
5mo ago
Woof. I think we’re just not going to agree.
155.
▲
by
akerl_
5mo ago
Sorry, but working on projects that interest you and going online to tell somebody they fucked up are not equivalent social behaviors.
156.
▲
by
akerl_
5mo ago
Again, this is not work and they are not customers. This is somebody spending their free time on code they enjoy and then putting the result online. The reason businesses are careful about which customers they fire is because they want to k
157.
▲
by
akerl_
5mo ago
Sure. But an open source project is not a professional setting.
158.
▲
by
akerl_
5mo ago
I think you may be confusing popularity with existence. The thing that makes a project die is if the maintainers all leave. Users don’t make a project exist. They make it popular. If the user community all up and left, rsync would still exi
159.
▲
by
akerl_
5mo ago
This is not a professional setting. This is an open source project that somebody published to the internet. Using it does not make you a customer, and it doesn’t matter if it “struck a nerve” with users.
160.
▲
by
akerl_
5mo ago
This doesn’t seem related to my comment. Did you mean to reply to me upthread? Saying ~“maybe it’s not ok to do <thing> but <reasons they might do thing>” is nothing like your example and does imply it’s acceptable to the speake
161.
▲
by
akerl_
5mo ago
There’s so much to unpack here, but let’s say I grant your premises that AIs are equivalent to people and Claude is making its own decisions about the project and the OG maintainer has ceded control of the repo to Mr Claude. I don’t, but le
162.
▲
by
akerl_
5mo ago
If I were the rsync maintainer I’d probably set the repo to only allow issues and PRs from prior contributors until people learn to behave.
163.
▲
by
akerl_
5mo ago
That’s exactly what I was calling out. Customers pay money for goods and services. They thus get a bunch of social, ethical, and legal positions in terms of their relationship with the seller. Rsync is an open source project that its mainta
164.
▲
by
akerl_
5mo ago
The target of the issue title is pretty clearly the maintainer. They’re the one being told to stop using AI. I guess this answers the question of whether you think maybe it’s ok to spit in the face of open source developers.
165.
▲
by
akerl_
5mo ago
The title of the original issue, by the original issue submitter, is “Please Do Not Vibe Fuck Up This Software”.
166.
▲
by
akerl_
5mo ago
Do you believe the comments in this GitHub issue are acceptable social discourse towards an open source maintainer?
167.
▲
by
akerl_
5mo ago
These are not customers.
168.
▲
by
akerl_
5mo ago
> Maybe it's not socially acceptable to spit in the face of a volunteer Why are you hedging this? Do you think maybe it is socially acceptable?
169.
▲
by
akerl_
5mo ago
Spamming an open source developer with angry comments because they decided to use a new tool for the code they write and publish freely is not normal.
170.
▲
by
akerl_
5mo ago
Why would it be the maintainer’s responsibly to fork their own repo? It wouldn’t even make sense; who would maintain the old repo? They also don’t need a reason, or owe you their reason, for changing what tools they use to work on their ope
171.
▲
by
akerl_
5mo ago
Are they? I've read them and they mostly just made me feel like shit. The amount of drive-by hate being thrown at project maintainers of an open source project is depressing.
172.
▲
by
akerl_
5mo ago
Openrsync is a project that’s existed for a long time and is a great example of people building what they want. This thread has people suggesting it’s good or important to go tell open source devs they’re using bad tools. The former is grea
173.
▲
by
akerl_
5mo ago
No clue; it wasn’t my concern.
174.
▲
by
akerl_
5mo ago
Many distros use rsync for that but also support unencrypted HTTP. They’re layering on checksums and signing such that they mostly don’t think about the trustworthiness of mirrors or the networks between them.
175.
▲
by
akerl_
5mo ago
I think you're answering a different objection than they're making. Their concern is that people will choose to spend 8 hours on your 4 hour problem but then tell you they only spent 4. Then you'll think they're a leet h
176.
▲
by
akerl_
5mo ago
It feels like your actual beef here is with CLAs, which often are designed to allow the current maintainers to relicense. CLAs are not an attribute of the GPL. They're an agreement that can be applied to contributions to any codebase w
177.
▲
by
akerl_
5mo ago
No. It's not important. It's actually pretty shitty to go around looking for projects and then telling the maintainers you disagree with how they develop.
178.
▲
by
akerl_
5mo ago
+1 to this. Other than people's reflexive anger or fear about AI coming for their code, I don't see anything to suggest that these are bugs that are due to the inclusion of AI vs bugs in a program with a bunch of complex interop w
179.
▲
by
akerl_
5mo ago
Microsoft's response to several recent stories including https://news.ycombinator.com/item?id=48315968 Reminder that CVD is a standard (in the same way that Test Driven Development is a standard approach that someone
180.
▲
Microsoft: Protecting customers through Coordinated Vulnerability Disclosure
(microsoft.com)
3 points
by
akerl_
5mo ago
|
1 comments
More ›