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

Zigbook Is Plagiarizing the Zigtools Playground

zigtools.org

Post reply on HN
Print view View original

91–100 of 156 posts

Re: Zigbook Is Plagiarizing the Zigtools Playground

#91

Post by the8472 »

dannyfritz07 wrote: post #89
the8472 wrote: post #85

Earlier quoted context omitted.

That's a useful feature for long-running issues to include updates in the opening post. Or to improve formatting when a bug reporter isn't familiar with markdown. And that it shows in the edit history should at least discourage abuse.

Allowing the maintainer to prepend a comment to the top seems more sensible to me to be honest. Would make API use harder potentially, but it would avoid weird abuse like this.

github is meant for collaboration, designing it around adversarial use would be a loss for everyone. Adding a function to report absusive edits rather than an entire post would be a better choice imo.

Re: Zigbook Is Plagiarizing the Zigtools Playground

#92

Post by PaulRobinson »

Disappointing.

When zigbook first appeared here, I took a cursory scan, and it looked pretty solid and a useful resource. Seems it duped me and got me good. I was even defending the use of AI a little - although the claim needed to go.

Seems they just were just trying to do over a nascent community that I'm interested in seeing growing and wasn't a member of yet.

Good riddance, then.

Re: Zigbook Is Plagiarizing the Zigtools Playground

#93

Post by merlindru »

projektfu wrote: post #83
NeckBeardPrince wrote: post #78

Earlier quoted context omitted.

What would be a valid reason to allow this? That just seems mind-numbingly stupid.

Censoring insults or illegal speech (depending on jurisdiction) would be the main reason I can think of.

That also means that some users will be pressured to censor illegal speech no? If you live under e.g. a regime that disallows or discourages criticism, now suddenly the onus is on you to do something about those comments because you have the ability to. If you couldn't edit the comments it's not your fault.

Either way I think it's a pretty stupid feature the way it's implemented; it should show the edit more clearly or indicate that the comment has been written by multiple people (like StackOverflow does), especially if edits change more than e.g. 10% of the original comment.

Re: Zigbook Is Plagiarizing the Zigtools Playground

#94

Post by jamiejquinn »

b800h wrote: post #81

Whenever I hear anything about Zig it seems to be drama. Very bizarre, will avoid.

Ditto... I love Zig as a language but I worry the high-level community builders (including Andrew) are a little too antagonistic to foster a positive, tolerant, patient community in the long term. In saying that, my infrequent interactions in the reddit and discord are always pleasant.

Re: Zigbook Is Plagiarizing the Zigtools Playground

#96

Post by tomalbrc »

halapro wrote: post #86
NeckBeardPrince wrote: post #78

Earlier quoted context omitted.

What would be a valid reason to allow this? That just seems mind-numbingly stupid.

This is particularly useful when editing the top-level comment of a popular issue to specify the current status. Or when a peer opened a placeholder issue and you fill it up. Etc. If you actually use GitHub as a social network of sorts, there are many reasons to do edit comments. All the edits are visible anyway. You're on Git-Hub, you can already edit everything you have write access to.

In which world would you want others to be able to edit your posts in a “SOCIAL NETWORK”? In today’s age of misinformation? Greeeeeeeat idea.

Re: Zigbook Is Plagiarizing the Zigtools Playground

#97

Post by tomalbrc »

the8472 wrote: post #85
jonathrg wrote: post #77

Earlier quoted context omitted.

It's unbelievable to me that Github allows repo admins to edit other people's comments.

That's a useful feature for long-running issues to include updates in the opening post. Or to improve formatting when a bug reporter isn't familiar with markdown. And that it shows in the edit history should at least discourage abuse.

It obviously does not discourage abuse

Re: Zigbook Is Plagiarizing the Zigtools Playground

#98

Post by the8472 »

tomalbrc wrote: post #97
the8472 wrote: post #85

Earlier quoted context omitted.

That's a useful feature for long-running issues to include updates in the opening post. Or to improve formatting when a bug reporter isn't familiar with markdown. And that it shows in the edit history should at least discourage abuse.

It obviously does not discourage abuse

No, that's not obvious at all. A single event is evidence that some abuse still happens, it does not tell us how much more abuse there would be in the counterfactual where the history wasn't available.

discourage != prevent all

Re: Zigbook Is Plagiarizing the Zigtools Playground

#99

Post by arccy »

gucci-on-fleek wrote: post #87
NeckBeardPrince wrote: post #78

Earlier quoted context omitted.

What would be a valid reason to allow this? That just seems mind-numbingly stupid.

Markdown is pretty tricky for new users to figure out, so quite often, users will just paste big snippets of code without formatting them, which is nearly unreadable. I'll usually edit these posts to add ```backticks``` around any code.

or they'll do what i assume is the jira style code blocks with just `multiple lines of code`

Re: Zigbook Is Plagiarizing the Zigtools Playground

#100

Post by jabbywocker »

tomalbrc wrote: post #96
halapro wrote: post #86

Earlier quoted context omitted.

This is particularly useful when editing the top-level comment of a popular issue to specify the current status. Or when a peer opened a placeholder issue and you fill it up. Etc. If you actually use GitHub as a social network of sorts, there are many reasons to do edit comments. All the edits are visible anyway. You're on Git-Hub, you can already edit everything you have write access to.

In which world would you want others to be able to edit your posts in a “SOCIAL NETWORK”? In today’s age of misinformation? Greeeeeeeat idea.

For GitHub specifically? This world. This is a useful feature
Post reply on HN