@tolmasky it's a classic. the “next link” should always...

@tolmasky it's a classic. the “next link” should always be a hash of the next posts, and unpredictable. also, some dumbass always says "this is complicated, can't we just use numbers” There’s always someone with a PHP script that can increment an integer!

Like 4 November at 0:01 | Wall-to-wall | Open on mastodon.social

4 comments

Niki Tonsky

@sayrer @tolmasky why should it be unpredictable? What’s wrong with guessing next link?

4 November at 10:09 | Open on mastodon.online

sayrer

@nikitonsky @tolmasky you can write a bot to fetch them all without reading them.

4 November at 14:20 | Open on mastodon.social

Niki Tonsky

@sayrer @tolmasky well, first, you can write bot either way.

Second, what’s the problem with that?

4 November at 18:51 | Open on mastodon.online

sayrer

@nikitonsky @tolmasky it's because it is a natural rate limiter (they have to parse the response to get only one next link). This is not a security mechanism, just cost savings. Old content is more expensive to serve than new content, this is how Twitter, IG, and even Netflix work. There is a computer in my local ISP that holds the current popular movies. Same idea, but for the Redis or edge server that powers your website.

4 November at 19:04 | Open on mastodon.social

Go Up