Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible idea: Auto thread or graceful truncation with link backs of posts over 300 characters #1002

Closed
StarrWulfe opened this issue May 5, 2024 · 2 comments

Comments

@StarrWulfe
Copy link

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.social via 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.im via 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.)

@revpriest
Copy link

For me, a link like:

...[Continued: boing.world/@pre/123]

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.

@snarfed
Copy link
Owner

snarfed commented May 5, 2024

Yup! This is #986.

@snarfed snarfed closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants