The Product Safety & Integrity team has reviewed this table and is considering this to be a low privacy risk as long the following privacy protecting strategy is implemented:

Confirming that @Rscout has been added to WMF-NDA , acl*security_secteam , and acl*security_team .

Thank you @SD0001 . The Product Safety & Integrity team has reviewed this table and is considering this to be a low privacy risk with no blockers to proceed.

Hi @SD0001 , is there any possible way for this data to be correlated back to an individual?

In T420601#11735901, @Novem_Linguae wrote:

Some food for thought for this one:

• Do we want to throttle the # of notifications somehow to maximum X per day?
  • Does a mechanism to throttle already exist, or would we have to build one?
• Should we give users a preference to turn off this type of notification in Special:Preferences -> Notifications tab?
  • Probably yes. For example, on enwiki, we have an interface administrator bot that keeps GitHub repos in sync with user scripts. I imagine if a user script developer such as myself had a bunch of these set up and was making lots of edits to user scripts, the notifications would get annoying.

From a privacy perspective, I support adding an edit tag whenever someone edits another user's user CS page and think this can follow the same approach as T420600 that @Novem_Linguae provided.

Security issue access has been granted for @CWilliams-WMF

Hi @CWilliams-WMF , please have your manager comment their approval on this ticket and then we can grant you security issue access. Thank you!

Security issue access has been granted for @Madalina

Security issue access has been granted for @JTweed-WMF .

Hi @gmodena , I will send you the link to the static analysis test results over Slack.

Hi everyone,

Hi everyone. Quick timeline update - we're working on this review and should have this completed by the end of next week. Thank you for your patience!

Security issue access has been granted for @dom_walden

Confirming that I can access the API and run search queries. Thank you so much for your help @tappof !

The Product Safety and Integrity (PSI) Team is rejecting this request as these services are not under WMF control.

From a Security perspective, we do not recommend enabling the ipfs:// URL scheme on Wikimedia projects as this is considered a HIGH privacy risk.

Hi everyone, we'd also like to add Alex Sanford (shell username is alexsanford) to this request as well. I updated the original ticket to include him. Thanks!

Hi there @tappof , we're able to authenticate to https://logs-api.svc.eqiad.wmnet/ (GET / works) using the credentials you gave us, but all search endpoints (/_search, /_msearch, _cat/*) return 401 Unauthorized.

From a privacy perspective, this proposal appears low risk. The request is limited to a small, explicit set of known WMCS operational services and avoids wildcard domains or user-controlled Toolforge tools, which were the primary privacy concerns in prior discussions.

The privacy team has reviewed this request and is concluding this to be a low risk as long as analytics collection is limited to aggregated metrics (e.g., page views and interaction events) and does not include personal identifiers.

Hi @ATitkov and @Jdrewniak ,

@ssingh I'm now able to access JupyterHub and have deleted the WMCS key. Thank you!

@cmooney @ssingh I just requested access through the online system. Thank you!

Hi @cmooney ! I'm having some trouble trying to access JupyterHub and after some poking around with @dr0ptp4kt and @BTullis we think it's because I don't have wmf LDAP access but we aren't 100% sure.

In T398650#10974346, @Clement_Goubert wrote:

Please make sure the Wikimedia global and developer accounts are correctly created and not conflicting.
There seems to be two existing deactivated accounts under the aprum-ctr@wikimedia.org email, linked with the Aranyap~labswiki and the Aranyap enwiki account, as well as the aprum dewiki and aprum~labswiki wikitech account as well, but no account for aprum@wikimedia.org.

Hi @CDanis , we took a look at this repository found minimal problems, please feel free to move forward with using OpenTelemetry!

Hi @Ejegg thanks for bringing this to our attention. I initially conducted a privacy review for Fundraise Up and deemed it to be a low risk for the particular use-case that was specified by @ERoden-WMF . As for any additional integrations, I'll need to consult with @JFishback_WMF and @samuelguebo to determine whether this needs further review. I'll update here once I get more info. Thanks!

This issue has been resolved, closing this ticket.

In T331067#8663266, @JMeybohm wrote:

Welcome @aranyap! Please add the ssh key type to your request as well (assuming it's a ed25519 key, but just to be precise about it).

@Jcross from the mail address this looks like a contractor hiring. In that case we'd need:

• Contract end date:
• Contract contact person: