Probably worth a Tech News note, it shouldn't affect editors in any visible way but it's interesting.

@Tgr how can we word this? Asking for Tech News.

Per T402850#11246764 the anonymous cache will also be Cassandra / Kask, but a separate instance. @Eevans please let us know when you are ready to proceed.

Is the relevant task T392170: sessionstorage namespacing? Also, do you still want the splits mentioned there (per wiki or deploy group)? That would be an easy addition if you think it is useful.

In T402853#11262331, @STei-WMF wrote:

@Tgr how can we word this? Asking for Tech News.

Not sure if it's worth adding, it won't be observable to editors (unless something goes very wrong).

If you want to mention it anyway, maybe something like

A session store is a database used to remember users of a website between successive page loads. Wikimedia is splitting its session store into separate instances for anonymous and logged-in users, to reduce the risk of web scrapers interfering with logged-in users' usage of the sites. There should be no visible changes.

or if that's too long,

A separate session store has been created for anonymous users, to reduce the risk of outages from web scrapers. There should be no visible changes.

I like that last one, but I'd flip it around. First the result, then the technology.

To reduce the risk of outages from web scrapers, a separate session store has been created for anonymous users. There should be no visible changes.

Thanks!

In T402853#11271825, @Tgr wrote:

In T402853#11262331, @STei-WMF wrote:

@Tgr how can we word this? Asking for Tech News.

Not sure if it's worth adding, it won't be observable to editors (unless something goes very wrong).

If you want to mention it anyway, maybe something like

A session store is a database used to remember users of a website between successive page loads. Wikimedia is splitting its session store into separate instances for anonymous and logged-in users, to reduce the risk of web scrapers interfering with logged-in users' usage of the sites. There should be no visible changes.

or if that's too long,

A separate session store has been created for anonymous users, to reduce the risk of outages from web scrapers. There should be no visible changes.

In T402853#11272660, @TheDJ wrote:

I like that last one, but I'd flip it around. First the result, then the technology.

To reduce the risk of outages from web scrapers, a separate session store has been created for anonymous users. There should be no visible changes.

Thanks!

@STei-WMF: Please avoid unneeded full quotes - keeps a task easier to read. Thanks. :)

In T402853#11271784, @Tgr wrote:

[ ... ]
Is the relevant task T392170: sessionstorage namespacing?

Let's use that as the tracking issue; I'll create subtasks of T392170 as necessary.

Also, do you still want the splits mentioned there (per wiki or deploy group)? That would be an easy addition if you think it is useful.

For now, we should probably stick with anon sessions. I will open a subtask for further splits though so we can discuss what that would look like/entail.

In T402853#11271825, @Tgr wrote:

Not sure if it's worth adding, it won't be observable to editors (unless something goes very wrong).

I will remove the #user-notice tag then, and unsubscribe. If you reconsider, please re-add the tag, or add the draft to the relevant edition of Tech News at the right time. Thanks.