To be fair a lot of ORMs provide updated_at or similar, so if you have a RESTful API you could just take that, or the max of all of them if you’re doing a more complex query. It might be a bit suboptimal but it shouldn’t be too expensive.
Now you can make use of the If-Modified-Since header. Return 304-not-modified if the data hasn’t changed. Now you can intelligently utilise the the client’s caching capability without sacrificing visibility and control. Using this header will let you serve new content instantly and also cache indefinitely. The best of both worlds.
Funny, but feels unfair to mastodon (as someone who doesn’t use mastodon), they are definitely not trying to destroy the world and could use donations too!
This is a pretty big surprise for a lot of people, immigration is not the thorniest issue this cabinet have dealt with… most likely a political move from at least one of the parties to break the coalition over this and try to snag more seats and a more favourable coalition next go around as opposed to a true vehement disagreement
What’s the most impactful 418-related incident you’ve witnessed? I remember a few years ago npm went down and was returning 418 which spawned jokes and chaos across the web
To be fair a lot of ORMs provide
updated_ator similar, so if you have a RESTful API you could just take that, or the max of all of them if you’re doing a more complex query. It might be a bit suboptimal but it shouldn’t be too expensive.