@Ahoelzl changes to the service or the site?

Updating the deploy target to 3-27-25 due to working group feedback and timeline for approvals from folks with conflicts this week.

@Aklapper didnt see that I made it users-only. Should be public now

Along with the above- is there a broader opportunity to update all known user agent strings and add new ones to ensure we are getting updated coverage of referrals from all new services (e.g. GPT and other AI folks, new search engines, Tiktok). Happy to file a request if so

Following this as well. Do we still need Tiktok to weigh in on the UA edge cases for this to be unblocked?

This would be very useful for us to be able to understand if known problematic reusers (see: https://phabricator.wikimedia.org/T317001) are similarly saturating other data streams to avoid correcting issue behavior.

Hi @derenrich - acknowledging this request. This is a known point of friction when trying to access specific page information. The current system does allow redirect-specific calls as it treats redirects in the same manner we do normal pages.

Hi folks - chiming in here from the Enterprise side. @fkaelin is correct that our snapshots are not historical. We likely will not be able to support that piece of the request if a specific historical dump is needed.