Thread refresh

✧✦Catherine✦✧ @whitequark@mastodon.social
replies: #2 #3 #6 #7

the "i am routinely looking at access logs of the static file server for purposes of development" version of "someone's talking about me, my ears are burning!":

someone (no idea who or where) posted a link to glasgow-embedded.org/latest/co, prompting the herd of mastodons to follow up with ~350 requests over the span of about 1 minute

✧✦Catherine✦✧ @whitequark@mastodon.social
in reply to #1 - replies: #5

the eagle-eyed of you may have noticed that i have, too, posted the link. and it even attracted 150% as many mastodons!

(by no means 5 req/s is a problem. i think it would have to get to 100-200 req/s for people to even start noticing that the server is under load, based on my earlier testing)

mei | fully hingeless architecture now in production @mei@donotsta.re
in reply to #1 - replies: #4
@whitequark hi, i posted that link in a reply what feels like just a few moments ago
✧✦Catherine✦✧ @whitequark@mastodon.social

@mei yeah i was deploying a change in configuration i was particularly concerned about, and just as i kicked it off i got the access logs scrolling up at lightspeed

Inga stands with 🇺🇦 🇵🇸 @IngaLovinde@embracing.space

@whitequark techbros: "oh no, mastodon of the indieweb is terrible and will kill your website by sending 500 requests over a minute if someone with a large following posts a link to it! We will call this the hug of death."

Also techbros: write "AI" scrapers which hammer your indieweb git forge "blame" endpoint at 1000 sustained requests per second.

leo vriska :light2: @leo@60228.dev

@whitequark this is really funny because these posts are on the same screen on my feed

@lillian
in reply to #1 - replies: #8

@whitequark what software are you using to generate this graph?