@Varenyaraj001122334455 In case users do not want to accept new terms of use, they can reach out to us through the contact form to delete their profile. Could you think of a way how to let users know about this option on the wireframe?

@Varenyaraj001122334455 The scope of design for this story is to visualize that an instance has been suspended for a generic reason.
I will create separate stories for suspending an instance due to intended use not being filled out and to give a warning before it actually happens (but it will happen later, when we start actually working on data governance workflows).

No design required, moving to review with the team

@Varenyaraj001122334455 Thanks for sharing the wireframes. As discussed during the review, please design with the assumption that there won't be automated comparison, but instead each new version of ToU will be complemented with a free-text summary of what changed compared to the previous version that the users should be able to access

Minimal design work for the footer link position (on wikibase.cloud) and the layout of the page itself

I suggest we resolve this ticket as Done, and deal with it in a separate initiative where we figure out what to do with the endpoints on the Allowlist that became non-operational (if we want to deal with them at all).

@Lydia_Pintscher The endpoint is still not responding. I think we still need to discuss how we deal with endpoints that go offline

A sample query worked:

A sample query worked:

@Lydia_Pintscher
Queries made on WDQS return an error
Unknown error: Status Code=403, Status Line=Forbidden, Response=Forbidden: Malicious request detected

@A_smart_kitten thank you!

@Aklapper I actually intentionally removed the tags, because these tasks were created as a way to group other tasks and they would just create the noise on the boards. Is there a better approach?