Re:Please Don't Share Our Links on Mastodon
by willcipriano on Wednesday May 01, 2024 @03:56PM
(#40228538)
A single user action can result in more than one http request to a service. The idea of the rule you are referring to is more about things that don't have any user input at all, like crawlers. A user asked for that, they said "I want all my pals to know about this page", even if it's a dumb thing that they asked for, they asked for it.
[ Parent
| on HN ]
Re:Please Don't Share Our Links on Mastodon
by jefftk on Wednesday May 01, 2024 @03:59PM
(#40228576)
In step 3 the servers asking for the image are acting as agents of the followers, not of the original poster, no?
Re:Please Don't Share Our Links on Mastodon
by willcipriano on Wednesday May 01, 2024 @04:11PM
(#40228726)
Why did the original poster post it if not to have the image downloaded to be displayed in his friends feeds?
Re:Please Don't Share Our Links on Mastodon
by jefftk on Wednesday May 01, 2024 @05:04PM
(#40229392)
The image isn't actually the issue: it's the html for the web page. The image is static and quick to serve, the html is often dynamically generated for each visitor.
Thinking about other similar distributed systems, if I put a link to an html page in an RSS feed or a mailing list message, it's not normal for subscribers to be using clients that fetch linked pages. But if they did it's clearly as an agent of that user, and not as an agent of the poster?
Re:Please Don't Share Our Links on Mastodon
by willcipriano on Wednesday May 01, 2024 @06:35PM
(#40230463)
If I was the web service getting hit I'd be glad that somebody is even interested enough that I'm having this problem. I also have the wisdom to know complaining is unlikely to solve my issue.
I get paid to basically solve this sort of scaling problems so I'm not a great barometer but it isn't that hard to handle a traffic spike like this.