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
I hope that I got this right and am not mistaken, but it makes sense though is not clear in the UI. If in the ActivityPub plugin the Author-Profiles are disabled and only the Blog-User is activated then the Plugin still lets me send follow requests to other ActivityPub actors, but they are not received. This leaves the user in a state where one does not know if something went wrong and if yes what might went wrong.
Using the blog-actor also for following others might be useful for quite a lot of people as I found out after talking about WordPress ActivityPub to people who might wanna use it. Any idea on how this could be solved elegantly? I would draft a pull request after having some initial feedback about this.
The text was updated successfully, but these errors were encountered:
Good point, thank you! Together with #285 this conflicts with the notion of one-user-per-blog. But similar as the ActivityPub plugin has found this solution, maybe a change in data structure can allow per-user friends pages and thus you could also get a "blog user" friends page.
With the changes I had to do in #215, this actually became more feasible as soon as we remove the whole "user part."
I hope that I got this right and am not mistaken, but it makes sense though is not clear in the UI. If in the ActivityPub plugin the Author-Profiles are disabled and only the Blog-User is activated then the Plugin still lets me send follow requests to other ActivityPub actors, but they are not received. This leaves the user in a state where one does not know if something went wrong and if yes what might went wrong.
Using the blog-actor also for following others might be useful for quite a lot of people as I found out after talking about WordPress ActivityPub to people who might wanna use it. Any idea on how this could be solved elegantly? I would draft a pull request after having some initial feedback about this.
The text was updated successfully, but these errors were encountered: