Features
WebsitesPortfolioMediaConservationClient deliveryCoursesCommerceTeam
FoundationSolutionsPricing
DocumentationDeveloper APISoftwareGuides
About
AboutCommitmentNewsroom
Sign In
ArtInStack

The creative operating system

Product

  • Features overview
  • Websites
  • Portfolio
  • Media
  • Conservation
  • Client delivery
  • Courses
  • Commerce
  • Team
  • Solutions

Resources

  • Guides
  • Software
  • Documentation
  • Developer API
  • Platform foundation
  • Pricing
  • Changelog
  • Roadmap

About

  • About
  • Commitment
  • Newsroom
  • Status
  • Talk to us

Customer login

© 2026 ArtInStack. All rights reserved.

Privacy policyTerms of service
All documentation

Discovery and distribution

  • How visitors discover your work
  • Publish an RSS feed for your blog
  • Preview your links when shared
  • Let visitors share on social networks
  • Reach Mastodon and the open web
  • Turn on Open Web Distribution
  • Choose what to share to the open web
Blog and Content MarketingNext: Email marketing
Documentation/Discovery and distribution

Reach Mastodon and the open web

Learn what Open Web Distribution is—and is not—how the fediverse discovers your selected public work, why the business stays on your site, what public means, updates and removals, UTMs, and a practical strategy without likes, boosts, or a social inbox.

ArtInStack helps your work travel without asking you to move your business onto another social platform.

Open Web Distribution is optional push of selected public posts and photos into the fediverse—independent servers (Mastodon, Pixelfed, and others) that speak ActivityPub. People follow your studio on their home server. Your site remains the home for booking, prints, stories, and brand.

What the fediverse / open web means here

  • Many servers, one shared protocol—not one corporate feed.
  • Your identity is @handle@your-custom-domain on your domain, not @[email protected].
  • Followers use apps they already have; you keep publishing from ArtInStack.

What Open Web Distribution does

  1. You enable it for the workspace (plan + connected custom domain + handle).
  2. You choose individual public posts or photos to share.
  3. Compatible servers receive a public post with text, a web-safe image when relevant, and a link back to your site.
  4. Edits and removals send updates or deletion signals when delivery succeeds.

What happens when you publish a photo or post

StepResult
Item is public and eligibleShare control available
You turn Share onCreate delivered to followers / shared inboxes
Someone views it on Mastodon (etc.)They see caption/description and can open your link
You edit caption/descriptionUpdate delivered when possible
You turn Share offDeletion (tombstone) signaled—caches not guaranteed

Why the content remains on your website

The federated post is a distribution copy with a home link. Commerce, full series, EXIF, booking, and your design system stay on the photographer site. Open-web links include standard UTM tags (utm_source=fediverse, utm_medium=social, campaign for photo vs post) so your analytics can attribute visits when you use a compatible tag manager or reports. ArtInStack does not run a platform-wide fediverse analytics product on top of that.

How remote users discover it

  • Someone follows @handle@your-domain from Mastodon (or compatible apps).
  • Their server receives the activities you share.
  • Boosts or mentions on those networks are their social graph—not an ArtInStack inbox.

What “public” means

Remote servers may fetch, index, cache, and recompress public derivatives and text. Tombstones ask them to drop content; third-party removal cannot be guaranteed. Only share work you accept seeing outside your site. Terms and the in-product enable disclosure state the same risk.

Updates and removals

  • Updates apply when remotes accept them (Mastodon needs a proper update timestamp—handled by the platform).
  • Share off / delete → deletion signal.
  • Share on again after a full tombstone → new public object, not a silent revive of the old identity.

ArtInStack is not a social network

ArtInStack providesArtInStack does not provide
Outbound distribute of your selected public workA social feed of likes, boosts, and replies inside the dashboard
Followable studio identity on your domainRunning Mastodon for you as a hosted community product
Links home with UTM-ready URLsGuaranteed purge of every remote cache
Thin protocol follow/accept as required for deliverySocial Activity inbox, engagement CRM, or “go viral” tooling

Inbound engagement stays on the remote apps on purpose. Your business operating system remains the site and dashboard you already use.

Practical distribution strategy

  1. Enable once; share a few flagship pieces; follow yourself from a personal account to verify.
  2. Prefer series and stories over dumping the library.
  3. Write captions for strangers who have never heard of you.
  4. Measure return visits in your analytics via UTMs—not vanity counts inside ArtInStack.
  5. Stop whenever it stops serving the studio.

Next: Turn on Open Web Distribution, then Choose what to share to the open web.

Related documentation

  • How visitors discover your work
  • Turn on Open Web Distribution
  • Choose what to share to the open web