Use hashtags for greater visibility on Mastodon

[rimu@piefed.social]

I've followed all the frequent posters on piefed.social using my mastodon.social account so we should be seeing a lot more PieFed content showing up there now. But unless you use hashtags, I'll be the only one seeing it!

When making your post, put a few words into the Tags field below the Body field, separated by a comma. No need to include the # character.

[johnnyenzyme@piefed.social]

Oof... I hadn't been thinking of that at all.

Any idea if this works retroactively? For example, if I go back and label posts from the last week or two in the hopes that they might get caught up in Mastodon feeds?

[rimu@piefed.social]

Yes it probably would although anything older than 1 day on Mastodon gets zero views so I wouldn't bother.

[johnnyenzyme@piefed.social]

Oh!
I was able to get today's earlier post to show up there, but it seems totally unable to recognise any of the Lemmy-style image samples, for example ye olde ![label](imageURL) format.

I also added the raw URL's under the images, but it just went ahead and listed them as URL's. (expected, TBF)

[rimu@piefed.social]

Ah. PieFed is just throwing the same html at Mastodon that we use in the PF web app and then Mastodon is stripping out things it can't handle. Perhaps we should do some pre-chewing of the html so that it degrades more gracefully, e.g. convert inline images to links.

[julian@activitypub.space]

In general that's a good idea because you should never trust content coming from somewhere else (even in an S2S context)

For reference, NodeBB literally sanitizes the bejeezus out of what it gets from anywhere. All classes are removed, all attributes are removed. I want it as close to semantic HTML as possible, and classes/attributes mean absolutely nothing because:

1. I don't use the same CSS classes
2. Attributes may not follow my own rules for when and where they are added.

For example, Mastodon messes with any URL it federates out. It chops the anchor text in half, hides the rest behind invisible or something, and adds an ellipsis. invisible does something different in NodeBB, so there is a CSS conflict here. I strip everything and just show the URL as it was intended.