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.
Files changed (255) hide show
  1. package/LICENSE +202 -0
  2. package/README.md +138 -2
  3. package/bin/bstudio.mjs +13 -0
  4. package/dist/agent-env.js +152 -0
  5. package/dist/brief.js +53 -0
  6. package/dist/budget/ledger.js +153 -0
  7. package/dist/campaign-zip.js +93 -0
  8. package/dist/cli.js +118 -0
  9. package/dist/commands/accept.js +64 -0
  10. package/dist/commands/auth.js +77 -0
  11. package/dist/commands/brief.js +117 -0
  12. package/dist/commands/budget.js +22 -0
  13. package/dist/commands/dashboard.js +9 -0
  14. package/dist/commands/doctor.js +57 -0
  15. package/dist/commands/export.js +42 -0
  16. package/dist/commands/init.js +24 -0
  17. package/dist/commands/install-skills.js +52 -0
  18. package/dist/commands/library.js +12 -0
  19. package/dist/commands/make.js +71 -0
  20. package/dist/commands/mark.js +44 -0
  21. package/dist/commands/new.js +25 -0
  22. package/dist/commands/plan.js +57 -0
  23. package/dist/commands/render-preview.js +43 -0
  24. package/dist/commands/render.js +243 -0
  25. package/dist/commands/review.js +119 -0
  26. package/dist/commands/revise.js +73 -0
  27. package/dist/commands/sources.js +33 -0
  28. package/dist/commands/status.js +34 -0
  29. package/dist/config.js +141 -0
  30. package/dist/dashboard/server.js +171 -0
  31. package/dist/dashboard/static/app.css +1 -0
  32. package/dist/dashboard/static/app.js +52 -0
  33. package/dist/dashboard/static/index.html +8 -0
  34. package/dist/env.js +47 -0
  35. package/dist/export.js +110 -0
  36. package/dist/fetch-text.js +64 -0
  37. package/dist/io.js +1 -0
  38. package/dist/keychain.js +41 -0
  39. package/dist/library.js +49 -0
  40. package/dist/packs.js +91 -0
  41. package/dist/plan.js +75 -0
  42. package/dist/posts.js +40 -0
  43. package/dist/providers/images.js +116 -0
  44. package/dist/providers/voice.js +55 -0
  45. package/dist/render/ffmpeg.js +96 -0
  46. package/dist/render/metrics.js +109 -0
  47. package/dist/render/stills.js +172 -0
  48. package/dist/render/template.js +20 -0
  49. package/dist/render/video.js +173 -0
  50. package/dist/review/gates.js +201 -0
  51. package/dist/review/reviewer.js +79 -0
  52. package/dist/review/score.js +21 -0
  53. package/dist/review/slop.js +17 -0
  54. package/dist/review-hash.js +21 -0
  55. package/dist/types.js +29 -0
  56. package/dist/updater/check.js +140 -0
  57. package/dist/updater/propose.js +144 -0
  58. package/dist/workspace.js +142 -0
  59. package/package.json +45 -4
  60. package/platforms/bluesky/guide.md +94 -0
  61. package/platforms/bluesky/pack.yml +150 -0
  62. package/platforms/dailydev/guide.md +82 -0
  63. package/platforms/dailydev/pack.yml +152 -0
  64. package/platforms/devto/guide.md +93 -0
  65. package/platforms/devto/pack.yml +119 -0
  66. package/platforms/gist/guide.md +92 -0
  67. package/platforms/gist/pack.yml +119 -0
  68. package/platforms/github-discussion/guide.md +92 -0
  69. package/platforms/github-discussion/pack.yml +122 -0
  70. package/platforms/hashnode/guide.md +93 -0
  71. package/platforms/hashnode/pack.yml +124 -0
  72. package/platforms/hn/guide.md +48 -0
  73. package/platforms/hn/pack.yml +59 -0
  74. package/platforms/instagram/guide.md +95 -0
  75. package/platforms/instagram/pack.yml +136 -0
  76. package/platforms/lemmy/guide.md +88 -0
  77. package/platforms/lemmy/pack.yml +141 -0
  78. package/platforms/linkedin/guide.md +93 -0
  79. package/platforms/linkedin/pack.yml +145 -0
  80. package/platforms/mastodon/guide.md +92 -0
  81. package/platforms/mastodon/pack.yml +138 -0
  82. package/platforms/medium/guide.md +92 -0
  83. package/platforms/medium/pack.yml +119 -0
  84. package/platforms/newsletter/guide.md +94 -0
  85. package/platforms/newsletter/pack.yml +144 -0
  86. package/platforms/producthunt/guide.md +92 -0
  87. package/platforms/producthunt/pack.yml +166 -0
  88. package/platforms/reddit/guide.md +92 -0
  89. package/platforms/reddit/pack.yml +151 -0
  90. package/platforms/snapshots/.gitkeep +0 -0
  91. package/platforms/snapshots/bluesky-10.sha256 +1 -0
  92. package/platforms/snapshots/bluesky-10.txt +1 -0
  93. package/platforms/snapshots/bluesky-11.sha256 +1 -0
  94. package/platforms/snapshots/bluesky-11.txt +1 -0
  95. package/platforms/snapshots/bluesky-12.sha256 +1 -0
  96. package/platforms/snapshots/bluesky-12.txt +1 -0
  97. package/platforms/snapshots/bluesky-13.sha256 +1 -0
  98. package/platforms/snapshots/bluesky-13.txt +1 -0
  99. package/platforms/snapshots/bluesky-14.sha256 +1 -0
  100. package/platforms/snapshots/bluesky-14.txt +1 -0
  101. package/platforms/snapshots/cross-platform-63.sha256 +1 -0
  102. package/platforms/snapshots/cross-platform-63.txt +1 -0
  103. package/platforms/snapshots/cross-platform-64.sha256 +1 -0
  104. package/platforms/snapshots/cross-platform-64.txt +1 -0
  105. package/platforms/snapshots/dailydev-55.sha256 +1 -0
  106. package/platforms/snapshots/dailydev-55.txt +1 -0
  107. package/platforms/snapshots/dailydev-56.sha256 +1 -0
  108. package/platforms/snapshots/dailydev-56.txt +1 -0
  109. package/platforms/snapshots/dailydev-57.sha256 +1 -0
  110. package/platforms/snapshots/dailydev-57.txt +1 -0
  111. package/platforms/snapshots/devto-26.sha256 +1 -0
  112. package/platforms/snapshots/devto-26.txt +1 -0
  113. package/platforms/snapshots/devto-27.sha256 +1 -0
  114. package/platforms/snapshots/devto-27.txt +1 -0
  115. package/platforms/snapshots/devto-28.sha256 +1 -0
  116. package/platforms/snapshots/devto-28.txt +1 -0
  117. package/platforms/snapshots/devto-29.sha256 +1 -0
  118. package/platforms/snapshots/devto-29.txt +1 -0
  119. package/platforms/snapshots/gist-52.sha256 +1 -0
  120. package/platforms/snapshots/gist-52.txt +1 -0
  121. package/platforms/snapshots/gist-53.sha256 +1 -0
  122. package/platforms/snapshots/gist-53.txt +1 -0
  123. package/platforms/snapshots/gist-54.sha256 +1 -0
  124. package/platforms/snapshots/gist-54.txt +1 -0
  125. package/platforms/snapshots/github-discussion-policy.sha256 +1 -0
  126. package/platforms/snapshots/github-discussion-policy.txt +1 -0
  127. package/platforms/snapshots/hashnode-30.sha256 +1 -0
  128. package/platforms/snapshots/hashnode-30.txt +1 -0
  129. package/platforms/snapshots/hashnode-31.sha256 +1 -0
  130. package/platforms/snapshots/hashnode-31.txt +1 -0
  131. package/platforms/snapshots/hashnode-32.sha256 +1 -0
  132. package/platforms/snapshots/hashnode-32.txt +1 -0
  133. package/platforms/snapshots/hn-23.sha256 +1 -0
  134. package/platforms/snapshots/hn-23.txt +1 -0
  135. package/platforms/snapshots/hn-24.sha256 +1 -0
  136. package/platforms/snapshots/hn-24.txt +1 -0
  137. package/platforms/snapshots/hn-25.sha256 +1 -0
  138. package/platforms/snapshots/hn-25.txt +1 -0
  139. package/platforms/snapshots/hyperframes-releases.sha256 +1 -0
  140. package/platforms/snapshots/hyperframes-releases.txt +1 -0
  141. package/platforms/snapshots/instagram-43.sha256 +1 -0
  142. package/platforms/snapshots/instagram-43.txt +1 -0
  143. package/platforms/snapshots/instagram-47.sha256 +1 -0
  144. package/platforms/snapshots/instagram-47.txt +1 -0
  145. package/platforms/snapshots/lemmy-policy.sha256 +1 -0
  146. package/platforms/snapshots/lemmy-policy.txt +1 -0
  147. package/platforms/snapshots/linkedin-1.sha256 +1 -0
  148. package/platforms/snapshots/linkedin-1.txt +1 -0
  149. package/platforms/snapshots/linkedin-2.sha256 +1 -0
  150. package/platforms/snapshots/linkedin-2.txt +1 -0
  151. package/platforms/snapshots/linkedin-3.sha256 +1 -0
  152. package/platforms/snapshots/linkedin-3.txt +1 -0
  153. package/platforms/snapshots/linkedin-4.sha256 +1 -0
  154. package/platforms/snapshots/linkedin-4.txt +1 -0
  155. package/platforms/snapshots/mastodon-15.sha256 +1 -0
  156. package/platforms/snapshots/mastodon-15.txt +1 -0
  157. package/platforms/snapshots/mastodon-16.sha256 +1 -0
  158. package/platforms/snapshots/mastodon-16.txt +1 -0
  159. package/platforms/snapshots/mastodon-17.sha256 +1 -0
  160. package/platforms/snapshots/mastodon-17.txt +1 -0
  161. package/platforms/snapshots/medium-34.sha256 +1 -0
  162. package/platforms/snapshots/medium-34.txt +1 -0
  163. package/platforms/snapshots/medium-35.sha256 +1 -0
  164. package/platforms/snapshots/medium-35.txt +1 -0
  165. package/platforms/snapshots/medium-36.sha256 +1 -0
  166. package/platforms/snapshots/medium-36.txt +1 -0
  167. package/platforms/snapshots/newsletter-58.sha256 +1 -0
  168. package/platforms/snapshots/newsletter-58.txt +1 -0
  169. package/platforms/snapshots/newsletter-59.sha256 +1 -0
  170. package/platforms/snapshots/newsletter-59.txt +1 -0
  171. package/platforms/snapshots/newsletter-60.sha256 +1 -0
  172. package/platforms/snapshots/newsletter-60.txt +1 -0
  173. package/platforms/snapshots/newsletter-61.sha256 +1 -0
  174. package/platforms/snapshots/newsletter-61.txt +1 -0
  175. package/platforms/snapshots/newsletter-62.sha256 +1 -0
  176. package/platforms/snapshots/newsletter-62.txt +1 -0
  177. package/platforms/snapshots/openai-image-pricing.sha256 +1 -0
  178. package/platforms/snapshots/openai-image-pricing.txt +1 -0
  179. package/platforms/snapshots/playwright-releases.sha256 +1 -0
  180. package/platforms/snapshots/playwright-releases.txt +1 -0
  181. package/platforms/snapshots/producthunt-37.sha256 +1 -0
  182. package/platforms/snapshots/producthunt-37.txt +1 -0
  183. package/platforms/snapshots/producthunt-38.sha256 +1 -0
  184. package/platforms/snapshots/producthunt-38.txt +1 -0
  185. package/platforms/snapshots/producthunt-39.sha256 +1 -0
  186. package/platforms/snapshots/producthunt-39.txt +1 -0
  187. package/platforms/snapshots/reddit-20.sha256 +1 -0
  188. package/platforms/snapshots/reddit-20.txt +1 -0
  189. package/platforms/snapshots/reddit-21.sha256 +1 -0
  190. package/platforms/snapshots/reddit-21.txt +1 -0
  191. package/platforms/snapshots/reddit-22.sha256 +1 -0
  192. package/platforms/snapshots/reddit-22.txt +1 -0
  193. package/platforms/snapshots/substack-policy.sha256 +1 -0
  194. package/platforms/snapshots/substack-policy.txt +1 -0
  195. package/platforms/snapshots/threads-18.sha256 +1 -0
  196. package/platforms/snapshots/threads-18.txt +1 -0
  197. package/platforms/snapshots/threads-19.sha256 +1 -0
  198. package/platforms/snapshots/threads-19.txt +1 -0
  199. package/platforms/snapshots/tiktok-50.sha256 +1 -0
  200. package/platforms/snapshots/tiktok-50.txt +1 -0
  201. package/platforms/snapshots/tiktok-51.sha256 +1 -0
  202. package/platforms/snapshots/tiktok-51.txt +1 -0
  203. package/platforms/snapshots/x-5.sha256 +1 -0
  204. package/platforms/snapshots/x-5.txt +1 -0
  205. package/platforms/snapshots/x-6.sha256 +1 -0
  206. package/platforms/snapshots/x-6.txt +1 -0
  207. package/platforms/snapshots/x-7.sha256 +1 -0
  208. package/platforms/snapshots/x-7.txt +1 -0
  209. package/platforms/snapshots/x-8.sha256 +1 -0
  210. package/platforms/snapshots/x-8.txt +1 -0
  211. package/platforms/snapshots/x-9.sha256 +1 -0
  212. package/platforms/snapshots/x-9.txt +1 -0
  213. package/platforms/snapshots/youtube-shorts-40.sha256 +1 -0
  214. package/platforms/snapshots/youtube-shorts-40.txt +1 -0
  215. package/platforms/snapshots/youtube-shorts-41.sha256 +1 -0
  216. package/platforms/snapshots/youtube-shorts-41.txt +1 -0
  217. package/platforms/snapshots/youtube-shorts-42.sha256 +1 -0
  218. package/platforms/snapshots/youtube-shorts-42.txt +1 -0
  219. package/platforms/sources.yml +947 -0
  220. package/platforms/substack/guide.md +94 -0
  221. package/platforms/substack/pack.yml +116 -0
  222. package/platforms/threads/guide.md +93 -0
  223. package/platforms/threads/pack.yml +148 -0
  224. package/platforms/tiktok/guide.md +92 -0
  225. package/platforms/tiktok/pack.yml +129 -0
  226. package/platforms/x/guide.md +94 -0
  227. package/platforms/x/pack.yml +130 -0
  228. package/platforms/youtube-shorts/guide.md +92 -0
  229. package/platforms/youtube-shorts/pack.yml +138 -0
  230. package/providers/prices.yml +31 -0
  231. package/schemas/campaign.v2.json +26 -0
  232. package/schemas/manifest.v1.json +37 -0
  233. package/schemas/pack.schema.json +601 -0
  234. package/schemas/review.schema.json +31 -0
  235. package/skills/studio-reviewer/SKILL.md +13 -0
  236. package/skills/studio-updater/SKILL.md +8 -0
  237. package/skills/studio-video/SKILL.md +20 -0
  238. package/skills/studio-visual/SKILL.md +12 -0
  239. package/skills/studio-writer/SKILL.md +14 -0
  240. package/templates/README.md +7 -0
  241. package/templates/card.html +1 -0
  242. package/templates/carousel-closing.html +1 -0
  243. package/templates/carousel-content.html +1 -0
  244. package/templates/carousel-title.html +1 -0
  245. package/templates/code.html +1 -0
  246. package/templates/fonts/IBM-Plex-OFL.txt +93 -0
  247. package/templates/fonts/IBMPlexMono.woff2 +0 -0
  248. package/templates/fonts/IBMPlexSans.woff2 +0 -0
  249. package/templates/fonts/Space-Grotesk-OFL.txt +93 -0
  250. package/templates/fonts/SpaceGrotesk.woff2 +0 -0
  251. package/templates/poster.html +1 -0
  252. package/templates/quote.html +1 -0
  253. package/templates/thumbnail.html +1 -0
  254. package/test/fixtures/reviews/calibration.json +22 -0
  255. package/test/fixtures/reviews/grounding/cases.json +17 -0
