You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of Bluesky's hard limit of 300 characters per post, the following idea was suggested:
BridgyFed for the Fediverse should post as threads if the post exceeds 300 characters. Now it just truncates 500 char posts and people have no idea about the rest of it without any link or context. I know it’s early, but this would be great. -- @rolle@mementomori.socialvia fediverse
Yep! I only noticed this earlier today.
I'm also thinking, if it's not possible to thread it, a link back to the original post.
It's a good future feature! ^_^@youronlyone@c.imvia fediverse
Maybe some sort of graceful truncation/linkback or auto-threading not unlike how some of the old Twitter thread posting services or even SMS message handlers do, would be a good feature when posting to Bsky and other platforms with hard character counts. (ActivityPub doesn't have a message transmission limit; these are simply Mastodon constructs in the inputting of messages at some instances, so it's not needed there I believe.)
The text was updated successfully, but these errors were encountered:
would be my preferred thing really. I don't like breaking text into threads much at the best of times even with it's planned and happens at paragraph breaks. This is why I can't follow cory.
Robots/scripts don't break up text into threads well either, they do it badly.
Because of Bluesky's hard limit of 300 characters per post, the following idea was suggested:
Maybe some sort of graceful truncation/linkback or auto-threading not unlike how some of the old Twitter thread posting services or even SMS message handlers do, would be a good feature when posting to Bsky and other platforms with hard character counts. (ActivityPub doesn't have a message transmission limit; these are simply Mastodon constructs in the inputting of messages at some instances, so it's not needed there I believe.)
The text was updated successfully, but these errors were encountered: