I know it's hard to give new ideas a chance in today's internet, where our attention spans are constantly attacked. Despite the hostility of our systems, please try to persevere with this presentation. I believe there are some novel ideas in it which will fundamentally alter how we interact with each other.
Locally-hosted software is definitely important in the short term, but I think that distributed software will be enough in the long term. When everything is public, then there won't be the same risks associated with using networked software. In the long term, I expect the intermediaries to be public too.
But locally-hosted software should always still be possible. I included something similar as one of the core tenets in the repo where I outline an idea for how we get things going: "After cloning this repository, it should be possible to start a development instance of bartok with a single command." Based on your feedback I think we should tweak this to emphasise local use, because there's a distinction between using software locally for development and using it locally because you're using it locally. (https://gitlab.com/bartokio/bartok)
Using Google Docs isn't ideal, and I didn't want to. However, I believe that the time has come that "ordinary people" (i.e. not HN readers) need to get interested in open source. I needed a solution that would be familiar and would definitely scale if the presentation got traffic.
Speaking as the initial author: you are correct on all counts (though I think _lying_ is a bit harsh, we've been around the internet).
Despite its appearance, it wasn't actually generated by GPT. I put a lot of work into this. Based on your comment history, I think you might actually come to agree with me.
I think I might have stumbled on the impossible miracle passive income technique you're referring to, though. I'm trying to get some traction, but it's hard because of virality filters. Please could you take a look at this and see if it matches your experience?
"On average, probably once a week or so, somebody will go in the lake. Most of the time when they miss, they miss coming back onto the boat. So somebody's outgoing mail might get wet.
We've got a little pool skimmer down below. If we have to, we have somebody lean out the door and scoop stuff back up out of the lake."
Indeed. Unfortunately the article lost me when I saw the graph of "extent to which you consider second order and subsequent consequences" vs "odds of success".
I usually assume that I can't take sales people at face value. If it's a badge of honour, they're incentivised to say that they don't work hard even if they are in fact actually working hard (this includes pretending to enjoy golf).
Having said that, 30 people is a lot of people, so I'm inclined to accept your assessment at face value.
If you've written 400 daily poems and it doesn't seem to be having a positive effect, then it's certainly time to stop. If it's going well, then fair enough, you do you.
This is a small thing, but one of the first sentences in the documentation you linked is "At least I have never thought about API dependencies before building WunderGraph." It makes the problem seem small, as if you can get away with not thinking about it.
This sounds so unethical. If I were a dieter or ex-smoker I would definitely not sign up for this sort of study.