I quit emacs 10 years ago. But i have fond menories from magit. Why was the manual taken offline?
Why didn't you just follow the link and find out?
Magit manuals are available online again
21–30 of 60 posts
Re: Magit manuals are available online again
#22Earlier quoted context omitted.
Nah, just add a rate limiter (which any public website should have anyways). Alternatively, add some honeypot URLs to robots.txt, then setup fail2ban to ban any IP accessing those URLs and you'll get rid of 99% of the crawling in half a day.
I gave up after blocking 143,000 unique IPs hitting my personal Forgejo server one day. Rate limiting would have done literally nothing against the traffic patterns I saw.
2 unique IPs or 200,000 shouldn't make a difference, ban the ones that make too many requests automatically and you basically don't have to do anything.
Are people not using fail2ban and similar at all anymore? Used to be standard practice until I guess before people started using PaaS instead and "running web applications" became a different role than "developing web applications".
Re: Magit manuals are available online again
#23Earlier quoted context omitted.
> AWS CloudFront pricing seems pretty competitive with other CDNs Sure, but it's unlikely you actually have to place a CDN in front of your manual, it's mostly text with few images. People default to using CDNs way too quickly today.
The whole point of CDNs is to host static assets, why wouldn't you use one? They are dead simple to use.
Because caddy/nginx/apache (any web server really) can serve that content as well as any other? Better question is; why default to using more things before you actually need them?
Personally, software engineering for me is mostly about trying to avoid accidental complexity. People obsessing about "web scale" and "distributed architecture" before they even figured out if people actually want to use the platform/product/tool they've used tends to add a lot of complexity.
Re: Magit manuals are available online again
#24>I immediately burned down my account with that hosting provider1, because they did not allow setting a spending limit. Is this true? He mentions the provider being AWS, surely some sort of threshold can be set?
There are two widely understood downsides of AWS: 1. High egress costs 2. No hard spending limits Both of these were problems for the author. I don't mean to "blame the victim" but the choice of AWS here had a predictable outcome. Static documentation is the easiest content to host and AWS is the most expensive way to host it.
Really high bandwidth costs in general. I've never worked anywhere large enough to hit them, but I've heard inter-AZ traffic in the same region can become quite expensive once you're big enough
Re: Magit manuals are available online again
#25Earlier quoted context omitted.
I gave up after blocking 143,000 unique IPs hitting my personal Forgejo server one day. Rate limiting would have done literally nothing against the traffic patterns I saw.
2 unique IPs or 200,000 shouldn't make a difference, ban the ones that make too many requests automatically and you basically don't have to do anything. Are people not using fail2ban and similar at all anymore? Used to be standard practice until I guess before people started using PaaS instead and "running web applications" became a different role than "developing web applications".
It makes a difference if there's 143,000 unique IPs and 286,000 requests. I think that's what the parent post is saying (lots of requests but also not very many per IP since there's also lots of IPs)
Even harder with IPv6 considering things like privacy extensions where the IPs intentionally and automatically rotate
Re: Magit manuals are available online again
#26Earlier quoted context omitted.
Nah, just add a rate limiter (which any public website should have anyways). Alternatively, add some honeypot URLs to robots.txt, then setup fail2ban to ban any IP accessing those URLs and you'll get rid of 99% of the crawling in half a day.
If only it were that easy.
The poison's also the cure! Just ask AI for a haproxy rate limit config
Re: Magit manuals are available online again
#27Earlier quoted context omitted.
The whole point of CDNs is to host static assets, why wouldn't you use one? They are dead simple to use.
Far more expensive than just having a dumb server somewhere at some normal host. People simply do not understand how expen$ive AWS is, and how little value it actually has for most people.
Most people will never make it past the free tier on any of CloudFront, Cloudflare, Netlify, Render, etc.
You can just drag and drop a folder and have a static site hosted in a few minutes.
Re: Magit manuals are available online again
#28Earlier quoted context omitted.
The whole point of CDNs is to host static assets, why wouldn't you use one? They are dead simple to use.
Because caddy/nginx/apache (any web server really) can serve that content as well as any other? Better question is; why default to using more things before you actually need them? Personally, software engineering for me is mostly about trying to avoid accidental complexity. People obsessing about "web scale" and "distributed architecture" before they even figured out if people actually want to use the platform/produc…
How is setting up a web server not using more things than you need when you could just drag and drop a folder using one of many different CDN providers? (Or of course set up integrations as you want)
Re: Magit manuals are available online again
#29"Thanks to LLM scrapers, hosting costs went up 5000% last month"
Uggghhhh! AI crawling is fast becoming a headache for self-hosted content. Is using a CDN the "lowest effort" solution? Or is there something better/simpler?
Depending on the content and software stack, caching might be a fairly easy option. For instance, Wordpress W3 Total Cache used to be pretty easy to configure and could easily bring a small VPS from 6-10req/sec to 100-200req/sec.
Also some solutions for generating static content sites instead of "dynamic" CMS where they store everything in a DB
If it's new, I'd say the easiest option is start with a content hosting system that has built-in caching (assuming that exists for what you're trying to deploy)
Re: Magit manuals are available online again
#30Earlier quoted context omitted.
The whole point of CDNs is to host static assets, why wouldn't you use one? They are dead simple to use.
Far more expensive than just having a dumb server somewhere at some normal host. People simply do not understand how expen$ive AWS is, and how little value it actually has for most people.
It's really a tradeoff of saving time by paying more money. A lot of people chose it when they'd rather not pay more money and end up unhappy
A lot of other people also pick it for very narrow use cases where it wouldn't have been that much more time to learn and do it themselves and end up paying a lot of money and also aren't happy
It's pretty nice for mid-size startups to completely ignore performance and capacity planning and be able to quickly churn out features while accumulating tech debt and hoping they make it long enough to pay the tech debt back