@nutomic I changed these to their full names, they're urls so no reason to not be explicit, and /c/ could be either a community or a comment.
Not gonna work, you would have to change them in routes/federation.rs as well. Anyway I think we will have to change the URLs so that they are the same for html and activity+json content types, so that you can simply copy the URL into the Masto search and have it fetch the object.
Gonna revert this for now, anyway we are not federating comments yet.
Added some helper DB methods.
Could you explain how you imagine this to work with federation?
Activitypub calls deletes "tombstones" I think, and it'll have to post that to all its recipients.
Ah okay, thats still far away. And the update_ap_id() method is for db migrations or on comment creation then, I see.
Necessary since the post ap_id comes from the row id.
Necessary in what case?
You mean why a post needs an activitypub id? Our instance might have local posts, or federated ones. The local ones can use this helper method, the federated ones that we receive will have their external ones here.
No due date set.
This pull request currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?