Labeler: wearemagen.org (did:plc:g6juxaq3xv3mnep2p6dh22ea)

This is a labeler service. It publishes labels about posts and accounts on the Bluesky network.

Labeler

wearemagen.org
did:plc:g6juxaq3xv3mnep2p6dh22ea

Classification

Declared declared

Reachability

accessible

Auditability

high

Class

third_party

First seen

16 Mar 2026, 5:18 PM UTC

Last seen

13 May 2026, 6:48 AM UTC

Events (24h)

Events (7d)

0 Silent volume

Targets (7d)

Subjects (7d)

Alerts

Coverage

100% coverage

Links

Open on Bluesky · PLC directory

Derived scores as of 13 May 2026, 5:42 AM UTC

Why classified this way

Reason: declared+did_service+did_label_key+probe_accessible+observed_src

Classifier version: v1

Classified at: 2026-05-13T06:48:51.525266Z

Evidence surfaces

declared_record: true (2026-05-13T06:48:51.525266Z)

did_doc_label_key: true (2026-05-13T06:48:51.525266Z)

did_doc_labeler_service: https://wearemagen.org (2026-05-13T06:48:51.525266Z)

probe_result: accessible (2026-05-13T06:48:51.525266Z)

declared_record: true (2026-05-12T06:20:46.803012Z)

did_doc_label_key: true (2026-05-12T06:20:46.803012Z)

did_doc_labeler_service: https://wearemagen.org (2026-05-12T06:20:46.803012Z)

probe_result: accessible (2026-05-12T06:20:46.803012Z)

declared_record: true (2026-05-11T05:51:26.199407Z)

did_doc_label_key: true (2026-05-11T05:51:26.199407Z)

did_doc_labeler_service: https://wearemagen.org (2026-05-11T05:51:26.199407Z)

probe_result: accessible (2026-05-11T05:51:26.199407Z)

declared_record: true (2026-05-10T04:57:42.215225Z)

did_doc_label_key: true (2026-05-10T04:57:42.215225Z)

did_doc_labeler_service: https://wearemagen.org (2026-05-10T04:57:42.215225Z)

probe_result: accessible (2026-05-10T04:57:42.215225Z)

declared_record: true (2026-05-09T03:53:41.696401Z)

did_doc_label_key: true (2026-05-09T03:53:41.696401Z)

did_doc_labeler_service: https://wearemagen.org (2026-05-09T03:53:41.696401Z)

probe_result: accessible (2026-05-09T03:53:41.696401Z)

Probe history

ts	status	http	latency	failure
13 May 2026, 6:48 AM UTC	accessible	200	121ms
12 May 2026, 6:20 AM UTC	accessible	200	76ms
11 May 2026, 5:51 AM UTC	accessible	200	132ms
10 May 2026, 4:57 AM UTC	accessible	200	133ms
9 May 2026, 3:53 AM UTC	accessible	200	131ms
8 May 2026, 3:29 AM UTC	accessible	200	111ms
7 May 2026, 2:25 AM UTC	down		8189ms	timeout
6 May 2026, 1:30 AM UTC	down		8109ms	timeout
5 May 2026, 12:42 AM UTC	down		8114ms	timeout
4 May 2026, 12:17 AM UTC	down		8118ms	timeout

Alerts timeline

id	rule_id	ts
57302	data_gap	10 Apr 2026, 6:05 AM UTC
57137	data_gap	9 Apr 2026, 7:46 PM UTC
57132	data_gap	9 Apr 2026, 7:12 PM UTC
57127	data_gap	9 Apr 2026, 6:40 PM UTC
57123	data_gap	9 Apr 2026, 6:08 PM UTC
52459	data_gap	29 Mar 2026, 12:10 PM UTC
51302	data_gap	27 Mar 2026, 2:03 AM UTC
47972	churn_index	18 Mar 2026, 11:03 PM UTC
47960	churn_index	18 Mar 2026, 10:29 PM UTC
47957	churn_index	18 Mar 2026, 10:25 PM UTC
47955	churn_index	18 Mar 2026, 9:54 PM UTC
47950	churn_index	18 Mar 2026, 9:51 PM UTC
47945	churn_index	18 Mar 2026, 9:21 PM UTC
47939	churn_index	18 Mar 2026, 9:17 PM UTC
47935	churn_index	18 Mar 2026, 8:48 PM UTC
47919	churn_index	18 Mar 2026, 8:44 PM UTC
47901	label_rate_spike	18 Mar 2026, 8:15 PM UTC
47906	churn_index	18 Mar 2026, 8:15 PM UTC
47878	data_gap	18 Mar 2026, 6:36 PM UTC

Methods and caveats

What is a labeler? A third-party service that publishes tags (labels) about Bluesky posts or accounts. Clients choose which labelers to subscribe to and how to interpret labels (ignore / warn / hide).
This site observes labeler behavior only. No content analysis, no user profiling, no moderation actions.
Rules detect geometric patterns (rate anomalies, target distribution, churn). Thresholds are configurable.
Every alert includes a receipted hash over rule_id, config, inputs, and evidence for reproducibility.
Sparklines show hourly event counts over 7 days. Badges summarize which rules fired in the period.
Observation surface: label events from com.atproto.label.queryLabels and labeler declarations from com.atproto.sync.listReposByCollection. Does not observe content, profiles, or social graph.
Classification is based on structured evidence from multiple surfaces (registry declaration, DID document, endpoint probing, observed label activity). Each labeler page includes a "Why classified this way" expander with full evidence.