blast-studio 0.0.0-stage → 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/README.md +138 -2
- package/bin/bstudio.mjs +13 -0
- package/dist/agent-env.js +152 -0
- package/dist/brief.js +53 -0
- package/dist/budget/ledger.js +153 -0
- package/dist/campaign-zip.js +93 -0
- package/dist/cli.js +118 -0
- package/dist/commands/accept.js +64 -0
- package/dist/commands/auth.js +77 -0
- package/dist/commands/brief.js +117 -0
- package/dist/commands/budget.js +22 -0
- package/dist/commands/dashboard.js +9 -0
- package/dist/commands/doctor.js +57 -0
- package/dist/commands/export.js +42 -0
- package/dist/commands/init.js +24 -0
- package/dist/commands/install-skills.js +52 -0
- package/dist/commands/library.js +12 -0
- package/dist/commands/make.js +71 -0
- package/dist/commands/mark.js +44 -0
- package/dist/commands/new.js +25 -0
- package/dist/commands/plan.js +57 -0
- package/dist/commands/render-preview.js +43 -0
- package/dist/commands/render.js +243 -0
- package/dist/commands/review.js +119 -0
- package/dist/commands/revise.js +73 -0
- package/dist/commands/sources.js +33 -0
- package/dist/commands/status.js +34 -0
- package/dist/config.js +141 -0
- package/dist/dashboard/server.js +171 -0
- package/dist/dashboard/static/app.css +1 -0
- package/dist/dashboard/static/app.js +52 -0
- package/dist/dashboard/static/index.html +8 -0
- package/dist/env.js +47 -0
- package/dist/export.js +110 -0
- package/dist/fetch-text.js +64 -0
- package/dist/io.js +1 -0
- package/dist/keychain.js +41 -0
- package/dist/library.js +49 -0
- package/dist/packs.js +91 -0
- package/dist/plan.js +75 -0
- package/dist/posts.js +40 -0
- package/dist/providers/images.js +116 -0
- package/dist/providers/voice.js +55 -0
- package/dist/render/ffmpeg.js +96 -0
- package/dist/render/metrics.js +109 -0
- package/dist/render/stills.js +172 -0
- package/dist/render/template.js +20 -0
- package/dist/render/video.js +173 -0
- package/dist/review/gates.js +201 -0
- package/dist/review/reviewer.js +79 -0
- package/dist/review/score.js +21 -0
- package/dist/review/slop.js +17 -0
- package/dist/review-hash.js +21 -0
- package/dist/types.js +29 -0
- package/dist/updater/check.js +140 -0
- package/dist/updater/propose.js +144 -0
- package/dist/workspace.js +142 -0
- package/package.json +45 -4
- package/platforms/bluesky/guide.md +94 -0
- package/platforms/bluesky/pack.yml +150 -0
- package/platforms/dailydev/guide.md +82 -0
- package/platforms/dailydev/pack.yml +152 -0
- package/platforms/devto/guide.md +93 -0
- package/platforms/devto/pack.yml +119 -0
- package/platforms/gist/guide.md +92 -0
- package/platforms/gist/pack.yml +119 -0
- package/platforms/github-discussion/guide.md +92 -0
- package/platforms/github-discussion/pack.yml +122 -0
- package/platforms/hashnode/guide.md +93 -0
- package/platforms/hashnode/pack.yml +124 -0
- package/platforms/hn/guide.md +48 -0
- package/platforms/hn/pack.yml +59 -0
- package/platforms/instagram/guide.md +95 -0
- package/platforms/instagram/pack.yml +136 -0
- package/platforms/lemmy/guide.md +88 -0
- package/platforms/lemmy/pack.yml +141 -0
- package/platforms/linkedin/guide.md +93 -0
- package/platforms/linkedin/pack.yml +145 -0
- package/platforms/mastodon/guide.md +92 -0
- package/platforms/mastodon/pack.yml +138 -0
- package/platforms/medium/guide.md +92 -0
- package/platforms/medium/pack.yml +119 -0
- package/platforms/newsletter/guide.md +94 -0
- package/platforms/newsletter/pack.yml +144 -0
- package/platforms/producthunt/guide.md +92 -0
- package/platforms/producthunt/pack.yml +166 -0
- package/platforms/reddit/guide.md +92 -0
- package/platforms/reddit/pack.yml +151 -0
- package/platforms/snapshots/.gitkeep +0 -0
- package/platforms/snapshots/bluesky-10.sha256 +1 -0
- package/platforms/snapshots/bluesky-10.txt +1 -0
- package/platforms/snapshots/bluesky-11.sha256 +1 -0
- package/platforms/snapshots/bluesky-11.txt +1 -0
- package/platforms/snapshots/bluesky-12.sha256 +1 -0
- package/platforms/snapshots/bluesky-12.txt +1 -0
- package/platforms/snapshots/bluesky-13.sha256 +1 -0
- package/platforms/snapshots/bluesky-13.txt +1 -0
- package/platforms/snapshots/bluesky-14.sha256 +1 -0
- package/platforms/snapshots/bluesky-14.txt +1 -0
- package/platforms/snapshots/cross-platform-63.sha256 +1 -0
- package/platforms/snapshots/cross-platform-63.txt +1 -0
- package/platforms/snapshots/cross-platform-64.sha256 +1 -0
- package/platforms/snapshots/cross-platform-64.txt +1 -0
- package/platforms/snapshots/dailydev-55.sha256 +1 -0
- package/platforms/snapshots/dailydev-55.txt +1 -0
- package/platforms/snapshots/dailydev-56.sha256 +1 -0
- package/platforms/snapshots/dailydev-56.txt +1 -0
- package/platforms/snapshots/dailydev-57.sha256 +1 -0
- package/platforms/snapshots/dailydev-57.txt +1 -0
- package/platforms/snapshots/devto-26.sha256 +1 -0
- package/platforms/snapshots/devto-26.txt +1 -0
- package/platforms/snapshots/devto-27.sha256 +1 -0
- package/platforms/snapshots/devto-27.txt +1 -0
- package/platforms/snapshots/devto-28.sha256 +1 -0
- package/platforms/snapshots/devto-28.txt +1 -0
- package/platforms/snapshots/devto-29.sha256 +1 -0
- package/platforms/snapshots/devto-29.txt +1 -0
- package/platforms/snapshots/gist-52.sha256 +1 -0
- package/platforms/snapshots/gist-52.txt +1 -0
- package/platforms/snapshots/gist-53.sha256 +1 -0
- package/platforms/snapshots/gist-53.txt +1 -0
- package/platforms/snapshots/gist-54.sha256 +1 -0
- package/platforms/snapshots/gist-54.txt +1 -0
- package/platforms/snapshots/github-discussion-policy.sha256 +1 -0
- package/platforms/snapshots/github-discussion-policy.txt +1 -0
- package/platforms/snapshots/hashnode-30.sha256 +1 -0
- package/platforms/snapshots/hashnode-30.txt +1 -0
- package/platforms/snapshots/hashnode-31.sha256 +1 -0
- package/platforms/snapshots/hashnode-31.txt +1 -0
- package/platforms/snapshots/hashnode-32.sha256 +1 -0
- package/platforms/snapshots/hashnode-32.txt +1 -0
- package/platforms/snapshots/hn-23.sha256 +1 -0
- package/platforms/snapshots/hn-23.txt +1 -0
- package/platforms/snapshots/hn-24.sha256 +1 -0
- package/platforms/snapshots/hn-24.txt +1 -0
- package/platforms/snapshots/hn-25.sha256 +1 -0
- package/platforms/snapshots/hn-25.txt +1 -0
- package/platforms/snapshots/hyperframes-releases.sha256 +1 -0
- package/platforms/snapshots/hyperframes-releases.txt +1 -0
- package/platforms/snapshots/instagram-43.sha256 +1 -0
- package/platforms/snapshots/instagram-43.txt +1 -0
- package/platforms/snapshots/instagram-47.sha256 +1 -0
- package/platforms/snapshots/instagram-47.txt +1 -0
- package/platforms/snapshots/lemmy-policy.sha256 +1 -0
- package/platforms/snapshots/lemmy-policy.txt +1 -0
- package/platforms/snapshots/linkedin-1.sha256 +1 -0
- package/platforms/snapshots/linkedin-1.txt +1 -0
- package/platforms/snapshots/linkedin-2.sha256 +1 -0
- package/platforms/snapshots/linkedin-2.txt +1 -0
- package/platforms/snapshots/linkedin-3.sha256 +1 -0
- package/platforms/snapshots/linkedin-3.txt +1 -0
- package/platforms/snapshots/linkedin-4.sha256 +1 -0
- package/platforms/snapshots/linkedin-4.txt +1 -0
- package/platforms/snapshots/mastodon-15.sha256 +1 -0
- package/platforms/snapshots/mastodon-15.txt +1 -0
- package/platforms/snapshots/mastodon-16.sha256 +1 -0
- package/platforms/snapshots/mastodon-16.txt +1 -0
- package/platforms/snapshots/mastodon-17.sha256 +1 -0
- package/platforms/snapshots/mastodon-17.txt +1 -0
- package/platforms/snapshots/medium-34.sha256 +1 -0
- package/platforms/snapshots/medium-34.txt +1 -0
- package/platforms/snapshots/medium-35.sha256 +1 -0
- package/platforms/snapshots/medium-35.txt +1 -0
- package/platforms/snapshots/medium-36.sha256 +1 -0
- package/platforms/snapshots/medium-36.txt +1 -0
- package/platforms/snapshots/newsletter-58.sha256 +1 -0
- package/platforms/snapshots/newsletter-58.txt +1 -0
- package/platforms/snapshots/newsletter-59.sha256 +1 -0
- package/platforms/snapshots/newsletter-59.txt +1 -0
- package/platforms/snapshots/newsletter-60.sha256 +1 -0
- package/platforms/snapshots/newsletter-60.txt +1 -0
- package/platforms/snapshots/newsletter-61.sha256 +1 -0
- package/platforms/snapshots/newsletter-61.txt +1 -0
- package/platforms/snapshots/newsletter-62.sha256 +1 -0
- package/platforms/snapshots/newsletter-62.txt +1 -0
- package/platforms/snapshots/openai-image-pricing.sha256 +1 -0
- package/platforms/snapshots/openai-image-pricing.txt +1 -0
- package/platforms/snapshots/playwright-releases.sha256 +1 -0
- package/platforms/snapshots/playwright-releases.txt +1 -0
- package/platforms/snapshots/producthunt-37.sha256 +1 -0
- package/platforms/snapshots/producthunt-37.txt +1 -0
- package/platforms/snapshots/producthunt-38.sha256 +1 -0
- package/platforms/snapshots/producthunt-38.txt +1 -0
- package/platforms/snapshots/producthunt-39.sha256 +1 -0
- package/platforms/snapshots/producthunt-39.txt +1 -0
- package/platforms/snapshots/reddit-20.sha256 +1 -0
- package/platforms/snapshots/reddit-20.txt +1 -0
- package/platforms/snapshots/reddit-21.sha256 +1 -0
- package/platforms/snapshots/reddit-21.txt +1 -0
- package/platforms/snapshots/reddit-22.sha256 +1 -0
- package/platforms/snapshots/reddit-22.txt +1 -0
- package/platforms/snapshots/substack-policy.sha256 +1 -0
- package/platforms/snapshots/substack-policy.txt +1 -0
- package/platforms/snapshots/threads-18.sha256 +1 -0
- package/platforms/snapshots/threads-18.txt +1 -0
- package/platforms/snapshots/threads-19.sha256 +1 -0
- package/platforms/snapshots/threads-19.txt +1 -0
- package/platforms/snapshots/tiktok-50.sha256 +1 -0
- package/platforms/snapshots/tiktok-50.txt +1 -0
- package/platforms/snapshots/tiktok-51.sha256 +1 -0
- package/platforms/snapshots/tiktok-51.txt +1 -0
- package/platforms/snapshots/x-5.sha256 +1 -0
- package/platforms/snapshots/x-5.txt +1 -0
- package/platforms/snapshots/x-6.sha256 +1 -0
- package/platforms/snapshots/x-6.txt +1 -0
- package/platforms/snapshots/x-7.sha256 +1 -0
- package/platforms/snapshots/x-7.txt +1 -0
- package/platforms/snapshots/x-8.sha256 +1 -0
- package/platforms/snapshots/x-8.txt +1 -0
- package/platforms/snapshots/x-9.sha256 +1 -0
- package/platforms/snapshots/x-9.txt +1 -0
- package/platforms/snapshots/youtube-shorts-40.sha256 +1 -0
- package/platforms/snapshots/youtube-shorts-40.txt +1 -0
- package/platforms/snapshots/youtube-shorts-41.sha256 +1 -0
- package/platforms/snapshots/youtube-shorts-41.txt +1 -0
- package/platforms/snapshots/youtube-shorts-42.sha256 +1 -0
- package/platforms/snapshots/youtube-shorts-42.txt +1 -0
- package/platforms/sources.yml +947 -0
- package/platforms/substack/guide.md +94 -0
- package/platforms/substack/pack.yml +116 -0
- package/platforms/threads/guide.md +93 -0
- package/platforms/threads/pack.yml +148 -0
- package/platforms/tiktok/guide.md +92 -0
- package/platforms/tiktok/pack.yml +129 -0
- package/platforms/x/guide.md +94 -0
- package/platforms/x/pack.yml +130 -0
- package/platforms/youtube-shorts/guide.md +92 -0
- package/platforms/youtube-shorts/pack.yml +138 -0
- package/providers/prices.yml +31 -0
- package/schemas/campaign.v2.json +26 -0
- package/schemas/manifest.v1.json +37 -0
- package/schemas/pack.schema.json +601 -0
- package/schemas/review.schema.json +31 -0
- package/skills/studio-reviewer/SKILL.md +13 -0
- package/skills/studio-updater/SKILL.md +8 -0
- package/skills/studio-video/SKILL.md +20 -0
- package/skills/studio-visual/SKILL.md +12 -0
- package/skills/studio-writer/SKILL.md +14 -0
- package/templates/README.md +7 -0
- package/templates/card.html +1 -0
- package/templates/carousel-closing.html +1 -0
- package/templates/carousel-content.html +1 -0
- package/templates/carousel-title.html +1 -0
- package/templates/code.html +1 -0
- package/templates/fonts/IBM-Plex-OFL.txt +93 -0
- package/templates/fonts/IBMPlexMono.woff2 +0 -0
- package/templates/fonts/IBMPlexSans.woff2 +0 -0
- package/templates/fonts/Space-Grotesk-OFL.txt +93 -0
- package/templates/fonts/SpaceGrotesk.woff2 +0 -0
- package/templates/poster.html +1 -0
- package/templates/quote.html +1 -0
- package/templates/thumbnail.html +1 -0
- package/test/fixtures/reviews/calibration.json +22 -0
- package/test/fixtures/reviews/grounding/cases.json +17 -0
|
@@ -0,0 +1,141 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "lemmy",
|
|
3
|
+
"name": "Lemmy",
|
|
4
|
+
"marketBlaster": "lemmy",
|
|
5
|
+
"ai": "outline",
|
|
6
|
+
"aiSource": "lemmy-policy",
|
|
7
|
+
"formats": [
|
|
8
|
+
"text",
|
|
9
|
+
"image"
|
|
10
|
+
],
|
|
11
|
+
"textLimit": "unknown",
|
|
12
|
+
"titleLimit": "unknown",
|
|
13
|
+
"media": [],
|
|
14
|
+
"disclosure": {
|
|
15
|
+
"text": "unknown",
|
|
16
|
+
"media": "unknown",
|
|
17
|
+
"voice": "unknown"
|
|
18
|
+
},
|
|
19
|
+
"rubric": [
|
|
20
|
+
{
|
|
21
|
+
"id": "hook",
|
|
22
|
+
"question": "Does the human-written opening explain the concrete problem or lesson?",
|
|
23
|
+
"anchors": {
|
|
24
|
+
"0": "The opening has no identifiable subject or result.",
|
|
25
|
+
"1": "A subject appears, but the problem or outcome is vague or delayed.",
|
|
26
|
+
"2": "The opening identifies the subject and a concrete problem or outcome."
|
|
27
|
+
}
|
|
28
|
+
},
|
|
29
|
+
{
|
|
30
|
+
"id": "audience-fit",
|
|
31
|
+
"question": "Is the chosen community and instance relevant to the subject?",
|
|
32
|
+
"anchors": {
|
|
33
|
+
"0": "No intended reader or relevant situation is identifiable.",
|
|
34
|
+
"1": "A reader group or situation is hinted at but not connected to the content.",
|
|
35
|
+
"2": "The intended reader and relevant situation are explicit."
|
|
36
|
+
}
|
|
37
|
+
},
|
|
38
|
+
{
|
|
39
|
+
"id": "simplicity",
|
|
40
|
+
"question": "Can the reader understand the result without following a promotional link?",
|
|
41
|
+
"anchors": {
|
|
42
|
+
"0": "The reader cannot reconstruct the main point or sequence.",
|
|
43
|
+
"1": "The main point is present but key context or ordering is missing.",
|
|
44
|
+
"2": "The main point and necessary steps are clear and ordered."
|
|
45
|
+
}
|
|
46
|
+
},
|
|
47
|
+
{
|
|
48
|
+
"id": "anti-slop",
|
|
49
|
+
"question": "Are generic launch copy and repeated cross-community promotion absent?",
|
|
50
|
+
"anchors": {
|
|
51
|
+
"0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
|
|
52
|
+
"1": "Some concrete substance is present but generic or inflated language remains.",
|
|
53
|
+
"2": "Concrete language replaces hype and claims are supported."
|
|
54
|
+
}
|
|
55
|
+
},
|
|
56
|
+
{
|
|
57
|
+
"id": "platform-fit",
|
|
58
|
+
"question": "Do the selected instance and community permit this post type and promotion?",
|
|
59
|
+
"anchors": {
|
|
60
|
+
"0": "The candidate ignores the destination’s format or community rules.",
|
|
61
|
+
"1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
|
|
62
|
+
"2": "The format and relevant destination rules are checked and followed."
|
|
63
|
+
}
|
|
64
|
+
},
|
|
65
|
+
{
|
|
66
|
+
"id": "visual-quality",
|
|
67
|
+
"question": "Are any attached diagrams or images readable and described?",
|
|
68
|
+
"anchors": {
|
|
69
|
+
"0": "The visual is unreadable or lacks its relevant alternative or captions.",
|
|
70
|
+
"1": "The visual is partly readable or an alternative or caption is incomplete.",
|
|
71
|
+
"2": "Key content is readable and relevant alternatives or accurate captions are present."
|
|
72
|
+
},
|
|
73
|
+
"appliesTo": [
|
|
74
|
+
"image",
|
|
75
|
+
"carousel",
|
|
76
|
+
"poster",
|
|
77
|
+
"video",
|
|
78
|
+
"diagram",
|
|
79
|
+
"logo",
|
|
80
|
+
"terminal-demo"
|
|
81
|
+
]
|
|
82
|
+
},
|
|
83
|
+
{
|
|
84
|
+
"id": "value",
|
|
85
|
+
"question": "Does the post offer an evidence-backed lesson independent of a pitch?",
|
|
86
|
+
"anchors": {
|
|
87
|
+
"0": "No supported takeaway or useful example is identifiable.",
|
|
88
|
+
"1": "A takeaway is present but its evidence or practical detail is incomplete.",
|
|
89
|
+
"2": "A specific takeaway is supported by a concrete example or source."
|
|
90
|
+
}
|
|
91
|
+
},
|
|
92
|
+
{
|
|
93
|
+
"id": "community-rules",
|
|
94
|
+
"question": "Were the selected instance and community’s posting and promotion rules checked?",
|
|
95
|
+
"anchors": {
|
|
96
|
+
"0": "The selected community prohibits the post or its rules were not checked.",
|
|
97
|
+
"1": "The instance is named but the community’s promotion or posting rules remain unchecked.",
|
|
98
|
+
"2": "The selected instance and community rules are checked against the proposed post."
|
|
99
|
+
}
|
|
100
|
+
}
|
|
101
|
+
],
|
|
102
|
+
"outlineRubric": [
|
|
103
|
+
{
|
|
104
|
+
"id": "coverage",
|
|
105
|
+
"question": "Do the talking points cover the problem, relevant context and useful takeaway for members of a named community on a specific instance?",
|
|
106
|
+
"anchors": {
|
|
107
|
+
"0": "The problem or takeaway is absent.",
|
|
108
|
+
"1": "The problem and takeaway are present but important context is missing.",
|
|
109
|
+
"2": "The problem, relevant context and actionable takeaway are covered as talking points."
|
|
110
|
+
}
|
|
111
|
+
},
|
|
112
|
+
{
|
|
113
|
+
"id": "evidence",
|
|
114
|
+
"question": "Do the talking points identify evidence for the a self-hosting lesson example without inventing experience?",
|
|
115
|
+
"anchors": {
|
|
116
|
+
"0": "The outline asserts unsupported facts or invented experience.",
|
|
117
|
+
"1": "Some evidence is identified but a material assertion lacks a source.",
|
|
118
|
+
"2": "Material assertions point to evidence and uncertainty is noted."
|
|
119
|
+
}
|
|
120
|
+
},
|
|
121
|
+
{
|
|
122
|
+
"id": "community-rules-checked",
|
|
123
|
+
"question": "Have the rules and authorship policy for the intended lemmy destination been checked before the human writes?",
|
|
124
|
+
"anchors": {
|
|
125
|
+
"0": "The target or its rules are not identified.",
|
|
126
|
+
"1": "The target is named but current rules or authorship restrictions are unchecked.",
|
|
127
|
+
"2": "The named destination’s current rules and authorship restrictions are recorded."
|
|
128
|
+
}
|
|
129
|
+
}
|
|
130
|
+
],
|
|
131
|
+
"sources": [
|
|
132
|
+
"lemmy-policy",
|
|
133
|
+
"cross-platform-63",
|
|
134
|
+
"cross-platform-64"
|
|
135
|
+
],
|
|
136
|
+
"notes": [
|
|
137
|
+
"[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
|
|
138
|
+
"Check actual account, route, community and current requirements before publication.",
|
|
139
|
+
"Instance and community policies and limits vary; check the target server."
|
|
140
|
+
]
|
|
141
|
+
}
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
# LinkedIn
|
|
2
|
+
|
|
3
|
+
## Who reads it
|
|
4
|
+
|
|
5
|
+
[JUDGEMENT] Write for developer leads and founders sharing a professional lesson. Identify the actual reader and their situation, not a generic “everyone”.
|
|
6
|
+
|
|
7
|
+
## How distribution works
|
|
8
|
+
|
|
9
|
+
Feed recommendations consider professional relevance and quality, viewer relationships and activity, context and potential engagement; overly promotional or incoherent content may have limited reach. [LinkedIn](https://www.linkedin.com/help/linkedin/answer/a1499047). Text, images, documents/PDF, links and video are format options; no primary evidence reviewed proves a universal native-format preference, external-link penalty, ideal hashtag count, or that links belong in comments. **[JUDGEMENT]** A specific opening in the first two lines helps a human skimming; the exact truncation point varies by surface and is not a fixed platform specification. AI and paid partnership requirements are in the disclosure table.
|
|
10
|
+
|
|
11
|
+
[JUDGEMENT] Treat distribution as context, not a formula. No hook or format guarantees reach.
|
|
12
|
+
|
|
13
|
+
## Formats that work here
|
|
14
|
+
|
|
15
|
+
[JUDGEMENT] Choose the smallest format that can carry the evidence:
|
|
16
|
+
|
|
17
|
+
- Text: start with the professional problem; show one action and example; end with the lesson rather than a pitch.
|
|
18
|
+
|
|
19
|
+
- Document/carousel: one proposition per page, then a concrete example and takeaway; export a legible PDF.
|
|
20
|
+
|
|
21
|
+
- Video: show the problem, the action and the result; check the pack’s video duration and byte limits.
|
|
22
|
+
|
|
23
|
+
Check `pack.yml` for sourced limits and explicit unknowns; verify the live route and account.
|
|
24
|
+
|
|
25
|
+
## Hooks
|
|
26
|
+
|
|
27
|
+
[JUDGEMENT] The examples are hypothetical hook patterns, not claims; use them only when supported by actual evidence.
|
|
28
|
+
|
|
29
|
+
- **Problem first:** identify the recurring problem and who it affects.
|
|
30
|
+
Hypothetical example: “A stale CI cache kept our release pipeline failing after the lockfile changed.”
|
|
31
|
+
|
|
32
|
+
- **Unexpected constraint:** lead with the specific constraint uncovered during a deployment incident.
|
|
33
|
+
Hypothetical example: “Our migration had to run while both old and new application versions were live.”
|
|
34
|
+
|
|
35
|
+
- **Before and after:** lead with the observed state before and after a deployment incident, if supported.
|
|
36
|
+
Hypothetical example: “The test failed with the old schema; after the migration it passed against the new one.”
|
|
37
|
+
|
|
38
|
+
- **Decision tradeoff:** lead with the alternative considered during a deployment incident and its cost.
|
|
39
|
+
Hypothetical example: “We chose a reversible database migration over a shorter but irreversible script.”
|
|
40
|
+
|
|
41
|
+
- **Reproduction:** lead with the smallest reproducible input behind a deployment incident.
|
|
42
|
+
Hypothetical example: “This five-line test reproduces the timeout when the connection pool has one slot.”
|
|
43
|
+
|
|
44
|
+
- **Practical lesson:** lead with the action another developer can take after a deployment incident.
|
|
45
|
+
Hypothetical example: “Before changing a cache key, include the dependency lockfile in the key inputs.”
|
|
46
|
+
|
|
47
|
+
Banned patterns: clickbait that withholds the subject, fake urgency, and engagement bait asking for votes or empty replies.
|
|
48
|
+
|
|
49
|
+
## Structure template
|
|
50
|
+
|
|
51
|
+
[JUDGEMENT] Fill in only details supported by the source material:
|
|
52
|
+
|
|
53
|
+
- Audience and situation: [who encounters the problem, where]
|
|
54
|
+
- Specific problem or observation: [what happened]
|
|
55
|
+
- Evidence: [primary link, reproduction or verified example]
|
|
56
|
+
- Action and result: [what changed and what was observed]
|
|
57
|
+
- Takeaway or open question: [useful implication, without hype]
|
|
58
|
+
- Required affiliation, rights and disclosure: [checks]
|
|
59
|
+
|
|
60
|
+
## Visual and video recipes
|
|
61
|
+
|
|
62
|
+
[JUDGEMENT] Use visuals to make the actual lesson easier to understand, not as decorative proof.
|
|
63
|
+
|
|
64
|
+
- Image or diagram: label the subject and flow; keep mobile text legible and provide meaningful alt text.
|
|
65
|
+
- Carousel where supported: topic → context → one step per slide → observed result → concise takeaway.
|
|
66
|
+
- Video where supported: 0–3 s subject, 3–15 s demonstration, then the result and context; adapt timings to the material, not an alleged platform optimum.
|
|
67
|
+
- Captions: accurately transcribe speech, synchronize with audio and keep text clear of interface overlays.
|
|
68
|
+
- Inspect output, rights and the pack’s route-specific limits; do not infer unknown values.
|
|
69
|
+
|
|
70
|
+
## Anti-patterns
|
|
71
|
+
|
|
72
|
+
- Do not make a partnership invisible or replace the lesson with a product pitch.
|
|
73
|
+
- Do not invent metrics, testimonials, first-person experience or a guaranteed reach outcome.
|
|
74
|
+
- Avoid generic superlatives, duplicated points and context-free screenshots.
|
|
75
|
+
|
|
76
|
+
## AI and disclosure
|
|
77
|
+
|
|
78
|
+
LinkedIn recommends disclosing substantial non-obvious AI use. Paid brand relationships require the partnership label.
|
|
79
|
+
|
|
80
|
+
## Checklist
|
|
81
|
+
|
|
82
|
+
- [ ] The intended reader and supported takeaway are identifiable.
|
|
83
|
+
- [ ] Claims link to evidence; uncertainties and limitations remain visible.
|
|
84
|
+
- [ ] Actual route, account, community rules and pack limits were checked.
|
|
85
|
+
- [ ] Images have relevant alternatives and spoken media has accurate captions.
|
|
86
|
+
- [ ] Authorship, affiliation, rights and applicable disclosure were checked.
|
|
87
|
+
|
|
88
|
+
## Sources
|
|
89
|
+
|
|
90
|
+
- [algorithm / feed recommendations](https://www.linkedin.com/help/linkedin/answer/a1499047)
|
|
91
|
+
- [specs / organic video](https://www.linkedin.com/help/linkedin/answer/a7494039)
|
|
92
|
+
- [AI policy](https://www.linkedin.com/help/linkedin/answer/a1481496)
|
|
93
|
+
- [community rules / branded content](https://www.linkedin.com/help/linkedin/answer/a1627083)
|
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "linkedin",
|
|
3
|
+
"name": "LinkedIn",
|
|
4
|
+
"marketBlaster": "linkedin",
|
|
5
|
+
"ai": "draft",
|
|
6
|
+
"aiSource": "linkedin-3",
|
|
7
|
+
"safeZones": { "video": "unknown", "image": "unknown" },
|
|
8
|
+
"formats": [
|
|
9
|
+
"text",
|
|
10
|
+
"image",
|
|
11
|
+
"carousel",
|
|
12
|
+
"video"
|
|
13
|
+
],
|
|
14
|
+
"textLimit": "unknown",
|
|
15
|
+
"titleLimit": "unknown",
|
|
16
|
+
"marketBlasterMedia": { "source": "mb-check", "allowedKinds": ["image", "document"], "maxCount": 20 },
|
|
17
|
+
"media": [
|
|
18
|
+
{
|
|
19
|
+
"kind": "video",
|
|
20
|
+
"maxBytes": {
|
|
21
|
+
"value": 5000000000,
|
|
22
|
+
"source": "linkedin-2"
|
|
23
|
+
},
|
|
24
|
+
"maxSeconds": {
|
|
25
|
+
"value": 900,
|
|
26
|
+
"source": "linkedin-2"
|
|
27
|
+
}
|
|
28
|
+
}
|
|
29
|
+
],
|
|
30
|
+
"disclosure": {
|
|
31
|
+
"text": "recommended",
|
|
32
|
+
"media": "unknown",
|
|
33
|
+
"voice": "unknown"
|
|
34
|
+
},
|
|
35
|
+
"sponsorship": {
|
|
36
|
+
"rule": "Paid brand relationships, including free products exchanged for value, require the partnership label.",
|
|
37
|
+
"source": "linkedin-4"
|
|
38
|
+
},
|
|
39
|
+
"rubric": [
|
|
40
|
+
{
|
|
41
|
+
"id": "hook",
|
|
42
|
+
"question": "Does the opening name a concrete professional problem or outcome before the backstory?",
|
|
43
|
+
"anchors": {
|
|
44
|
+
"0": "The opening has no identifiable subject or result.",
|
|
45
|
+
"1": "A subject appears, but the problem or outcome is vague or delayed.",
|
|
46
|
+
"2": "The opening identifies the subject and a concrete problem or outcome."
|
|
47
|
+
}
|
|
48
|
+
},
|
|
49
|
+
{
|
|
50
|
+
"id": "audience-fit",
|
|
51
|
+
"question": "Can a developer lead or founder tell why the lesson matters to their work?",
|
|
52
|
+
"anchors": {
|
|
53
|
+
"0": "No intended reader or relevant situation is identifiable.",
|
|
54
|
+
"1": "A reader group or situation is hinted at but not connected to the content.",
|
|
55
|
+
"2": "The intended reader and relevant situation are explicit."
|
|
56
|
+
}
|
|
57
|
+
},
|
|
58
|
+
{
|
|
59
|
+
"id": "simplicity",
|
|
60
|
+
"question": "Can a reader identify the problem, action and takeaway without decoding jargon?",
|
|
61
|
+
"anchors": {
|
|
62
|
+
"0": "The reader cannot reconstruct the main point or sequence.",
|
|
63
|
+
"1": "The main point is present but key context or ordering is missing.",
|
|
64
|
+
"2": "The main point and necessary steps are clear and ordered."
|
|
65
|
+
}
|
|
66
|
+
},
|
|
67
|
+
{
|
|
68
|
+
"id": "anti-slop",
|
|
69
|
+
"question": "Are unsupported superlatives and generic motivational claims absent?",
|
|
70
|
+
"anchors": {
|
|
71
|
+
"0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
|
|
72
|
+
"1": "Some concrete substance is present but generic or inflated language remains.",
|
|
73
|
+
"2": "Concrete language replaces hype and claims are supported."
|
|
74
|
+
}
|
|
75
|
+
},
|
|
76
|
+
{
|
|
77
|
+
"id": "platform-fit",
|
|
78
|
+
"question": "Does the post teach a professional lesson rather than burying it under a pitch?",
|
|
79
|
+
"anchors": {
|
|
80
|
+
"0": "The candidate ignores the destination’s format or community rules.",
|
|
81
|
+
"1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
|
|
82
|
+
"2": "The format and relevant destination rules are checked and followed."
|
|
83
|
+
}
|
|
84
|
+
},
|
|
85
|
+
{
|
|
86
|
+
"id": "visual-quality",
|
|
87
|
+
"question": "Are document pages and images readable on a phone and described in alt text?",
|
|
88
|
+
"anchors": {
|
|
89
|
+
"0": "The visual is unreadable or lacks its relevant alternative or captions.",
|
|
90
|
+
"1": "The visual is partly readable or an alternative or caption is incomplete.",
|
|
91
|
+
"2": "Key content is readable and relevant alternatives or accurate captions are present."
|
|
92
|
+
},
|
|
93
|
+
"appliesTo": [
|
|
94
|
+
"image",
|
|
95
|
+
"carousel",
|
|
96
|
+
"poster",
|
|
97
|
+
"video",
|
|
98
|
+
"diagram",
|
|
99
|
+
"logo",
|
|
100
|
+
"terminal-demo"
|
|
101
|
+
]
|
|
102
|
+
},
|
|
103
|
+
{
|
|
104
|
+
"id": "value",
|
|
105
|
+
"question": "Does a verifiable example show what the reader can apply?",
|
|
106
|
+
"anchors": {
|
|
107
|
+
"0": "No supported takeaway or useful example is identifiable.",
|
|
108
|
+
"1": "A takeaway is present but its evidence or practical detail is incomplete.",
|
|
109
|
+
"2": "A specific takeaway is supported by a concrete example or source."
|
|
110
|
+
}
|
|
111
|
+
},
|
|
112
|
+
{
|
|
113
|
+
"id": "verifiable-example",
|
|
114
|
+
"question": "Is one example traceable to an accessible source or demonstrated result?",
|
|
115
|
+
"anchors": {
|
|
116
|
+
"0": "No example or source is supplied.",
|
|
117
|
+
"1": "An example is described but cannot be traced to evidence.",
|
|
118
|
+
"2": "An accessible source or demonstrated result supports the example."
|
|
119
|
+
}
|
|
120
|
+
},
|
|
121
|
+
{
|
|
122
|
+
"id": "partnership-disclosure",
|
|
123
|
+
"question": "Is any paid brand relationship identified with the required partnership label?",
|
|
124
|
+
"anchors": {
|
|
125
|
+
"0": "A required partnership label is missing.",
|
|
126
|
+
"1": "A relationship is acknowledged but its label is unresolved.",
|
|
127
|
+
"2": "The applicable partnership label is present or no relationship exists."
|
|
128
|
+
}
|
|
129
|
+
}
|
|
130
|
+
],
|
|
131
|
+
"sources": [
|
|
132
|
+
"mb-check",
|
|
133
|
+
"linkedin-1",
|
|
134
|
+
"linkedin-2",
|
|
135
|
+
"linkedin-3",
|
|
136
|
+
"linkedin-4",
|
|
137
|
+
"cross-platform-63",
|
|
138
|
+
"cross-platform-64"
|
|
139
|
+
],
|
|
140
|
+
"notes": [
|
|
141
|
+
"[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
|
|
142
|
+
"Check actual account, route, community and current requirements before publication.",
|
|
143
|
+
"LinkedIn recommends disclosure of substantial non-obvious AI use; this is not a universal mandatory AI label."
|
|
144
|
+
]
|
|
145
|
+
}
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# Mastodon
|
|
2
|
+
|
|
3
|
+
## Who reads it
|
|
4
|
+
|
|
5
|
+
[JUDGEMENT] Write for people in a chosen federated instance or community. Identify the actual reader and their situation, not a generic “everyone”.
|
|
6
|
+
|
|
7
|
+
## How distribution works
|
|
8
|
+
|
|
9
|
+
Home and live timelines are chronological, not a single centrally ranked feed; Explore/discovery is a separate surface, so do not claim that all Mastodon discovery has no ranking. Follows, boosts, hashtags, visibility settings and server federation affect exposure; federated feeds only include posts known to the server. [Network](https://docs.joinmastodon.org/user/network/), [posting](https://docs.joinmastodon.org/user/posting/). Rules differ per instance. **[JUDGEMENT]** Use relevant CamelCase hashtags for readability, not a promised ranking boost; no evidence establishes a universal external-link penalty.
|
|
10
|
+
|
|
11
|
+
[JUDGEMENT] Treat distribution as context, not a formula. No hook or format guarantees reach.
|
|
12
|
+
|
|
13
|
+
## Formats that work here
|
|
14
|
+
|
|
15
|
+
[JUDGEMENT] Choose the smallest format that can carry the evidence:
|
|
16
|
+
|
|
17
|
+
- Text: state the point without relying on a link; use relevant readable CamelCase hashtags if useful.
|
|
18
|
+
|
|
19
|
+
- Image/video: explain the media and add alt text; use the target instance’s settings rather than assuming defaults.
|
|
20
|
+
|
|
21
|
+
- Community context: select visibility and a content warning appropriate to the instance and material.
|
|
22
|
+
|
|
23
|
+
Check `pack.yml` for sourced limits and explicit unknowns; verify the live route and account.
|
|
24
|
+
|
|
25
|
+
## Hooks
|
|
26
|
+
|
|
27
|
+
[JUDGEMENT] The examples are hypothetical hook patterns, not claims; use them only when supported by actual evidence.
|
|
28
|
+
|
|
29
|
+
- **Problem first:** identify the recurring problem and who it affects.
|
|
30
|
+
Hypothetical example: “A stale CI cache kept our release pipeline failing after the lockfile changed.”
|
|
31
|
+
|
|
32
|
+
- **Unexpected constraint:** lead with the specific constraint uncovered during a self-hosting migration.
|
|
33
|
+
Hypothetical example: “Our migration had to run while both old and new application versions were live.”
|
|
34
|
+
|
|
35
|
+
- **Before and after:** lead with the observed state before and after a self-hosting migration, if supported.
|
|
36
|
+
Hypothetical example: “The test failed with the old schema; after the migration it passed against the new one.”
|
|
37
|
+
|
|
38
|
+
- **Decision tradeoff:** lead with the alternative considered during a self-hosting migration and its cost.
|
|
39
|
+
Hypothetical example: “We chose a reversible database migration over a shorter but irreversible script.”
|
|
40
|
+
|
|
41
|
+
- **Reproduction:** lead with the smallest reproducible input behind a self-hosting migration.
|
|
42
|
+
Hypothetical example: “This five-line test reproduces the timeout when the connection pool has one slot.”
|
|
43
|
+
|
|
44
|
+
- **Practical lesson:** lead with the action another developer can take after a self-hosting migration.
|
|
45
|
+
Hypothetical example: “Before changing a cache key, include the dependency lockfile in the key inputs.”
|
|
46
|
+
|
|
47
|
+
Banned patterns: clickbait that withholds the subject, fake urgency, and engagement bait asking for votes or empty replies.
|
|
48
|
+
|
|
49
|
+
## Structure template
|
|
50
|
+
|
|
51
|
+
[JUDGEMENT] Fill in only details supported by the source material:
|
|
52
|
+
|
|
53
|
+
- Audience and situation: [who encounters the problem, where]
|
|
54
|
+
- Specific problem or observation: [what happened]
|
|
55
|
+
- Evidence: [primary link, reproduction or verified example]
|
|
56
|
+
- Action and result: [what changed and what was observed]
|
|
57
|
+
- Takeaway or open question: [useful implication, without hype]
|
|
58
|
+
- Required affiliation, rights and disclosure: [checks]
|
|
59
|
+
|
|
60
|
+
## Visual and video recipes
|
|
61
|
+
|
|
62
|
+
[JUDGEMENT] Use visuals to make the actual lesson easier to understand, not as decorative proof.
|
|
63
|
+
|
|
64
|
+
- Image or diagram: label the subject and flow; keep mobile text legible and provide meaningful alt text.
|
|
65
|
+
- Carousel where supported: topic → context → one step per slide → observed result → concise takeaway.
|
|
66
|
+
- Video where supported: 0–3 s subject, 3–15 s demonstration, then the result and context; adapt timings to the material, not an alleged platform optimum.
|
|
67
|
+
- Captions: accurately transcribe speech, synchronize with audio and keep text clear of interface overlays.
|
|
68
|
+
- Inspect output, rights and the pack’s route-specific limits; do not infer unknown values.
|
|
69
|
+
|
|
70
|
+
## Anti-patterns
|
|
71
|
+
|
|
72
|
+
- Do not assume instance rules, visibility or media settings are universal.
|
|
73
|
+
- Do not invent metrics, testimonials, first-person experience or a guaranteed reach outcome.
|
|
74
|
+
- Avoid generic superlatives, duplicated points and context-free screenshots.
|
|
75
|
+
|
|
76
|
+
## AI and disclosure
|
|
77
|
+
|
|
78
|
+
Check home and receiving server rules; a network-wide AI disclosure mandate is unverified.
|
|
79
|
+
|
|
80
|
+
## Checklist
|
|
81
|
+
|
|
82
|
+
- [ ] The intended reader and supported takeaway are identifiable.
|
|
83
|
+
- [ ] Claims link to evidence; uncertainties and limitations remain visible.
|
|
84
|
+
- [ ] Actual route, account, community rules and pack limits were checked.
|
|
85
|
+
- [ ] Images have relevant alternatives and spoken media has accurate captions.
|
|
86
|
+
- [ ] Authorship, affiliation, rights and applicable disclosure were checked.
|
|
87
|
+
|
|
88
|
+
## Sources
|
|
89
|
+
|
|
90
|
+
- [algorithm / federation and discovery](https://docs.joinmastodon.org/user/network/)
|
|
91
|
+
- [specs / posting and visibility](https://docs.joinmastodon.org/user/posting/)
|
|
92
|
+
- [specs / instance configuration](https://docs.joinmastodon.org/entities/Instance/)
|
|
@@ -0,0 +1,138 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "mastodon",
|
|
3
|
+
"name": "Mastodon",
|
|
4
|
+
"marketBlaster": "mastodon",
|
|
5
|
+
"ai": "draft",
|
|
6
|
+
"formats": [
|
|
7
|
+
"text",
|
|
8
|
+
"image",
|
|
9
|
+
"video"
|
|
10
|
+
],
|
|
11
|
+
"textLimit": {
|
|
12
|
+
"value": 500,
|
|
13
|
+
"source": "mastodon-16"
|
|
14
|
+
},
|
|
15
|
+
"titleLimit": "unknown",
|
|
16
|
+
"marketBlasterMedia": { "source": "mb-check", "allowedKinds": ["image", "video"], "maxCount": 4 },
|
|
17
|
+
"media": [
|
|
18
|
+
{
|
|
19
|
+
"kind": "image",
|
|
20
|
+
"maxCount": {
|
|
21
|
+
"value": 4,
|
|
22
|
+
"source": "mastodon-16"
|
|
23
|
+
},
|
|
24
|
+
"maxBytes": {
|
|
25
|
+
"value": 16000000,
|
|
26
|
+
"source": "mastodon-16"
|
|
27
|
+
}
|
|
28
|
+
},
|
|
29
|
+
{
|
|
30
|
+
"kind": "video",
|
|
31
|
+
"maxBytes": {
|
|
32
|
+
"value": 99000000,
|
|
33
|
+
"source": "mastodon-16"
|
|
34
|
+
}
|
|
35
|
+
}
|
|
36
|
+
],
|
|
37
|
+
"disclosure": {
|
|
38
|
+
"text": "unknown",
|
|
39
|
+
"media": "unknown",
|
|
40
|
+
"voice": "unknown"
|
|
41
|
+
},
|
|
42
|
+
"rubric": [
|
|
43
|
+
{
|
|
44
|
+
"id": "hook",
|
|
45
|
+
"question": "Does the opening explain the useful point without requiring a click?",
|
|
46
|
+
"anchors": {
|
|
47
|
+
"0": "The opening has no identifiable subject or result.",
|
|
48
|
+
"1": "A subject appears, but the problem or outcome is vague or delayed.",
|
|
49
|
+
"2": "The opening identifies the subject and a concrete problem or outcome."
|
|
50
|
+
}
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"id": "audience-fit",
|
|
54
|
+
"question": "Is the target instance and its community relevant to this topic?",
|
|
55
|
+
"anchors": {
|
|
56
|
+
"0": "No intended reader or relevant situation is identifiable.",
|
|
57
|
+
"1": "A reader group or situation is hinted at but not connected to the content.",
|
|
58
|
+
"2": "The intended reader and relevant situation are explicit."
|
|
59
|
+
}
|
|
60
|
+
},
|
|
61
|
+
{
|
|
62
|
+
"id": "simplicity",
|
|
63
|
+
"question": "Is the post intelligible without expanding a link or decoding tag clutter?",
|
|
64
|
+
"anchors": {
|
|
65
|
+
"0": "The reader cannot reconstruct the main point or sequence.",
|
|
66
|
+
"1": "The main point is present but key context or ordering is missing.",
|
|
67
|
+
"2": "The main point and necessary steps are clear and ordered."
|
|
68
|
+
}
|
|
69
|
+
},
|
|
70
|
+
{
|
|
71
|
+
"id": "anti-slop",
|
|
72
|
+
"question": "Are inflated claims and generic promotional slogans absent?",
|
|
73
|
+
"anchors": {
|
|
74
|
+
"0": "The candidate relies on hype, fabricated urgency or unsupported claims.",
|
|
75
|
+
"1": "Some concrete substance is present but generic or inflated language remains.",
|
|
76
|
+
"2": "Concrete language replaces hype and claims are supported."
|
|
77
|
+
}
|
|
78
|
+
},
|
|
79
|
+
{
|
|
80
|
+
"id": "platform-fit",
|
|
81
|
+
"question": "Do visibility, content warning, hashtags and promotion respect the chosen server?",
|
|
82
|
+
"anchors": {
|
|
83
|
+
"0": "The candidate ignores the destination’s format or community rules.",
|
|
84
|
+
"1": "The format or community is identified but a relevant rule or constraint remains unchecked.",
|
|
85
|
+
"2": "The format and relevant destination rules are checked and followed."
|
|
86
|
+
}
|
|
87
|
+
},
|
|
88
|
+
{
|
|
89
|
+
"id": "visual-quality",
|
|
90
|
+
"question": "Do images have meaningful alt text and readable labels?",
|
|
91
|
+
"anchors": {
|
|
92
|
+
"0": "The visual is unreadable or lacks its relevant alternative or captions.",
|
|
93
|
+
"1": "The visual is partly readable or an alternative or caption is incomplete.",
|
|
94
|
+
"2": "Key content is readable and relevant alternatives or accurate captions are present."
|
|
95
|
+
},
|
|
96
|
+
"appliesTo": [
|
|
97
|
+
"image",
|
|
98
|
+
"carousel",
|
|
99
|
+
"poster",
|
|
100
|
+
"video",
|
|
101
|
+
"diagram",
|
|
102
|
+
"logo",
|
|
103
|
+
"terminal-demo"
|
|
104
|
+
]
|
|
105
|
+
},
|
|
106
|
+
{
|
|
107
|
+
"id": "value",
|
|
108
|
+
"question": "Is there enough detail for another operator to apply the lesson?",
|
|
109
|
+
"anchors": {
|
|
110
|
+
"0": "No supported takeaway or useful example is identifiable.",
|
|
111
|
+
"1": "A takeaway is present but its evidence or practical detail is incomplete.",
|
|
112
|
+
"2": "A specific takeaway is supported by a concrete example or source."
|
|
113
|
+
}
|
|
114
|
+
},
|
|
115
|
+
{
|
|
116
|
+
"id": "instance-rules",
|
|
117
|
+
"question": "Were the selected server’s current media and promotion rules checked?",
|
|
118
|
+
"anchors": {
|
|
119
|
+
"0": "The target server’s rules were not checked or are violated.",
|
|
120
|
+
"1": "The server is named but media or promotion rules remain unchecked.",
|
|
121
|
+
"2": "Current rules for the named server and applicable post type are checked."
|
|
122
|
+
}
|
|
123
|
+
}
|
|
124
|
+
],
|
|
125
|
+
"sources": [
|
|
126
|
+
"mb-check",
|
|
127
|
+
"mastodon-15",
|
|
128
|
+
"mastodon-16",
|
|
129
|
+
"mastodon-17",
|
|
130
|
+
"cross-platform-63",
|
|
131
|
+
"cross-platform-64"
|
|
132
|
+
],
|
|
133
|
+
"notes": [
|
|
134
|
+
"[JUDGEMENT] Rubric scores are editorial aids, not predictions of reach.",
|
|
135
|
+
"Check actual account, route, community and current requirements before publication.",
|
|
136
|
+
"Instance and community policies and limits vary; check the target server."
|
|
137
|
+
]
|
|
138
|
+
}
|