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

Feature/webfinger (1 / X Pull requests for Activitypub support) #1490

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

Sythelux
Copy link

This is the first of probably many pull requests to add activitypub and hopefully activitystream support.

Webfinger will allow another activitypub server like mastodon to see if weasyl can "speak" activitypub it also can be used to lookup users although you will not be able to follow those, yet that will be one of the next pull requests, but all depend on this feature.

!! we might want to add a config setting for people to opt in to federation feature.

Next steps will be:

  • get user profile as json
  • ability to follow a user
  • outbox implementation so that everything posted on weasyl by a user can be synchronized to the fediverse
    • this is the feature that is very close to RSS feed and could be implemented along with it.

at that point weasyl would be ready to send stuff to the fediverse

inbox features would need to be discussed:

  • commenting below a post would be a good post.

I have absolutely no idea how weasyl should render if someone from weasyl wants to follow someone on mastodon, but this isn't possible on wordpress either as far as I'm aware so maybe we don't need it that way.

I leave this as draft until we have discussed the feature here or on gitter.

"""Handle WebFinger requests."""
resource = request.params.get('resource')
if not resource or not resource.startswith('acct:'):
raise WeasylError("Invalid resource parameter")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for taking so long to start to take a look at this. The string parameter that the constructor for WeasylError takes should match one of the keys of weasyl.errorcode.error_messages. The value for that key becomes the error message that is shown to the user when WeasylError is thrown.

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

Successfully merging this pull request may close these issues.

2 participants