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

Support ActivityPub Notes #220

Merged
merged 4 commits into from Mar 5, 2021
Merged

Support ActivityPub Notes #220

merged 4 commits into from Mar 5, 2021

Conversation

@thebaer
Copy link
Member

@thebaer thebaer commented Dec 5, 2019

This is an experimental change to see what Note support in WriteFreely might look like.

This proof-of-concept federates posts that don't include a double-line break as Notes -- otherwise they go out as Articles, as before.

The idea to use this indicator to separate Notes and Articles was inspired by a SocialHub discussion.

Another option for marking a post as a Note might be to use a #note hashtag. Any other ideas?

This proof-of-concept sends out posts that don't include a double-line
break as Notes -- otherwise they go out as Articles, as before.

Inspired by the discussion here:
https://socialhub.activitypub.rocks/t/resolving-the-note-vs-article-distinction/258
@thebaer
Copy link
Member Author

@thebaer thebaer commented Feb 9, 2020

If we're getting wild, I'd love to see this be totally configurable -- maybe as an admin-defined value or small script that determines Note vs. Article.

@upstreamist
Copy link

@upstreamist upstreamist commented Jul 28, 2020

Similar suggestion here: https://discuss.write.as/t/full-text-when-federating-short-posts/1642 — difference being that posts would go out as Note if they (a) have no user-defined title, and (b) contain 280 characters or fewer. Otherwise, they'd publish as Article.

Character limit could be adjustable, given that some Fediverse platforms allow more that 280 characters.

If you want a more user-deliberate way to flag different content types, I'd suggest adapting the @-name format, rather than using a hashtag — i.e. address a new post to @note to send it as a Note. Likewise, @Article could specify Article-type, but should be superfluous in most cases, assuming Article is the default type.

If @-name causes too much confusion, or conflicts with potential Webmention implementation, maybe a less familiar notation, like &note, would work better.

Whatever the final decision, one setting I'd like to see implemented with this is the option to only federate Note-type posts, or federate both Note and Article.

@thebaer thebaer added this to the 0.13 milestone Sep 2, 2020
When setting `notes_only = true` in the `[app]` configuration section, WF will only send out `Note` objects. Otherwise, it will send out both `Note`s and `Article`s.
@thebaer
Copy link
Member Author

@thebaer thebaer commented Sep 2, 2020

Thanks for your input, @upstreamist! We can definitely adjust this in the future, including triggering Notes with character limits or particular tags.

For now, I went ahead with your suggestion to add an option to only send out Notes. This happens with a new configuration value admins can set in the [app] config section for their instance: notes_only = true. By default, WF will federate both Notes and Articles.

Any other feedback is welcome! Otherwise we'll get this merged for our next (v0.13) release.

@thebaer
Copy link
Member Author

@thebaer thebaer commented Mar 5, 2021

Merging now!

@thebaer thebaer merged commit 4f32af2 into develop Mar 5, 2021
@thebaer thebaer deleted the support-notes branch Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants