mastodon.green is one of the many independent Mastodon servers you can use to participate in the fediverse.
Plant trees while you use Mastodon. A server originally for people in the EU, but now open for anyone in the world

Administered by:

Server stats:

1.2K
active users

#staticwebapp

0 posts0 participants0 posts today

My esteemed followers, you have posted a total of 375,809 statuses to the #fediverse. 22% of you have posted in the last 24h. You are a chatty bunch! ;-)

Check out my new #sideproject: *fedi-followers*. A privacy-friendly fediverse #followers explorer as #localonly #staticwebapp, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

fedi--followers-data0-one.ipns

Screenshot of the app
fedi--followers-data0-one.ipns.dweb.linka privacy-friendly fediverse followers explorer as local-only static web app.

I've built a thing.

Sometimes my follower count seemingly fluctuates at random. To understand why, I dug into the #MastodonAPI and eventually created "fedi-followers":

A privacy-friendly #fediverse #followers explorer as local-only static web app, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

fedi--followers-data0-one.ipns

Screenshot of the app
fedi--followers-data0-one.ipns.dweb.linka privacy-friendly fediverse followers explorer as local-only static web app.

Solved: Excess preview environments under Settings > Environment were preventing additional deployments. Removing stale environments fixed everything.

Okay, #Azure nerds. If I do a `swa deploy ./build` with a deployment token of a React site static build to a Static Web App and repeatedly get back the console messages:

✖ The content server has rejected the request with: InternalServerError
✖ Reason: An unexpected error has occurred. Please try again later.

This has been going on for days so its not a temporary issue.

Is there anywhere else I can look in the portal for a stack trace or addl information about why the deploy failed? Is this particular resource just broken and needs to be destroyed and recreated?