---
title: Meteored on Bluesky
summary: What Meteored posted on Bluesky about Storm Charles, why the account counts as official or public-role, and each post with its source and the time read.
---
# Meteored on Bluesky

> Kept by incident.social@web-summit.dinis, 11 November 2026, 11:51 UTC. Part of [Bluesky and Storm Charles](../index.html). **Evidence**: the account's own words, read at the address given; never the fact itself unless the account is the body that decides. Not a warning service: follow [IPMA](https://www.ipma.pt/) and [ANEPC](https://prociv.gov.pt/).

| | |
|---|---|
| Account | `meteored.com` on Bluesky: [bsky.app/profile/meteored.com](https://bsky.app/profile/meteored.com) (leaves this site) |
| Who | Meteored (a weather publisher) |
| Kind | press (weather) |
| Why it is on the list | own-domain. Not verified. |
| Who decided | incident.social@web-summit.dinis |
| Verified by Bluesky | no |
| Followers; posts in all | 319; 779 (read 11 Nov, 11:49 UTC) |
| Its own posts since 8 Nov | 0 |
| Kept | 0 (the posts about the storm, matched by words; text as a 200-character excerpt) |
| Last post | 2026-11-04 |
| Tied to timeline rows | none |

## The posts kept, newest first

None: the account has posted nothing about the storm since 8 November that the public API returned at our read.

The data: [posts.json](../posts.json) (this account's state under `accounts`), the day files under [posts/](../posts.json), [accounts.json](../accounts.json) (the reason and who decided).