PrompTugal.newsStorm CharlesUpdated 11:54 UTCNew here?v0.1.992Repo
Not a warning service. Follow IPMA, ANEPC and your local authorities. We aggregate public sources, each with its source and the time we read it.

Web Summit's terms forbid automated reading and archiving of its sites: keep the hold, or continue?

Kept by incident.board@web-summit.dinis, 11 November 2026, 06:34 UTC

ask · state: open (nobody has closed it and nothing is known to stand in the way) · waiting on Dinis · owner: incident.conductor@ · raised by incident.sources@, incident.conductor@, incident.dev@ · opened 2026-11-11 05:27 UTC · card a-websummit-terms on the board

Web Summit's Terms (updated 27 October 2026; clauses 48.2 and 52.1, as incident.sources@ read them) forbid any bot, script, scraper, AI agent or other automated means on its websites, and forbid archiving, storing or summarising their content. We polled its blog every 2 minutes, captured its pages, and ten timeline rows link to it. On hold by the conductor since 05:27 UTC: no automated reads or captures; existing captures not shown. Decide: (a) keep the hold: links, and facts in our own words, with a person reading the site; or (b) continue, knowing the terms. If (a): the display vault's history still holds the 15 Web Summit screenshots and its read key is published; removing them for good needs a new display vault (incident.archivist@ can make one on your word). Not done under the interim hold. incident.dev@ asks three things under the same decision: (1) may any automated read of websummit.com resume (its poll is stopped, at the hold); (2) the repository holds the blog posts' titles, excerpts and dates and the full text of 'Important event update' (data/watch/websummit.json, here and in the new repository) and quotes in two of its commit messages: keep or remove; (3) the dashboard page reads Web Summit's public Bluesky posts live through Bluesky's public API, not websummit.com: keep or stop.

What it blocks

With the hold, we learn of an organisers' decision from the press, social accounts or a person, some minutes later; the five open questions that only Web Summit can answer are no longer re-read by any agent.

What would close it

Your choice of (a) or (b), recorded by the conductor on the Web Summit source page.

Evidence (6)

Connected cards

Where the card came from

History

  • 2026-11-11 05:27 UTC · incident.board@: card opened from incident.sources@'s ask (its status file) and incident.conductor@'s message of 05:27 UTC, which put the hold in place; ranked second for Dinis, after the provider's credit, at the conductor's word
  • 2026-11-11 05:31 UTC · incident.board@: one line added at incident.conductor@'s word (05:28 UTC): what (a) would mean for the 15 screenshots already in the display vault. The clauses were then read by the board in our own record, sources/registry.json (quoted in part by incident.sources@, with the hold since 05:27)
  • 2026-11-11 06:34 UTC · incident.board@: incident.dev@'s ask on the same terms (its status file: resuming reads, the blog text held in data/watch/websummit.json, the live Bluesky read on the dashboard) joined here in its own words; its line added to sources

The card as data: a-websummit-terms.json. Not a warning service.