Talk about a self-defeating message. Now I get timeouts. Things you get on BigEvilHost's platform: * SEO, discoverability * ability to handle HN hug-of-death * distribution * some SRE/dev-op makes sure your article isn't 404'd * backups etc. > Avoid unnecessary middlemen. They just proved why they're necessary.
Netlify or s3 or cloudflare + learning seo covers the above points. Unless no one wants to learn stuff anymore. We need an evil corp because no one can change their oil anymore?
Publish (on your) Own Site, Syndicate Elsewhere (POSSE) is a much more flexible idea IMO. You ultimately own your content, and it's the source of truth, but it gets automatically syndicated out and linked back to whatever proprietary or open platforms you think people will see it on.
Are you seriously trying to say that he can't make this point unless he builds his own twitter? https://i.imgur.com/iBAIRqF.png
I'm both a programmer and a pedant, so my opinion is that he's allowed to make this point and be an active Twitter user if his domain is OwnYourPlatform.com, but not if his domain is AlwaysOwnYourPlatform.com. :)
No point in owning your own platform unless you are in the business of building and running a platform. The real advice is to always be ready to abandon your platform at any moment and move on to a new one should its policies no longer be in your favor. Always be preparing for this scenario. What’s your contingency plan?
Exactly. These sorts of "Always" messages end up being overly simplistic. People should approach it as a business decision and part of that includes risk. I recruit a lot of authors into my publications and I'm hyper aware of the cases where we might not be offering a good deal. For example, for authors aspiring to write mainstream books, the size of their book advance is going to be heavily correlated with the size of their mailing list. So I always point out that these types of authors would be better off publishing first on their own site with an email collection CTA and then only secondarily republishing to other places like the pubs I run. However, not all authors have that goal and so they end up with totally different factors to weigh.
Not Found The requested URL / was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Always Own Your Platform
Talk about a self-defeating message. Now I get timeouts. Things you get on BigEvilHost's platform: * SEO, discoverability * ability to handle HN hug-of-death * distribution * some SRE/dev-op makes sure your article isn't 404'd * backups etc. > Avoid unnecessary middlemen. They just proved why they're necessary.
The HN "Hug-o-Death" can be handled by a potato unless your product is layers of bad code. No reasonable app should just die from 20MBps of traffic.
> ability to handle HN hug-of-death Seriously, this is bullshit. When my blog was on the frontpage, CPU load on my single 1-core VPS peaked at 5% and bandwidth usage was about 1 megabit per second. No Netlify, no Cloudflare, no nothing. If your website cannot handle the HN crowd, it's just badly engineered. Period. Source: https://xyrillian.de/thoughts/posts/latency-matters-aftermat...
I would expect open connections to be the bottleneck (not CPU or mem). Do you just have very low latency and thus relatively few concurrent open connections (yes, I saw the graphs in your link, but it's hard to figure out how many concurrent connections are open at a time)? EDIT: Downvoters, would really like to know why you're downvoting? Am I being naive in thinking a blog would be bottlenecked on connections?
My site has been on the front page a few times.
Concurrent requests were usually in the 400-800 range depending on where it ranked and what it was about. That's going by Google Analytics too which means it's likely higher since devs tend to disable as much tracking as possible.
nginx won't even break a sweat if you're on a low end VPS and are serving static content. You'll have pretty much the same latency as serving 1 concurrent request (single digit milliseconds + whatever network latency there is between your server and the visitor).
Talk about a self-defeating message. Now I get timeouts. Things you get on BigEvilHost's platform: * SEO, discoverability * ability to handle HN hug-of-death * distribution * some SRE/dev-op makes sure your article isn't 404'd * backups etc. > Avoid unnecessary middlemen. They just proved why they're necessary.
The HN "Hug-o-Death" can be handled by a potato unless your product is layers of bad code. No reasonable app should just die from 20MBps of traffic.
Have you considered: what if it's connected to a 10 MBps pipe?
Talk about a self-defeating message. Now I get timeouts. Things you get on BigEvilHost's platform: * SEO, discoverability * ability to handle HN hug-of-death * distribution * some SRE/dev-op makes sure your article isn't 404'd * backups etc. > Avoid unnecessary middlemen. They just proved why they're necessary.
> ability to handle HN hug-of-death Seriously, this is bullshit. When my blog was on the frontpage, CPU load on my single 1-core VPS peaked at 5% and bandwidth usage was about 1 megabit per second. No Netlify, no Cloudflare, no nothing. If your website cannot handle the HN crowd, it's just badly engineered. Period. Source: https://xyrillian.de/thoughts/posts/latency-matters-aftermat...
A blog typically comes with a comment function. That's something dynamic which requires lookup in some sort of database. Your page is purely static and does not even have pagination between posts. Hosting that is trivial and nothing to boast about. Your comparison is really unfair and needlessly nasty.