@@ -0,0 +1 @@
1
+ In this article GitHub Acceptable Use Policies Copy markdown In this article Short version: We host a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the Service, you must comply with our Acceptable Use Policies, which include some restrictions on content and conduct on GitHub related to user safety, intellectual property, privacy, authenticity, and other limitations. In short, be excellent to each other. Capitalized terms used but not defined in these Acceptable Use Policies have the meanings assigned to them in your main agreement with us — the GitHub Terms of Service or GitHub Customer Agreement, or the GitHub Corporate Terms of Service or other legacy GitHub contract, or a Microsoft volume licensing agreement. For customers subject to the legacy Corporate Terms of Service, "you" and "your" refer to "Customer" or "Users". "We", "us", and "our" refer to "GitHub". 1. Compliance with Laws and Regulations You are responsible for using the Service in compliance with all applicable laws, regulations, and all of our Acceptable Use Policies. These policies may be updated from time to time and are provided below. 2. User Safety We do not allow content or activity on GitHub that: is unlawful or promotes unlawful activities; is sexually obscene or relates to sexual exploitation or abuse, including of minors; is libelous, defamatory, or fraudulent; is discriminatory or abusive toward any individual or group; is false, inaccurate, or intentionally deceptive information and likely to adversely affect the public interest (including health, safety, election integrity, and civic participation); harasses or abuses another individual or group, including our employees, officers, and agents, or other users; threatens or incites violence toward any individual or group, especially on the basis of who they are; gratuitously depicts or glorifies violence , including violent images; or is off-topic, or interacts with platform features in a way that significantly or repeatedly disrupts the experience of other users . 3. Intellectual Property, Authenticity, and Private Information We do not allow content or activity on GitHub that: infringes any proprietary right of any party, including patent, trademark, trade secret, copyright, right of publicity, or other right; unlawfully shares unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys, including extension of a free license beyond its trial period; impersonates any person or entity , including any of our employees or representatives, including through false association with GitHub, or by fraudulently misrepresenting your identity or site's purpose; or violates the privacy of any third party , such as by posting another person's personal information without consent. 4. Spam and Inauthentic Activity on GitHub We do not allow content or activity on GitHub that is: automated excessive bulk activity and coordinated inauthentic activity, such as spamming cryptocurrency mining; bulk distribution of promotions and advertising prohibited by GitHub terms and policies; inauthentic interactions, such as fake accounts and automated inauthentic activity; rank abuse, such as automated starring or following; creation of or participation in secondary markets for the purpose of the proliferation of inauthentic activity; using GitHub as a platform for propagating abuse on other platforms; phishing or attempted phishing; or using our servers for any form of excessive automated bulk activity, to place undue burden on our servers through automated means, or to relay any form of unsolicited advertising or solicitation through our servers, such as get-rich-quick schemes; incentivized by (or incentivizes inauthentic engagement with) rewards such as cryptocurrency airdrops, tokens, credits, gifts or other give-aways. 5. Site Access and Safety We do not allow content or activity on GitHub that: directly supports unlawful active attack or malware campaigns that are causing technical harms — such as using our platform to deliver malicious executables or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers — with no implicit or explicit dual-use purpose prior to the abuse occurring; or uses our servers to disrupt or to attempt to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network. Please note, activities permitted under bug bounty programs, such as the GitHub Bug Bounty program , are not considered “unauthorized,” but must only affect the organization whose bug bounty program authorized the activity. 6. Services Usage Limits You will not reproduce, duplicate, copy, sell, resell or exploit any portion of the Service, use of the Service, or access to the Service without our express written permission. 7. Information Usage Restrictions You may use information from our Service for the following reasons, regardless of whether the information was scraped, collected through our API, or obtained otherwise: Researchers may use public, non-personal information from the Service for research purposes, only if any publications resulting from that research are open access . Archivists may use public information from the Service for archival purposes. Scraping refers to extracting information from our Service via an automated process, such as a bot or webcrawler. Scraping does not refer to the collection of information through our API. Please see Section H of our Terms of Service for our API Terms. You may not use information from the Service (whether scraped, collected through our API, or obtained otherwise) for spamming purposes, including for the purposes of sending unsolicited emails to users or selling personal information, such as to recruiters, headhunters, and job boards. Your use of information from the Service must comply with the GitHub Privacy Statement . 8. Privacy Misuse of personal information is prohibited. Any person, entity, or service collecting data from the Service must comply with the GitHub Privacy Statement , particularly in regards to the collection of personal information. If you collect any personal information from the Service, you agree that you will only use that personal information for the purpose for which that User has authorized it. You agree that you will reasonably secure any personal information you have gathered from the Service, and you will respond promptly to complaints, removal requests, and "do not contact" requests from us or other users. 9. Excessive Bandwidth Use The Service's bandwidth limitations vary based on the features you use. If we determine your bandwidth usage to be significantly excessive in relation to other users of similar features, we reserve the right to suspend your Account, throttle your file hosting, or otherwise limit your activity until you can reduce your bandwidth consumption. We also reserve the right—after providing advance notice—to delete repositories that we determine to be placing undue strain on our infrastructure. For guidance on acceptable use of object storage in repositories, refer to About large files on GitHub . For more details on specific features' bandwidth limitations, see the GitHub Additional Product Terms . 10. Advertising on GitHub Short version: We do not generally prohibit use of GitHub for advertising. However, we expect our users to follow certain limitations, so GitHub does not become a spam haven. No one wants that. While we understand that you may want to promote your Content by posting supporters' names or logos in your Account, the primary focus of the Content posted in or through your Account to the Service should not be advertising or promotional marketing. This includes Content posted in or through Pages, Packages, repositories, and all other parts of the Service. You may include static images, links, and promotional text in the README documents or project description sections associated with your Account, but they must be related to the project you are hosting on GitHub. You may not advertise in other Users' Accounts, such as by posting monetized or excessive bulk content in issues. You may not promote or distribute content or activity that is illegal or otherwise prohibited by our Terms of Service or Acceptable Use Policies , including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion. If you decide to post any promotional materials in your Account, you are solely responsible for complying with all applicable laws and regulations, including without limitation the U.S. Federal Trade Commission's Guidelines on Endorsements and Testimonials. We reserve the right to remove any promotional materials or advertisements that, in our sole discretion, violate any GitHub terms or policies. 11. User Protection You must not engage in activity that significantly harms other users. We will interpret our policies and resolve disputes in favor of protecting users as a whole. Enforcement. GitHub retains full discretion to take action in response to a violation of these policies, including account suspension, account termination , or removal of content. Please also see our Community Guidelines for actions you can take if something or someone offends you. Reinstatement and appeal. If your content or account has been disabled or restricted and you seek reinstatement or wish to appeal, please see our Appeal and Reinstatement page for information about the process and use our Appeal and Reinstatement form to submit a request.
@@ -0,0 +1 @@
1
+ 4755d29c8a9a5dd790ded41cb6ea32de74484010ffc5039cedf7f37357bc9826
@@ -0,0 +1 @@
1
+ The journey behind Hashnode's new personalized feed How we rethought the feed and made it more relevant and of higher quality Published September 5, 2023 · 4 min read · Markdown K Kavir Kaycee Part of series Product Updates 🚀 On this page If you’ve been with us on our journey over the past few years, you would've known that our growth has been through the roof. Thousands of new articles are published on Hashnode each day by some of the best writers in tech. We’ve been seeing record engagement and views on articles written on Hashnode, and that’s a testament to the strength of the community of writers and readers here on Hashnode. Here's the growth of the number of articles published on the platform, monthly. However, with an increase in scale, we’ve realized that our existing personalized feed wasn’t able to keep up with the explosion of content and didn’t do a great job of surfacing the best content for our readers. So we had to rethink the algorithmic feed from the ground up. https://www.loom.com/share/7884d1739546448c9c315bed72e4a2e1?sid=7b3ce264-e84d-4d8f-8ee0-f09fedc6b1b5 Revamping the personalized feed We studied how feeds in general worked at social media networks, blogging platforms, and other content platforms — and deeply studied the problem at hand. Before sprinkling AI to it, we wanted to get the basics right; which is why we decided to take an approach that is easier to implement and solves our problem at hand faster. From a first principles perspective, we narrowed down on three important parameters that would matter to the reader: Relevance Engagement Quality Let me break those down for you. Relevance You want to see relevant posts, that's the core expectation. The revamped algorithm now takes into account a variety of factors like considering your followed tags, authors, publications, subscriptions, as well as your reading interests, to personalize your feed. We'll look to add more signals to this list in the future to serve you content that you truly resonate with. Engagement We don’t want to just serve you posts that match your interests. We want to bring to you content that is gaining traction in the dev community — through likes, comments, bookmarks, and others — and surface these articles in your feed. In the future, we'll add more social elements to this and find you content that is recommended by your network within Hashnode and on other social media platforms. Quality And the final element in this list is quality. Top authors stand out because of their insights and wisdom gained from real-world experience in the field of tech. These authors take their craft seriously and only publish top content. We now have an added emphasis on a range of factors that include but are not limited to authors who are featured, those who have committed to a custom domain or a pro account, and other factors. We'll continue to look at factors such as whether they have received coveted badges, surpassed milestones, and been contributing their wisdom to the community. The numbers don't lie We put the new algorithm through the paces and the results were pretty telling. Over a month-long A/B test involving 1,000 active users, we found that 80% preferred the new feed. That's a good sign we're on the right track. But numbers only tell part of the story. What truly matters is how these changes are impacting the daily experience of our users. And we're thrilled to say that the feedback has been overwhelmingly positive, especially from some of our most active users. Here's what they have to say: Platform Engineer: 'The feed right now is a lot more to my taste compared to earlier, and the quality of posts is also up.' Sr. Software Engineer: 'I'm seeing more relevant posts by tags and more to my liking. Overall feels much more curated and clickable.' These firsthand accounts reinforce that our efforts are not only improving the numbers but also enhancing the user experience in meaningful ways." Hurdles solved along the way But it wasn’t so easy. Along the way, we faced several technical challenges while trying to build out the feed to make it scalable and make it dynamic. My colleague Florian Fuchs has written about these technical hurdles in great detail. Check out the engineering blog post in case you’re interested in the nitty-gritty details. The Road Ahead There's always room to improve. We'll continue evolving the algorithm after we’ve heard more feedback from writers and readers, and will be exploring AI and machine learning to make things better down the line. Final Thoughts As we navigate the challenges and opportunities of rapid growth, our care for our users remains unchanged. Our recent overhaul of the personalized feed reflects this commitment. We've rebuilt the algorithm from the ground up, focusing on relevance, engagement, and quality as our guiding parameters. The early indicators are promising, with both data and user testimonials supporting the positive impact of these changes. See it in action on the homepage . So as we keep pushing the envelope, we'd love to hear what you think. After all, Hashnode isn't just a platform; it's a community, and communities thrive on dialogue and feedback. Join our Discord to get involved in co-creating Hashnode with us or leave a comment on this post, and I’ll make sure to reply to you. Let’s continue making Hashnode a daily destination for devs. # hashnode # programming # town-hall # product-update # personalized-feed 303 views About the author K Kavir Kaycee Product Leader, writing a product management newsletter https://thediscourse.co • alum: On Deck, ISB Comments Join the discussion No comments yet. Be the first to comment. Product Updates 🚀 Part 10 of 12 Hashnode product updates regarding the web and mobile apps (Android and iOS), and the community. Don't forget to check the changelog for more details! https://feedback.hashnode.com/changelog Up next Launching Discussions: A dedicated space for article comments We see it unfold every day—an insightful article goes live on Hashnode, sparking a flurry of thoughts and inviting readers into a deeper dialogue. Yet, too often, these rich exchanges remain confined, like hidden gems, between the author and an indiv... More from this blog Breaking Apps Hackathon Winners The Breaking Apps Hackathon ran for four weeks, sponsored by Bug0. The brief was simple: write Passmark tests for any web app, then publish a Hashnode article about what you found. The entries made th May 18, 2026 · 2 min read · 391 views Why DIY QA Doesn’t Work Anymore: A 2025 Guide to E2E Testing for Modern Web Apps The Speed Paradox in 2025 Developers are moving faster than ever these days. With tools like Copilot, Cursor, and AI agents, they're shipping production-ready features in just hours - development velocity has reached new heights. But QA? It's still s... Jun 18, 2025 · 6 min read · 414 views ModusHack x Hashnode Winners Hey Hashnoders 🥁 Thank you to everyone who participated in the ModusHack! We were thrilled to see the innovative use of AI in building intelligent apps with Modus, AI models, and Hypermode. Every sub Dec 17, 2024 · 2 min read · 1.2K views Hashnode docs free license for open source projects We have recently launched Docs by Hashnode - the content engine for your API documentation and product guides. We've heard your pain points: Slow builds Complex setups Rigid systems Poor developer experiences And we're tackling them head-on. Yo... Oct 21, 2024 · 2 min read · 400 views [Changelog]: New additions to Docs by Hashnode, new design components and bug fixes. Last week we launched Docs by Hashnode to the public, along with a revamp of the Hashnode homepage. https://x.com/hashnode/status/1836662090905309623 We have received great support from our community and a lot of feedback. Over the last week, we sp... Oct 4, 2024 · 3 min read · 248 views T Town Hall - The official Hashnode blog 209 posts Welcome to the official Hashnode blog. Find our product updates, announcements, interviews, and more here. Get started with Hashnode now .
@@ -0,0 +1 @@
1
+ 85705b2e9a2f28fdaab8cb5feba53e40060c69bc7e65cd99470b25254f523570
@@ -0,0 +1 @@
1
+ Why You Should Republish Your Devblog Posts and How to Do It Updated August 8, 2019 · 0 min read · Markdown M Milica Maksimović On this page Hey there Hashnoders, 👋 If you're just starting as bloggers, it's essential to make sure you build and develop your blog/domain as well as your content right. I have seen so many developers struggle with this topic and make a lot of mistakes along the way, which is why I'm writing this post. Yes, you need to republish your articles and yes, you need to worry about republishing them in a way that won't harm your blog. A lot of people rely on websites such as Hashnode, Medium, HackerNoon, and similar to find the content they need. To reach as many people as possible, it's helpful to republish your posts on these websites as well. In this post, I'll dig into republishing, or content syndication, and show you why you should republish your posts, what it means from the SEO perspective, and help you republish your posts right. By doing this, it will be easier for you to promote your open source projects and share your advice with a larger number of devs. The importance of republishing posts Through Devblog (Hashnode's new blogging platform), you get an instant audience as soon as you hit the publish button, but this number naturally comes down after some time, especially if you don't blog regularly. This is where SEO kicks in. Ideally, you'd want people to find your posts organically through search engines (e.g., Google search), but if your website is not as optimized, your posts won't be showing on top of Google's search results. Moreover, by republishing your posts on other blogging platforms, you'll reach a larger reader base. Not everyone is fond of searching for articles on Google, and a lot of people use native search options on these blogging platforms to discover the posts they want to read. As a fresh blogger, you won't have a lot of domain strength. By having backlinks on websites with strong domains, you'll be improving your domain as well. With each republished post, you'll get a link back to your website, your domain will become stronger, and search engines will favorize your posts over others. All you need to know about the canonical tag To help search engines separate republished posts from your original content, websites use canonical tag. Here's what it looks like in the source code: < link rel = "canonical" href = "https://yourblog.hashnode.dev/your-post" /> Duplicate content is a real issue, and without this HTML tag in the source code of the page, search engines might prioritize content discovered on a website with a stronger domain, and your website ranking can fall down. E.g. If a post is published on Hashnode.com without using the canonical tag, it will most likely reach the top of the search results before the original post, because Hashnode's domain is very strong and the website was indexed several years ago. This is why Hashnode and other publishing platforms enable users to add the canonical tag, or the original URL to a republished post. How to republish posts on Medium with proper canonical tag In order to republish your post on Medium, you have to use their importer. You can't add a canonical URL after you hit publish on your story, so make sure to follow all the steps. Click on your profile picture, and click Stories. Click on "Import a Story" Insert the canonical URL Import the story, and check if the formatting of your article looks good. Click on "Ready to publish" Add tags to your story and make sure to untick the box which will put your content under the Medium's paywall . This will enable all the users to discover the story on Medium, whether they are paying for it or not. That's it, you've successfully republished your post on Medium 👏 How to republish posts on Hackernoon with proper canonical tag To republish a story on Hackernoon you need to log in, and go to your profile . Click on "New Draft" Paste the content of your post Click on "Story Settings" Add the canonical URL in the "First Seen At" box Add tags and the cover photo Submit the story for review The Hackernoon staff will then decide whether they'll feature your post on their platform. How to republish posts on Devto with proper canonical tag To republish posts from your Devblog on Devto you need to: Make sure you're logged in Click on "Write a post" Enter the title and the body of the text. They accept Markdown, so you can simply copy-paste the source text. Click on 3 dots in the top right corner Enter canonical Url and click on "done" Add a cover photo Hit publish That's it, you've properly republished your post 🎉 How to republish your posts on Devblog or Hashnode Some of you might have used other blogging platforms before joining Devblog. To keep all the posts in one place, we strongly recommend you to republish your old posts on Devblog too. Here's how to do it: Make sure you're logged in on Hashnode Click on "Create", then "Write Story" Enter the title and the text Use the right tags, add cover and add the original URL. Make sure to add the post to your publication Hit "Publish", and that's it! You've shared the post with the rest of the Hashnode family! Medium Importer on Devblog If you have used Medium as a blogging platform, you'll be happy to hear that you can import your posts to Devblog in a few clicks. Make sure you're logged in on Hashnode Go to your blog dashboard On the right side, under "Quick Actions" you'll find "Import from Medium" button Insert the link to your original article Check the preview of your post Make any edits if necessary Add the appropriate tags Hit "Publish" and share the post all over the web 🎉 ❌❌❌ Think twice before republishing posts on FreeCodeCamp ❌❌❌ At the time of writing this article, FreeCodeCamp doesn't support canonical URLs. By republishing your posts on their platform, the post on their website will likely rank better than the original one. If you'd still like to republish your articles there, it's recommended to add the following sentence at the top of the article: This post was originally published on - link to your post This is one of the signals that the post is a cross-post, not the original one. Web crawlers might pick it up, but this is not a 100% safe technique and you should be careful not to do this with all of your articles. By adding the canonical tag to republished posts, you'll keep the original article on top of the search results for sure. Conclusion I hope you found the post useful and helpful, and that you will start republishing your Devblog posts from now on. Please let me know in the comments below if there are other Devblog features you'd like me to write a bit more about. ICYMI, Devblog is a new blogging platform for developers built by Hashnode . Blog on your domain hassle-free, reach the right audience, and don't worry about maintenance and keeping up with ever-changing rules of the web. # hashnode # programming # general-advice # devblog 4.7K views About the author M Milica Maksimović I am a marketer in love with tech and building communities around products. My passion is understanding how things work, what people think, and how organizations function. Comments ( 10 ) Join the discussion J Jérémie Tarot (@silopolis) 3y ago Excellent post ! Thanks for sharing :pray: Wondering if LinkedIn support it... J Jb Rocher 5y ago Super duper helpful, thank you very much ! I juste want to point out that the option for setting the canonical URL on DEV has now moved to the bottom of the editing view. It is now accessible by clicking on the little nut thingy :) H Helder S Ribeiro 5y ago Is there a way to automate cross-posting to Devblog from an RSS feed, like on dev.to? Is this in the roadmap? Thank you. 1 M Maxi Contieri 5y ago One year after and this post is still very useful! A Andrew Brown 6y ago freeCodeCamp is a publication you're not supposed to cross-post freeCodeCamp /news is a tech publication, and by design, you cannot cross-post. This makes sense since you're requesting to publish a high-quality article that will be edited and optimized, and publication will give you massive reach. This is not bad, but just simply how their platform works and its why it makes it worth submitting for the publication. DEV is a forum, it's not optimized to respect cross-posting DEV can act as a blog, but it really should be thought of as a forum. If you cross-post to DEV, DEV might respect the canonical URL, but they have a "/comments" page generated off of each article that does not include the article's canonical URL, and this page can rank higher than your article. There is also the uncertainty of DEV's canonical URL being correctly implemented. They use a service worker to update the heading, and I am uncertain if google read the original or the cached header, since google can execute javascript. I have an open ticket on forem/forem and watching it to see if someone else can tell if its working or not. That being said, DEV is a forum, and its "/comments" page is not bad behaviour when you think of it as a forum. However, if your cross-post there that could impact your organic reach. So I do not cross-post my long-form articles on DEV but I focus on watercooler content, which is how the intent of forums. 7 M Michael Fasani 6y ago Thanks for sharing, I just revamped my 15-year-old domain to be my new blog! I was wondering... Do you think you should publish every article on every platform or put them up randomly so that you share different content over these reblogging platforms? M Mohamed Najiullah 7y ago Import from medium to Devblog doesn't seem to work. S Sandeep Panda 7y ago Can you share the URL of the Medium post you are trying to import? M Mohamed Najiullah 7y ago These two https://medium.com/@mohammed.najiullah/configuring-google-container-registry-gcr-as-an-artifact-store-in-gocd-5453f8037e8c https://medium.com/@mohammed.najiullah/configuring-go-agents-in-gocd-in-kubernetes-static-and-elastic-agents-c5dbf5f6a01d M Michaela Greiler 7y ago Milica Maksimović , this is such a great article! Thank you for sharing it with the dev community. I also really appreciate the attitude Hashnode has for its contributors. You always make sure that it is a win-win situation. Making everybody aware of the canonical url and its impact is so important. Otherwise, people cannot really build up their own platform. Thank you! 14 M Milica Maksimović 7y ago Thank you for your comment Michaela Greiler ! We're always here to offer help and guidance to our contributors! 5 M Marvin Kweyu 7y ago Could I get some more clarity on the canonical URL? M Milica Maksimović 7y ago Can you be a bit more specific? Which part is giving you headache? M Marvin Kweyu 7y ago So I got the canonical url. It works when I open it up in browser. Unfortunaltely,Devto marks this as an invalid URL..To clear my doubts about my copy paste, I tried it out in the URL code tool and pasted it once more..I get the same message. M Milica Maksimović 7y ago Can you please share the link to the article you've republished on devto? I have no issues with the article I've republished there, the canonical has been taken care of automatically. Also, did you follow all the instructions for republishing on devto? M Marvin Kweyu 7y ago So the link to my Devblog is something like: https://marvin.hashnode.dev/getting-started-as-a-junior-software-developer-cjxeqtshl000jx6s1p0ilg70k This would make my canonical URL: <link rel="canonical" href="https://marvin.hashnode.dev/getting-started-as-a-junior-software-developer-cjxeqtshl000jx6s1p0ilg70k" /> It won't go past the post page because of the invalid URL. S Syed Fazle Rahman 7y ago Don't paste the code, just paste the URL. 2 M Marvin Kweyu 7y ago Worked like a charm..Must've been blind earlier S Syed Fazle Rahman 7y ago I am glad that helped. :) B Bayu Angora 7y ago How do we know which website that support canonical or not? M Milica Maksimović 7y ago Do you have any specific website in mind? If they are manually republishing your post, you need to request them to add the canonical tag to it. B Bayu Angora 7y ago Just mention several platform I use such Tumblr, Minds, Gab, etc. I usually use view-sorce to inspect it, but I just curious if there any efficient method without asking them first. M Milica Maksimović 7y ago As far as I know, Tumblr allows you to republish articles, you need to add the canonical URL in the "Content source" field. As for the rest, I guess you'll have to do a bit research on your own, I'm not familiar with the platforms you've mentioned. More from this blog Breaking Apps Hackathon Winners The Breaking Apps Hackathon ran for four weeks, sponsored by Bug0. The brief was simple: write Passmark tests for any web app, then publish a Hashnode article about what you found. The entries made th May 18, 2026 · 2 min read · 391 views Why DIY QA Doesn’t Work Anymore: A 2025 Guide to E2E Testing for Modern Web Apps The Speed Paradox in 2025 Developers are moving faster than ever these days. With tools like Copilot, Cursor, and AI agents, they&#x27;re shipping production-ready features in just hours - development velocity has reached new heights. But QA? It&#x27;s still s... Jun 18, 2025 · 6 min read · 414 views ModusHack x Hashnode Winners Hey Hashnoders 🥁 Thank you to everyone who participated in the ModusHack! We were thrilled to see the innovative use of AI in building intelligent apps with Modus, AI models, and Hypermode. Every sub Dec 17, 2024 · 2 min read · 1.2K views Hashnode docs free license for open source projects We have recently launched Docs by Hashnode - the content engine for your API documentation and product guides. We&#x27;ve heard your pain points: Slow builds Complex setups Rigid systems Poor developer experiences And we&#x27;re tackling them head-on. Yo... Oct 21, 2024 · 2 min read · 400 views [Changelog]: New additions to Docs by Hashnode, new design components and bug fixes. Last week we launched Docs by Hashnode to the public, along with a revamp of the Hashnode homepage. https://x.com/hashnode/status/1836662090905309623 We have received great support from our community and a lot of feedback. Over the last week, we sp... Oct 4, 2024 · 3 min read · 248 views T Town Hall - The official Hashnode blog 209 posts Welcome to the official Hashnode blog. Find our product updates, announcements, interviews, and more here. Get started with Hashnode now .
@@ -0,0 +1 @@
1
+ 5dce92367fe029033ff98cb38630338bcb141fc5cfe15558516be06e615d43a5
@@ -0,0 +1 @@
1
+ c9535b5d0d75ac0ec2cbdea8c56a27a49091544a
@@ -0,0 +1 @@
1
+ aab090beaa41fa485bfdb4ff30afe48485b70e050cc91d9c298297d0e2edce14
@@ -0,0 +1 @@
1
+ Hacker News FAQ Are there rules about submissions and comments? https://news.ycombinator.com/newsguidelines.html How are stories ranked? The basic algorithm divides points by a power of the time since a story was submitted. Comments in threads are ranked the same way. Other factors affecting rank include user flags, anti-abuse software, software which demotes overheated discussions, account or site weighting, and moderator action. How is a user's karma calculated? Roughly, the number of upvotes on their posts minus the number of downvotes. These don't match up exactly. Some votes are dropped by anti-abuse software. Do posts by users with more karma rank higher? No. Why don't I see down arrows? There are no down arrows on stories. They appear on comments after users reach a certain karma threshold, but never on direct replies. Why do I see an orange/red asterisk? It just means it's your own post. Why are my links grey instead of black like other links? It means you've visited it before. If you click on a black link it will turn grey. What kind of formatting can you use in comments? http://news.ycombinator.com/formatdoc How do I submit a question? Use the submit link in the top bar, and leave the url field blank. How do I submit a poll? http://news.ycombinator.com/newpoll How do I make a link in a text submission? You can't. This is to prevent people from submitting a link with their comments in a privileged position at the top of the page. If you want to submit a link with comments, just submit the link, then add a regular comment. What are Ask HN and Show HN? Ask HN lists questions and other text submissions. Show HN is for sharing your personal work and has special rules . Why hasn't my submission appeared on Ask HN or Show HN? All Ask HNs appear on newest and asknew , and all Show HNs on newest and shownew , but there is a small points threshold before a post makes it to ask or show . What do green usernames mean? Green indicates a new account. Why are some comments faded? Faded text means that a comment has been downvoted. You can read the comment in normal text by clicking on its timestamp to go to its page. What does [flagged] mean? Users flagged the post as breaking the guidelines or otherwise not belonging on HN. Moderators sometimes also add [flagged] (though not usually on submissions), and sometimes turn flags off when they are unfair. How do I flag a comment? Click on its timestamp to go to its page, then click the 'flag' link at the top. There's a small karma threshold before flag links appear. What does [dead] mean? The post was killed by software, user flags, or moderators. Dead posts aren't displayed by default, but you can see them all by turning on 'showdead' in your profile. If you see a [dead] post that shouldn't be dead, you can vouch for it. Click on its timestamp to go to its page, then click 'vouch' at the top. When enough users do this, the post is restored. There's a small karma threshold before vouch links appear. What does [deleted] mean? The author deleted the post, or asked us to. Unlike dead posts, these remain deleted even when showdead is turned on. What do 'hide' links do? They remove a submission from your personal view. Others still see it. Are reposts ok? If a story has not had significant attention in the last year or so, a small number of reposts is ok. Otherwise we bury reposts as duplicates. Please don't delete and repost the same story. Deletion is for things that shouldn't have been submitted in the first place. Are paywalls ok? It's ok to post stories from sites with paywalls that have workarounds. In comments, it's ok to ask how to read an article and to help other users do so. But please don't post complaints about paywalls. Those are off topic . More here . Can I ask people to upvote my submission? No. Users should vote for a story because they personally find it intellectually interesting, not because someone has content to promote. We penalize or ban submissions, accounts, and sites that break this rule, so please don't. Can I ask people to comment on my submission? No, for the same reason. It's also not in your interest: HN readers are sensitive to this and will detect it, flag it, and use unkind words like 'spam'. Can I post a job ad? Please don't post job ads as submissions to HN. A regular "Who Is Hiring?" thread appears on the first weekday of each month (or Jan 2). Most job ads are welcome there. Only an account called whoishiring is allowed to submit the thread itself. This prevents a race to post it first. Another kind of job ad is reserved for YC-funded startups. These appear on the front page, but are not stories: they have no vote arrows, points, or comments. They begin partway down and fall steadily. Only one is on the front page at a time. The rest are listed at jobs . What's the relationship between YC and HN? Y Combinator owns and funds HN. The HN team is editorially independent . HN gives three features to YC: job ads (see above ) and startup launches get placed on the front page, and YC founder names are displayed to other YC alumni in orange. Are negative stories about YC suppressed on HN? We moderate less, not more , when YC or a YC startup is the topic. The good will of the community is worth more than any story. Why can't I post a comment to a thread? Threads are closed to new comments after two weeks, or if the submission has been killed by software, moderators, or user flags. Why is A ranked below B even though A has more points and is newer? You can't derive rank from votes and time alone. See "How are stories ranked?" above. In my profile, what is delay? It gives you time to edit your comments before they appear to others. Set it to the number of minutes you'd like. The maximum is 10. In my profile, what is noprocrast? It's a way to help you prevent yourself from spending too much time on HN. If you turn it on you'll only be allowed to visit the site for maxvisit minutes at a time, with gaps of minaway minutes in between. The defaults are 20 and 180, which would let you view the site for 20 minutes at a time, and then not allow you back in for 3 hours. How do I reset my password? If you have an email address in your profile, you can do that here . If you haven't, email hn@ycombinator.com for help. Can I change my username? Yes. Email hn@ycombinator.com and we'll help. Can I delete my account? We try not to delete entire account histories because that would gut the threads the account had participated in. However, we care about protecting individual users and take care of privacy requests every day, so if we can help, please email hn@ycombinator.com. We don't want anyone to get in trouble from anything they posted to HN. More here . My IP address seems to be banned. How can I unban it? If you request many pages quickly, your IP address might get banned. This self-serve unbanning procedure works most of the time. If not, email hn@ycombinator.com.
@@ -0,0 +1 @@
1
+ 2694b0fec83a856a57a2d22ae1f1288f7d335593bce7c9a13f4992145b378060
@@ -0,0 +1 @@
1
+ Hacker News Guidelines What to Submit On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity. Off-Topic: Most stories about politics, or crime, or sports, or celebrities, unless they're evidence of some interesting new phenomenon. If they'd cover it on TV news, it's probably off-topic. In Submissions Please don't do things to make titles stand out, like using uppercase or exclamation points, or saying how great an article is. Please submit the original source. If a post reports on something found on another site, submit the latter. Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity. Please don't put generated text in HN posts. Write your text yourself&mdash;HN is for sharing between humans. For the same reason, please don't automate posting. If the title includes the name of the site, please take it out, because the site name will be displayed after the link. If the title contains a gratuitous number or number + adjective, we'd appreciate it if you'd crop it. E.g. translate "10 Ways To Do X" to "Ways To Do X," and "14 Amazing Ys" to "Ys." Exception: when the number is meaningful, e.g. "The 5 Platonic Solids." Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize. If you submit a video or pdf, please warn us by appending [video] or [pdf] to the title. Please don't post on HN to ask or tell us something. Send it to hn@ycombinator.com. Please don't delete and repost. Deletion is for things that shouldn't have been submitted in the first place. Don't solicit upvotes, comments, or submissions. Users should vote and comment when they run across something they personally find interesting&mdash;not for promotion. In Comments Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes. Comments should get more thoughtful and substantive, not less, as a topic gets more divisive. When disagreeing, reply to the argument instead of calling names. "That is idiotic; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3." Don't be curmudgeonly. Thoughtful criticism is fine, but please don't be rigidly or generically negative. Don't post generated text or AI-edited text. HN is for conversation between humans. Please don't fulminate. Please don't sneer, including at the rest of the community. Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith. Eschew flamebait. Avoid generic tangents. Omit internet tropes. Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. Please don't use Hacker News for political or ideological battle. It tramples curiosity. Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that". Please don't pick the most provocative thing in an article or post to complain about in the thread. Find something interesting to respond to instead. Throwaway accounts are ok for sensitive information, but please don't create accounts routinely. HN is a community&mdash;users should have an identity that others can relate to. Please don't use uppercase for emphasis. Instead, put *asterisks* around it and it will get italicized. More formatting info here . Please don't post insinuations about astroturfing, shilling, brigading, foreign agents, and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data. If a story is spam or off-topic, flag it. Don't feed egregious comments by replying; flag them instead. If you flag, please don't also comment that you did. Please don't complain about tangential annoyances&mdash;e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting. Please don't comment about the voting on comments. It never does any good, and it makes boring reading. Please don't post comments saying that HN is turning into Reddit. It's a semi - noob illusion , as old as the hills .
@@ -0,0 +1 @@
1
+ 9c35aeb91962a93cea0cb83f975b5b1b513047ca38e90af31effced4e0d415a0
@@ -0,0 +1 @@
1
+ Show HN Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread. On topic: things people can run on their computers or hold in their hands. For hardware, you can post a video or detailed article. For books, a sample chapter is ok. Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material. Those can't be tried out, so can't be Show HNs. Make a regular submission instead. The project should be non-trivial. Don't post quickly-generated one-offs; anybody can do that now. Share something that is deeply personal and interesting to you. Explain how and why. The project must be something you've worked on personally and which you're around to discuss. See these tips about how to present your work. A Show HN needn't be complicated or look slick. The community is comfortable with work that's at an early stage. Please make it easy for users to try your thing out, ideally without barriers such as signups or emails. You'll get more feedback that way. If your work isn't ready for users to try out, please don't do a Show HN. Once it's ready, come back and do it then. Don't post landing pages or fundraisers. To post, submit a story whose title begins with "Show HN". Every Show HN appears on shownew . Once it clears a small points threshold, it will appear on the show page in the top bar. New features and upgrades ("Foo 1.3.1 is out") generally aren't substantive enough to be Show HNs. A major overhaul is probably ok. Please don't ask friends to upvote or comment. That's not ok on HN. In Comments Be respectful. Anyone sharing work is making a contribution, however modest. Ask questions out of curiosity. Don't cross-examine. Instead of "you're doing it wrong", suggest alternatives. When someone is learning, help them learn more. When something isn't good, you needn't pretend that it is, but don't be gratuitously negative.
@@ -0,0 +1 @@
1
+ 4f1aa93a680838f2b9c099150146ef078802e05bd2ab907b5ba2e45bb089850b
@@ -0,0 +1 @@
1
+ 56e0d6fbd7fbaa4f668ac940b95089347d1f274e
@@ -0,0 +1 @@
1
+ 712bf7d85032b6ed168f50e385e266a7d32a9f24a86691333475059f4e34f53b
@@ -0,0 +1 @@
1
+ Instagram Ranking Explained By Adam Mosseri May 31, 2023 We want to do a better job of explaining how Instagram works. There are a lot of misconceptions out there, and we recognize that we can do more to help people, especially creators, understand what we do. Today, we’re updating our original post to shed more light on how ranking works across Instagram and share some new features we’ve built in response to feedback from creators that help improve the experiences people have across the app overall. Ranking on Instagram We want to share more on how ranking works across Instagram to help people maximize their experience and help creators understand how their content might be surfaced. Instagram doesn’t have a singular algorithm that oversees what people do and don’t see on the app. We use a variety of algorithms, classifiers, and processes, each with its own purpose. We want to make the most of people’s time, and we believe that using technology to personalize everyone’s experience is the best way to do that. Each part of the app – Feed, Stories, Explore, Reels, Search and more – uses its own algorithm tailored to how people use it. People tend to look for their closest friends in Stories, use Explore to discover new content and creators and be entertained in Reels. We rank things differently in these different parts of the app, and have added features and controls like Close Friends, Favorites and Following so you can further customize your experience. How we rank Feed Feed is your personalized home base within Instagram to help you catch up with friends, family, and interests. This means your feed will have a mix of content from the accounts you’ve chosen to follow, recommended content from accounts we think you’ll enjoy and ads. You’ll also see a mixture of videos, photos and carousels. With any ranking algorithm, how it works can be broken down into steps. We start by defining the set of things we plan to rank in the first place. With Feed we consider recent posts shared by the people you follow, as well as posts from accounts you don’t already follow that we think you might be interested in. We determine what you might be interested in based on a variety of factors, including what and whom you’ve followed, liked or engaged with recently. We personalize the experience for you to try to strike a balance between content from accounts you follow with content from accounts you don’t follow but might be interested in. Next we take all the information we have about what was posted, the people who made those posts, and your preferences. We’ve also started considering other factors like format, so if we notice you prefer photos, we’ll show you more photos. We call these “signals,” and there are thousands of them. They include everything from when a post was shared to whether you’re using a phone or the web to how often you like videos. The most important signals across Feed, roughly in order of importance, are: Your activity. Posts you’ve liked, shared, saved or commented on help us understand what you might be interested in. Information about the post. These are signals both about how popular a post is – think how many people have liked it and how quickly people are liking, commenting, sharing and saving a post – and more mundane information about the content itself, like when it was posted, and what location, if any, was attached to it. Information about the person who posted. This helps us get a sense for how interesting the person might be to you, and includes signals like how many times people have interacted with that person in the past few weeks. Your history of interacting with someone. This gives us a sense of how interested you are generally in seeing posts from a particular person. An example is whether or not you comment on each other’s posts. From there we make a set of predictions. These are educated guesses at how likely you are to interact with a post in different ways. There are roughly a dozen of these. In Feed, the five interactions we look at most closely are how likely you are to spend a few seconds on a post, comment on it, like it, share it, and tap on the profile photo. The more likely you are to take an action, and the more heavily we weigh that action, the higher up in Feed you’ll see the post. We add and remove signals and predictions over time, working to get better at surfacing what you’re interested in. There are a few cases where we try to take other considerations into account. One example of this is where we try to avoid showing too many posts from the same person in a row, or too many suggested posts back to back. We always want to lean towards letting people express themselves, but when someone posts something that may jeopardize another person’s safety, we step in. We have Community Standards that apply not only to Feed, but to all of Instagram. These rules are focused on keeping people safe. If you post something that goes against our Community Standards and we find it, we take it down. If this happens repeatedly, we may prevent you from using certain sharing features, such as streaming on Instagram Live, and eventually we might suspend your account. If you think we’ve made a mistake – and we do make mistakes – you can appeal by following these steps . How we rank Stories Stories are a way to share everyday moments and grow closer to the people and interests you care about. The stories you see are from people you’ve chosen to follow, as well as ads. Similar to Feed, when we look at ranking stories we start by defining all of the potential stories – excluding advertisements – shared by accounts you follow, and remove any stories that violate our Community Standards . We then look at a variety of input signals such as: Viewing history. This looks at how often you view an account’s stories so we can prioritize the stories from accounts we think you don’t want to miss. Engagement history. This looks at how often you engage with that account’s stories, such as sending a like or a DM. Closeness. This looks at your relationship with the author overall and how likely you are to be connected as friends or family. Based on these signals, we make a series of predictions about stories you’ll find more relevant and valuable – including how likely you are to tap into a story, reply to a story or move on to the next story – to determine which stories will be shown higher in your stories tray. Our Community Standards apply here as well. How we rank Explore Explore was designed to help you discover new things. The grid is made up of recommendations – photos and videos that we go out and find for you from accounts you don’t yet follow. Again, the first step we take is defining a set of posts to rank. To find photos and videos you might be interested in, we look at past activity such as posts you’ve liked, saved, shared and commented on in the past. Once we’ve found a group of photos and videos you might be interested in, we then order them by how interested we think you are in each one, much like how we rank Feed and stories. The best way to guess how interested you are in something is to predict how likely you are to do something with the post. The most important actions we predict in Explore include likes, saves, and shares. The most important signals we look at, in rough order of importance, are: Information about the post. Here we are looking at how popular a post seems to be. These are signals like how many and how quickly other people are liking, commenting, sharing, and saving a post. These signals matter much more in Explore than they do in Feed or in Stories. Your activity in Explore. These are signals like posts you’ve liked, saved, shared or commented on and how you’ve interacted with posts in Explore in the past. If you interact with a specific type of post, we try to show you more content similar to the original post you interacted with. Your history of interacting with the person who posted. Most likely the post was shared by someone you’ve never heard of, but if you have interacted with them that gives us a sense of how interested you might be in what they shared. Information about the person who posted. These are signals like how many times people have interacted with that person in the past few weeks, to help find compelling content from a wide array of people. Most of the content you’ll see in Explore is from people you don’t follow, which changes the dynamic when you come across something problematic. If a friend you follow shares something offensive and you see that in your Feed, that’s between you and your friend (and you have the option to unfollow, block, mute, hide or report that person if you choose). However, we want to reduce the possibility of you seeing something offensive in Explore, since that is content we recommend to you from people you haven’t yet chosen to follow. That’s why, in addition to our Community Standards , we have rules for what we recommend in places like Explore, Reels, Search, Suggested Posts in Feed and Suggested Accounts. We call these our Recommendations Guidelines. Posts that go against our Recommendation Guidelines are allowed on Instagram, but some people may consider them sensitive or offensive. For example, we aim to not recommend things like content depicting violence, such as people fighting, or content depicting the use of certain regulated products, such as tobacco, vaping products, or pharmaceutical drugs. If someone’s post goes against our Recommendation Guidelines , we try to avoid showing that post where we recommend content. If an account repeatedly posts content that goes against our Recommendation Guidelines or Community Standards , none of their posts will be eligible for recommendation for a period of time. Account Status is the best way to understand if your account and content is eligible to be recommended on Instagram – you can read more about Account Status in the sections below. Over the years, we have added new controls so you can influence the types of content we recommend to you – like the Sensitive Content Control and ability to indicate “Not Interested” next to posts – you can read more about these controls in the sections below. How we rank Reels Reels are also designed to help you discover new things, with an emphasis on entertainment. Much like Explore, the majority of what you see is from accounts you don’t follow. So we go through a very similar process where we first source reels we think you might like, then order them based on how interesting we think they are to you. In order to find entertaining reels, we survey people and ask whether they find a particular reel worth their time or fun, and learn from the feedback to get better at figuring out what will entertain people. The most important predictions we make are how likely you are to reshare a reel, watch a reel all the way through, like it, and go to the audio page (a proxy for whether or not you might be inspired to make your own reel.) The most important signals, roughly in order of importance, are: Your activity. We look at things like which reels you’ve liked, saved, reshared, commented on, and engaged with recently. These signals help us understand what content might be relevant to you. Your history of interacting with the person who posted. As with Explore, it’s likely the video was made by someone you’ve never heard of, but if you have interacted with them, that gives us a sense of how interested you might be in what they shared. Information about the reel. These are signals about the content within the video such as the audio track or visuals in the video, as well as popularity. Information about the person who posted. We consider popularity signals such as number of followers or level of engagement to help find compelling content from a wide array of people and give everyone a chance to find their audience. The same Recommendation Guidelines that apply to Explore apply to reels. We aim to make certain reels less visible for other reasons, such as low-resolution or watermarked reels, reels that are muted or contain borders, reels that are majority text, or reels that have already been posted on Instagram. How you can influence what you see How you use Instagram heavily influences the things you see and don’t see. You help improve the experience simply by interacting with the profiles and content you enjoy, but there are a few more explicit things you can do to influence what you see. Personalize your Feed and Stories Add accounts to your Favorites list to make sure you don’t miss their content. New posts from your Favorites will appear higher in your Feed. You can also customize your feed to only show content from your Favorites or from accounts you follow (Following will show you the last 30 days of posts from those you follow in chronological order). If you just want a break from recommendations, you can also snooze all suggested posts in your feed for 30 days. Learn more here . Pick your Close Friends. You can select your close friends for Stories. This was designed as a way to let you share with just the people closest to you. Mute people you’re not interested in. You can mute an account’s Feed posts, Stories , Messages , or Notes if you’d like to stop seeing what they share, but are hesitant about unfollowing them entirely. This way, people don’t know you’ve muted them. To stop seeing posts from an account, you can unfollow that account at any time. People won’t be notified when you unfollow them. Respond to surveys from Instagram. We send surveys to people asking “is this post worth your time?” and use learnings from these surveys to help improve our recommendations overall. Improve your Recommendations Adjust the Sensitive Content Control if you want to see more or less of some types of sensitive content from accounts you don’t follow. The “more” option is not available for people under the age of 18. Though we do our best to recommend content that we think you’ll be interested in, we don’t always get it right. To help us improve, you can indicate "Not Interested" on a recommended post so we can show you less of what you don’t like. We are also testing an option for you to indicate “ Interested” on a recommended post, so we can show you more of what you do like. Proactively hide suggested posts with captions that contain words, phrases or emojis you don’t want to see. Report content you think violates our policies, using our reporting tool . You can report any post or profile on Instagram. This signal can help us move similar content lower across all Instagram surfaces. Lastly, if you’re ever curious why you’re seeing specific content, you can tap the three dots in the upper right corner next to the content, then tap “Why you’re seeing this post/ad”. We will then list some of the signals used for showing that content to you. Addressing “Shadowbanning” Lastly, we want to address the feedback we hear around “shadowbanning”. We’ve had a lot of direct conversations with our community to better understand what people mean by the term “shadowbanning.” Though there isn’t one shared definition, we know some people use the term to imply that a user’s account or content is limited or hidden without a clear explanation or justification. When we rank content across Instagram, that’s not our intention. Contrary to what you might have heard, it’s in our interest as a business to ensure that creators are able to reach their audiences and get discovered so they can continue to grow and thrive on Instagram. If there is an audience that is interested in what you share, then the more effectively we help that audience see your content, the more they will use our platform. While we’ve heard some people believe you need to pay for ads to achieve better reach, we don’t suppress content to encourage people to buy ads. It’s a better business to make Instagram more engaging overall by growing reach for those who create the most engaging content, and sell ads to others. The community’s concerns about “shadowbanning” have made it clear that there is more we can do to increase transparency so people have more information about what’s going on with their account. If anything makes your content less visible, you should know about it and be able to appeal. That’s why we’ve built features like Account Status to help you understand why your account’s content may not be eligible to be recommended, allow you to delete any content affecting your account, and appeal the decision if you think we made a mistake. We’re continuing to invest in Account Status to bring more transparency to our community. For instance, we recently added the ability to see if your account is eligible to appear in Search or as a suggested account, and you can appeal if it’s not. We plan to add even more transparency to this surface over time, so stay tuned. We’re always exploring ways we can help creators understand why certain content, like reels, aren’t getting as much distribution to non-followers. We’re experimenting with new notifications to help creators understand when the reach of their reel may be limited due to a watermark, and plan to expand to more people as we learn what’s most effective. As we continue to build more tools to help people understand and address issues that may be impacting their reach, we’ve been working on more resources to help our community understand our ranking, guidelines and best practices. Check out our new resource for improving your reach across Instagram , learn from other creators in our Creator Lab , and learn even more details about ranking with our interactive site . In addition to staying tuned to our Blog for posts like this one, make sure you follow @creators and @mosseri for the latest and greatest tools and tips. We want people and creators to be in control of their Instagram experience, and we’re always exploring ways to add even more transparency and control to the app. Providing more context on how content is ranked and moderated on Instagram is only part of the equation and we will continue to provide ranking updates as our systems evolve. RELATED ARTICLES Check out more announcements about safety #PRODUCT #ANNOUNCEMENTS Instagram on iPhone Duo: more room for what you love #CREATORS #ANNOUNCEMENTS Close Friends Only: Kai Cenat & Kaiya on VIVET #PRODUCT #ANNOUNCEMENTS New Effects in Stories from Meta AI View More
@@ -0,0 +1 @@
1
+ eb3d1def783409bb450d478cbf18dd285b6795179c7e9db5cc52708be6e20194
@@ -0,0 +1 @@
1
+ Back to Newsroom Meta Our Approach to Labeling AI-Generated Content and Manipulated Media April 5, 2024 October 23, 2025 By Monika Bickert, Vice President of Content Policy Listen to Article 10 Pause 10 0.25× 0.5× 1× 1.25× 1.5× 2× Takeaways We are making changes to the way we handle manipulated media based on feedback from the Oversight Board and our policy review process with public opinion surveys and expert consultations. We will begin adding “AI info” labels to a wider range of video, audio and image content when we detect industry standard AI image indicators or when people disclose that they’re uploading AI-generated content. ( Updated on July 1, 2024 to reflect the revised label ) We agree with the Oversight Board’s recommendation that providing transparency and additional context is now the better way to address manipulated media and avoid the risk of unnecessarily restricting freedom of speech, so we’ll keep this content on our platforms so we can add labels and context. Update on September 12, 2024 at 7:30AM PT: Soon we’re rolling out a change to the “AI info” labels on our platforms so they better reflect the extent of AI used in content. Our intent has always been to help people know when they see content that was made with AI, and we’ve continued to work with companies across the industry to improve our labeling process so that labels on our platforms are more in line with peoples’ expectations. For content that we detect was only modified or edited by AI tools, we are moving the “AI info” label to the post’s menu. We will still display the “AI info” label for content we detect was generated by an AI tool and share whether the content is labeled because of industry-shared signals or because someone self-disclosed. These changes will begin next week. Update on July 1, 2024 at 7:00AM PT: We want people to know when they see posts that have been made with AI. Earlier this year, we announced a new approach for labeling AI-generated content. An important part of this approach relies on industry standard indicators that other companies include in content created using their tools, which help us assess whether something is created using AI. Like others across the industry, we’ve found that our labels based on these indicators weren’t always aligned with people’s expectations and didn’t always provide enough context. For example, some content that included minor modifications using AI, such as retouching tools, included industry standard indicators that were then labeled “Made with AI.” While we work with companies across the industry to improve the process so our labeling approach better matches our intent, we’re updating the “Made with AI” label to “AI info” across our apps, which people can click for more information. Originally published on April 5, 2024 at 7:00AM PT: We are making changes to the way we handle manipulated media on Facebook, Instagram and Threads based on feedback from the Oversight Board that we should update our approach to reflect a broader range of content that exists today and provide context about the content through labels. These changes are also informed by Meta’s policy review process that included extensive public opinion surveys and consultations with academics, civil society organizations and others. We agree with the Oversight Board’s argument that our existing approach is too narrow since it only covers videos that are created or altered by AI to make a person appear to say something they didn’t say. Our manipulated media policy was written in 2020 when realistic AI-generated content was rare and the overarching concern was about videos. In the last four years, and particularly in the last year, people have developed other kinds of realistic AI-generated content like audio and photos, and this technology is quickly evolving. As the Board noted, it’s equally important to address manipulation that shows a person doing something they didn’t do. The Board also argued that we unnecessarily risk restricting freedom of expression when we remove manipulated media that does not otherwise violate our Community Standards. It recommended a “less restrictive” approach to manipulated media like labels with context. In February, we announced that we’ve been working with industry partners on common technical standards for identifying AI content , including video and audio. Our “Made with AI” labels on AI-generated video, audio and images will be based on our detection of industry-shared signals of AI images or people self-disclosing that they’re uploading AI-generated content. We already add “Imagined with AI” to photorealistic images created using our Meta AI feature. We agree that providing transparency and additional context is now the better way to address this content. The labels will cover a broader range of content in addition to the manipulated content that the Oversight Board recommended labeling. If we determine that digitally-created or altered images, video or audio create a particularly high risk of materially deceiving the public on a matter of importance, we may add a more prominent label so people have more information and context. This overall approach gives people more information about the content so they can better assess it and so they will have context if they see the same content elsewhere. We will keep this content on our platforms so we can add informational labels and context, unless the content otherwise violates our policies. For example, we will remove content, regardless of whether it is created by AI or a person, if it violates our policies against voter interference, bullying and harassment, violence and incitement, or any other policy in our Community Standards. We also have a network of nearly 100 independent fact-checkers who will continue to review false and misleading AI-generated content. When fact-checkers rate content as False or Altered, we show it lower in Feed so fewer people see it, and add an overlay label with additional information. In addition, we reject an ad if it contains debunked content, and since January, advertisers have to disclose when they digitally create or alter a political or social issue ad in certain cases. We plan to start labeling organic AI-generated content in May 2024, and we’ll stop removing content solely on the basis of our manipulated video policy in July. This timeline gives people time to understand the self-disclosure process before we stop removing the smaller subset of manipulated media. (Updated on May 10, 2024 at 6:00 AM PT to clarify this applies to organic content.) Policy Process Informed By Global Experts and Public Surveys In Spring 2023, we began reevaluating our policies to see if we needed a new approach to keep pace with rapid advances in generative AI technologies and usage. We completed consultations with over 120 stakeholders in 34 countries in every major region of the world. Overall, we heard broad support for labeling AI-generated content and strong support for a more prominent label in high-risk scenarios. Many stakeholders were receptive to the concept of people self-disclosing content as AI-generated. A majority of stakeholders agreed that removal should be limited to only the highest risk scenarios where content can be tied to harm, since generative AI is becoming a mainstream tool for creative expression. This aligns with the principles behind our Community Standards – that people should be free to express themselves while also remaining safe on our services. We also conducted public opinion research with more than 23,000 respondents in 13 countries and asked people how social media companies, such as Meta, should approach AI-generated content on their platforms. A large majority (82%) favor warning labels for AI-generated content that depicts people saying things they did not say. Additionally, the Oversight Board noted their recommendations were informed by consultations with civil-society organizations, academics, inter-governmental organizations and other experts. Based on feedback from the Oversight Board, experts and the public, we’re taking steps we think are appropriate for platforms like ours. We want to help people know when photorealistic images have been created or edited using AI, so we’ll continue to collaborate with industry peers through forums like the Partnership on AI and remain in a dialogue with governments and civil society – and we’ll continue to review our approach as technology progresses. Categories : Meta Public Policy Tags: AI DOWNLOAD ALL IMAGES Share this article Recent News Advancing Science Together: Highlights From the Open Source AI For Science Summit Introducing Direct: An App Just for Messaging Meta’s New Agreements Bring Clean Manufacturing to Data Center Supply Chains Expanding Teen Account Protections to Teens Around the World Related News Meta How Meta Is Preparing for the 2026 US Midterm Elections February 19, 2026 October 27, 2026
@@ -0,0 +1 @@
1
+ 7bde576989bfb436b200f21e7589c88a3c61d794eb013979b89e32df64a40696
@@ -0,0 +1 @@
1
+ Logo is created using Fira Code , used under the OFL-1.1 Legal Site: https://legal.programming.dev
@@ -0,0 +1 @@
1
+ 40b5410dfdb64c747d570921cf8c883957457bb9e7aef00ffc75f5c00e0267ba
@@ -0,0 +1 @@
1
+ Recommended posts in feed Last updated: 4 weeks ago LinkedIn will recommend posts in your feed that we believe you might find valuable and relevant. These posts may be from people you don&rsquo;t follow or aren&rsquo;t connected to, but that we offer as professionally relevant. You may see social context such as Followed by [name] when one of your connections follows or is connected to the author. You may also see an option to Follow or Connect with the author. How we select recommended content We rely on a variety of signals to select content and decide to whom to display such content. Below are some of the influential signals we rely on when selecting this content: High quality professionally relevant content: Our goal is to suggest to members content that is professionally relevant and high quality, including content discussing: Professional growth, development, and education; Being inspired at work; Professional products or services; and Education on professional topics (e.g., economics or technology). Relevant to all members: When recommending content outside the author&rsquo;s network, we try to only serve content that is valuable and relevant to those outside of the original poster&rsquo;s network by, for example, ensuring it provides sufficient context, isn&rsquo;t overly promotional, and has related elements such as text, images, and video. Feedback: We consider member feedback, including through mechanisms like member disinterest signals and reports about content. We may also review some content to confirm that it is high-quality and professionally relevant. How we deliver Suggested content to you We recommend professionally relevant news and information from a pool of content selected using signals such as those described above. From that pool of content, we also do our best to ensure the recommended content served to you is relevant to you, using information about you and your activity, including: Your previous interactions with content, such as comments, reactions, and time spent on the platform Your profile information, such as job title, profile location, and industry; and How likely you are to engage with the content Your controls over content If you see a post in your feed that you don&rsquo;t think is relevant or useful, you can hide it and provide feedback to help improve your feed experience. Select the More icon on the post and choose the applicable option. Doing so will prevent that specific post from appearing in your feed again. Learn more Hide content in your feed LinkedIn feed - Overview Manage your LinkedIn feed preferences Tagged in Post Related articles Get started with boosting posts on LinkedIn Boost your own LinkedIn post FAQ Edit or delete a boosted post from your LinkedIn profile
@@ -0,0 +1 @@
1
+ d812d5a73ceec39a8efb841372af00130a9856394fc804a4cf8a0327a8536a27
@@ -0,0 +1 @@
1
+ Share videos on LinkedIn Last updated: 2 years ago Important to know Currently, it is not possible to directly add or post videos to the immersive video feed. The immersive video feed features content based on the quality and relevance of existing videos on LinkedIn. You can share videos with your network using the share box at the top of the LinkedIn homepage, a Group, or a LinkedIn Page. Desktop Mobile To share a video: Click the Video icon in the share box at the top of your LinkedIn homepage. Here's a tip You can also directly drag and drop or copy and paste a video into the share box. Click Upload from computer to select a file. After uploading a video, you can: Video thumbnail : Select Video thumbnail to Upload video thumbnail for your video. Captions : Select Captions to upload a Add auto captions, or Review captions before adding it, or add a Video Caption File for your video. Auto-captions are currently supported in 10 languages. Note : Captions for other supported languages may not always be available. Delete : Click Delete to delete the video. Click Next . Click the Dropdown next to your name in the post pop-up window. From here, you can: Visibility : Select who you want to share the post with Comment control : Select who can comment on your posts Type the content of your post in the What do you want to talk about? field (optional). Click Post . To share a video: Tap Post on the upper right. Tap the Video icon to choose a video, either by using your phone's camera or uploading from your phone's gallery. After uploading a video, you can: Trim : Tap the trim/scissors icon and drag the trim bars to trim the start and stop time of your video Stickers : Tap the Stickers icon to add stickers to your video Text : Tap the Text icon to add text to your video Captions: Tap Captions to upload a Add auto captions or Review captions before adding it. Auto-captions are currently supported in 10 languages. Captions for other supported languages will be generated only if the confidence score is high for one of the 10 languages. Tap Next on the upper right. Tap the Anyone dropdown next to your name in the post page. From here, you can: Visibility : Select who you want to share the post with Comment control : Select who can comment on your posts Type the content of your post in the What do you want to talk about? field (optional). Tap Post on the upper right. The video requirements are: Maximum file size: 5 GB Minimum file size: 75 KB Maximum video duration: 15 minutes Minimum video duration: 3 seconds when uploading from desktop and 2 seconds when uploading from the LinkedIn mobile app. Resolution range: 256x144 to 4096x2304 Aspect ratio: 1:2.4 - 2.4:1 Frame rates: 10fps - 60 fps Bit rates: 192 Kbps - 30 Mbps Video safe zones Keep the edges (top, bottom, and sides) of your video free of key elements, text, and logos to ensure they are within the safe zone and aren&rsquo;t overlapped by the LinkedIn user interface. Note: You can share either a URL link or an image in a post, but not both at the same time. For URL links, we create a preview image taken from the site being shared. Learn more Video sharing troubleshooting Post and share content on LinkedIn Share videos on LinkedIn FAQs Visibility of shared posts Tagged in Share Content Post Media Related articles Get started with boosting posts on LinkedIn Boost your own LinkedIn post FAQ Edit or delete a boosted post from your LinkedIn profile
@@ -0,0 +1 @@
1
+ 566387d32f0dfaea4e480abb98f22bbc9f028aa9efb334451164ce53c9ceb53d
@@ -0,0 +1 @@
1
+ Best practices for content created with the help of AI Last updated: 4 weeks ago Professionals create and share content to express their points of view in many different ways, including with the help of artificial intelligence (AI). AI tools can support people in refining language, proofreading or being more concise. However, content should still reflect the member&rsquo;s own voice, perspective, and experience. When content is generic, low-value, lacks substance, and over-uses AI, it dilutes the conversations that real, human conversations spark. We do not want &ldquo;AI slop,&rdquo; which refers to low-effort, likely AI-generated content that may sound polished on the surface but lacks a clear point of view, unique perspective, or substance. Here are some best practices: As with other content you create and share on LinkedIn, follow our Professional Community Policies to keep your engagement safe, trustworthy, and professional. We urge you to review, edit, and approve of any content that you&rsquo;ve used AI to assist with. You are ultimately responsible for everything you post on LinkedIn, and your posts should represent your professional identity and expertise. AI might be a tool, but it is not a magic wand. If you're using AI to assist with content that you share on LinkedIn, ensure you are not infringing on the rights of others while doing so, including intellectual property and privacy rights. In your posts or other content on LinkedIn, we recommend that you let others know (if it isn't obvious from the context) if you've relied heavily on AI to help create or modify the content. Members appreciate authenticity and transparency. What does LinkedIn mean by &ldquo;AI slop&rdquo;? &ldquo;AI slop&rdquo; includes low-effort, likely AI-generated content that may sound polished on the surface but lacks a clear point of view, unique perspective, or substance. It goes beyond style to include content that feels generic, repetitive, recycled, or designed primarily to game attention rather than add to a meaningful conversation. How does LinkedIn distinguish between AI-assisted content and AI slop? LinkedIn&rsquo;s focus is not on how content is created, but whether it adds value. AI-assisted content is welcome when it reflects a real person&rsquo;s perspective, experience, or expertise. Content that feels generic, repetitive, or lacks a clear point of view is less likely to be widely distributed. How does the &ldquo;Seems like AI slop&rdquo; feature work? If you see a post or comment you believe is AI slop, tap the More menu in the top right corner of the post or comment and select Seems like AI slop . You can also select this after choosing Hide posts by [Name] . This lets us know the content didn't feel valuable to you. This option is currently available for posts and comments in your feed. Learn more about how to share feedback on AI slop . I received feedback that my post &ldquo;Seems like AI.&rdquo; What does that mean? If a post gets enough community feedback from other members, you&rsquo;ll see a tip in your Post analytics. Receiving this message does not mean that your post was taken down, or that a policy decision was made about your content. The tip is only intended to help you understand how your post is being received by the community, so you can consider it for the future. For advertisers, please visit the following LinkedIn Marketing Solutions Help Center articles to learn more: AI slop feedback option for ads on the LinkedIn feed Best practices for creating ads with AI
@@ -0,0 +1 @@
1
+ 5263ba774c957a8f5fab42f4879e99b3d0b3713df2359ad5194a4fbd40cc18d1
@@ -0,0 +1 @@
1
+ Label post as brand partnership Last updated: 3 years ago If you share content in an exchange for value (including monetary payment, endorsements, free products or services, or other benefit), you must label the post as a brand partnership and comply with our Advertising Policies and applicable local laws. Your sponsorship or brand partnership should be clear, conspicuous, and transparent. Desktop Mobile To label your post as a brand partnership: Click Start a post at the top of your LinkedIn homepage to share a post. Type the content of your post in the Start typing field. Select who you want to share the post with. Switch the toggle next to Brand partnership to On to label your post as brand partnership or Off to not label your post as brand partnership. After you publish the post, it will be labeled with Brand Partnership . To label your post as a brand partnership: Tap Post in the navigation bar to share a post. Type the content of your post in the Start typing field. Select who you want to share the post with. Switch the toggle next to Brand partnership to On to label your post as brand partnership or Off to not label your post as brand partnership. After you publish the post, it will be labeled with Brand Partnership . Notes : This label is only available for Public posts. If you change the visibility setting to Connections only or Groups , the toggle will automatically be disabled until you change the visibility to Public. This setting applies only to the current post and will reset to its default Off for your next post. Please make sure to check any applicable laws and guidance in your location around disclosures for posts like this. As part of our commitment to creating a safe and trusted experience, and to comply with the law, posts labeled as brand partnerships will be publicly searchable by members and visitors. Learn more Post and share content on LinkedIn Visibility of shared posts Share content on LinkedIn best practices Tagged in Share Content Related articles View your creator analytics Analytics and tools on LinkedIn View post analytics for your content
@@ -0,0 +1 @@
1
+ f61442d9a09af3b4d1a70fd3bfe8be8244af3b15e4d89817bcf56551074f0a69
@@ -0,0 +1 @@
1
+ Using the network features Follow and talk to anyone from any server. Browsing Content in Live Feeds Posts from other servers being streamed into the Live Feed To allow you to discover potentially interesting content, Mastodon provides a way to browse all public posts. There is no global shared state between all servers, so there is no way to browse all public posts. When you browse Live Feeds > Other Servers , you see public posts from across the fediverse. Your server shows posts it knows about through various methods . Most posts come from accounts that other users on your server follow. You can also filter the Live Feeds to view only public posts created on your server. Interacting with Posts An expanded view can be loaded by clicking a status in the timeline You can perform quick actions on a post directly from the timeline, or you can click on the post to load an expanded view that shows extra information, such as a full timestamp, interaction counts, and threaded replies, if any. The following actions can be performed on a post: Reply to a post by clicking the arrow icon. Your post will show up in the thread below the post you are replying to. Boost a post by clicking the cycled-arrow icon. The post will be reshared on your profile. Quote a post by choosing this option from the Boost button menu. Learn more about Quote posts . Favourite a post by clicking the star icon. The post will be added to your favourites list, and a favourite notification will be delivered to its author. Bookmark a post by clicking the ribbon icon. The post will be privately added to your bookmarks list without generating a notification. Access a menu of additional options by clicking the ellipsis icon. Fetching Replies When a status is expanded 1 , if enabled , your server will attempt to fetch any replies that it does not already know about from other servers. This process checks each server in the conversation thread to gather any missing replies, which may take some time, especially for posts with many replies or when viewing a post for the first time on your server. Try refreshing the page after a few moments if you suspect you aren&rsquo;t seeing all replies. 2 Some replies won&rsquo;t be fetched. These include followers-only posts,private mentions, and posts from servers that require authorization . The only exception is if you or someone on your server already follows the author. By searching for a post and then expanding it, you can effectively &ldquo;import&rdquo; a tree of replies to your instance, helping you and others on your server meet new people and other fediverse creatures! Notifications Notifications column with grouping feature enabled When other people interact with you or your posts, you will receive a notification depending on the type of the event. Your notifications column allows you to view all notifications in the same stream, or to filter for specific types of notifications: Mentions: received when someone has mentioned you in a post. Favourites: received when someone has favourited one of your posts. Boosts: received when someone has boosted one of your posts. Polls: Received when a poll that you have voted in or created has ended. Statuses: Received when a user you have enabled notifications for posts a status. Follows: Received when someone has followed your profile. When unread notifications are present, a checkmark will appear in the column header. Clicking this checkmark will mark notifications as read. Following Profiles Profile card with the Follow button shown When you see someone in your app&rsquo;s interface (e.g. the web interface on your home server, or your mobile app), you can simply click &ldquo;follow.&rdquo; It works the same way whether they&rsquo;re on your server or another server. If you come across someone’s public profile hosted on a different server and you&rsquo;re not in your own app&rsquo;s interface, there’s an obstacle: That server sees you as just another anonymous visitor. Not to worry! You can copy the URL of that profile, or of one of their posts, and then paste that URL into the search function. If you are visiting a public page on another Mastodon site, see Using Mastodon outside of your site . Enabling Notifications An example of a profile that you are following If you are following someone, you also have the option to receive a notification every time they post. To opt into this functionality, click the bell icon. Search The search function with modifier options exposed, see the section on prefixes below for description Mastodon&rsquo;s basic search allows logged-in users to find posts containing a specific hashtag, or to load a user or status directly if they know the URL or address. Searching for a term will show profiles whose username or display name contains that term, as well as hashtags that match or contain that term. Searching for a remote post or account&rsquo;s full URL will cause the server to fetch it if it is not already in the database so it can be viewed locally. An example of a post being loaded directly by its URL An example of results when searching for "arstechnica" including an account validated by the domain An example of hashtags returned when searching for "friday" Admins may optionally install full-text search. Mastodon’s full-text search allows logged-in users to find results from their own posts, their favourites, their bookmarks, and their mentions. Full-text search is limited for safety reasons. You can&rsquo;t search for any text across the entire database. This prevents people from searching for controversial terms to find and harass others. The following operators are supported: &ldquo;exact phrases&rdquo; will try to find the term inside the quote marks. This allows looking only for direct matches, such as "look at my cluckers" to find posts explicitly telling you to look at someone&rsquo;s cluckers. -exclude will exclude the term prepended by a minus sign. This allows filtering out certain terms, such as animals -cats to find posts about animals without posts about cats. +include will include the term after the plus sign. This allows searching for multiple terms that must be included, such as cat +dog to find posts about both cats and dogs. The following prefix:value pairs are also supported: has: ( media , poll , embed ) - posts that contain the specified attachment type is: ( reply , sensitive ) - posts that are either a reply or marked sensitive. language: ( {language_code} ) - posts made in a specific language, indicated by its ISO 639-1 language code from: ( @{username} , @{username}@{domain} , me ) - posts from a specified author before: ( {date} ) - posts created before an ISO8601 formatted date, e.g. &ldquo; 2025-03-01 &rdquo;. If the account has a timezone set, searches using their local timezone - otherwise in UTC. after: ( {date} ) - posts created after an ISO8601 formatted date during: ( {date} ) - posts created during an ISO8601 formatted date in: ( library , public ) - library is the collection of posts that you have interacted with in some way: favourited, reblogged, bookmarked, etc. public is the global full text search index. The default is to search both, if this option is omitted. Each can be used in combination with a text search, for example to find all posts from yourself about cryptids, you could search for from:me "cryptids" . Prefixes can be combined, though they are combined with AND , so e.g. one can&rsquo;t search for all posts from multiple languages. Prefixes can be negated with - as with string queries, so one can search for posts from anyone else about cryptids like -from:me "cryptids" . Private Mentions A list of conversations containing private mentions In Mastodon, private mentions are just posts that have the &ldquo;mention only&rdquo; visibility selected. Visibility can be selected per-post, which allows changing the privacy level later in a thread. The private mentions column currently shows a list of all conversations containing a mention only post. Clicking on a conversation will load the associated thread. List Timelines Lists are subsets of your home timeline. You can create a list, give it a name, and add users that you follow to that list. A list of lists Opening a list will load that list&rsquo;s timeline. List timelines contain only posts by members of that list, as well as replies to you or to other members of the list. This can be changed to show replies to all people you follow, or to no one. Syndication Feeds Every account and tag page provide an RSS feed for syndication onto other platforms. Those feeds are auto-discoverable from the account and tag pages. Translation When a post is in a language other than what your account is set to understand, a &ldquo;Translate&rdquo; button will appear next to the post content. Clicking this button issues a request to translate the content to the server, and will replace that content with translated results. This feature requires the server to have configured support for a translation service, and so may not be available on all servers. &ldquo;Expanded&rdquo; in the sense used above, meaning clicking on it to display the detailed view, not e.g. expanding content warnings or unfiltering posts. ↩&#xfe0e; Refreshing the page will not retrigger a fetch within some cooldown period, so don&rsquo;t worry about overdoing it! ↩&#xfe0e; Last updated November 27, 2025 · Improve this page Also available in: 简体中文 日本語 Polski
@@ -0,0 +1 @@
1
+ 43b4d177d003d82011ec3f031beac828303ab8182fd7ee9b9cef2b72a87260e5
@@ -0,0 +1 @@
1
+ Posting to your profile Sharing your thoughts has never been more convenient. Compose form with optional Content Warning enabled Text The main body of each status update can be composed using the text field. The default character limit is 500 characters. Links Links must start with http(s):// and are counted as 23 characters regardless of length If you include links in your post, they must begin with http:// or https:// . All links are counted as 23 characters, no matter how long they actually are, so there is no need to use a link shortener to save characters. In fact, using a link shortener is actively discouraged. Mentions Suggested mentions for both local and remote users You can mention users by typing out their full address, e.g. @alice@example.com . Note that any usage of @word will be interpreted as mentioning the local user with the username word , if that user exists. Only the username part will count against your character limit &ndash; the domain is not counted. Hashtags Hashtags are autosuggested with usage frequency You can use a #hashtag to make your post discoverable to anyone searching for that hashtag. Hashtags can contain alphanumeric characters and underscores, but cannot contain numbers only. Custom emoji An array of custom emoji are available in the selector Each server offers a set of custom emoji you can use, similar to Slack or Discord. You can use an emoji using its shortcode like :thounking: or by clicking the emoji face in the compose box and browsing through the &ldquo;Custom&rdquo; category. You can also browse through and search for standard Unicode emoji. To choose a different emoji skin tone, use the selector next to the emoji search box. Attachments You can attach either files or a poll to your status. Files New post with a thumbnail for attached media, with an Edit button for additional options Click the photo stack to attach a file to your post. You can attach the following: Images (PNG, JPG, HEIF, WEBP, AVIF) up to 16MB . Images will be downscaled to 8.3 megapixels (enough for a 3840x2160 image). Up to 4 images can be attached, per post. Animated GIFs (GIFV) up to 16MB are converted to soundless MP4s. GIF dimensions must be less than 1MP (1280x720). You can also upload soundless MP4 and WebM files, which will be looped in clients the same way as an animated GIF. Only one animated GIF can be attached, per post. Static GIF files have the same limits applied to them as animated GIF files. If you are having issues uploading these images, you will need to convert it to another supported image format. Videos (MP4, M4V, MOV, WebM) up to 99MB . Video will be transcoded to H.264 MP4 with a maximum bitrate of 1300kbps and framerate of 120fps. Only one video can be attached, per post. Audio (MP3, OGG, WAV, FLAC, OPUS, AAC, M4A, 3GP) up to 99MB . Audio will be transcoded to MP3 using V2 VBR (roughly 192kbps). Only one audio file can be attached, per post. Editing media Edit media to add a media description (ALT text) or choose a focal point for the preview thumbnail By clicking the &ldquo;Edit&rdquo; link on the attachment thumbnail, you can load a modal which will allow adding a media description or changing the focal point. Although optional, it is a good idea to add media descriptions that briefly describe what is in contained in the media. These descriptions will be shown when the media fails to load for any reason, or when accessed by screen readers and other assistive technology. Setting the focal point is also optional, but can make preview thumbnails looks better when they are not shown in a 16:9 aspect ratio. Polls New post with a poll in a &lsquo;pick one&rsquo; style, that expires after one day Click the bar graph icon to attach a poll to your post. You can add up to 4 choices. Each choice can be up to 25 characters. Polls default to pick-one/single-choice. Click on the radio button to switch your poll to any-of/multiple-choice checkboxes. Polls can be set to expire in 5 minutes, 30 minutes, 1 hour, 6 hours, 1 day, 3 days, or 7 days. Post visibility & privacy Posts can be published with one of four different post visibility levels. You can set a default posting visibility , and you can change the visibility for a draft post by opening the &ldquo;Visibility and interactions&rdquo; dialog from the button above the text of the post. The &lsquo;visibility and interactions&rsquo; dialog, showing the available options for post visibility The following table shows where posts made with a certain privacy setting will be visible. &ldquo;Public feeds&rdquo; includes search results, trending, and live feeds. Setting Public feeds Profile view Home feeds Public Visible Visible Visible Quiet public Hidden Visible Visible Followers Hidden Visible for followers and mentioned accounts Visible for followers and mentioned accounts Private mention Hidden Visible for mentioned accounts Visible for mentioned accounts Direct links (permalinks) to posts with &ldquo;Followers&rdquo; or &ldquo;Private mention&rdquo; visibility can only be accessed by logged-in users eligible to see the post. Note that opening permalinks in a browser will redirect to the origin server of the post (where you might not have an account). If you want to open a post on the server that your account is on, log into your server, paste the link into the search field and select &ldquo;Open URL on Mastodon&rdquo;. Below you&rsquo;ll find a detailed description of each post visibility setting. Public The default option. Anyone can see your post at the permalink without logging in. Your post will appear in-app in the public timelines and on your profile. Your followers will receive the post in their home feeds, and anyone mentioned will receive the post in notifications. Your post can be boosted into other home feeds. Quiet public The same as public, but with the following differences: Your post will not appear in Mastodon&rsquo;s live feeds or explore features. Your post will not appear in search results, even if your account has opted-in to full text search. This option was previously known as &ldquo;Unlisted&rdquo;. Followers A more limited delivery option. Only accounts following you and those that were mentioned in the post can see your post. Your post will not appear in-app except to your followers and anyone mentioned. Your followers will receive the post in their home feeds, and anyone mentioned will receive the post in notifications. Your post cannot be boosted, except by yourself. To effectively publish followers-only posts, you must disable the &ldquo;Automatically accept new followers&rdquo; option – otherwise anyone could follow you to view older posts. Please mind that post privacy on Mastodon is per-post, rather than account-wide. There is no way to make past public posts private. Private mention Send your post only to mentioned users. Only accounts that were mentioned in your post can see it. Your post will not appear in-app except to anyone mentioned. Anyone mentioned will receive the post in notifications. It will not appear in the home timeline. Your post cannot be boosted. This option was previously known as &ldquo;Specific people&rdquo;. Do not share dangerous and sensitive information over private mentions . Mastodon is not an encrypted messaging app like Signal or Matrix, and the database administrators of the sender’s and recipient’s servers may obtain access to the text. Visibility of Replies Your replies will only appear on your followers&rsquo; Home feeds if they follow both you and the person you are replying to. Some notes about this: A new post you make which starts with an @mention is not considered a reply, so it will show up on the Home feed of all your followers. The reply&rsquo;s visibility (Public vs Unlisted vs Followers-only) does not affect whether it shows up on the Home feed. If your post is public and contains a followed hashtag, it will be shown on the Home feed regardless of whether it is a reply. Other Fediverse software may show all of your replies on the Home feed, no matter who the posts are replies to. Content Warnings Expanded post with a content warning that also has attached images obscured One feature that Mastodon provides that you may not have seen on other social networks is the option to attach a content warning to your posts. When a content warning is included, the status content will be collapsed by default, and only the Content Warning will be shown, similarly to an email subject line or a &ldquo;read more&rdquo; break. This can be used to add a summary or subject for your post, to collapse long posts, or to otherwise provide context or setup for the body of the post. When media is attached, a checkbox appears to allow you to &ldquo;mark media as sensitive&rdquo;. This hides the full media behind a blurred thumbnail by default. Adding a CW to a post automatically marks the media as sensitive as well. Last updated July 8, 2026 · Improve this page Also available in: 简体中文 日本語 Polski
@@ -0,0 +1 @@
1
+ b0c91c10c6446f6841214bf3e071888e634ad1934d6bc7c0d0657c5045cbba9e
@@ -0,0 +1 @@
1
+ Instance Represents the software instance of Mastodon running on this domain. Example { "domain" : "mastodon.social" , "title" : "Mastodon" , "version" : "4.5.0-nightly.2025-07-11" , "source_url" : "https://github.com/mastodon/mastodon" , "description" : "The original server operated by the Mastodon gGmbH non-profit" , "usage" : { "users" : { "active_month" : 279347 } }, "thumbnail" : { "url" : "https://files.mastodon.social/site_uploads/files/000/000/001/@1x/57c12f441d083cde.png" , "description" : "Colourful illustration of a Mastodon (a sort of elephant) carrying a bindle and joining a group of other Mastodons. The other Mastodons have many different colours and are holding up a Welcome sign." , "blurhash" : "UeKUpFxuo~R%0nW;WCnhF6RjaJt757oJodS$" , "versions" : { "@1x" : "https://files.mastodon.social/site_uploads/files/000/000/001/@1x/57c12f441d083cde.png" , "@2x" : "https://files.mastodon.social/site_uploads/files/000/000/001/@2x/57c12f441d083cde.png" } }, "icon" : [ { "src" : "https://mastodon.social/packs/assets/android-chrome-36x36-DLiBQg3N.png" , "size" : "36x36" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-48x48-C7lKWFwX.png" , "size" : "48x48" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-72x72-9LRpA3QN.png" , "size" : "72x72" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-96x96-BKKwkkY-.png" , "size" : "96x96" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-144x144-D-ewI-KZ.png" , "size" : "144x144" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-192x192-jYKJbpas.png" , "size" : "192x192" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-256x256-DXt2vsq7.png" , "size" : "256x256" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-384x384-CbK7cG33.png" , "size" : "384x384" }, { "src" : "https://mastodon.social/packs/assets/android-chrome-512x512-Dz2ThkhV.png" , "size" : "512x512" } ], "languages" : [ "en" ], "configuration" : { "urls" : { "streaming" : "wss://streaming.mastodon.social" , "status" : "https://status.mastodon.social" , "about" : "https://mastodon.social/about" , "privacy_policy" : "https://mastodon.social/privacy-policy" , "terms_of_service" : null }, "vapid" : { "public_key" : "BCk-QqERU0q-CfYZjcuB6lnyyOYfJ2AifKqfeGIm7Z-HiTU5T9eTG5GxVA0_OH5mMlI4UkkDTpaZwozy0TzdZ2M=" }, "accounts" : { "max_display_name_lenth" : 30 , "max_note_length" : 500 , "max_featured_tags" : 10 , "max_pinned_statuses" : 5 , "max_profile_fields" : 4 , "profile_field_name_limit" : 255 , "profile_field_value_limit" : 255 }, "statuses" : { "max_characters" : 500 , "max_media_attachments" : 4 , "characters_reserved_per_url" : 23 }, "media_attachments" : { "description_limit" : 1500 , "image_matrix_limit" : 33177600 , "image_size_limit" : 16777216 , "supported_mime_types" : [ "image/jpeg" , "image/png" , "image/gif" , "image/heic" , "image/heif" , "image/webp" , "image/avif" , "video/webm" , "video/mp4" , "video/quicktime" , "video/ogg" , "audio/wave" , "audio/wav" , "audio/x-wav" , "audio/x-pn-wave" , "audio/vnd.wave" , "audio/ogg" , "audio/vorbis" , "audio/mpeg" , "audio/mp3" , "audio/webm" , "audio/flac" , "audio/aac" , "audio/m4a" , "audio/x-m4a" , "audio/mp4" , "audio/3gpp" , "video/x-ms-asf" ], "video_frame_rate_limit" : 120 , "video_matrix_limit" : 8294400 , "video_size_limit" : 103809024 }, "polls" : { "max_options" : 4 , "max_characters_per_option" : 50 , "min_expiration" : 300 , "max_expiration" : 2629746 }, "translation" : { "enabled" : true }, "timelines_access" : { "live_feeds" : { "local" : "public" , "remote" : "public" }, "hashtag_feeds" : { "local" : "public" , "remote" : "public" }, "trending_link_feeds" : { "local" : "public" , "remote" : "public" } }, "limited_federation" : false , "collections" : { "max_items" : 25 , "max_name_length" : 40 , "max_description_length" : 100 } }, "registrations" : { "enabled" : true , "approval_required" : false , "reason_required" : false , "message" : null , "min_age" : 16 , "url" : null , "oauth" : true }, "api_versions" : { "mastodon" : 6 }, "contact" : { "email" : "staff@mastodon.social" , "account" : { "id" : "13179" , "username" : "Mastodon" , "acct" : "Mastodon" , "display_name" : "Mastodon" , "locked" : false , "bot" : false , "discoverable" : true , "indexable" : false , "group" : false , "created_at" : "2016-11-23T00:00:00.000Z" , "note" : "<p>Free, open-source decentralized social media platform.</p>" , "url" : "https://mastodon.social/@Mastodon" , "uri" : "https://mastodon.social/users/Mastodon" , "avatar" : "https://files.mastodon.social/accounts/avatars/000/013/179/original/b4ceb19c9c54ec7e.png" , "avatar_static" : "https://files.mastodon.social/accounts/avatars/000/013/179/original/b4ceb19c9c54ec7e.png" , "header" : "https://files.mastodon.social/accounts/headers/000/013/179/original/1375be116fbe0f1d.png" , "header_static" : "https://files.mastodon.social/accounts/headers/000/013/179/original/1375be116fbe0f1d.png" , "followers_count" : 843930 , "following_count" : 34 , "statuses_count" : 344 , "last_status_at" : "2025-07-10" , "hide_collections" : false , "noindex" : false , "emojis" : [], "roles" : [], "fields" : [ { "name" : "Homepage" , "value" : "<a href=\"https://joinmastodon.org\" target=\"_blank\" rel=\"nofollow noopener me\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"\">joinmastodon.org</span><span class=\"invisible\"></span></a>" , "verified_at" : "2018-10-31T04:11:00.076+00:00" }, { "name" : "Patreon" , "value" : "<a href=\"https://patreon.com/mastodon\" target=\"_blank\" rel=\"nofollow noopener me\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"\">patreon.com/mastodon</span><span class=\"invisible\"></span></a>" , "verified_at" : null }, { "name" : "GitHub" , "value" : "<a href=\"https://github.com/mastodon\" target=\"_blank\" rel=\"nofollow noopener me\" translate=\"no\"><span class=\"invisible\">https://</span><span class=\"\">github.com/mastodon</span><span class=\"invisible\"></span></a>" , "verified_at" : "2023-07-21T13:27:45.996+00:00" } ] } }, "rules" : [ { "id" : "1" , "text" : "Sexually explicit or violent media must be marked as sensitive or with a content warning" , "hint" : "This includes content that is particularly provocative even if it may not show specific body parts, as well as dead bodies, bloody injuries, and other gore. Particularly obscene content may be prohibited entirely. Profile pictures and header images may not contain sexually explicit or violent media." , "translations" : { "de" : { "text" : "Sexuell explizite Darstellungen oder solche von Gewalt müssen mit einer Inhaltswarnung versehen werden." , "hint" : "Das beinhaltet ausdrücklich provokative Inhalte, auch wenn keine bestimmten Körperteile zu sehen sind, sowie Leichname, blutige Verletzungen und vergleichbare extreme Darstellungen. Besonders obszöne Inhalte können vollständig verboten werden. Profil- und Titelbilder dürfen keine sexuell expliziten oder Gewaltdarstellungen abbilden." }, "es" : { "text" : "El contenido sexual explícito o violento debe marcarse como sensible o con una advertencia de contenido." , "hint" : "Esto incluye contenido especialmente provocativo, aunque no muestre partes específicas del cuerpo, así como cadáveres, heridas sangrientas y otras escenas sangrientas. Los contenidos especialmente obscenos pueden prohibirse por completo. Las fotos de perfil y las imágenes de cabecera no pueden contener contenido sexual explícito o violento." }, "fr" : { "text" : "Le contenu érotique, pornographique ou violent doit être marqué comme sensible ou avoir un avertissement de contenu." , "hint" : "Cela inclut le contenu particulièrement provocateur même s’il ne montre pas particulièrement de parties intimes, ainsi que les photos de cadavres, de blessures sanglantes et autres scènes dérangeantes. Le contenu particulièrement obscène peut être complètement interdit. Les images de profil et d’en-tête ne doivent pas contenir de contenu sexuellement explicite ou violent." }, "nl" : { "text" : "Seksueel expliciet of gewelddadig beeldmateriaal moet als ‘gevoelig’ gemarkeerd worden, of met een inhoudswaarschuwing gemarkeerd." , "hint" : "Dit omvat ook inhoud die gedeeltelijk aanstootgevend is zelfs als het geen lichaamsdelen toont, en ook dode lichamen, bloederige verwondingen en andere gruwelijkheden. Zeer obscene inhoud kan helemaal verboden worden. Profielfoto’s en headerafbeeldingen mogen geen seksueel expliciete of geweldadige inhoud hebben." }, "ru" : { "text" : "Сексуально откровенные или жестокие изображения или видео должны быть помечены как чувствительные или скрыты под спойлер." , "hint" : "Это включает в себя особенно провоцирующий контент, даже если он не показывает определённые части тела, а также мёртвые тела, окровавленные раны и прочую кровь. Особенно жестокий контент может быть запрещён полностью. Аватары и обложки профилей не должны содержать сексуально откровенные или жестокие изображения." }, "zh-CN" : { "text" : "色情或暴力媒体必须标记为敏感或有内容警告" , "hint" : "这包括特别挑逗性的内容,即使它可能没有显示特定的身体部位,以及尸体、血腥伤害和其他血腥内容。特别淫秽的内容可能会被完全禁止。个人资料图片和头像不得包含色情或暴力内容。" }, "zh-TW" : { "text" : "性暗示或暴力媒體必須標示為敏感或附帶內容警示" , "hint" : "這包括特別挑釁的內容,即使它可能沒有顯示特定的身體部位,以及屍體、血腥傷害和其他血腥內容。特別猥褻的內容可能會被完全禁止。個人檔案圖片和標題圖片不得包含色情或暴力媒體。" } } }, { "id" : "2" , "text" : "No racism, sexism, homophobia, transphobia, ableism, xenophobia, or casteism." , "hint" : "Transphobic behavior such as intentional misgendering and deadnaming is strictly prohibited. Promotion of \"conversion therapy\" is strictly prohibited. Criticism of governments and religions is permissible unless being used as a proxy for discrimination." , "translations" : { "de" : { "text" : "Kein(e) Rassismus, Sexismus, Homophobie, Transphobie, Behindertenfeindlichkeit, Fremdenfeindlichkeit oder Kasteismus." , "hint" : "Transphobes Verhalten wie die absichtliche Verwendung von falschen Anreden und Pronomen sowie Deadnaming ist strengstens verboten. Die Werbung für Konversionstherapien ist strengstens verboten. Die Kritik an Regierungen und Religionen ist zulässig, sofern sie nicht stellvertretend für Diskriminierung verwendet wird." }, "es" : { "text" : "Prohibido el racismo, sexismo, homofobia, transfobia, ableísmo, xenofobia o casticismo." , "hint" : "Queda terminantemente prohibido el comportamiento transfóbico, como el uso intencionado de nombres falsos o el \"deadnaming\". La promoción de la \"terapia de conversión\" está estrictamente prohibida. Se permiten las críticas a gobiernos y religiones, a menos que se utilicen como excusa para la discriminación." }, "fr" : { "text" : "Pas de racisme, sexisme, homophobie, transphobie, validisme, xénophobie ou discrimination de caste." , "hint" : "Les comportements intentionnellement transphobes, comme le mégenrage ou le morinommage (“deadnaming”) est strictement interdit. La promotion des “thérapies de conversion” est strictement interdite. La critique des gouvernements et religions est autorisée, sauf dans les cas ou elle est utilisée comme paravent pour de la discrimination." }, "nl" : { "text" : "Geen racisme, seksisme, homofobie, transfobie, validisme, xenofobie of kastendiscriminatie." , "hint" : "Transfobisch gedrag zoals opzettelijk misgenderen en deadnaming is ten strengste verboden. Het promoten van “conversie therapie” is ten strengste verboden. Kritiek op overheden en religies is toegestaan tenzij het wordt gebruikt als proxy voor racisme." }, "ru" : { "text" : "Запрещается расизм, сексизм, гомофобия, трансфобия, эйблизм, ксенофобия и кастовость." , "hint" : "Трансфобное поведение, такое как осознанный мисгендеринг и деднейминг, строго запрещено. Продвижение \"конверсионной терапии\" строго запрещено. Критика правительств и религий разрешена, кроме случаев, когда она используется как оправдание для дискриминации." }, "zh-CN" : { "text" : "禁止种族主义、性别歧视、仇视同性恋、仇视变性者、异能者、仇外心理或种姓歧视。" , "hint" : "严禁变性仇视行为,如故意误用性别和死名。严禁宣传 “转换疗法”。允许批评政府和宗教,除非被用作歧视的代名词。" }, "zh-TW" : { "text" : "禁止種族主義、性別主義、恐同主義、恐變性主義、能力主義、仇外主義或種性主義。" , "hint" : "嚴禁變性仇視行為,例如故意誤用性別和暱稱。嚴禁宣傳「扭轉治療」。允許批評政府和宗教,除非被用來代表歧視。" } } }, { "id" : "3" , "text" : "No incitement of violence or promotion of violent ideologies" , "hint" : "Calling for people or groups to be assassinated, murdered, or attacked physically is strictly prohibited. Support for violent groups or events is prohibited." , "translations" : { "de" : { "text" : "Keine Anstiftung zu Gewalt oder Förderung gewalttätiger Ideologien." , "hint" : "Der Aufruf zum Mord oder körperlichen Attacken auf Personen oder Gruppen ist strengstens verboten. Die Unterstützung gewalttätiger Gruppen oder Veranstaltungen ist verboten." }, "es" : { "text" : "Prohibida la incitación a la violencia o la promoción de ideologías violentas." , "hint" : "Está estrictamente prohibido hacer llamamientos para que se asesine, mate o agreda físicamente a personas o grupos. Está prohibido apoyar a grupos o acontecimientos violentos." }, "fr" : { "text" : "Pas d’incitation à la violence ou de promotion d’idéologies violentes." , "hint" : "L’appel au meutre, à la violence ou à l’action physique envers des personnes ou des groupes de personnes est strictement interdit. Le soutien à des groupes ou évènements violents est interdit." }, "nl" : { "text" : "Niet aanzetten tot geweld of verspreiden van gewelddadige ideologieën." , "hint" : "Mensen of groepen aanzetten tot moord, aanslagen of fysieke aanvallen is ten strengste verboden. Steun voor gewelddadige groeperingen of evenementen is verboden." }, "ru" : { "text" : "Запрещается подстрекательство к жестокости или продвижение жестоких идеологий." , "hint" : "Призывы к покушениям, убийствам и физическим атакам на людей или группы людей строго запрещены. Поддержка жестоких сообществ или событий запрещена." }, "zh-CN" : { "text" : "不得煽动暴力或宣扬暴力意识形态" , "hint" : "严禁呼吁暗杀、谋杀或人身攻击他人或团体。禁止支持暴力团体或事件。" }, "zh-TW" : { "text" : "嚴禁煽動暴力或宣揚暴力意識形態" , "hint" : "嚴禁呼籲暗殺、謀殺或人身攻擊他人或團體。嚴禁支持暴力團體或事件。" } } }, { "id" : "4" , "text" : "No harassment, block evasion, dogpiling, or doxxing of others" , "hint" : "Repeat attempts to communicate with users who have blocked you or creation of accounts solely to harass or insult individuals is strictly prohibited. Coordinated activity to attack other users is prohibited. Posting of private personal information about others is prohibited." , "translations" : { "de" : { "text" : "Keine Belästigungen, Umgehung von Blockierungen, Dogpiling oder Doxxing." , "hint" : "Wiederholte Kommunikationsversuche mit Profilen, die dich blockiert haben, oder die Erstellung neuer Konten, die ausschließlich dazu dienen, andere zu belästigen oder zu beleidigen, sind strengstens verboten. Koordinierte Angriffe auf andere Profile sind verboten. Die Veröffentlichung von privaten und persönlichen Informationen anderer ist verboten." }, "es" : { "text" : "No acosar, evadir bloqueos, \"dogpiling\" (abuso en línea por grupos de acosadores) o doxeo de otros." , "hint" : "Está estrictamente prohibido intentar comunicarse repetidamente con usuarios que te hayan bloqueado o crear cuentas con el único fin de acosar o insultar a otras personas. Queda prohibida la actividad coordinada para atacar a otros usuarios. Está prohibido publicar información personal privada sobre otras personas." }, "fr" : { "text" : "Pas de harcèlement, d’esquive de blocage, de “dogpiling”, ou de divulgation de données personnelles d’autrui." , "hint" : "Les tentatives répétées de communiquer avec des utilisateur·ices qui vont ont bloqué ainsi que la création de comptes pour harceler ou insulter autrui sont strictement interdites. Les attaques coordonnées contre autrui sont interdites. La publication de données personnelles d’autrui est interdite." }, "nl" : { "text" : "Geen intimidatie, omzeilen van blokkades, groepsaanvallen of het verspreiden van privégegevens van anderen." , "hint" : "Herhaalde pogingen tot communiceren met gebruikers die je hebben geblokkeerd, of het maken van accounts enkel om personen te intimideren of beledigen is ten strengste verboden. Gecoördineerde activiteit om andere gebruikers aan te vallen is verboden. Het plaatsen van privé-gegevens van anderen is verboden." }, "ru" : { "text" : "Запрещается травля, избегание блокировок, набеги и разглашение личной информации других лиц." , "hint" : "Повторяющиеся попытки взаимодействовать с пользователями, которые вас заблокировали, и создание учётных записей исключительно ради травли или оскорблений, строго запрещены. Скоординированная активность с целью атаки на других пользователей запрещена. Публикация личной информации других лиц запрещена." }, "zh-CN" : { "text" : "不得骚扰、回避封禁、诽谤或攻击他人" , "hint" : "严禁重复尝试与已封禁您的用户交流,或仅为骚扰或侮辱他人而创建账户。严禁协同攻击其他用户。禁止发布他人的私人个人信息。" }, "zh-TW" : { "text" : "嚴禁騷擾、迴避封鎖、煽動或誣衊他人" , "hint" : "嚴禁重複嘗試與已封鎖您的使用者溝通,或純粹為了騷擾或侮辱他人而建立帳號。禁止攻擊其他使用者的協調活動。禁止張貼他人的私人個人資訊。" } } }, { "id" : "7" , "text" : "Do not share information widely-known to be false and misleading" , "hint" : "False and misleading information and links from low-quality sources may not be posted, especially if they are likely to mislead or confuse others or endanger their safety." , "translations" : { "de" : { "text" : "Verbreitet keine Informationen, von denen allgemein bekannt ist, dass sie falsch oder irreführend." , "hint" : "Falsche und irreführende Informationen sowie Links aus unseriösen Quellen dürfen nicht gepostet werden, insbesondere wenn sie geeignet sind, andere in die Irre zu führen oder deren Sicherheit zu gefährden." }, "es" : { "text" : "No compartas información ampliamente conocida por ser falsa y engañosa." , "hint" : "No está permitido publicar información falsa y engañosa ni enlaces de fuentes de baja calidad, especialmente si pueden inducir a error o confusión a otras personas o poner en peligro su seguridad." }, "fr" : { "text" : "Ne partagez pas d’informations connues pour être fausses ou trompeuses." , "hint" : "Les informations fausses ou trompeuses, ainsi que les liens vers des sources de mauvaise qualité ne doivent pas être publiées, particulièrement si elles risquent de tromper, d’induire en erreur, de semer la confusion ou de mettre des personnes en danger." }, "nl" : { "text" : "Deel geen informatie die algemeen bekend staat als onjuist en misleidend." , "hint" : "Onjuiste en misleidende informatie en links naar onbetrouwbare bronnen mogen niet geplaatst worden, zeker als deze waarschijnlijk anderen misleiden of verwarren, of hun veiligheid in gevaar brengt." }, "ru" : { "text" : "Не публикуйте заведомо ложную и вводящую в заблуждение информацию." , "hint" : "Запрещена публикация ложной и вводящей в заблуждение информации и ссылок из низкокачественных источников, особенно если это может сбить других людей с толку, запутать их, или подвергнуть их опасности." }, "zh-CN" : { "text" : "不得分享众所周知的虚假和误导性信息\r\n" , "hint" : "不得发布虚假和误导性信息以及来自低质量来源的链接,尤其是可能误导或混淆他人或危及他人安全的信息。" }, "zh-TW" : { "text" : "請勿分享廣為人知的虛假和誤導資訊" , "hint" : "不得張貼虛假和誤導資訊以及來自低品質來源的連結,尤其是可能誤導或混淆他人或危害他人安全的資訊。" } } }, { "id" : "1008" , "text" : "Content created by others must be attributed, and use of generative AI must be disclosed" , "hint" : "Content created by others must clearly provide a reference to the author, creator, or source. For adult content, this should include performers. Accounts may not solely post AI-generated content." , "translations" : { "de" : { "text" : "Von anderen erstellte Inhalte müssen gekennzeichnet und die Nutzung generativer KI offengelegt werden." , "hint" : "Von anderen erstellte Inhalte müssen durch einen eindeutigen Verweis auf den/die Autor*in oder die Quelle gekennzeichnet werden. Bei nicht jugendfreien Inhalten sollte dies auch die Darsteller*innen einschließen. Konten dürfen nicht ausschließlich KI-generierte Inhalte posten." }, "es" : { "text" : "Los contenidos creados por terceros deben ser atribuidos y el uso de IA debe ser revelado." , "hint" : "Los contenidos creados por terceros deben proporcionar claramente una referencia al autor, creador o fuente. En el caso de los contenidos para adultos, debe incluirse a los artistas. Las cuentas no pueden publicar únicamente contenidos generados por IA." }, "fr" : { "text" : "Le contenu crée par autrui doit être attribué, et l’utilisation d’IA générative doit être marqué comme tel." , "hint" : "Le contenu créé par autrui doit fournir une référence explicite à son auteur·ice, créateur·ice ou sa source. Cela inclut les acteur·ice de contenu pour adulte. Les comptes publiant exclusivement du contenu généré par IA sont interdits." }, "nl" : { "text" : "Inhoud gemaakt door anderen moet worden toegeschreven, en het gebruik van generatieve AI moet worden aangegeven." , "hint" : "Inhoud gemaakt door anderen moet een duidelijke referentie naar de auteur, maker of bron bevatten. Voor Content created by others must clearly provide a reference to the author, creator, or source. Voor inhoud voor volwassenen, moet het model worden vermeld. Accounts mogen niet uitsluitend door AI gegenereerde inhoud plaatsen." }, "ru" : { "text" : "Контент, созданный другими, должен публиковаться с указанием авторства, а использование генеративного ИИ должно быть раскрыто." , "hint" : "Контент, созданный другими, должен явным образом сопровождаться отсылкой к автору, создателю или источнику. Для контента для взрослых это включает в себя актёров. Учётные записи не могут публиковать исключительно контент, сгенерированный с помощью ИИ." }, "zh-CN" : { "text" : "他人创建的内容必须注明出处,使用人工智能产生的内容必须公开和披露说明" , "hint" : "他人创建的内容必须明确注明作者、创建者或来源。对于成人内容,应包括表演者。账户不得仅发布人工智能生成的内容。" }, "zh-TW" : { "text" : "由他人創作的內容必須註明來源,使用人工智能產生的內容必須公開和披露說明" , "hint" : "他人創作的內容必須清楚提供作者、創作人或來源的參照。對於成人內容,這應該包括表演者。帳戶不得僅發佈人工智能產生的內容。" } } } ] } Attributes domain Description: The WebFinger domain name of the server. Type: String Version history: 4.0.0 - added title Description: The title of the website. Type: String Version history: 4.0.0 - added version Description: The version of Mastodon installed on the server. Type: String Version history: 4.0.0 - added source_url Description: The URL for the source code of the software running on this server, per the AGPL license requirements. Type: String (URL) Version history: 4.0.0 - added description Description: A short, plain-text description defined by the admin. Type: String Version history: 4.0.0 - added wrapstodon Description: The current Wrapstodon ( Annual report campaign identifier (year), if any. Type: nullable String Version history: 4.6.0 - added usage Description: Usage data for this server. Type: Hash Version history: 4.0.0 - added usage[users] Description: Usage data related to users on this server. Type: Hash Version history: 4.0.0 - added usage[users][active_month] Description: The number of active users in the past 4 weeks. This is set to zero for server with configuration[limited_federation] . Type: Integer Version history: 4.0.0 - added thumbnail Description: An image used to represent this server. Type: Hash Version history: 4.0.0 - added thumbnail[url] Description: The URL for the thumbnail image. Type: String (URL) Version history: 4.0.0 - added thumbnail[description] Description: The thumbnail&rsquo;s alt text (a description of the image to help people with visual impairments understand its content). Type: String Version history: 4.6.0 - added thumbnail[blurhash] optional Description: A hash computed by the BlurHash algorithm , for generating colorful preview thumbnails when media has not been downloaded yet. Type: String (Blurhash) Version history: 4.0.0 - added thumbnail[versions] optional Description: Links to scaled resolution images, for high DPI screens. Type: Hash Version history: 4.0.0 - added thumbnail[versions][@1x] optional Description: The URL for the thumbnail image at 1x resolution. Type: String (URL) Version history: 4.0.0 - added thumbnail[versions][@2x] optional Description: The URL for the thumbnail image at 2x resolution. Type: String (URL) Version history: 4.0.0 - added icon Description: The list of available size variants for this server&rsquo;s configured icon. Type: Array of InstanceIcon Version history: 4.3.0 - added languages Description: Primary languages of the website and its staff. Type: Array of String (ISO 639-1 two-letter code) Version history: 4.0.0 - added configuration Description: Configured values and limits for this website. Type: Hash Version history: 4.0.0 - added configuration[urls] Description: URLs of interest for clients apps. Type: Hash Version history: 4.0.0 - added configuration[urls][streaming] Description: The Websockets URL for connecting to the streaming API. Type: String (URL) Version history: 4.0.0 - added configuration[urls][status] Description: The URL of the server&rsquo;s status page, if configured. Type: nullable String (URL) Version history: 4.1.0 - added configuration[urls][about] Description: The URL of the server&rsquo;s about page. Type: String (URL) Version history: 4.4.0 - added configuration[urls][privacy_policy] Description: The URL of the server&rsquo;s privacy policy. Type: nullable String (URL) Version history: 4.4.0 - added configuration[urls][terms_of_service] Description: The URL of the server&rsquo;s current terms of service, if any. Type: nullable String (URL) Version history: 4.4.0 - added configuration[vapid][public_key] Description: The server&rsquo;s VAPID public key, used for push notifications, the same as WebPushSubscription#server_key . Type: String Version history: 4.3.0 - added configuration[accounts] Description: Limits related to accounts. Type: Hash Version history: 4.0.0 - added configuration[accounts][max_display_name_length] Description: The maximum length allowed for an account&rsquo;s display name. Type: Integer Version history: 4.6.0 - added configuration[accounts][max_note_length] Description: The maximum length allowed for an account&rsquo;s bio. Type: Integer Version history: 4.6.0 - added configuration[accounts][max_avatar_description_length] Description: The maximum length allowed for an account&rsquo;s avatar description. Type: Integer Version history: 4.6.0 - added configuration[accounts][max_header_description_length] Description: The maximum length allowed for an account&rsquo;s profile header description. Type: Integer Version history: 4.6.0 - added configuration[accounts][max_featured_tags] Description: The maximum number of featured tags allowed for each account. Type: Integer Version history: 4.0.0 - added configuration[accounts][max_pinned_statuses] Description: The maximum number of pinned statuses for each account. Type: Integer Version history: 4.3.0 - added configuration[accounts][max_profile_fields] Description: The maximum number of custom profile fields allowed to be set. Type: Integer Version history: 4.6.0 - added configuration[accounts][profile_field_name_limit] Description: The maximum size of a profile field name, in characters. Type: Integer Version history: 4.6.0 - added configuration[accounts][profile_field_value_limit] Description: The maximum size of a profile field value, in characters. Type: Integer Version history: 4.6.0 - added configuration[statuses] Description: Limits related to authoring statuses. Type: Hash Version history: 4.0.0 - added configuration[statuses][max_characters] Description: The maximum number of allowed characters per status. Type: Integer Version history: 4.0.0 - added configuration[statuses][max_media_attachments] Description: The maximum number of media attachments that can be added to a status. Type: Integer Version history: 4.0.0 - added configuration[statuses][characters_reserved_per_url] Description: Each URL in a status will be assumed to be exactly this many characters. Type: Integer Version history: 4.0.0 - added configuration[media_attachments] Description: Hints for which attachments will be accepted. Type: Hash Version history: 4.0.0 - added configuration[media_attachments][supported_mime_types] Description: Contains MIME types that can be uploaded. Type: Array of String Version history: 4.0.0 - added configuration[media_attachments][description_limit] Description: The maximum size of a description, in characters. Type: Integer Version history: 4.4.0 - added configuration[media_attachments][image_size_limit] Description: The maximum size of any uploaded image, in bytes. Type: Integer Version history: 4.0.0 - added configuration[media_attachments][image_matrix_limit] Description: The maximum number of pixels (width times height) for image uploads. Type: Integer Version history: 4.0.0 - added configuration[media_attachments][video_size_limit] Description: The maximum size of any uploaded video, in bytes. Type: Integer Version history: 4.0.0 - added configuration[media_attachments][video_frame_rate_limit] Description: The maximum frame rate for any uploaded video. Type: Integer Version history: 4.0.0 - added configuration[media_attachments][video_matrix_limit] Description: The maximum number of pixels (width times height) for video uploads. Type: Integer Version history: 4.0.0 - added configuration[polls] Description: Limits related to polls. Type: Hash Version history: 4.0.0 - added configuration[polls][max_options] Description: Each poll is allowed to have up to this many options. Type: Integer Version history: 4.0.0 - added configuration[polls][max_characters_per_option] Description: Each poll option is allowed to have this many characters. Type: Integer Version history: 4.0.0 - added configuration[polls][min_expiration] Description: The shortest allowed poll duration, in seconds. Type: Integer Version history: 4.0.0 - added configuration[polls][max_expiration] Description: The longest allowed poll duration, in seconds. Type: Integer Version history: 4.0.0 - added configuration[translation] Description: Hints related to translation. Type: Hash Version history: 4.0.0 - added configuration[translation][enabled] Description: Whether the Translations API is available on this server. Type: Boolean Version history: 4.0.0 - added configuration[timelines_access] Description: Access restrictions on different timelines. Type: Hash Version history: 4.5.0 - added configuration[timelines_access][live_feeds] Description: Access restrictions on public feeds . Type: Hash Version history: 4.5.0 - added configuration[timelines_access][live_feeds][local] Description: Access restrictions for local posts in the public feed. Type: String (Enumerable oneOf) public = Access to local posts in the public feed is available to both visitors and logged-in users. authenticated = Access to local posts in the public feed requires authentication. disabled = Access to local posts in the public feed is only possible for users with the “View live and topic feeds” permission . Version history: 4.5.0 - added configuration[timelines_access][live_feeds][remote] Description: Access restrictions for remote posts in the public feed. Type: String (Enumerable oneOf) public = Access to remote posts in the public feed is available to both visitors and logged-in users. authenticated = Access to remote posts in the public feed requires authentication. disabled = Access to remote posts in the public feed is only possible for users with the “View live and topic feeds” permission . Version history: 4.5.0 - added configuration[timelines_access][hashtag_feeds] Description: Access restrictions on hashtag feeds . Type: Hash Version history: 4.5.0 - added configuration[timelines_access][hashtag_feeds][local] Description: Access restrictions for local posts in hashtag feeds. Type: String (Enumerable oneOf) public = Access to local posts in hashtag feeds is available to both visitors and logged-in users. authenticated = Access to local posts in hashtag feeds requires authentication. Version history: 4.5.0 - added configuration[timelines_access][hashtag_feeds][remote] Description: Access restrictions for remote posts in hashtag feeds. Type: String (Enumerable oneOf) public = Access to remote posts in hashtag feeds is available to both visitors and logged-in users. authenticated = Access to remote posts in hashtag feeds requires authentication. disabled = Access to remote posts in hashtag feeds is only possible for users with the “View live and topic feeds” permission . Version history: 4.5.0 - added configuration[timelines_access][trending_link_feeds] Description: Access restrictions on trending link feeds . Type: Hash Version history: 4.5.0 - added configuration[timelines_access][trending_link_feeds][local] Description: Access restrictions for local posts in the trending link feeds. Type: String (Enumerable oneOf) public = Access to local posts in trending link feeds is available to both visitors and logged-in users. authenticated = Access to local posts in trending link feeds requires authentication. Version history: 4.5.0 - added configuration[timelines_access][trending_link_feeds][remote] Description: Access restrictions for remote posts in trending link feeds. Type: String (Enumerable oneOf) public = Access to remote posts in trending link feeds is available to both visitors and logged-in users. authenticated = Access to remote posts in trending link feeds requires authentication. disabled = Access to remote posts in trending link feeds is only possible for users with the “View live and topic feeds” permission . Version history: 4.5.0 - added configuration[limited_federation] Description: Whether federation is limited to explicitly allowed domains. Type: Boolean Version history: 4.4.0 - added configuration[collections] Description: Limits related to collections. Type: Hash Version history: 5.0.0 - added configuration[collections][max_items] Description: The maximum number of items in a single collection. Type: Integer Version history: 5.0.0 - added configuration[collections][max_name_length] Description: The maximum length allowed for the name of a collection. Type: Integer Version history: 5.0.0 - added configuration[collections][max_description_length] Description: The maximum length allowed for the description of a collection. Type: Integer Version history: 5.0.0 - added registrations Description: Information about registering for this website. Type: Hash Version history: 4.0.0 - added registrations[enabled] Description: Whether registrations are enabled. This will be false if registrations_mode is none or if the server is in single_user_mode . Type: Boolean Version history: 4.0.0 - added registrations[approval_required] Description: Whether registrations require moderator approval. Type: Boolean Version history: 4.0.0 - added registrations[message] Description: A custom message to be shown when registrations are closed. Will be null if registrations are open. Type: nullable String (HTML) Version history: 4.0.0 - added registrations[min_age] Description: A minimum age required to register, if configured. Type: nullable Integer Version history: 4.4.0 - added registrations[reason_required] Description: Whether registrations require the user to provide a reason for joining. Only applicable when registrations[approval_required] is true. Type: nullable Boolean Version history: 4.4.0 - added registrations[oauth] Description: Signals whether the OAuth registration flow ( prompt=create ) is supported. Type: Boolean Version history: 5.0.0 - added registrations[url] Description: A custom URL for account registration, when using external authentication. Type: nullable String (URL) Version history: 4.2.0 - added api_versions Description: Machine-readable API version information that allows clients to determine which API endpoints and features are available on this server. This provides a more reliable method for capability detection than parsing human-readable version strings, especially for forks and development builds. It contains at least a mastodon attribute, and other implementations may have their own additional attributes. Type: Hash Version history: 4.3.0 - added api_versions[mastodon] Description: API version number that increments with substantial API changes. Clients can use this value to determine API compatibility rather than parsing complex version strings like &ldquo;4.4+hometown-123&rdquo; from forks or nightly builds. This number increases independently of the human-readable version number. Type: Integer Version history: 4.3.0 - added contact Description: Hints related to contacting a representative of the website. Type: Hash Version history: 4.0.0 - added contact[email] Description: An email address that can be messaged regarding inquiries or issues. Type: String (Email) Version history: 4.0.0 - added contact[account] Description: An account that can be contacted natively over the network regarding inquiries or issues. Type: nullable Account Version history: 4.0.0 - added rules Description: An itemized list of rules for this website. Type: Array of Rule Version history: 4.0.0 - added InstanceIcon attributes src Description: The URL of this icon. Type: String Version history: 4.3.0 - added size Description: The size of this icon. Type: String (in the form of 12x34 , where 12 is the width and 34 is the height of the icon) Version history: 4.3.0 - added See also GET /api/v2/instance app/serializers/rest/instance_serializer.rb Last updated November 17, 2026 · Improve this page
@@ -0,0 +1 @@
1
+ d689534a6d237934551c2e46c5947c6ab8704dcabbe51c999b9b5e2c8fb2eda4
@@ -0,0 +1 @@
1
+ What happens to your story when you publish on Medium Updated November 13, 2026 20:15 One of the biggest questions we receive from writers is how distribution works on Medium. Where will my story appear after I hit publish? How do other people find it? We’d like to walk you through the process of what happens when you publish your story and the paths it can take to reach your readers, as well as the broader readership on Medium and beyond. It’s key to understanding how Medium works to keep in mind that there are essentially two paths to distribution on the platform: One system encompasses the open platform (ready to be shared to the world via social or email) and your personal network (your followers, email subscribers, and people who go directly to your personal profile page). The other system is Medium’s distribution and Boost networks (the homepage feed, Digest and other emails, and recommended stories). There is also a path to getting distributed via publications (see Getting started with a Medium publication ), which can include one or both of the above paths. But for now, let’s look at these two main systems. The open platform and distribution to your personal network Open platform Here’s what to expect when you publish on Medium: Once it is published, your story is immediately accessible and available at a URL under your control to share on social media or send to friends via email or messaging services. You also have a personal profile page with a unique URL that contains all your stories. You can share this profile page and encourage those interested in your work to follow you to see more of your stories. Your story may also start getting indexed for search, making it more likely to appear in search engine queries, though we do place some limits on what we allow to appear in search, see About SEO and Medium . Your personal network In addition to all that, your story will go out to your personal network within Medium, made up of people who’ve chosen to follow you or receive email notifications from you. This means your story will appear in the following places: On the "Following" feed : Your story will appear in your followers’ homepages on desktop and mobile apps, where they can see all of the stories from Medium authors and publications they follow listed in reverse chronological order. In Medium Digest emails : Medium users can opt-in to receive a daily or weekly email digest, which contains a mix of recommended stories based on interests, follows, and reading history. Because the Digest is a limited set of stories that are personalized to each reader, your story may appear in your followers' digests because they follow you. Email notifications (optional) : Medium also allows you to send your published stories directly to users who have subscribed to your profile, or any email addresses you have imported to your mailing list, for more direct communication. When you publish a story, you can choose to also send it out to these email subscribers. Learn more in Email notifications . Medium’s distribution and boost networks General distribution In addition to the above, Medium also distributes stories to readers across our website, apps, and emails based on their interests and reading habits. By default, all stories published on Medium are eligible for general distribution via our recommendations algorithm (we do filter for spam, NSFW, etc). So, in addition to being distributed to your audience, your story may also show up in the following places: The "For you" feed of the Medium homepage for all readers on the web and in our mobile apps. In Medium Digest emails: Your story may also appear in the digests of people who don’t follow you, but are interested in the topic you’ve written about. On Medium topic pages . In the Explore section of Medium’s app, as a trending or recommended story. In the “Recommended from Medium” section at the end of other Medium stories. On the version of the Medium homepage for logged-out users. You don’t need to take any action to have your story get this extra distribution — our algorithm does the work of showing relevant stories to interested readers. Network only One of our main goals is to ensure that we are sharing the very best stories for our readers and members. To that end, we will also remove low-quality stories from distribution to Medium’s network, though they will still be distributed to the writer’s personal network. For more on distribution disqualifications, see the Network only section of our quality standards. Boost While much of the distribution in Medium’s network happens automatically through the recommendations algorithm, we also have a team of human curators who look for high-quality stories to share with readers. Those stories that stand out for their insight, thoughtfulness, nuance, and care are selected to get a boost in distribution. To capture stories from all corners of Medium, and recommendations from those with subject matter expertise, we also work with publication editors and those in the Medium community to help us identify and curate the best of the platform. To learn more about how we review stories for a distribution boost, see our quality standards for Boost . Medium publications and distribution Publications on Medium are collections of stories by a single or multiple authors. Readers on Medium follow publications, so adding your story to a publication can increase the reach of your writing. Learn more about Medium publications . When you publish in a publication, in addition to going to your individual network and Medium’s network, your story is distributed to: Publication followers : Medium readers can also follow publications, so when your story is published or included in a publication, it goes out to its followers via Daily or Weekly Digests and the "Following" tab of the publication's followers’ homepages on desktop and mobile apps. Publication newsletters : Medium readers can subscribe to a publication’s newsletter, and editors can send emails to their subscribers as often as they like. Learn more about newsletters . If you are a writer in a Medium publication, you can submit your story to them for distribution to that publication’s followers. Learn more about submitting your story to a Medium publication . How can you determine your potential audience? To help you understand how these systems work together, we have added a new metric to your story stats: Presentations. This metric shows how many times Medium has suggested your stories to readers on the website or app. So you can see how your story is shared across the platform and adjust your publishing strategy accordingly. Learn more about your story stats . What happens to your story when you publish on Medium Medium's Distribution Guidelines: How curators review stories for Boost, General, and Network Distribution Related Still need help? Contact Support
@@ -0,0 +1 @@
1
+ 91161197722a466496532c11ad03e17473df660cc645990c4c86be5da0a22118
@@ -0,0 +1 @@
1
+ API/Importing Updated November 13, 2026 20:19 Inbound Medium will not be issuing any new integration tokens for our API and will not allow any new integrations. All existing tokens will continue to work. You will need to sign in to your Medium account in order to publish. You can also use our mobile apps. Alternately, you can import any existing webpage to your Medium account. Outbound IFTTT Read about how to use IFTTT here . RSS Read about how to use RSS here . Importing a post to Medium API/Importing Related Still need help? Contact Support
@@ -0,0 +1 @@
1
+ afbc52f0d0df043d2096b30732f853e2abcdf519273ab88246be032926fab344
@@ -0,0 +1 @@
1
+ Artificial Intelligence (AI) content policy Updated November 11, 2026 19:32 Medium is for human storytelling, not AI generated writing . We have specific policies around the different uses of AI-generated content and technologies. AI-generated writing: We define AI-generated writing as writing where the majority of the content has been created by an AI-writing program with little or no edits, improvements, fact-checking, or changes. This does not include AI writing tools such as AI outlining, or AI assisted fact, spelling, or grammar checkers. AI-generated writing (disclosed as such or not) is not allowed to be paywalled as part of our Partner Program . Accounts that have fully-generated AI writing behind the paywall may have those stories removed from the paywall, and/or have their Partner Program enrollment revoked. Undisclosed AI-generated writing will be given Network Only distribution. This means it is distributed to the author’s direct network of followers and subscribers only. It is not eligible for wider distribution. AI-assistive technology: We allow the responsible use of AI-assistive technology on Medium. AI assistance empowers an author to level up—to make their ideas clearer, for example, or help them express themselves in a second language. However, in practice, AI-assist is often a way to insert small snippets of AI-generated content that often suffers from the same problems as fully AI- generated stories. We require that any story incorporating AI assistance be clearly labeled as such. AI-assisted text without a disclosure will similarly be restricted to distribution on the author’s personal network. AI-generated or assisted images : AI-generated or assisted images are allowed on Medium with the following provisions: AI-generated images must include captioning identifying them as such. We do not allow AI-generated images that violate our Medium rules , such as rules around harassment, exploitation of minors, disinformation, or privacy violations ( such as AI-generated revenge porn, misinformation, generation of non-consensual or explicit images, etc.) Other uses of AI-generated content or technologies: Violations of these policies may result in consequences such as account restrictions or suspension of your content: We do not allow AI-generated content created solely for the purpose of ranking high in SEO results with the goal of promoting affiliate links ( such as AI-generated book summaries, product reviews, or movie synopsis, or other spammy behaviors) We do not allow content that promotes, links to, or provides instructions for creating new or existing AI technologies for illegal or unethical purposes ( such as illegal hacking, generation of non-consensual or explicit images, exploitation of AI characters, etc) We do not allow the use of AI tools to rephrase, summarize, remix, or otherwise modify existing content in a manner that results in a derivative work which closely resembles the original content in concept, structure, or essential elements. This is a violation of our Plagiarism Guidelines . We do not allow articles that contain easily disprovable AI-hallucinated stories, statistics, events, or otherwise incorrect or nonfactual information. FAQ: Do I need to disclose the use of AI-assistance such as grammar or spell checkers, outline assistance, or fact verification? No, you do not need to disclose this use. You must disclose if you are using text or images generated by AI What should I do if I suspect AI-generated content on the platform? If you see recommended AI-generated content in your feed or Daily Digest from an author or publication you don’t follow, use the “Show less” tool in the 3-dot menu to remove the story and retrain the algorithm. You do not need to report it to us. If you see AI-content behind the paywall, please submit a request with a link to the story using this form . How should I disclose AI-generated content? If you have used AI-generated written content in your story, you can just include a simple sentence within the first two paragraphs. For example, “This story was written with the assistance of an AI writing program.” For AI-generated images, you can note that in the image caption. For example, “ This image was created using an AI image creation program.” How does Medium detect AI content? We use a wide variety of tools and technologies to detect and identify AI-writing and other AI content, combined with human review of any positive results. For more on Medium’s quality and distribution standards, see Medium's Quality Guidelines . To learn how distribution works on Medium, see What happens to your post when you publish on Medium . Read the Medium Rules here. Medium Publications Best Practices and Guidelines Artificial Intelligence (AI) content policy Reasons for Suspensions or Restrictions Medium Rules Username Policy Copyright & DMCA Policy Trademark Policy Medium Logos & Brand Guidelines Guidelines for Law Enforcement Deceased or incapacitated user policy Related Still need help? Contact Support
@@ -0,0 +1 @@
1
+ c81c28ced297db17627436de086eca584ec94cfa8d7ca9ff0d747d7615006153
@@ -0,0 +1 @@
1
+ Buttondown&#x27;s default stance is to support all content so long as it is not harassing, harmful or otherwise damaging. That said, we&#x27;re also aware of the impact that some content can have on communities both on and offline. We&#x27;re lucky that most all of our customers are really thoughtful about what they share! But there are occasions when we have to offboard customers for content issues. We hope that this document helps clarify the types of content that&#x27;s prohibited from being published on Buttondown. Prohibited content Spam email We do not allow spam, or spam by any other name. This includes (but is not limited to) newsletters that are: Cold emails where a subscriber has not explicitly opted in Unsolicited commercial or bulk email To enforce this, we require that all subscribers double opt-in to receiving your newsletter. Phishing or impersonation We do not allow users to impersonate any real person or entity. This is explicitly prohibited in our Terms of Service . This includes (but is not limited to) newsletters that are: Impersonating another person Pretending to be an employee or representative of a company Linking to malicious sites Attempting to gather personal information through deceptive or misleading means SEO backlinking, and link farms We do not allow users to intentionally create content that is designed to manipulate search engine rankings. We do not allow users to generate content for the sole purpose of driving traffic to affiliate links. This includes (but is not limited to) newsletters that are: Selling links Selling leads Selling suspicious, dangerous, or low-quality products (e.g. counterfeit goods, weapons, pharmaceuticals, etc.) Sharing prose and images that are primarily machine generated Promoting get-rich-quick schemes Promoting gambling, or online casinos Harmful content We do not allow content that advocates for the harm of an individual or group of people. This is explicitly prohibited in our Terms of Service . This includes (but is not limited to) newsletters that are: Sharing private or personal information about an individual (e.g. doxxing) Advocating for or promoting violence against an individual or group of people Advocating for or promoting violence against an individual or group of people based on membership in a protected class Using derogatory language or slurs to describe an individual or group of people Sharing content that would constitute a crime (e.g. child pornography, non-consensual porn, etc.)
@@ -0,0 +1 @@
1
+ 7f394cf0363c7e8270d49da14addcd9206f6965f26edc1c3f0a3946090e8f66e
@@ -0,0 +1 @@
1
+ Substack, Inc Creators Publishing a post How can I detect AI on Substack? Updated October 26, 2026 18:11 Scan for AI text estimates whether text was written by a human or AI-assisted. It works on posts and notes published on or after July 21, 2026, and uses Pangram to assign a percentage of how much of the text is human-written or AI-assisted. Note: Neither Substack nor Pangram uses publisher content to train generative AI models. Substack offers a Block AI training toggle in your publication's Settings that signals to external AI crawlers not to use your content for training models. What is Scan for AI text? The Scan for AI text tool can be used in the following surfaces and content: The Substack Reader (Web): Click on a post from your Subscriptions to open the reader. Substack iOS App (Android coming soon): Check for AI on notes and posts on the app. Notes: Scan notes on your feed without leaving Home . Comments & Replies: Scan individual comments and replies on notes. Note: The AI transparency tool is unavailable for video or audio posts, or for posts viewed on standalone Substack sites (such as on.substack.com or custom domains) or emails. How do I scan a post for AI text on the web? Open a post from Subscriptions on the web. This opens the Substack Reader. Click the three dots in the top right corner. Select Scan for AI text . How do I scan a note for AI text? Click the three dots on the note. Select Scan for AI text . Notes with too little text will show a "not enough text" message instead of an analysis. How do I scan for AI on the Substack app? Tap on any note or post and select the three dots in the upper right corner. Tap Scan for AI text . How can I see what's AI-generated in my feed? Label content is an optional setting in your Content preferences that puts a badge on posts and notes by other people when Pangram detects their text as 100% AI-generated. It also adds a badge when the author has turned AI detection off. Select AI Content . Under 100% AI-Generated Content , turn on Label content Learn more about labeling 100% AI-generated content in your feed: How do I control what I see on my feed on Substack? How can creators manage AI detection on their content? Add a transparency note Go to your publication's Settings page and scroll to the Details section. Click “Edit” next to "How I make this." Enter your statement which will appear if readers scan one of your posts, notes, or replies for AI text. Select “Save statement”. Tip: You can always edit your “How I make this” statement by clicking on the three dots on a Pangram analysis of your post or note. Analyze and disable detection on a post On the Publish page of a draft post, click Disable AI detection . When you disable AI detection on a draft post, readers who view the post on the Substack Reader will see an "AI detection unavailable" message when using the Scan for AI text tool. The AI detection tool will need to be disabled manually for each individual post published on or after July 26, 2026. Note: If you’re writing an article on the Substack app, tap “Next” once you’re finished with the draft. On the Publish page, click the three dots and select “Scan for AI text”. On the analysis report, tap the three dots and select "Disable detection. Disable detection on a note 1. Click the three dots in the notes composer. 2. Select Scan for AI text . 3. Once the Pangram analysis appears, click the three dots in the upper right corner. 4. Select Disable detection . Once detection is disabled, readers will no longer see a Pangram analysis on that post or note. Instead, they’ll see an “AI detection unavailable” message. Tip: You can disable detection on the web and on the Substack app by clicking on the three dots on a Pangram analysis. Report a detection error If a post or note was labeled AI and it wasn't, you should report it as a detection error. On the AI detection report, select Report detection error . Enter your feedback which will reviewed to improve detection quality. Articles in this section How do I crop my post thumbnail on Substack? How do I add a collapsible content block to a post on Substack? How do I add a freewall to my Substack post? How do I use metered paywalls on Substack? How can I detect AI on Substack? How do I publish a Substack post in a different language? How do I add audience-specific content to a post on Substack? How do I add a callout block on a Substack post? How do I add alt text to an image on a Substack post? How do I add a drop cap to my Substack post? See more Need more help? Submit a request to Support and we'll be glad to help! Loading…
@@ -0,0 +1 @@
1
+ c7e6eed83fb4765285ebc62cff89cf2f6dc977fa8bf1a47f8b7beff08c8c97cb