Indeed, async v. sync should be a matter of the application and the application only.

[0]: https://en.wikipedia.org/wiki/LulzSec

Comments URL: https://news.ycombinator.com/item?id=36132359

Points: 1

# Comments: 0

This is only my deductions from my experiences with Foo Bar, it might only be in that case, I am not exactly sure, but you should assume they do.

I believe, in this time of humanity where economy matters, that Blockchains have built-in economics for two reasons:

1. They all started copying Bitcoin, which by nature is an economic system (this is the goal of the Bitcoin's paper). 2. Reward by money is a common way to attract a sustainable amount of active users that keep the network alive without evil intention appart from making "quick bucks". In contract to volunteer networks such as Tor, where a lot (even a majority) of nodes are run by gov. agencies with the goal of identifying users, popular blockchains are still run properly since users are focusing on money and not destroying the network.

I have to disagree on this take. Almost all code dumping is useful since you can always learn something from it (either a new technique or stuff TO NOT DO...). What is important is to state the status of the project. If someone is still using the project and having difficulties with it even if you added a disclaimer, then it is their problem, and they should not expect any support (unless your license requires so)...

> But if you get a pull request, then someone else has spent time on your project, and just throwing that away is not good.

Sure, but once again communication is key here. I absolutely understands maintainers that do not have a look at merge requests but let them open. It allows anyone with the same problem to easily search in opened issues/merge requests and find the patch, which may help them (even if it is not in the "main" remote).

> I ended up completely dropping out of that project as a way of preserving my mental health. In fact, I dropped out of all my (F)OSS projects, and I even deleted some of my “code dump” projects on GitHub.

Hope you feel better now.

This. We often try to build something for everyone, letting our opinions asides to avoid any form of trouble. Yet I think that expressing our likes and dislikes (in a polite manner), and accepting our ideas/visions is the best way to succeed. We have various exemples, such as Steve Jobs' vision in Apple or Elon Musk's attitudes. While there are a lot of variables in success, I'm pretty sure expressing our opinions in our projects is one of the most important points.

The best thing I do that helped is to say "fuck you" to yourself and spend more time thinking (like a philosopher) about the world and my view on it. I couldn't really explain how but it really helps me.

So I guess I recommend trying to take an external view on your problems instead of studying to fix them as it is, to me, the best self-improvement thing anyone could obtain.

But I feel like these guidances to not be precise enough, especially the part on "Author bylines". Could it be possible for Google to voluntary remove from results AI-generated content? Google is strongly able to detect the presence of AI in content, I doubt however they can understand it well (for instance, low-quality and automated comparisons sites can still hit the first result of Search). Therefore it could lead to bad quality bans and mass-move to "human-generated content" (which is AI-generated with quick review for human), leading to more problems.