Then again, the whole effort would probably be halfway futile. I'd barely reach anyone in the Fediverse, even with hundreds of Mastodon contacts. I guess many of them have muted me without unfollowing me because I post stuff they don't want to read, and they don't know how to filter. Some may have blocked me without unfollowing me for the same reason. Others may actually have unfollowed me, but as they keep their followers lists secret, I don't know.
Besides, hardly anyone follows any of the hashtags I'd use on that post, also because only a tiny minority of Mastodon users even know that you can follow hashtags on Mastodon because they couldn't do that on Twitter. And I guess those who do follow one of these hashtags have long since muted or blocked me.
So my reach within the ActivityPub-based Fediverse, especially on Mastodon, is limited to federated timelines. And hardly anyone uses them.
What few are left who might actually see the post I'm planning will most likely ignore it because it will be over 500 characters long. And I can't do that in 500 characters or fewer for obvious reasons: The full image description will have to go somewhere, and that somewhere can only be the post text body itself because it'll be too long and too informative for alt-text.
At least I can't find any traces of entire Mastodon instances having banned me or my home hub. But that could also be that Mastodon doesn't reject posts from banned users or instances and instead receives and deletes them which Hubzilla's delivery reports can't detect.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
Accessibility #
A11y #
Inclusion #
FediverseWorldSightDay #
GlobalAccessibilityAwarenessDay